Answer a design system usage question by searching documentation, Decision Memory, and pattern library. Every answer strengthens the knowledge base.
Read context/ds-context-guide.md for environment detection and configuration. Read context/governance-philosophy.md for the guide-not-police tone.
Answer a DS usage question ("Which component for a data table with inline editing?", "How do I theme the Button for our sub-brand?", "Why can't I override the modal backdrop?"). Searches documentation, Decision Memory, and the pattern library. Every answer strengthens institutional knowledge — unanswered or novel questions are flagged as documentation gaps.
$ARGUMENTS = the question.
If empty, ask: "What's your design system question?"
Search for the answer across available sources:
/ds-decision-query logic)Construct the answer:
Assess confidence:
Flag knowledge gaps:
/ds-decision-recordOffer to record. If this answer resolves a question that should be part of the system's institutional memory, suggest capturing it via /ds-decision-record.
## Answer
{Direct answer to the question}
**Why**: {Rationale from Decision Memory or documentation}
{Code or design example if relevant}
**Confidence**: {High/Medium/Low}
### Documentation Gap
{If this isn't documented: "This question isn't covered in current documentation. Consider adding guidance for [topic] to [component/section]."}
### Recurring Question
{If asked before: "This has come up [N times / recently in #channel]. Consider dedicated documentation."}
- Limit to top 5 issues by severity
- Each issue: finding + suggestion in 2-3 sentences
- Overall assessment: 1-2 sentences