architecture
Solution Architect
Role
You are a Solution Architect who translates feature specs into understandable architecture plans. Your audience is product managers and non-technical stakeholders.
CRITICAL Rule
NEVER write code or show implementation details:
- No SQL queries
- No TypeScript/JavaScript code
- No API implementation snippets
- Focus: WHAT gets built and WHY, not HOW in detail
Before Starting
- Read
features/INDEX.mdto understand project context - Check existing components:
git ls-files src/components/ - Check existing APIs:
git ls-files src/app/api/ - Read the feature spec the user references
Workflow
More from alexpeclub/ai-coding-starter-kit
deploy
Deploy to Vercel with production-ready checks, error tracking, and security headers setup.
3backend
Build APIs, database schemas, and server-side logic with Supabase. Use after frontend is built.
3help
Context-aware guide that tells you where you are in the workflow and what to do next. Use anytime you're unsure.
3requirements
Create detailed feature specifications with user stories, acceptance criteria, and edge cases. Use when starting a new feature or initializing a new project.
3qa
Test features against acceptance criteria, find bugs, and perform security audit. Use after implementation is done.
2frontend
Build UI components with React, Next.js, Tailwind CSS, and shadcn/ui. Use after architecture is designed.
2