architect

Designs software architecture sketches with types, signatures, and module boundaries before implementation.

4|1|Updated Dec 16, 2023
One-click install
npx skills add https://github.com/Shtian/AuthentiClash --skill architect-shtian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/Shtian/AuthentiClash/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/Shtian/AuthentiClash --skill architect-shtian

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 structure, forcing painful rewrites later. This Skill enforces a design-first workflow that sketches types, function signatures, and module boundaries before any implementation begins. ## Core Features & Use Cases - Grounded Design Process: Traces the existing system first, then produces at least two structurally distinct design candidates from different models before synthesizing one. - Design Quality Screening: Filters candidates against documented red flags like shallow modules, information leakage, temporal decomposition, and pass-through methods. - Scrap-and-Redesign Loop: Detects patterns of implementation friction that signal a wrong architecture and triggers a first-principles redesign instead of bolted-on fixes. - Use Case: When asked to add a significant feature to an existing codebase, invoke this Skill to produce a type sketch, module map, and written rationale before writing any real code. ## Quick Start Ask the AI to architect this feature before implementing it, describing the problem and the systems it touches.

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 derive the design from the caller's usage. This Skill runs a five-phase workflow: ground the problem, sketch candidates, optionally agree with a human, implement against the sketch, and scrap if the design proves wrong.

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

Generate at least two structurally distinct design candidates from different models, then compare them on interface depth. Prefer the design that hides more complexity behind a smaller public surface, and screen each candidate for red flags like information leakage and pass-through methods.

When should I scrap an architecture and redesign it?▼

Scrap when friction forms a pattern: repeated workarounds, types needing escape hatches like casts or any, or callers forced to know internal rules. Single edge cases do not condemn a design, but two or more independent deviations of the same shape signal a wrong architecture.

Does this design workflow require human approval before implementation?▼

No, human checkpoints are opt-in only. By default the workflow proceeds directly from the synthesized design to implementation, but you can request a checkpoint with phrases like 'stop and show me before implementing' 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 an interface that does not save callers from learning the implementation.