Practices
Practices are reusable approaches for recurring work. The public version focuses on what each area helps produce and why it matters.
A good practice is not a giant manual. It is a repeatable way to avoid the same mistake twice: what to read first, what to check, what to avoid, and how to finish cleanly.
| Practice area | Used for |
|---|---|
| Site operations | Review, page checks, and publishing decisions. |
| Project tracking | Work records, decisions, review, and follow-up. |
| Service changes | Safer handling of services, site configuration, schedules, storage, and persistent data. |
| Site health checks | Status checks, alerts, and bounded operations summaries. |
| Task tracking | Capturing follow-ups that should not be lost. |
| Design/system planning | Turning broad ideas into implementable specs. |
| Review and verification | Finding risks, checking outcomes, and validating rendered behavior. |
Practice Pattern
Most reusable practices follow the same shape:
- identify when the practice applies
- load the right context
- choose the smallest useful action
- check with a rendered page, screenshot, command, or review note
- update the process when the work reveals a better path
