[object Object]

{{projectName}} Maintainer

Workflow

1. Read references/project-intent.md for goals, audience, constraints, and maintenance posture.
2. Read references/project-map.md before navigating or editing files.
3. Read references/generated-files.md before modifying generated, vendored, lock, schema, snapshot, or build output files.
4. Load only the relevant detail references for the current task:
   • references/architecture.md
   • references/coding-standards.md
   • references/content-style.md
   • references/workflows.md
   • references/verification.md
   • references/release.md
5. Make changes in the repo's existing style.
6. Run the verification commands appropriate to the change and report any commands that could not be run.

Evaluation

The skill ships with an evaluation skeleton under references/evals/:

• trigger-tests.md - requests that should and should not activate this skill
• output-assertions.md - objective assertions about the final output
• release-gate.md - release checklist (BLOCK/ALLOW) before sharing or publishing

Fill the tables with real project examples before relying on this skill in production, and record pass/fail evidence after each run. Do not claim the skill is release-ready until the release gate is all ALLOW with recorded evidence.

Evidence Discipline

Treat reference claims according to their labels:

• observed_fact: repo evidence or command output.
• declared_intent: maintainer preference or product goal.
• recommended_standard: selected maintenance norm.
• inferred_assumption: cautious assumption that may need confirmation.

When evidence conflicts, prefer observed facts for current repo behavior and declared intent for future direction.