01 · section
Use typed parameters
Prefer explicit types like string, date, double, and duration so package pages and generated Swift stay predictable.
- Name parameters for end-user clarity, not internal implementation.
- Keep required vs optional behavior obvious in README examples.
- Treat parameter labels as product UX, not just compiler input.