AgentSkillsCN

app-builder

应用构建者的专家工具集

SKILL.md
--- frontmatter
name: app-builder
description: Expert toolkit for app-builder

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.

FileDescriptionWhen to Read
project-detection.mdKeyword matrix, project type detectionStarting new project
tech-stack.md2026 default stack, alternativesChoosing technologies
agent-coordination.mdAgent pipeline, execution orderCoordinating multi-agent work
scaffolding.mdDirectory structure, core filesCreating project structure
feature-building.mdFeature analysis, error handlingAdding features to existing project
templates/SKILL.mdProject templatesScaffolding new project

📦 Templates (13)

Quick-start scaffolding for new projects. Read the matching template only!

TemplateTech StackWhen to Use
nextjs-fullstackNext.js + PrismaFull-stack web app
nextjs-saasNext.js + StripeSaaS product
nextjs-staticNext.js + FramerLanding page
nuxt-appNuxt 3 + PiniaVue full-stack app
express-apiExpress + JWTREST API
python-fastapiFastAPIPython API
react-native-appExpo + ZustandMobile app
flutter-appFlutter + RiverpodCross-platform mobile
electron-desktopElectron + ReactDesktop app
chrome-extensionChrome MV3Browser extension
cli-toolNode.js + CommanderCLI app
monorepo-turborepoTurborepo + pnpmMonorepo

🔗 Related Agents

AgentRole
project-plannerTask breakdown, dependency graph
frontend-specialistUI components, pages
backend-specialistAPI, business logic
database-architectSchema, migrations
devops-engineerDeployment, preview

Usage Example

code
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

Agent Coordination

How App Builder orchestrates specialist agents.

Agent Pipeline

code
┌─────────────────────────────────────────────────────────────┐
│                   APP BUILDER (Orchestrator)                 │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│                     PROJECT PLANNER                          │
│  • Task breakdown                                            │
│  • Dependency graph                                          │
│  • File structure planning                                   │
│  • Create {task-slug}.md in project root (MANDATORY)             │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│              CHECKPOINT: PLAN VERIFICATION                   │
│  🔴 VERIFY: Does {task-slug}.md exist in project root?       │
│  🔴 If NO → STOP → Create plan file first                    │
│  🔴 If YES → Proceed to specialist agents                    │
└─────────────────────────────────────────────────────────────┘
                              │
          ┌───────────────────┼───────────────────┐
          ▼                   ▼                   ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ DATABASE        │ │ BACKEND         │ │ FRONTEND        │
│ ARCHITECT       │ │ SPECIALIST      │ │ SPECIALIST      │
│                 │ │                 │ │                 │
│ • Schema design │ │ • API routes    │ │ • Components    │
│ • Migrations    │ │ • Controllers   │ │ • Pages         │
│ • Seed data     │ │ • Middleware    │ │ • Styling       │
└─────────────────┘ └─────────────────┘ └─────────────────┘
          │                   │                   │
          └───────────────────┼───────────────────┘
                              ▼
┌─────────────────────────────────────────────────────────────┐
│                 PARALLEL PHASE (Optional)                    │
│  • Security Auditor → Vulnerability check                   │
│  • Test Engineer → Unit tests                               │
│  • Performance Optimizer → Bundle analysis                  │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│                     DEVOPS ENGINEER                          │
│  • Environment setup                                         │
│  • Preview deployment                                        │
│  • Health check                                              │
└─────────────────────────────────────────────────────────────┘

Execution Order

PhaseAgent(s)Parallel?PrerequisiteCHECKPOINT
0Socratic Gate-✅ Ask 3 questions
1Project PlannerQuestions answeredPLAN.md created
1.5PLAN VERIFICATIONPLAN.md existsFile exists in root
2Database ArchitectPlan readySchema defined
3Backend SpecialistSchema readyAPI routes created
4Frontend SpecialistAPI ready (partial)UI components ready
5Security Auditor, Test EngineerCode readyTests & audit pass
6DevOps EngineerAll code readyDeployment ready

🔴 CRITICAL: Phase 1.5 is MANDATORY. No specialist agents proceed without PLAN.md verification.


Feature Building

How to analyze and implement new features.

Feature Analysis

code
Request: "add payment system"

Analysis:
├── Required Changes:
│   ├── Database: orders, payments tables
│   ├── Backend: /api/checkout, /api/webhooks/stripe
│   ├── Frontend: CheckoutForm, PaymentSuccess
│   └── Config: Stripe API keys
│
├── Dependencies:
│   ├── stripe package
│   └── Existing user authentication
│
└── Estimated Time: 15-20 minutes

Iterative Enhancement Process

code
1. Analyze existing project
2. Create change plan
3. Present plan to user
4. Get approval
5. Apply changes
6. Test
7. Show preview

Error Handling

Error TypeSolution Strategy
TypeScript ErrorFix type, add missing import
Missing DependencyRun npm install
Port ConflictSuggest alternative port
Database ErrorCheck migration, validate connection

Recovery Strategy

code
1. Detect error
2. Try automatic fix
3. If failed, report to user
4. Suggest alternative
5. Rollback if necessary

Project Type Detection

Analyze user requests to determine project type and template.

