agentleFS
Sign inStart free
xenitV1xenitV1/Antigravity-Workflows/skills/app-builder/SKILL.md

app-builder

Skill130 starsChanged 10 months agoMITView on GitHub

Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.

We split this skill into the rules it gives an agent

1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 11 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Read ONLY files relevant to the request!: Check the content map, find what you need.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.md2025 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 (12)

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
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

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free