| name | senior-practices |
| description | Version-pinned coding and framework best practices from official docs and corroborated senior/maintainer guidance — use for unfamiliar stacks, upgrades, migrations, architecture reviews, "best practice" questions, or before introducing a new pattern when style governance says improve might be warranted. |
Senior practices skill
Companion to .cursor/rules/composer-senior-practices.mdc. Load when external, current guidance is needed — not when matching an obvious local pattern suffices.
For multi-vendor audits or contradictory literature, pair with deep-research. For applying findings without scope creep, follow composer-coding-excellence § Style governance.
See reference.md for compact repeatable checklists.
Operating stance
Training data is a hypothesis until anchored to this repo's versions and T1 sources. Prefer falsification: check deprecations, breaking changes, and "do not use" guidance before recommending a pattern.
Do not imitate private chain-of-thought. Make the work inspectable: version inventory, source list, reconciled recommendations, and apply-now vs follow-up split.
Phase A — Inventory (this repo)
- Read manifests:
package.json, go.mod, Cargo.toml, pyproject.toml, Gemfile, etc.
- Record exact versions of the framework, runtime, and relevant libraries.
- Note existing project standards: eslint/prettier, ADRs, README, CI config.
- Scan how similar problems are already solved (2–3 examples).
