It’s a mythical and magical creature everyone talks about—but no one has truly seen. A unicorn. A pegasus. Even Nessie, the Loch Ness Monster. Yet everywhere you look, there are so-called gurus promising to sell you the ultimate master prompt. The one prompt that will magically build your app, create your business, generate your videos, automate your life, and turn your ideas into reality. They sell you the spell. But they never teach you how to write the book of magic. Because the truth is simple: The power was never in the prompt. The power is in the thinking that happens before the prompt. The Paper Is More Powerful Than the Prompt Before ChatGPT. Before Claude. Before Perplexity. Before AI. There was paper. Ancient. Analog. Silent. Honest paper. Notion is fast. Google Docs is convenient. But paper forces clarity. Paper forces intention. Paper forces you to think. When you sit down with a blank sheet, something changes. You are no longer reacting. You are designing. So start there. Not in Claude. Not in ChatGPT. Not in your IDE. Start on paper. Write: What you want to create What it should do How it should behave What it should look like What it should sound like How it should evolve Write everything. Messy. Incomplete. Imperfect. Because this is not the prompt. This is the blueprint. Design It Like an Architect An architect does not walk into a construction site and say: “Build me a building.” They bring plans. Dimensions. Materials. Systems. Naming conventions. You must do the same. If you want graphics: Write that. Describe them. Name them. Example: ###### Graphic Name: hero_image_v1 Description: Minimal futuristic illustration of AI agent assisting a business owner. Orbix titanium and glass aesthetic. Dark gradient background. Professional. Clean. Graphic Name: dashboard_preview Description: Screenshot-style graphic showing automation workflows connected visually. ###### If you want video: Write that too. If you want automation:

When most people hear the word automation, they think of something simple: a repetitive task that gets done automatically so they can save time. And honestly? That part is true. At its most basic level, an automation is a system that takes Task A, applies a defined set of rules, and reliably delivers Result B — every time, without human intervention. No breaks. No forgetting. No inconsistency. That alone already has value. But that definition barely scratches the surface of what automation really means in a business context. Automation Is Not the Tool — It’s the Outcome A common mistake businesses make is focusing on the tool instead of the outcome. Automation is not: - n8n - Zapier - Make - AI agents - APIs - Scripts Those are just instruments. Automation is the intentional design of a process that removes friction, reduces waste, and produces consistent results aligned with business goals. The real question is never: “Can this be automated?” The real question is: “What business result do we want to achieve, and how do we design a system that gets us there reliably?” What Actually Happens Behind the Scenes This is where we come in. We are not “button clickers” or “workflow builders.” We are architects of business flow. Our job is to take something that exists in your business — an idea, a task, a process, a bottleneck, or even pure chaos — and design a structured path from Point A to Point B, based on your desired outcome. That “thing” can be: - A lead coming in - An email being received - A form submission - A customer action - A manual internal process - A recurring operational chore - A creative workflow - A reporting requirement Once the goal is defined, we design the logic, rules, validations, fallbacks, and integrations that make the system work reliably in the real world, not just in theory. The “Magic” Is Just Well-Designed Systems From the outside, automation often looks like magic. An email triggers a workflow. A lead gets scored automatically. A report is generated and sent. A video is created, branded, and posted across multiple platforms. A customer receives the right message at the right time.

For anyone planning to start charging for automations, this is a good place to start.Review the included documents and make sure they fit your situation.They’re meant to protect you and support you long-term. And as always, feel free to ask me anything. I’m here to help. Yes, they are .md files .md files are txt files, but you all already know that.

n8n Workflow Prompt Here is the master prompt that I use for starting to create an n8n workflow Feel free to modify it and add and remove things you think are and aren't necesarry. And note that I said starting. Because from there, I continue to build exactly what the client wants. AI and especially claude.ai can give you great workflows, but always check the end workflow for any mistakes that the AI might have done. n8n v2 Workflow Creation – System Prompt You are an n8n v2 expert. Your role is to design, validate, and document the automation I describe. Core Rules (Must Follow) - Use only verified, existing n8n v2 internal nodes - Use and verify the nodes from https://docs.n8n.io/integrations/builtin/node-types/ - Do NOT use Function nodes - Use Code nodes instead of Function nodes - Never invent node names, operations, credentials, or features - If you are not 100% sure a node or operation exists, do not use it - Prefer core n8n nodes whenever possible - Double-check the final workflow before presenting it If required information is missing, ask for clarification. Do not guess. Do not fill gaps. Required Deliverables (Mandatory) You must produce the following files: 1. A valid n8n workflow JSON file 2. A README.md file 3. An INSTALL.md file If any file cannot be produced, clearly explain why. Workflow Output Requirements - Verify every node before inclusion - Validate the workflow logic end-to-end - Do not include unused or unnecessary nodes - Ensure the workflow matches exactly what was requested Writing Style Rules - Be direct and concise - Use natural, plain language - Avoid marketing or hype - Avoid filler words and clichés Do NOT use phrases like: - “Let’s dive into…” - “Game-changing” - “Unleash your potential” Use instead: - “Here’s how it works.” - “This step does the following.”

If you’ve ever lost hours playing Factorio, Satisfactory, or any automation-style game, you already understand more about real-world workflows than you might think. That’s because these games don’t teach you how to click buttons — they teach you how to think. Resources, Inputs, and the First Spark of Logic In automation games, everything starts with a problem: - You need iron plates - To get iron plates, you need iron ore - To get iron ore, you need miners, power, and belts Very quickly, you stop thinking about individual actions and start thinking in systems. Now replace that with automation tools like n8n or other no-code platforms: - You need usable data - To get usable data, you need raw input - That input comes from webhooks, forms, emails, APIs, or databases Suddenly, “iron ore” becomes raw data, and “miners” become triggers. The mindset is the same. Processing Is Processing — No Matter the Medium In games, raw materials are almost useless by themselves.Iron ore isn’t helpful until it’s smelted, shaped, and assembled. Automation workflows work exactly the same way: - A form submission is just raw text - An email is unstructured information - A webhook payload is noise until processed Your workflow nodes are your assemblers: - Clean the data - Filter what matters - Transform formats - Enrich it with additional sources - Route it where it needs to go Just like in a factory game, efficiency isn’t about speed—it’s about flow. Bottlenecks, Debugging, and Why Things Break Anyone who’s played automation games knows this moment: “Why is everything backed up?” You trace the belts. You check power. You find the missing splitter. In workflow automation: - A node fails - A webhook times out - Data doesn’t match the expected format And you do the same thing:You trace the execution. You inspect inputs and outputs.