| name | patterns |
| description | Browse and load this project's reusable engineering/design patterns from _dream_context/knowledge/patterns/ — "/patterns" lists them, "/patterns <slug or keywords>" loads the matching one. Use when the user asks "which patterns do we have", "load the X pattern", "bir pattern var mıydı", or before building something a documented pattern already covers. |
Project Patterns (live from the brain)
The source of truth is _dream_context/knowledge/patterns/*.md — this skill carries NO
pattern content of its own; always read the live files.
- No argument → list: run
ls _dream_context/knowledge/patterns/ and show each
file's name + first sentence of description from its frontmatter (Read the files,
headers only). If the folder is missing or empty, say the project has no documented
patterns yet and stop — do not create the folder. Ask which to load if the user's
intent is unclear.
- With argument → resolve
<slug or keywords> against the filenames/descriptions
(recall fallback: dreamcontext memory recall "<keywords>" --types knowledge), then
Read the matched pattern IN FULL and apply/summarize it per the user's ask.
- When the current work is a NEW FEATURE, always surface
feature-integration-pattern.md — applying it before finishing is mandatory
(see the dreamcontext skill's Entity Router).
Do not copy pattern text into this file; do not edit patterns from here without
offer-and-confirm. Per-pattern "/" entries (generated shims) arrive with the
knowledge-workflows shim mechanism when that feature is built — this skill is the
interim, drift-free bridge.
