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 keisei
Validates architectural decisions against pattern rules, duplication limits, and stack compatibility. Loaded by other skills during code review and architecture planning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/keisei:architecture-rulesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Validating an architectural decision against Constructor Pattern rules, duplication limits, or stack compatibility.
architecture, debug-deep, and code-review skills — not normally invoked directly.This skill provides the rules database for architectural validation. It is loaded by other skills (architecture, debug-deep, code-review) when they need to validate decisions.
When analyzing code or planning architecture, load and apply rules from:
~/.claude/skills/architecture-rules/references/patterns.md — design patterns catalog~/.claude/skills/architecture-rules/references/antipatterns.md — what to avoid~/.claude/skills/architecture-rules/references/stack-compat.md — technology compatibility matrix~/.claude/skills/architecture-rules/references/duplication.md — duplication detection rules~/.claude/skills/architecture-rules/references/checklist.md — pre-implementation checklistFor each architectural decision, validate against these references and report violations.
npx claudepluginhub keiseilab/keiseikit --plugin keiseiGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.