Summary
Your conventions, available to the model before it writes.
Instead of restating house style in every prompt, the style lives in a file the assistant can search - so new code and refactors come back matching patterns you already approved rather than the model's defaults.
What it is
A store of your own coding patterns held as newline-delimited JSON. Each pattern carries a name, a category, a description, the situations it suits, the technologies it applies to and code examples keyed by language - and the assistant reads them before it writes.
What you get
- Patterns created in bulk against a fixed schema: category, description, when to use it, technologies, and examples
- The whole pattern set read back, or a single pattern opened by name
- Search across the set by technology, use case or style, so the right pattern is found rather than recalled
- Further code examples added to a pattern that already exists, so one pattern can carry several languages
- Patterns and individual examples deleted when they stop reflecting how you write
Requirements
An MCP client, and somewhere to keep the store: patterns are written as newline-delimited JSON, one object per line, so the file can be read, diffed and committed alongside the code it describes. No account and no key.