project-architect — Claude Code subagent
project-architect analyzes project requirements, recommends a tech stack, and scaffolds folder structure for new projects or architecture refactoring. Handles web apps, microservices, monorepos, and backend services.
no license ★ 1,357 updated 2026-03-01
.claude/agents/project-architect.mdWhat project-architect does
project-architect guides you through requirements analysis and recommends an appropriate technology stack—from frontend choices like React or Vue to backends in Node.js, Go, or Python. It covers common architectures: monolithic web apps, microservices, monorepos, and CLI tools.
Includes pre-built project templates, TypeScript and ESLint configurations, and sample docker-compose setups for local development. The subagent operates with Read, Write, Edit, Bash, and Glob tools, creating files, running setup scripts, and automating initialization.
Use it when starting a new project, adding a substantial feature that changes architecture, or restructuring existing code. Ensures consistent standards across your team: naming conventions, code organization, environment management.
What it helps with
- select technology stack based on project requirements
- create correct folder structure and configuration files
- set up linters, formatters, and pre-commit hooks
- prepare docker-compose for local development environment
- automate project initialization with setup scripts
Example prompts for the agent
- Create a new React app structure with TypeScript and Vite for a startup MVP
- Help me restructure the backend—what should change for a microservices architecture?
- Set up ESLint, Prettier, and pre-commit hooks for a team of five developers
How to install project-architect
Manually: put the files in place
.claude/agents/project-architect.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/project-architect.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/project-architect.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about project-architect
How do I install project-architect in Claude Code?
Copy the content from .claude/agents/project-architect.md into that folder in your project. Create the folder if it doesn't exist. Reload Claude Code, and the subagent will appear in your available agents list.
What does project-architect do?
It analyzes your project requirements, recommends a suitable tech stack (frontend, backend, database, tooling), creates a folder structure following best practices, generates TypeScript and ESLint configs, and automates the initial project setup.
When should I use this subagent?
When starting a new project from scratch, adding a major feature that requires architectural changes, or refactoring an existing codebase. The subagent proactively suggests using itself to maintain consistent standards across these scenarios.