MustafaKucukcoskun/Refine-agent-kit / .agents/skills/app-builder
app-builder
VerifiedMain application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
App Builder - Application Building Orchestrator
Analyzes user's requests, determines tech stack, plans structure, and coordinates agents.
π― Selective Reading Rule
Read ONLY files relevant to the request! Check the content map, find what you need.
| File | Description | When to Read |
|---|---|---|
project-detection.md | Keyword matrix, project type detection | Starting new project |
tech-stack.md | 2026 default stack, alternatives | Choosing technologies |
agent-coordination.md | Agent pipeline, execution order | Coordinating multi-agent work |
scaffolding.md | Directory structure, core files | Creating project structure |
feature-building.md | Feature analysis, error handling | Adding features to existing project |
blueprints/SKILL.md | Project blueprints | Scaffolding new project |
π¦ Blueprints (13)
These files are prompt-time reference blueprints, not executable starter repos. Read only the matching blueprint, then scaffold the project from that guidance.
| Blueprint | Tech Stack | When to Use |
|---|---|---|
| nextjs-fullstack | Next.js + Prisma | Full-stack web app |
| nextjs-saas | Next.js + Stripe | SaaS product |
| nextjs-static | Next.js + Framer | Landing page |
| nuxt-app | Nuxt 4 + Pinia | Vue full-stack app |
| express-api | Express + JWT | REST API |
| python-fastapi | FastAPI | Python API |
| react-native-app | Expo + Zustand | Mobile app |
| flutter-app | Flutter + Riverpod | Cross-platform mobile |
| electron-desktop | Electron + React | Desktop app |
| chrome-extension | Chrome MV3 | Browser extension |
| cli-tool | Node.js + Commander | CLI app |
| monorepo-turborepo | Turborepo + pnpm | Monorepo |
| astro-static | Astro + MDX | Blog / Docs |
π Related Agents
| Agent | Role |
|---|---|
project-planner | Task breakdown, dependency graph |
frontend-specialist | UI components, pages |
backend-specialist | API, business logic |
database-architect | Schema, migrations |
devops-engineer | Deployment, preview |
Usage Example
User: "Make an Instagram clone with photo sharing and likes"
App Builder Process:
1. Project type: Social Media App
2. Tech stack: Next.js + Prisma + Cloudinary + Clerk
3. Create plan:
ββ Database schema (users, posts, likes, follows)
ββ API routes (12 endpoints)
ββ Pages (feed, profile, upload)
ββ Components (PostCard, Feed, LikeButton)
4. Coordinate agents
5. Report progress
6. Start preview
Quality Upgrade Protocol (v1)
Use this protocol for every non-trivial build request.
1. Outcome-First Framing
Define success as product outcomes, not only code completion.
| Question | Why It Matters |
|---|---|
| What business/user outcome must improve? | Prevents feature-for-feature's-sake building |
| What does failure look like? | Creates guardrails for trade-offs |
| What is the quality bar for v1? | Aligns scope and ambition |
2. Dynamic Constraint Envelope
Classify constraints before stack selection:
| Level | Examples | Handling |
|---|---|---|
| Hard | Compliance, security baseline, SLA, accessibility | Must satisfy |
| Soft | Style preferences, team familiarity, optional libraries | Can be traded with rationale |
| Open | Areas where innovation is encouraged | Explore alternatives |
This prevents over-restrictive prompts like fixed color/component diktats while preserving quality.
3. Option Space Before Commitment
Generate at least 3 implementation candidates before locking architecture.
| Option | Shape | Strength | Risk |
|---|---|---|---|
| Conservative | Proven stack, low novelty | Predictable delivery | Lower differentiation |
| Balanced | Modern defaults + selective innovation | Strong quality/speed trade-off | Moderate complexity |
| Frontier | High-leverage novel approach | Differentiation and long-term upside | Higher execution risk |
4. ADR-Lite Decision Record (Mandatory)
For each major decision, record:
- Context and constraints.
- Options considered.
- Chosen option + why.
- Risks and rollback path.
- Trigger conditions for revisiting the decision.
5. Domain-Fit Innovation Pass
For product-facing work (landing pages, SaaS UX, onboarding, dashboards), propose 3 domain-compatible ideas users may not ask for directly.
Example framing:
- "If we add this concept, what user/job does it unlock?"
- "How does this reduce cognitive load or decision friction?"
- "Can this be implemented incrementally without architecture debt?"
6. Quality Gates (Before Final Output)
Do not finalize until these are explicit:
- Functional correctness and edge cases
- Security and data-safety checks
- Performance budget assumptions
- Maintainability and ownership clarity
- Test strategy (unit/integration/e2e scope)
Behavioral Rule: Avoid Rigid Design Dictation
Do not force arbitrary style constraints like fixed colors/components unless user or brand context explicitly requires them.
Preferred approach:
- Offer 2-3 justified directions.
- Explain trade-offs clearly.
- Let constraints adapt to goals, audience, and product stage.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 468k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why β repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" β or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself β your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |