product-builder
Skill7 starsChanged 5 months agoMITView on GitHub
Provides end-to-end product development support from idea conception to code implementation. Guides solo entrepreneurs through every stage of building software products including validation, specification, frontend/backend development, testing, deployment, and documentation. Use this skill when users want to build a digital product from scratch.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- jaskirat1616/grok-skillstheir own version, first seen Nov 1, 2026
- learner0408/Skillstheir own version, first seen Aug 20, 2026
- srednoff888-art/srednoff-os-for-claudetheir own version, first seen Jul 1, 2026
- kleberbernardo/claude-code-skillstheir own version, first seen Jun 14, 2026
- oleg-koval/product-buildertheir own version, first seen Mar 26, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- jaskirat1616/grok-skills★ 22same name
- kleberbernardo/claude-code-skills★ 2same name
- oleg-koval/product-builder★ 1same name
- srednoff888-art/srednoff-os-for-claude★ 1same name
- learner0408/Skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- assumption-archaeologistSkill
- collectorSkill
- connectorSkill
- inversion-engineSkill
- landingSkill
- marketing-growthSkill
- Mental Models LibrarySkill
- paradox-navigatorSkill
- PrincipleSkill
- solo-corn-research-integrationSkill
- strategic-decisionSkill
- systems-orchestratorSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
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
- Distinctive: line 125
Follow the full development lifecycle from idea to deployment.
- Distinctive: line 135
Start with validation: Always validate your idea before coding
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
Product Builder Skill
A comprehensive AI skill that transforms ideas into deployable products efficiently.
Core Capabilities
- Idea Validation: Market analysis, competitor landscape, feasibility assessment
- Specification Generation: PRD creation, user stories, acceptance criteria
- Wireframe & UI Design: Component design and layout guidance
- Frontend Development: React, Vue, Next.js component generation
- Backend Development: REST/GraphQL API generation
- Database Design: Schema design and migration scripts
- Test Generation: Unit, integration, and E2E tests
- Deployment: CI/CD configuration and deployment guides
- Documentation: API docs, README, and user guides
Development Phases
The product building workflow follows these phases:
Phase 1: Idea Validation
↓
Phase 2: Product Specification
↓
Phase 3: UI/UX Design
↓
Phase 4: Frontend Development
↓
Phase 5: Backend Development
↓
Phase 6: Database Implementation
↓
Phase 7: Testing
↓
Phase 8: Deployment
↓
Phase 9: DocumentationQuick Start
1. Validate Your Idea
User: "I want to build a task management app for remote teams"
→ Market analysis: Size, trends, growth potential
→ Competitor analysis: Who else is doing this?
→ Feasibility assessment: Technical and business viability
→ Idea scoring: Overall recommendation2. Generate Specification
User: "Help me create a spec for my task app"
→ PRD document with goals and requirements
→ User stories for each feature
→ Acceptance criteria
→ Wireframe descriptions3. Generate Code
User: "Generate React components for my task app"
→ Component structure and props
→ Production-ready code
→ Tailwind CSS styling
→ Unit testsDirectory Structure
product-builder/
├── SKILL.md (this file)
└── references/
├── idea-validation/ # Phase 1 resources
├── specification/ # Phase 2 resources
├── ui-design/ # Phase 3 resources
├── frontend/ # Phase 4 resources
├── backend/ # Phase 5 resources
├── database/ # Phase 6 resources
├── testing/ # Phase 7 resources
├── deployment/ # Phase 8 resources
└── documentation/ # Phase 9 resourcesSupported Technologies
Frontend
- React 18+
- Vue 3+
- Next.js 13+
- Tailwind CSS 3+
- TypeScript
Backend
- Node.js / Express
- Python / FastAPI
- GraphQL (Apollo Server)
- Authentication (JWT, OAuth)
Database
- PostgreSQL
- MongoDB
- SQLite
- Prisma ORM
Deployment
- Vercel
- Netlify
- AWS (ECS, Lambda)
- Docker
Usage Patterns
Pattern 1: Complete Workflow
Follow the full development lifecycle from idea to deployment.
Pattern 2: Specific Phase
Jump directly to any phase if you already have completed previous work.
Pattern 3: Code Generation Only
Generate specific components or APIs on-demand.
Best Practices
- Start with validation: Always validate your idea before coding
- Iterate incrementally: Build incrementally and test frequently
- Follow standards: Generated code follows industry best practices
- Review and adapt: Review generated code and adapt to your needs
- Document as you go: Maintain documentation throughout development
Trigger Keywords
This skill activates when users mention:
- "build a product"
- "create an app"
- "develop software"
- "generate code"
- "validate my idea"
- "create PRD"
- "deploy my project"
- "write tests"
Related Skills
- Research Integration: Validate ideas using research-backed frameworks
- Marketing Growth: Plan go-to-market strategy
- Customer Success: Design user support workflows
Interface Definition
Metadata
{
"name": "product-builder",
"version": "2.0.0",
"description": "Provides end-to-end product development support from idea to code implementation",
"author": "SOLO CORN SKILLS",
"category": ["product", "development"],
"tags": ["product", "development", "prd", "code-generation"]
}Input Schema
{
"inputs": [
{
"name": "problem",
"type": "string",
"required": true,
"description": "The problem to solve or product idea"
},
{
"name": "constraints",
"type": "string",
"required": false,
"description": "Constraints (tech stack, time, resources, etc.)"
},
{
"name": "targetUsers",
"type": "string",
"required": false,
"description": "Target user description"
}
]
}Output Schema
{
"outputs": [
{
"name": "prdDocument",
"type": "string",
"description": "Complete product requirements document"
},
{
"name": "userStories",
"type": "array",
"description": "List of user stories"
},
{
"name": "acceptanceCriteria",
"type": "array",
"description": "Acceptance criteria"
}
]
}Invoke Method
async invoke(params: InvocationParams): Promise<SkillResult> {
// Execute product development process
// 1. Validate idea
// 2. Generate specifications
// 3. Design UI
// 4. Develop code
// 5. Return results
}Usage via CLI
# Basic invocation
scs invoke product-builder --input '{"problem":"I want to build a task management app"}'
# Interactive invocation
scs invoke product-builder --interactive
# Chain invocation
scs invoke landing --then product-builderDoes 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.

