Claude-skill-registry architecting
Architects new features through the full lifecycle. Use when designing, planning, implementing, or extending features. Triggers on 'new feature', 'design', 'plan', 'implement', 'architect', 'prd', 'spec'.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/architecting" ~/.claude/skills/majiayu000-claude-skill-registry-architecting && rm -rf "$T"
manifest:
skills/data/architecting/SKILL.mdsource content
Architect Feature
Role: Oversee the entire lifecycle of a Feature—from 0 to 1 to N—ensuring architectural consistency and UX integrity.
When to use this skill
- Creating a new feature from scratch
- Extending an existing feature with new capabilities
- Implementing code based on a finalized design spec
How to use it
Choose a mode based on your intent:
| Mode | Trigger keywords | Scenario |
|---|---|---|
| DESIGN | new feature, 设计 | Create a brand-new feature directory from scratch |
| EXTEND | 扩展, add capability | Add sub-capabilities to an existing feature |
| BUILD | implement, 实现 | Code an already-designed spec |
DESIGN Mode (从 0 到 1)
- Context Check: Read
to avoid reinventing the wheel.src/features/ - KISS Check: Really need a new directory? If < 3 files, consider
.shared - Generate Spec: Use
.resources/spec-template.md - Tech Decisions: Define dependencies and Schema.
Output:
src/features/{name}/docs/spec.md
EXTEND Mode (从 1 到 N)
- Locate Host: Identify the target Feature.
- Architecture Conformance: Read the host's
, follow its design philosophy.spec.md - Incremental Design: Append an "Extension Section" instead of creating new docs.
Output: Updated
src/features/{name}/docs/spec.md or core code.
BUILD Mode (编码实现)
- Read Contract: Always read
first for scope.spec.md - Quality Gate: Establish "Type-First" (Zod Schema -> TypeScript Type).
- Layered Implementation:
- L1 Core: Schema & Service (no UI, pure logic)
- L2 UI: Components (no business logic)
- L3 Integration: Pages & Routing
- Self-Verify:
andnpm run type-check
must pass.npm run lint
Resources
| Resource | Purpose |
|---|---|
| spec-template.md | Standardized design doc template |
| kiss-checklist.md | Anti-over-engineering checklist |
| anti-patterns.md | Architecture anti-pattern warnings |
Quality Baseline
As an architect, you MUST reject:
- ❌ Circular Dependencies: Features importing each other.
- ❌ Global State Abuse: Local state pushed to global store.
- ❌ Any Type: Even one
is a disgrace.any - ❌ Implicit Logic: Critical logic without comments or docs.