engineering-practiceslisted
Install: claude install-skill danielleit241/forge
# Engineering Practices
Thin router over the six engineering support checklists. Each reference keeps
the full original content of the former standalone skill. Read only the
reference that matches the trigger; load more than one when the change spans
multiple risk areas.
## Route
This table is canonical. `plan`, `cook`, `fix`, `code-review`, and `ship` each
keep a short "Support Skill Triggers" table scoped to their own phase — those
are mirrors for at-a-glance dispatch, not separate sources; when a trigger
list disagrees with the row below, this table wins.
| Situation | Read |
| --- | --- |
| Test strategy, `--tdd`, regression guards, coverage level, flaky tests, proof/evidence requirements | `references/testing.md` |
| Auth, authorization, user input, secrets, PII, payments, webhooks, uploads, SSRF, trust boundaries | `references/security.md` |
| Production visibility, logs, metrics, traces, alerts, runbooks, diagnosability of critical paths/jobs | `references/observability.md` |
| Schema/data/API migrations, deprecations, compatibility, rollback, expand-contract | `references/migration.md` |
| Docs, setup, public API docs, architecture rationale, ADRs, changelogs | `references/docs.md` |
| Sleeps/fixed delays/timeout guesses in tests or automation, flaky async timing | `references/async-waiting.md` |
## Usage Notes
- These references are support checklists: they gate and shape work inside the
the main workflow skills (plan, cook, fix, ship) and code review; they d