Arsenal
Structured templates for real tasks. These aren't generic prompts: each one has a role, a structure and a concrete intent. Copy them, adapt the parts in brackets and use them directly with Claude.
When starting a new project or when Claude doesn't know how to behave in your repository.
Act as a digital-project architect. Create a CLAUDE.md file for this project. The file should include: - A description of the project and its main goal - The tech stack used - Code and style conventions - What Claude should NOT do in this project - How to add new modules or sections - The project's tone and voice, if applicable Be concise. No more than 40 lines. No unnecessary decoration.
When you have an idea you want to execute but you're not sure whether it's worth it or how to structure it.
Act as a blunt business analyst with no desire to please. I have this idea: [describe the idea in 2-3 lines] I want you to audit it using this structure: 1. The real problem it solves (is there verifiable demand?) 2. A viable monetization model 3. Relevant direct and indirect competitors 4. The main risks 5. What's missing to validate it in 30 days at the lowest possible cost Don't tell me what I want to hear. Tell me what I need to know.
When you identify a repetitive manual process and you want Claude to design the automation architecture before writing any code.
Act as an automation engineer. I want to automate this process: [describe the process step by step] What I currently do manually: [describe the task] Available tools: [list the ones you have: Claude Code, GitHub, APIs, scripts, etc.] Design: 1. The complete automated flow 2. Which tools or scripts I need 3. The implementation steps in order 4. What could go wrong and how to prevent it 5. How I'd test it before trusting it
When you finish a process or workflow and you need it documented so that someone else — or you in three months — can run it without asking.
Act as a technical writer specialized in operational documentation. I have this process I want to document: [describe the process] Create documentation in Markdown that includes: - The goal of the process and what it's for - Who runs it and when - Detailed, numbered steps - What to do if something fails at each critical step - How to know whether the process was executed correctly Format: clean Markdown. No unnecessary jargon. So that someone who has never done it can follow it.
When you've been repeating a task for a while and you want to turn it into a system that can be delegated, automated or documented before it grows any further.
Act as a work-systems designer. I do this task manually and repetitively: [describe the task in detail] Frequency: [daily / weekly / monthly] Current time per run: [X minutes / hours] Tools I use now: [list] Help me turn it into a replicable system: 1. Which parts I can automate today without complex infrastructure 2. What I need to build for it to run autonomously 3. Which parts require human oversight and why 4. How I'd document it so someone else can run it without asking me anything
The text in [brackets] are variables you should replace with your real context.