architect

Designs software architecture through parallel multi-model sketching before implementation begins.

2|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/imjasonh/playground --skill architect-imjasonh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/imjasonh/playground/tree/main/.cursor/skills/architect
Command: npx skills add https://github.com/imjasonh/playground --skill architect-imjasonh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Jumping straight into code on non-trivial work often locks in the wrong architecture, forcing painful rewrites later. This Skill enforces a design-first workflow that sketches types, signatures, and module boundaries before any implementation, so structural mistakes are caught while they are still cheap to fix. ## Core Features & Use Cases - Grounded design exploration: Traces the existing system first, then runs multiple parallel model runners to produce structurally distinct candidate designs. - Red-flag screening and synthesis: Screens candidates against shallow modules, information leakage, temporal decomposition, and pass-through methods, then synthesizes one design package with a written rationale. - Scrap-and-redesign loop: Detects recurring implementation friction patterns and triggers a full redesign from first principles instead of bolting fixes onto a wrong shape. - Use Case: Before building a new caching layer across three services, run the architect workflow to compare two or more candidate module structures, pick the one with the deepest interface, and implement against the agreed type sketch. ## Quick Start Ask the AI to architect the new feature before writing any code, describing the problem and the systems it must integrate with.

Frequently Asked Questions about architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design software architecture before writing code?▼

Sketch types, function signatures, and module boundaries with placeholder bodies first, then implement against that sketch. This Skill formalizes the process with grounding, parallel candidate sketches, synthesis, and an implementation phase that treats deviations as design signals.

What is the best way to compare multiple design candidates?▼

Generate at least two structurally distinct candidates, screen each against design red flags like shallow modules and information leakage, then compare on interface depth. Prefer the design hiding the most complexity behind the smallest public surface.

When should I scrap an architecture and redesign from scratch?▼

Redesign when friction forms a pattern: repeated workarounds, unrelated edge cases needing special branches, types needing escape hatches, or callers knowing internal rules. Single edge cases do not condemn a design; recurring shapes of friction do.

Does this design workflow require human approval before implementation?▼

No, the default flow proceeds directly from synthesis to implementation without a checkpoint. A human sign-off checkpoint is opt-in, triggered only when the invoker explicitly asks to review the design first.

What are signs of a shallow module in software design?▼

A shallow module exposes a large interface while hiding little complexity. Signs include callers coordinating several methods for one operation, public options exposing internal stages, and learning the interface not saving callers from learning the implementation.