Keyword Matrix

KeywordsProject TypeTemplate
blog, post, articleBlogastro-static
e-commerce, product, cart, paymentE-commercenextjs-saas
dashboard, panel, managementAdmin Dashboardnextjs-fullstack
api, backend, service, restAPI Serviceexpress-api
python, fastapi, djangoPython APIpython-fastapi
mobile, android, ios, react nativeMobile App (RN)react-native-app
flutter, dartMobile App (Flutter)flutter-app
portfolio, personal, cvPortfolionextjs-static
crm, customer, salesCRMnextjs-fullstack
saas, subscription, stripeSaaSnextjs-saas
landing, promotional, marketingLanding Pagenextjs-static
docs, documentationDocumentationastro-static
extension, plugin, chromeBrowser Extensionchrome-extension
desktop, electronDesktop Appelectron-desktop
cli, command line, terminalCLI Toolcli-tool
monorepo, workspaceMonorepomonorepo-turborepo

Detection Process

code
1. Tokenize user request
2. Extract keywords
3. Determine project type
4. Detect missing information → forward to conversation-manager
5. Suggest tech stack

Project Scaffolding

Directory structure and core files for new projects.


Next.js Full-Stack Structure (2025 Optimized)

code
project-name/
├── src/
│   ├── app/                        # Routes only (thin layer)
│   │   ├── layout.tsx
│   │   ├── page.tsx
│   │   ├── globals.css
│   │   ├── (auth)/                 # Route group - auth pages
│   │   │   ├── login/page.tsx
│   │   │   └── register/page.tsx
│   │   ├── (dashboard)/            # Route group - dashboard layout
│   │   │   ├── layout.tsx
│   │   │   └── page.tsx
│   │   └── api/
│   │       └── [resource]/route.ts
│   │
│   ├── features/                   # Feature-based modules
│   │   ├── auth/
│   │   │   ├── components/
│   │   │   ├── hooks/
│   │   │   ├── actions.ts          # Server Actions
│   │   │   ├── queries.ts          # Data fetching
│   │   │   └── types.ts
│   │   ├── products/
│   │   │   ├── components/
│   │   │   ├── actions.ts
│   │   │   └── queries.ts
│   │   └── cart/
│   │       └── ...
│   │
│   ├── shared/                     # Shared utilities
│   │   ├── components/ui/          # Reusable UI components
│   │   ├── lib/                    # Utils, helpers
│   │   └── hooks/                  # Global hooks
│   │
│   └── server/                     # Server-only code
│       ├── db/                     # Database client (Prisma)
│       ├── auth/                   # Auth config
│       └── services/               # External API integrations
│
├── prisma/
│   ├── schema.prisma
│   ├── migrations/
│   └── seed.ts
│
├── public/
├── .env.example
├── .env.local
├── package.json
├── tailwind.config.ts
├── tsconfig.json
└── README.md

Structure Principles

PrincipleImplementation
Feature isolationEach feature in features/ with its own components, hooks, actions
Server/Client separationServer-only code in server/, prevents accidental client imports
Thin routesapp/ only for routing, logic lives in features/
Route groups(groupName)/ for layout sharing without URL impact
Shared codeshared/ for truly reusable UI and utilities

Core Files

FilePurpose
package.jsonDependencies
tsconfig.jsonTypeScript + path aliases (@/features/*)
tailwind.config.tsTailwind config
.env.exampleEnvironment template
README.mdProject documentation
.gitignoreGit ignore rules
prisma/schema.prismaDatabase schema

Path Aliases (tsconfig.json)

json
{
  "compilerOptions": {
    "paths": {
      "@/*": ["./src/*"],
      "@/features/*": ["./src/features/*"],
      "@/shared/*": ["./src/shared/*"],
      "@/server/*": ["./src/server/*"]
    }
  }
}

When to Use What

NeedLocation
New page/routeapp/(group)/page.tsx
Feature componentfeatures/[name]/components/
Server actionfeatures/[name]/actions.ts
Data fetchingfeatures/[name]/queries.ts
Reusable button/inputshared/components/ui/
Database queryserver/db/
External API callserver/services/

Tech Stack Selection (2026)

Default and alternative technology choices for web applications.

Default Stack (Web App - 2026)

yaml
Frontend:
  framework: Next.js 16 (Stable)
  language: TypeScript 5.7+
  styling: Tailwind CSS v4
  state: React 19 Actions / Server Components
  bundler: Turbopack (Stable for Dev)

Backend:
  runtime: Node.js 23
  framework: Next.js API Routes / Hono (for Edge)
  validation: Zod / TypeBox

Database:
  primary: PostgreSQL
  orm: Prisma / Drizzle
  hosting: Supabase / Neon

Auth:
  provider: Auth.js (v5) / Clerk

Monorepo:
  tool: Turborepo 2.0

Alternative Options

NeedDefaultAlternative
Real-time-Supabase Realtime, Socket.io
File storage-Cloudinary, S3
PaymentStripeLemonSqueezy, Paddle
Email-Resend, SendGrid
Search-Algolia, Typesense

Built with ❤️ from Antigravity Kit & UXUI ProMax MIT © Vudovn