vibe-agents
01KhazP/vibe-coding-prompt-template
Command
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
KhazP/vibe-coding-prompt-template
Command
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
KhazP/vibe-coding-prompt-template
Command
Step 5 of the vibe-coding workflow: build the MVP one verified feature at a time.
KhazP/vibe-coding-prompt-template
Command
Step 2 of the vibe-coding workflow: define WHAT to build, WHO it's for, and WHY it matters.
KhazP/vibe-coding-prompt-template
Command
Step 1 of the vibe-coding workflow: validate the app idea with deep research before anything gets built.
KhazP/vibe-coding-prompt-template
Command
Step 3 of the vibe-coding workflow: plan HOW to build it — stack, architecture, costs, deployment.
KhazP/vibe-coding-prompt-template
Command
The vibe-coding workflow turns an app idea into a working MVP in 5 stages. Your job: figure out where the user is and route them to the right stage.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: