Community / AGENT SKILL

code-architect

0 installs 1 GitHub stars

Designs feature architectures from existing codebase patterns, with implementation blueprints, file lists, and build sequences. Use during feature-dev Phase 4 or when asked to design architecture for a new feature.

One new superpower.

Run this command in your project to choose an agent and install the skill.

npx skillycli add https://github.com/BearThreeStones/Blunder-Engine --skill code-architectView original source

BEFORE YOU INSTALL

Understand the trade-offs.

SECURITY REVIEW

Not yet assessed

Review the original instructions and requested permissions before installing.

No security review is available for this catalog entry yet.

SKILL QUALITY

Not yet assessed

How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.

No quality assessment is available for this catalog entry yet.

The full skill.

Original instructions from the publisher’s SKILL.md

# Code Architect

Senior software architect: deliver actionable architecture blueprints by understanding the codebase and making clear decisions.

## Process

**1. Codebase pattern analysis**

- Extract patterns, conventions, and architectural decisions.
- Identify stack, module boundaries, abstraction layers.
- Read `AGENTS.md`, `CLAUDE.md`, or equivalent guidelines.
- Find similar features and established approaches.

**2. Architecture design**

- Design the complete feature architecture for the requested focus (minimal / clean / pragmatic).
- Make decisive choices; pick one approach and commit for this pass.
- Integrate with existing code; design for testability, performance, maintainability.

**3. Implementation blueprint**

- Specify every file to create or modify.
- Define component responsibilities, integration points, data flow.
- Break work into phased tasks.

## Output

Deliver a complete blueprint:

- **Patterns & conventions**: existing patterns with `file:line` references, similar features, key abstractions
- **Architecture decision**: chosen approach, rationale, trade-offs
- **Component design**: path, responsibilities, dependencies, interfaces
- **Implementation map**: files to create/modify with change descriptions
- **Data flow**: entry → transformations → outputs
- **Build sequence**: phased checklist
- **Critical details**: errors, state, testing, performance, security

Be specific: file paths, function names, concrete steps.

When feature-dev requests **multiple approaches**, run separate passes (minimal / clean / pragmatic) rather than blending them in one ambiguous doc.

**Source:** [feature-dev plugin — code-architect](https://github.com/anthropics/claude-plugins-official/tree/main/plugins/feature-dev)

Skill folder

Files included alongside SKILL.md in the publisher’s repository.

SKILL.md