English

What is The Architect?

Imagine you want to build a house. Before anyone picks up a hammer, you need a blueprint — a detailed plan that shows every room, every wall, every pipe, and every wire. Without it, the builders wouldn't know what to do.

The Architect does this for software.

You open this project in Claude Code, tell it what you want to build (a website, an app, a SaaS, an API — anything), and The Architect:

1. Asks you smart questions about your idea
2. Designs the entire system — database, API, frontend, auth, payments, everything
3. Generates a blueprint file (.md) so detailed that another Claude Code instance can build the whole thing — step by step, without asking you anything

Think of it like this:

You: "I want to build a project management app like Trello"
         ↓
The Architect: asks questions, designs everything
         ↓
Blueprint.md: complete plan with tech stack, database schema,
              API routes, component hierarchy, build order...
         ↓
Claude Code: reads the blueprint → builds the entire app

You describe the idea. The Architect creates the plan. Claude Code builds it.

How It Works

The Architect follows a 4-phase workflow:

Phase 1: Discovery

"What are you building? Who is it for? How big should it be?"

The Architect asks 2-3 questions to understand your idea. Based on your answers, it classifies your project into one of 6 archetypes (project types).

Phase 2: Deep Dive

"Do you need user accounts? Payments? Real-time features?"

Now it asks questions specific to YOUR type of project. It also researches best practices using skills like /deep-research.

Phase 3: Architecture

"Here's what I'd build: Next.js + Supabase + Clerk + Stripe on Vercel..."

The Architect presents the complete tech stack and architecture with reasons for every decision. You confirm or adjust. For frontend projects, it designs a full visual system (colors, fonts, spacing) using /ui-ux-pro-max.

Phase 4: Generate

The Architect produces the final blueprint — a single .md file with 16 sections covering everything Claude Code needs to build your project from zero to deployed.

The Blueprint: 16 Sections

Every blueprint The Architect generates includes:

Section 9 (Build Order) is the most important. It tells Claude Code exactly what to build and in what order — so it can work autonomously without asking you questions.

Supported Project Types

The Architect knows how to design 6 types of projects, each with its own default stack, directory structure, and build order:

Don't see your project type? The Architect adapts — these are starting points, not limits.

Quick Start

Prerequisites

• Claude Code installed
• A Claude API subscription

Installation

# Clone this repo
git clone https://github.com/Hainrixz/the-architect.git

# Open the project in Claude Code
cd the-architect
claude

That's it. Claude Code reads the CLAUDE.md file and becomes The Architect.

Usage

Step 1: Tell The Architect what you want to build:

You: I want to build a SaaS for managing restaurant reservations
     with team accounts, Stripe payments, and a customer-facing booking page.

Step 2: Answer the questions (2-3 at a time, conversational).

Step 3: Review the proposed architecture. Confirm or adjust.

Step 4: The Architect generates your blueprint at output/<project-name>-blueprint.md.

Step 5: Use the blueprint to build your project:

# Create your new project
mkdir ~/my-restaurant-saas
cp output/restaurant-saas-blueprint.md ~/my-restaurant-saas/CLAUDE.md

# Open it in Claude Code — it builds everything from the blueprint
cd ~/my-restaurant-saas
claude

Fast-Track Mode

Don't want to answer many questions? Say:

You: Build me a SaaS for restaurant reservations. Just build it.

The Architect asks only 3 essential questions and uses smart defaults for everything else.

Project Structure

the-architect/
├── CLAUDE.md                          # The brain — makes Claude become The Architect
├── knowledge/
│   ├── archetypes/                    # 6 project type templates
│   │   ├── saas-webapp.md             #   SaaS apps
│   │   ├── marketing-site.md          #   Landing pages
│   │   ├── mobile-app.md              #   Mobile apps
│   │   ├── api-backend.md             #   APIs & backends
│   │   ├── internal-tool.md           #   Admin panels
│   │   └── content-platform.md        #   Blogs & CMS
│   ├── building-blocks/               # 8 cross-cutting decision guides
│   │   ├── auth-patterns.md           #   Authentication options
│   │   ├── database-patterns.md       #   Database & ORM choices
│   │   ├── deployment-patterns.md     #   Hosting & CI/CD
│   │   ├── api-design-patterns.md     #   REST vs tRPC vs GraphQL
│   │   ├── frontend-stacks.md         #   Framework comparisons
│   │   ├── testing-patterns.md        #   Testing strategies
│   │   ├── styling-systems.md         #   CSS & design tokens
│   │   └── state-management.md        #   State & real-time patterns
│   ├── skills-registry.md             # Maps Claude Code skills to blueprint sections
│   └── stack-compatibility.md         # What works together (and what doesn't)
├── templates/
│   ├── blueprint-template.md          # The 16-section output skeleton
│   └── claude-md-template.md          # Template for the target project's CLAUDE.md
├── questions/
│   ├── phase-1-discovery.md           # Universal discovery questions
│   ├── phase-2-branches.md            # Archetype-specific deep dives
│   └── phase-3-confirmation.md        # Architecture confirmation
└── output/                            # Generated blueprints go here

Skills Integration

The Architect leverages Claude Code skills during the design process:

And recommends skills for the build phase in the blueprint:

Contributing

Contributions are welcome! You can help by:

• Adding new archetypes — new project types in knowledge/archetypes/
• Improving building blocks — better decision matrices, newer tech options
• Enhancing the blueprint template — more sections, better structure
• Translating — help make The Architect accessible in more languages

License

MIT License. See LICENSE for details.

Built by tododeia.com

Español

Que es The Architect?

Imagina que quieres construir una casa. Antes de que alguien agarre un martillo, necesitas un plano — un plan detallado que muestre cada cuarto, cada pared, cada tuberia y cada cable. Sin el, los constructores no sabrian que hacer.