Remote script. The agent fetches the prompt from a remote URL and follows its instructions, so review the fetched file before letting it run commands.
Who it is forA founder or developer with a new product idea who wants a coherent starting point before writing features.
The problemStarting a new app means making many setup choices (framework, tests, linting, docs, agent instructions) before any product work happens.
The outcomeA Next.js project with PRODUCT.md, the official foundation, documentation, agent instructions, and validation, with the next MVP task identified.
What you need first
- An AI agent with terminal access, such as Claude Code or Codex
- A project directory, or an existing application root to configure
- Network access to raw.githubusercontent.com to fetch the prompt files
Steps
- Create or open an empty directory for the project and start Claude Code or Codex there.
- Paste the two-line prompt from the README that points to docs/prompts/11-next-project-bootstrap.md.
- Replace the second line with your project name, problem, audience, main flows, and constraints.
- Let the agent run the setup and review the generated PRODUCT.md and docs before continuing.
- Confirm the agent reports the checks it ran and the next MVP task.
Prompt for your agent
Read the repo soumatheusgomes/vibe-coding-toolkit at docs/prompts/11-next-project-bootstrap.md and execute the setup in this directory for the product described as <product description>. Report the generated files, the checks that passed, and the next MVP task. Verify that PRODUCT.md exists and that the validation step ran.
Caveat. The README says the shortcut works from the published main branch, so in an unpublished checkout you must use the local prompt file instead.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page