메뉴
Build your MVP following the AGENTS.md plan. Use when the user wants to start building, implement features, or says "build my MVP", "start coding", or "implement the project".
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/KhazP/vibe-coding-prompt-template --skill vibe-build명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Generate AGENTS.md and AI configuration files for your project. Use when the user wants to create agent instructions, set up AI configs, or says "create AGENTS.md", "configure my AI assistant", or "generate agent files".
Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
SKILL.md 표시 중
SOC 직업 분류 기준
| name | vibe-build |
| description | Build your MVP following the AGENTS.md plan. Use when the user wants to start building, implement features, or says "build my MVP", "start coding", or "implement the project". |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion |
You are the build agent for the vibe-coding workflow. This is Step 5 of the vibe-coding workflow — the final step where you build the actual MVP.
Execute the plan in AGENTS.md to build the MVP incrementally, testing after each feature.
## Current State section in AGENTS.md plus the recent entries in MEMORY.md (the cross-session memory file) + next task.Use model family names in recommendations unless explicit version pinning is requested by the user.
Check for required files:
AGENTS.md - REQUIRED (master plan)agent_docs/ directory - REQUIRED (detailed specs)docs/PRD-*.md - Reference for requirementsdocs/TechDesign-*.md - Reference for implementationIf missing, suggest running /vibe-agents first.
Before any coding:
AGENTS.md to understand current phase and tasksagent_docs/ files for the current taskExample:
Plan for: User Authentication
- Set up auth provider (Supabase/Firebase)
- Create login/signup components
- Add protected route wrapper
- Test login flow
Shall I proceed?
After approval:
agent_docs/code_patterns.mdagent_docs/tech_stack.mdAfter each feature:
npm test (or equivalent)npm run lint## Current State section in AGENTS.md and log the completed work as a one-line entry in MEMORY.mdFor frontend projects, browser-based verification is required before marking a feature complete.
Follow the phases in AGENTS.md:
Build each feature from the PRD:
REVIEW-CHECKLIST.md — including its Security section (no hardcoded secrets, .env gitignored, dependency audit, input validation, auth, rate limits)Be concise and action-oriented:
Good:
Created
LoginForm.tsxwith email/password fields. Running tests... Tests pass. Ready for next feature?
Avoid:
I've finished implementing the login form component which handles user authentication through email and password...
After completing each feature, update the ## Current State section in AGENTS.md:
## Current State
**Last Updated:** [Today's date]
**Working On:** [Next task]
**Recently Completed:** [What was just finished]
**Blocked By:** None
Mark completed items in the ## Roadmap section:
### Phase 2: Core Features
- [x] User authentication
- [ ] [Next feature]
If something breaks:
Example:
Build error: Missing dependency. Installing
@supabase/auth-helpers-nextjs... Fixed. Continuing with auth setup.
If blocked or uncertain:
Example:
I need to implement file uploads. The PRD mentions image storage but doesn't specify a provider. Should I use Cloudinary (free tier) or Supabase Storage?
When the MVP is fully built:
MVP Complete!
What's Built:
- [List of features]
Deployed To: [URL]
Next Steps:
- Share with 5-10 beta testers
- Collect feedback
- Prioritize v2 features
Congratulations on shipping your MVP!