eraser-diagrams
Generates architecture diagrams from code, infrastructure, or descriptions. Use when user asks to visualize, diagram, or document system architecture.
moai-domain-backend
>
dev-design
REQUIRED Phase 4 of /dev workflow. Proposes architecture approaches with trade-offs and gets user approval.
openspec-proposal-creation
Creates structured change proposals with specification deltas for new features, breaking changes, or architecture updates. Use when planning features, creating proposals, speccing changes, introducing new capabilities, or starting development workflows. Triggers include "openspec proposal", "create proposal", "plan change", "spec feature", "new capability", "add feature planning", "design spec".
fullstack-basics
Full-stack development fundamentals - architecture, patterns, integration
ios-fundamentals
Master iOS development foundations - Architecture, lifecycle, memory, concurrency
technical-discussion
Document technical discussions as expert architect and meeting assistant. Capture context, decisions, edge cases, debates, and rationale without jumping to specification or implementation. Second phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) Users discuss/explore/debate architecture or design, (2) Working through edge cases before specification, (3) Need to document technical decisions and their rationale, (4) Capturing competing solutions and why choices were made. Creates documentation in docs/workflow/discussion/{topic}.md that technical-specification uses to build validated specifications.
