schema: spec-driven

# Project context - injected into every planning request
# context: |

# Per-artifact rules
rules:
  proposal:
    - Follow openspec/PROPOSAL_DESIGN_GUIDELINES.md for all visualizations
    - UI changes: Include ASCII mockup + Mermaid sequence diagram for interaction flow
    - Code changes: Include Mermaid flowchart + change table
    - Error handling: Document error flows and UX considerations
    - Mermaid syntax: Use double quotes for nodes with special chars (parens, brackets, dots, slashes, spaces)
    - Use checklist in openspec/PROPOSAL_DESIGN_GUIDELINES.md before submission

  design:
    - Follow openspec/PROPOSAL_DESIGN_GUIDELINES.md for all visualizations
    - UI section: Detailed ASCII mockups + interaction sequence diagrams
    - Technical design: Architecture diagrams (Mermaid graph), data flow (flowchart), API calls (sequence)
    - Code changes: Structured tables for backend/frontend/database changes
    - Include error handling flows
    - Mermaid syntax: Use double quotes for nodes with special chars
