Contributions should improve the reusable starter, the review workflows, the rubrics, or the evidence behind a worked example.
Use starter/field-guide/ENTRY.md and
starter/workflows/distill-reviewed-session.md.
Every proposed entry needs:
- an inspectable source;
- an observed project-specific surprise or correction;
- guidance with honest scope;
- good and bad examples that differ in behavior;
- a verification method and exceptions;
- a human verifier before the entry becomes active.
Do not publish private conversations, proprietary prompts, credentials, customer information, or inaccessible repository evidence.
Explain the developer job the change improves. Include a small exercised case when changing a rubric, workflow, or template. Keep the core tool-neutral.
This repository does not accept:
- generated entry collections;
- generic best-practice lists without a project case;
- prompt libraries or thin vendor variants;
- unverifiable personal claims;
- copied articles or threads;
- a new rubric without good and bad fixtures.
Run starter/workflows/audit-field-guide.md quarterly for any field guide you
adopt. Move enforceable lessons into tests, lint rules, types, CI checks,
Skills, runbooks, contracts, or decisions instead of keeping every lesson in
Markdown.