Fuck it. I'm sharing the exact mega prompt that built my entire n8n automation empire. This single prompt turns Claude into an n8n expert that designs, codes, and deploys AI agents from scratch. Copy, paste, watch magic happen. ``` You are an expert n8n workflow automation engineer with 5+ years of experience building production-grade AI agents. Your task is to help me build a complete n8n AI agent workflow for [DESCRIBE YOUR USE CASE]. CONTEXT ABOUT MY NEEDS: - Use case: [Describe what you want the agent to do] - Data sources: [List your inputs - emails, APIs, databases, etc.] - Desired outputs: [What should the agent produce/do] - Integrations needed: [Slack, Gmail, Notion, etc.] - Complexity level: [Beginner/Intermediate/Advanced] REQUIREMENTS: 1. Design the complete workflow architecture 2. Provide step-by-step n8n node configuration 3. Include error handling and retry logic 4. Add data validation and transformation steps 5. Suggest optimization for production use DELIVERABLES I NEED: □ Workflow diagram description □ Complete node-by-node setup instructions □ JSON workflow file structure □ Testing and debugging checklist □ Scaling recommendations TECHNICAL SPECIFICATIONS: - Use Claude/OpenAI API for AI processing - Include webhook triggers where applicable - Add proper data sanitization - Implement logging for troubleshooting - Follow n8n best practices for node naming CONSTRAINTS: - Keep it production-ready, not a demo - Optimize for reliability over complexity - Include fallback mechanisms - Make it maintainable by someone else EXAMPLES TO INCLUDE: - Sample input/output data formats - Common edge cases and solutions - Performance benchmarks if relevant STEP-BY-STEP FORMAT: 1. Architecture overview 2. Node sequence with configurations 3. Connection mappings between nodes 4. Environment variables needed 5. Deployment checklist Start by asking clarifying questions about my specific use case, then provide the complete implementation plan. ``` How to Use This Prompt Step 1: Copy the mega prompt above Step 2: Replace the bracketed sections with your specific details: - Your use case (lead scoring, content creation, data sync, etc.) - Your data sources and integrations - Your complexity preferences Step 3: Paste into Claude and watch it become your personal n8n consultant Step 4: Follow the step-by-step instructions it provides What are you going to build? Let me know in the comments...
💡CLAUDE[.]md Tips & Tricks (Cheatsheet) CLAUDE[.]md is one of the most important files in any Claude Code project. Think of it as project memory + execution guidelines. It tells Claude what your project is, how the codebase is structured, what design rules to follow, and what patterns to avoid. Here are 8 practical tips for writing a better CLAUDE[.]md: 1⃣ Know the difference between project and global CLAUDE.md A project-based CLAUDE[.]md lives in your project root and is specific to that product. A global CLAUDE[.]md lives in your Claude env and defines reusable preferences across all projects. Project CLAUDE.md = project context Global CLAUDE.md = personal working style 2⃣ Structure it properly Claude performs better when information is grouped semantically. Thats why don’t write random instructions. Use clear sections like: ✅ Project Overview ✅ Tech Stack ✅ Folder Structure ✅ UI/UX Principles ✅ Component Rules ✅ Accessibility Requirements ✅ Testing Strategy ✅ Content Guidelines ✅ Deployment Notes 3⃣ Use [/]init to create the first draft You don’t need to start from a blank page. Run [/]init so Claude Code will scan your project and generate a first version of CLAUDE[.]md It won’t be perfect, but it gives you a solid starting point. 4⃣ Keep it short CLAUDE[.]md is loaded into every Claude Code session, so it consumes context. My rule of thumb: Keep it under 200 lines. Ideally, under 100. For detailed documentation, use routing rules 5⃣ Be specific Bad instruction: “Write clean code.” Better instruction: “Use descriptive prop names, no abbreviations” and “Prefer composition over inheritance.” The more precise your instructions are, the more deterministic Claude’s output becomes. 6⃣ Treat CLAUDE.md as a living document Don’t create it once and forget it. Update it when: ✅ Claude repeats the same mistake ✅ You introduce a new pattern ✅ Your product requirements change ✅ Your design system evolves ✅ Your team agrees on new rules The best CLAUDE.md files are built from real usage, not theory. 7⃣Use [.]claude/rules for modular instructions Instead of putting everything into one file, split rules by topic and then reference them from CLAUDE[.]md or directly in Claude Code chat. This creates cleaner, more focused context. 8⃣ Commit CLAUDE[.]md to Git Your project-based CLAUDE.md is part of your project infrastructure. When you commit it to Git, the whole team gets more consistent AI behavior. Complete guide 👇
I'm Boris and I created Claude Code. I wanted to quickly share a few tips for using Claude Code, sourced directly from the Claude Code team. The way the team uses Claude is different than how I use it. Remember: there is no one right way to use Claude Code -- everyones' setup is different. You should experiment to see what works for you! 1. Do more in parallel Spin up 3–5 git worktrees at once, each running its own Claude session in parallel. It's the single biggest productivity unlock, and the top tip from the team. Personally, I use multiple git checkouts, but most of the Claude Code team prefers worktrees -- it's the reason @amorriscode built native support for them into the Claude Desktop app! Some people also name their worktrees and set up shell aliases (za, zb, zc) so they can hop between them in one keystroke. Others have a dedicated "analysis" worktree that's only for reading logs and running BigQuery See https://t.co/yXde5dW1vZ
Claude Code tips that have made my life easier: (Add these to your CLAUDE .md file) 1. "Before writing any code, describe your approach and wait for approval. Always ask clarifying questions before writing any code if requirements are ambiguous." 2. "If a task requires changes to more than 3 files, stop and break it into smaller tasks first." 3. "After writing code, list what could break and suggest tests to cover it." 4. "When there’s a bug, start by writing a test that reproduces it, then fix it until the test passes." 5. "Every time I correct you, add a new rule to the CLAUDE .md file so it never happens again." The wording in the file is much more detailed than what I wrote above, but hopefully these show the spirit.
