From class-architect
System-level class structure design workflow — 7 steps from requirements to architecture
How this skill is triggered — by the user, by Claude, or both
Slash command
/class-architect:architecture-workflowWhen to use
The architect agent follows this procedure when designing multi-class systems.
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Defines a 7-step procedure for designing systems composed of multiple classes. Proceeds in order: requirements elicitation → responsibility allocation → relationship mapping → data flow verification → architecture pattern decision → SOLID validation → concurrency review. When issues are found in later steps, return to the originating step and revise.
Defines a 7-step procedure for designing systems composed of multiple classes. Proceeds in order: requirements elicitation → responsibility allocation → relationship mapping → data flow verification → architecture pattern decision → SOLID validation → concurrency review. When issues are found in later steps, return to the originating step and revise.
!cat "${CLAUDE_SKILL_DIR}/reference.md"
!cat "${CLAUDE_PLUGIN_ROOT}/rules/oop-design-rules.md" 2>/dev/null || echo "No rules"
!cat "${CLAUDE_PLUGIN_ROOT}/rules/architectural-rules.md" 2>/dev/null || echo "No rules"
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
npx claudepluginhub juyeongyi/jylee_claude_marketplace --plugin class-architect