How do I install the Architecting skill?

Run npx skillmds@latest add diegosouzapw/architecting in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Architecting safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Architecting?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Architecting free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Architecting?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Architecting by diegosouzapw — Agent Skill

Name: Architecting
Rating: 4.2 (5 reviews)
Author: diegosouzapw

File contents

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.md first 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-check and npm run lint must 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 any is a disgrace.
❌ Implicit Logic: Critical logic without comments or docs.

---name: architectingdescription: 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'.---# 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 itChoose 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)1. **Context Check**: Read `src/features/` to avoid reinventing the wheel.2. **KISS Check**: Really need a new directory? If < 3 files, consider `shared`.3. **Generate Spec**: Use `resources/spec-template.md`.4. **Tech Decisions**: Define dependencies and Schema.**Output**: `src/features/{name}/docs/spec.md`---### EXTEND Mode (从 1 到 N)1. **Locate Host**: Identify the target Feature.2. **Architecture Conformance**: Read the host's `spec.md`, follow its design philosophy.3. **Incremental Design**: Append an "Extension Section" instead of creating new docs.**Output**: Updated `src/features/{name}/docs/spec.md` or core code.---### BUILD Mode (编码实现)1. **Read Contract**: Always read `spec.md` first for scope.2. **Quality Gate**: Establish "Type-First" (Zod Schema -> TypeScript Type).3. **Layered Implementation**: * **L1 Core**: Schema & Service (no UI, pure logic) * **L2 UI**: Components (no business logic) * **L3 Integration**: Pages & Routing4. **Self-Verify**: `npm run type-check` and `npm run lint` must pass.---## Resources| Resource | Purpose ||----------|---------|| [spec-template.md](resources/spec-template.md) | Standardized design doc template || [kiss-checklist.md](resources/kiss-checklist.md) | Anti-over-engineering checklist || [anti-patterns.md](resources/anti-patterns.md) | Architecture anti-pattern warnings |---## Quality BaselineAs an architect, you MUST reject:- ❌ **Circular Dependencies**: Features importing each other.- ❌ **Global State Abuse**: Local state pushed to global store.- ❌ **Any Type**: Even one `any` is a disgrace.- ❌ **Implicit Logic**: Critical logic without comments or docs.

Frequently asked questions

Architecting