Delegate independent tasks to specialized agents working concurrently with isolated context.
Architect Feature
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'.
SKILL.md
Full skill instructions
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
src/features/to avoid reinventing the wheel. - 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
spec.md, follow its design philosophy. - 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
spec.mdfirst for scope. - 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:
npm run type-checkandnpm run lintmust pass.
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
anyis a disgrace. - ❌ Implicit Logic: Critical logic without comments or docs.
More Other skills
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
