rapid-builder
Skill0 starsChanged 3 months agoMITView on GitHub
Quickly prototype and build functional applications across web and mobile platforms. Focuses on speed-to-working-code, MVP development, and cross-platform solutions. Use when building prototypes, MVPs, proof-of-concepts, or rapid iterations.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- ai-engineerSkill
- api-clientSkill
- changelog-enforcerSkill
- code-cleanup-guardianSkill
- code-reviewerSkill
- contract-testSkill
- db-migrateSkill
- dep-auditSkill
- devops-automatorSkill
- env-configSkill
- error-observabilitySkill
- frontend-designSkill
- git-commit-helperSkill
- github-issues-managerSkill
- git-issue-syncSkill
- git-protocolSkill
- handoffSkill
- incident-responseSkill
- init-projectSkill
- karpathy-guidelinesSkill
- market-researcherSkill
- parallel-agent-git-isolationSkill
- product-strategistSkill
- pr-workflowSkill
- release-managerSkill
- resumeSkill
- scrutinizeSkill
- shadcn-uiSkill
- skill-builderSkill
- sprint-plannerSkill
- state-machine-diagramsSkill
- state-managementSkill
- surveySkill
- system-architectSkill
- tech-docsSkill
- unstuckSkill
- ux-design-systemSkill
- ux-researchSkill
- webapp-testingSkill
- web-dev-fundamentalsSkill
- workflow-optimizerSkill
The file
Files
Rapid Builder
Build functional prototypes and MVPs at maximum velocity without sacrificing quality foundations.
Philosophy
- Working > Perfect
- Functional > Feature-complete
- Validated > Assumed
Tech Stack Selection
Use the project's defined stack when it has one. For a greenfield prototype with no stack set, default to Next.js on Vercel with Supabase for auth, database, and API, and say why if the prototype calls for something else (a content-only site, self-hosting, real-time sync).
MVP Feature Checklist
Core (Day 1)
- User authentication (OAuth preferred)
- Core value proposition feature
- Basic data persistence
- Responsive layout
Polish (Day 2)
- Error handling with user feedback
- Loading states
- Basic analytics
- Mobile-friendly navigation
Launch (Day 3)
- Email notifications (if needed)
- Basic admin view
- Terms/Privacy pages
- Feedback collection
Anti-Patterns
AVOID: Custom auth systems, complex state management early, premature optimization, over-engineering database schema
EMBRACE: Third-party services, simple state (useState, Zustand), ship and iterate, minimal viable schema, user feedback driven development
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
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.