Pattern snapshot
A code-extracted representation of recurring patterns in a codebase — naming conventions, folder structure, modifier usage — that subagents read before generating new code so the output matches what a human reviewer expects.
A pattern snapshot is the convention-extraction step that runs before code generation. It catalogues the conventions actually present in your repository — public modifier discipline, async naming, folder layout, DTO suffix usage — so the implementing subagent generates code that reads as if a human on the team wrote it.
Placeholder body. Replace with the full glossary entry per playbook §9. Cite codewithmukesh’s
convention-learnerskill as a public reference implementation.
When to use
- Before any greenfield feature inside an existing codebase.
- When a new subagent is added to the team and needs to learn local conventions in one pass.
- After a large refactor that consolidates conventions, to refresh the snapshot.
Compare with
A coding standards document is human-readable; a pattern snapshot is agent-readable and derived from the actual code, so it stays current without a doc-maintenance ritual.