Worker Setup
in under 5 minutes.

Three steps. That's it.

Danilo sent you a folder called worker-setup. Drop it on your Desktop, paste a prompt into Claude, restart. Done.

1. Put the worker-setup folder on your Desktop

   Danilo sent you a zip file (over WhatsApp or Google Drive). Download it. Right-click the zip and choose Extract All, Windows unzips it. Drag the resulting worker-setup folder onto your Desktop.

   It needs to be on the Desktop exactly. Not Downloads, not Documents, Desktop.

2. Open Claude Code and paste this prompt

   Open a fresh Claude Code session. Copy the entire block below and paste it as your first message. Hit enter. Claude will figure out the right Windows paths and run all the setup itself.

   Copy this whole block, paste into Claude Code

   I'm on Windows. The worker-setup folder is on my Desktop. Set everything up for me, figure out the right Windows paths yourself (the Claude Code config folder, my user home folder, etc.) and run these in order. Confirm each one is done before moving to the next:
   
   1. Copy worker-setup\CLAUDE.md to my home folder as CLAUDE.md (overwrite if it exists).
   
   2. Make sure my Claude Code skills folder exists, then copy everything from worker-setup\skills\ into it.
   
   3. Copy all .py files from worker-setup\scripts\ into my Claude Code config folder.
   
   4. Copy all .json files from worker-setup\credentials\ into my Claude Code config folder.
   
   5. Look inside the Claude Code projects folder, find the one that matches my Windows username, make a memory subfolder inside it if it doesn't exist, then copy everything from worker-setup\memory\ into that memory folder.
   
   6. Run the Google authorization script, it's google_auth_setup.py with client_secret.json as the argument. Use python or python3, whichever works. A browser will open and I'll log in with the Google account Danilo gave me, then click Allow.
   
   7. When everything is done, tell me to fully close and reopen Claude Code so it picks up the new skills and memory.

3. Close and reopen Claude Code

   Once Claude tells you it's done, fully close Claude Code (close the window or Alt+F4) and reopen it. This makes it pick up the new skills and memory files.

   Test it worked: in your fresh Claude Code session, type /hankox. If Claude responds with the HankoX operating system, you're fully set up.

How to ship a campaign.

When Danilo gives you an email task, here's how it goes. You don't write code. You don't run scripts. You describe what you want in plain English, Claude does the work.

The flow

Danilo sends a brief → which client, what the campaign is about, when it sends, what audience. You open Claude Code and tell Claude what you're working on. Claude pulls the right skill automatically, drafts the copy. You iterate until it's good. Claude creates a Google Doc with the copy. If a banner is needed, you ask Claude to brief Jesus, it posts the doc link in #jesus-design on Discord. Once design is back, you tell Claude to upload to ActiveCampaign (NTW) or SendGrid (HankoX) and schedule it. Done.

Example prompts you can copy

How to spin up a client bot.

When Danilo asks you to build a support bot for a new client. You're cloning the Fewpips pattern, not starting from scratch.

The Fewpips bot took weeks to nail. Every gotcha (greeting doubles, infinite loops, markdown leaks, the wrong API version) is documented in the bot-builder skill. When you build for a new client, you're cloning that solved pattern.

What Danilo gives you before you start

• The client's knowledge base (markdown doc with FAQs, products, rules, contact emails)
• LiveChat credentials: account ID, PAT, bot agent ID
• Brand assets: logo, exact name spelling, brand color
• Email routing: which inbox handles support, finance, partners, PR
• Social media links: Discord, Twitter/X, Instagram, Trustpilot
• Escalation rules: what topics MUST go to a human
• OpenAI API key for the bot's GPT calls
• Railway access (where the bot deploys)

If anything's missing, message Danilo before starting. Don't try to fill gaps yourself.

The flow

You open Claude Code, paste in everything Danilo sent. Claude invokes /bot-builder automatically, walks you through forking the Fewpips template into a new GitHub repo, swapping all the brand-specific code (system prompt, greeting, knowledge base, support email, Trustpilot URL), helps you set up the LiveChat dashboard, deploys to Railway, gives you a 12-item test checklist for the live bot.

Example prompt to start

Your tools.

Each skill is a focused playbook. Type the command in Claude Code to invoke it. You don't need to memorize this, describe your task and Claude usually picks the right one.

What Claude already knows.

These auto-load every time Claude starts. You don't invoke them. They're available as context whenever a related topic comes up.

Quick reference.

Detailed brand guides are in the memory files and skill files for each client.