Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From class-architect
Module boundary design guide — opaque pointers, compilation firewalls, ABI stability
How this skill is triggered — by the user, by Claude, or both
Slash command
/class-architect:boundary-guideWhen to use
Used when an agent handles class design at library/module boundaries. Referenced by the architect agent during system boundary design.
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Covers physical coupling control concepts at module boundaries, the role and strategic placement of Pimpl/opaque pointer patterns as compilation firewalls, ABI-breaking vs. non-breaking change classification, the principle of minimal exposure, and the design differences between boundary surfaces and performance-critical paths.
Covers physical coupling control concepts at module boundaries, the role and strategic placement of Pimpl/opaque pointer patterns as compilation firewalls, ABI-breaking vs. non-breaking change classification, the principle of minimal exposure, and the design differences between boundary surfaces and performance-critical paths.
!cat "${CLAUDE_SKILL_DIR}/reference.md"
npx claudepluginhub juyeongyi/jylee_claude_marketplace --plugin class-architectGuides 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.