System architect
Skill batterfried-philosophy172/Agent-Startup-Skills/skills/system-architect
Build SaaS products using an 8-phase AI agent pipeline with mandatory approval gates for Antigravity, Claude Code, and Codex.
npx -y skills add batterfried-philosophy172/Agent-Startup-Skills --skill system-architectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
System architecture agent that designs tech stack, folder structure, API contracts, and external service integrations. Triggers on: system design, tech stack, architecture, API design, folder structure, choose framework.
SKILL.md
2.7 KB, as published. Nobody here has run it
System Architect — Design Agent
Purpose
Design a complete, justified system architecture before any code is written. Prevent "spaghetti architecture" by making deliberate, documented choices.
When to Use
- After MVP scope is approved
- When choosing a tech stack for a new project
- When designing API contracts or system structure
Process
Step 1: Tech Stack Selection
For each layer, recommend a technology with a one-line justification:
| Layer | Choice | Why |
|---|---|---|
| Frontend | e.g., Next.js | SSR for SEO, React ecosystem |
| Backend | e.g., Next.js API Routes | Unified codebase, serverless-ready |
| Database | e.g., PostgreSQL | Relational data, free tier on Supabase |
| Auth | e.g., NextAuth.js | Free, supports OAuth providers |
| Hosting | e.g., Vercel | Free tier, zero-config deploys |
Constraint: Prefer free-tier-friendly technologies unless the user specifies a budget.
Step 2: System Architecture
Describe the architecture in plain text or a mermaid diagram:
- How do the frontend, backend, and database connect?
- What is the request flow for the core user action?
- Where does authentication happen?
Step 3: Project File Structure
Present the complete folder/file tree:
project-root/
├── src/
│ ├── app/ # Pages and routes
│ ├── components/ # Reusable UI components
│ ├── lib/ # Business logic and utilities
│ ├── api/ # API route handlers
│ └── db/ # Database schema and migrations
├── tests/ # Test files
├── public/ # Static assets
├── .env.example # Environment variable template
├── package.json
└── README.md
Step 4: API Endpoint Inventory
List every API endpoint the MVP needs:
| Method | Endpoint | Description | Auth Required |
|---|---|---|---|
| POST | /api/auth/register | Create new user | No |
| POST | /api/auth/login | Authenticate user | No |
| GET | /api/[resource] | List resources | Yes |
Step 5: External Services
List any third-party services required:
- What it does, why it's needed, what it costs, and the free tier limits
Output
Produce an architecture.md file with all sections above.
Exit Criteria
- Every tech choice has a documented justification
- File structure is complete (no "etc." or "...")
- All API endpoints are listed with methods and auth requirements
- External service costs are identified