Agent Context
Run this skill before a user-facing implementation or review when the applicable knowledge is not already explicit.
Workflow
-
In a product repository with the npm package installed, verify
npx --no-install ai-design-context context --help. In the knowledge-source checkout, usenpm run context -- --help. -
Resolve the task, review target, or stable object:
bashnpm run context -- --task quick-capture --platform mobile --intent implement --format json npm run context -- --review examples/todo-reference --intent qa npm run context -- --object PAT-00002 --format jsonFor the installed npm package, replace
npm run context --withnpx --no-install ai-design-context contextin these examples. Markdown provides absolute reading paths; JSON addsabsolutePathwhile retaining relative graphpath. -
Read the selected files before proposing product guidance or code.
-
Apply only the returned rules and patterns that fit the task.
-
Preserve every returned evidence boundary;
draftandseeddo not justify broad product claims. -
If the resolver returns no match, create an observation or research need rather than inventing a rule.
-
Inspect each object's selection reason. Required dependencies are complete, while optional links in broad review gates must be followed explicitly when the review needs them.
Boundaries
- The CLI is read-only and does not replace
npm run check. --platformadds relevant context; it does not prove that a pattern applies.- Use
--format jsonfor another agent or script; errors are machine-readable on stderr. - Task matching is lexical. Simple English task wrappers are supported; arbitrary paraphrases and translation are not. Prefer an exact known slug or ID when available.


