Free prompts and agent rules for building software with AI: clarify what to build, keep the work focused, and carry project decisions into the next session.
Copy a prompt into your AI chat, answer its questions, and review the resulting specification or handoff. The templates are Markdown files; you can use them without cloning this repository or installing a package.
| What you need | Open this | What to bring | What you get |
|---|---|---|---|
| Turn an app idea into clear requirements | PRD prompt · Guide | Rough notes, intended users, and constraints | A draft Product Requirements Document built through questions and confirmation |
| Give your coding assistant clear working rules | Claude Opus 5 rules · Setup guide | Your existing project instructions and the matching model | Instructions for concise responses, task scope, and tool use |
| Continue a project in a fresh AI chat | Session-continuation prompt · Guide | The current conversation, while its history is still available | A reviewable handoff with decisions, progress, and remaining tasks |
- Open the PRD prompt file and copy its contents.
- Replace the text between
BRAINDUMP STARTandBRAINDUMP ENDwith your idea; fill or remove the other bracketed placeholders. - Paste the prompt into your AI chat, answer the questions, and confirm the decisions before asking for the final draft.
Already have a PRD and a concise MVP concept? Use the ultra-lean build prompt to define the first build's purpose, features, and technical approach.
You can enter at the step you need; each folder explains its required inputs.
| Step | Resource | Output |
|---|---|---|
| Plan user research | Research questionnaire | Questionnaire draft, then an evidence-linked PRD input from collected responses |
| Define the product | PRD generation | Goals, users, requirements, and constraints |
| Map the experience | UX and user flow | User journeys and interface requirements |
| Choose the first release | MVP concept | Core problem, hypothesis, and limited feature scope |
| Plan the build | MVP development plan or ultra-lean build specification | Detailed development plan or a smaller build specification |
| Plan verification | Test plan | Test scope, cases, and acceptance criteria |
| Prepare a visual brief | v0 design prompts | A design prompt using your UX specification and MVP scope |
| Prepare the next session | Session continuation | Current state, corrections, and next tasks |
For the full instructions, see the prompt template guide.
The agent configuration guide separates behavioral instructions from tool permissions:
- Claude Opus 5 instructions: review the model scope and merge relevant rules with your existing project instructions.
- Claude Code permission guardrails: an optional strict policy with broad restrictions; read its effects before using it.
The prompts use guided questions, confirmation points, and inputs from earlier steps to help you make explicit decisions. Outputs remain drafts: review requirements, code, and handoffs before relying on them, and remove private information you do not need to share with your AI tool.
Star this repository to save it for your next project. If you find an unclear step, open an issue with the template name and a small, non-sensitive example.
I develop these resources using official documentation, AI tools, and my own software development work. My separate Prompt Rulebook covers broader prompting techniques.
This toolkit is free to use, adapt, and share under the MIT license.