Weird Jobs Generalist Quiz Join the Community

AI Cheatsheet

Claude Code for Generalists:
The Meta-Prompt Vault

By Milly Tamati, founder of Generalist World. From Scotland, without writing a single line of code herself.

The Story

I’m not a developer. I run a professional network for people with squiggly careers. And over the last few months I’ve shipped:

A job board with 500,000+ page views that made $300 in its first hour
A talent matching service that grew organically from people DMing me
My own custom link-in-bio page (goodbye Linktree)
Hundreds of auto-generated SEO pages
Social media banners, a sponsorship hub, and brand assets
Automated scouts that search the internet every morning while I sleep

All of it built by talking to Claude Code in plain English. Without writing a single line of code myself. No developer. No bootcamp.

“The prompts aren’t the magic. The thinking is. Anyone can type ‘build me a website.’ The reason my stuff actually works is how I frame the problem, how I describe what I want, and how I stack one thing on top of another.”

So I had Claude Code crawl through ALL of my files and projects to reverse-engineer my own process – and package the thinking into something you can use today.

Part 1: The Thinking Framework

These are the 5 mental models behind everything I’ve built. The prompts in Part 2 only work because the thinking is right.

Framework 1

The Compounding File

Before you do anything else, create a file called CLAUDE.md in your project folder. This is the single most important thing I’ve done.

Every time you open Claude Code, it reads this file first. It’s your business’s instruction manual. Mine contains: what my business does, every tool I use and how they connect to each other, how my systems work, and rules Claude needs to follow.

This file compounds. Every time you discover something Claude needs to know, you add it. After a few months, Claude knows your business better than any contractor you’ve ever hired.

Why this mattersWithout this file, every conversation starts from zero. With it, every conversation starts from full context. That’s the difference between Claude as a chatbot and Claude as a team member.

Framework 2

Describe Outcomes, Not Steps

I never tell Claude how to build things. I tell it what I want to exist.

Claude is better at figuring out the “how” than you are. Your job is to be clear about the “what” and the “why.”

Bad vs GoodBad: “Write Python code that connects to the WordPress REST API using urllib and base64 authentication, then creates a new page with the parent ID 10100”

Good: “I want every job in my Notion database to automatically get its own page on my WordPress site. The jobs page is at generalist.world/jobs/ and each job should be a child page of that.”

Framework 3

Stack, Don’t Start Over

Every project I’ve built has led to the next one. The job board created demand for the talent service. The programmatic SEO pages came from realising the job board could generate hundreds of keyword-targeted pages. The sponsorship hub came from having sponsors.

When you finish building something, ask: “What does this make possible that wasn’t possible before?” That’s your next project. And because Claude already knows the first thing (it’s in your CLAUDE.md), building the next thing is faster.

Framework 4

Automate the Gathering, Keep the Decisions

My scheduled tasks don’t make decisions. They gather, sort, and present. Every morning Claude searches for jobs, evaluates them, and puts them in my Notion. I make the final call on what gets published.

The patternAutomate everything except the judgment. The judgment is the generalist skill. The gathering is the busy work.

Framework 5

Test in Hours, Not Months

Because shipping is so cheap and fast, I test ideas that would have taken months to validate. The talent matching service? I built it in a day because the job board infrastructure already existed. If nobody wanted it, I’d have lost an afternoon. They did want it.

Part 2: The Meta-Prompt Vault

15+ prompts across 6 categories. Each includes the thinking, the prompt (copy-paste ready), and how I actually used it. Customise the [bracketed sections] for your own business.

Category 1: The Compounding File (CLAUDE.md)

1.1 First-Time CLAUDE.md Setup

Creates the foundation file that makes everything else work.

The thinking: Most people skip this or write something vague. The key is being SPECIFIC about your tools, how they connect, and what you want Claude to do with them – that’s what lets Claude actually help, not just write about them.

I’m setting up this project folder for my business. Help me create a CLAUDE.md file.My business: [one sentence about what you do] My website: [platform] at [URL] My email tool: [e.g. Beehiiv/ConvertKit/Mailchimp] My database: [e.g. Notion/Airtable/Google Sheets] My payment tool: [e.g. Stripe/Gumroad]For each tool, explain what it does, how it connects to the others, and what I’d need to know to work with it. Then create the CLAUDE.md with everything organised so you understand my whole setup.

Why this worksYou’re not just describing your business – you’re asking Claude to map out your whole setup. Claude will tell you what information it needs and explain what everything means in plain English.

1.2 Add a New Tool or Platform

Expands your CLAUDE.md when you start using a new tool.

I just started using [tool name] for [what you use it for]. Update my CLAUDE.md with whatever you need to connect to it and interact with it directly. Tell me what credentials or settings I need to get from the tool and where to find them.

1.3 The “What Do You Wish You Knew?” Audit

Identifies gaps in your CLAUDE.md after you’ve been using it for a while.

The thinking: After a few weeks of working together, Claude knows what information it keeps having to ask you for. This prompt surfaces those gaps.

Based on our recent conversations and the work we’ve done together, what information do you keep needing that isn’t in my CLAUDE.md? What would make you more effective if I added it? Update the file with anything that’s missing.

Category 2: Shipping Things

2.1 The “I Want This to Exist” Prompt

Turns a vague idea into a built thing.

The thinking: This is the most important prompt pattern. You describe the WHAT and WHO and WHY. You never describe the HOW. Claude is better at the how than you are.

I want to build [what it is] for [who it’s for].The problem it solves: [why someone would use this] Where it lives: [your website, a standalone page, Notion, etc.] What it connects to: [any existing tools or data it should use]Here’s what a user would experience: [describe the journey from their perspective – what they see, what they do, what happens]Build it.

How I used this“I want to build a job board for people with non-linear careers. The problem it solves: generalists can never find jobs that actually want their range. It lives on my WordPress site at generalist.world/jobs. It connects to my Notion database where I track all jobs. Here’s what a user would experience: they land on the page, see jobs organised by archetype and region, click one, and see a detail page with the full description and an apply link.”

2.2 The “Stack on Top” Prompt

Builds a new thing using an existing thing as the foundation.

The thinking: This is how ideas compound. You never start from zero after the first project.

[Existing thing] is working well. Now I want to build [new thing] on top of it.The connection: [how the new thing relates to or uses the existing thing] What’s different: [what the new thing does that the existing thing doesn’t] Who it’s for: [same audience? different audience?]Use whatever infrastructure already exists. Don’t rebuild anything – extend what’s there.

How I used this“The job board is working well. Now I want to build a talent matching service on top of it. The connection: companies are DMing me asking for candidates, and I have job seekers visiting the board. What’s different: instead of just listing jobs, I’m matching specific candidates to specific companies.”

2.3 The Quick Test

Validates an idea in hours instead of months.

I want to test whether [audience] would actually want [idea]. Build me the simplest version that lets me find out. Use [existing infrastructure] as the base. Don’t over-build it – I just want to put it in front of people and see if they bite.

2.4 The “Replace a SaaS” Prompt

Builds a custom version of something you’re paying a subscription for.

The thinking: If you’re paying for a simple tool (Linktree, a basic CRM, a simple dashboard), Claude can often build you a custom version that’s better because it’s tailored to your exact needs and brand.

I’m currently paying for [tool] and I use it for [what you use it for]. Can you build me my own version? Here’s what I actually need it to do: [list the specific features you use]. It should match my brand: [colours, fonts, style]. I want it on my own domain.

How I used this“I’m currently paying for Linktree and I use it for my link-in-bio on social media. Can you build me my own version? Here’s what I actually need: my photo at the top, 4-5 links to my main pages, my social media icons, and it needs to look like my brand. I want it on my own domain at generalist.world/links.”

Category 3: Automating the Boring Stuff

3.1 The “I Do This Every Week” Prompt

Turns a recurring manual task into an automated one.

The thinking: Don’t start with “what should I automate?” Start with “what am I doing every week that I wish would just happen?” That’s always the right first automation.

Every [frequency] I manually do this task: [describe exactly what you do, step by step].It takes me about [time]. The inputs come from [where]. The output goes to [where].Can you do this for me right now? And then can we set it up so it happens automatically on [schedule]?

3.2 The “Scout” Prompt

Sets up Claude to search the internet for things you care about on a recurring schedule.

The thinking: This is the pattern behind my job scout. It works for anything – leads, press mentions, competitor moves, content ideas, partnership opportunities.

I need you to regularly search for [what you’re looking for].Where to look: [specific platforms, sites, search queries] What qualifies: [your criteria for “this is a good find” – be specific] What doesn’t qualify: [things to skip] Where to put the results: [Notion database, spreadsheet, email, Slack] How to present them: [what information to include for each find]Before adding anything, check against [existing database/list] to avoid duplicates. Set the status to [status] so I can review before anything goes live.

How I used this“I need you to regularly search for generalist jobs. Where to look: Twitter, Hacker News, LinkedIn, Ashby career pages. What qualifies: roles that are cross-functional, require range, involve wearing many hats. What doesn’t qualify: standard software engineering roles, anything older than 30 days, broken URLs. Where to put the results: my Notion database with status ‘New’ so I can review before publishing.”

3.3 The “Process and Publish” Prompt

Takes raw data from one place, processes it, and publishes it somewhere else.

When a new [entry type] appears in [source] with [trigger condition]:1. Read it and extract: [what information to pull] 2. Process it: [any categorisation, formatting, or enrichment] 3. Publish it to: [destination] 4. Update the source: [change status, add IDs, mark as processed] 5. Notify: [where to send a notification, if anywhere]

Category 4: Programmatic SEO

4.1 The “One Database, Hundreds of Pages” Prompt

Turns a database of items into a network of SEO-optimised pages.

The thinking: If you have any kind of catalogue, directory, or listing – jobs, products, members, resources – each item can be its own indexed page targeting specific keywords.

I have a [database/spreadsheet/list] of [items] with these fields: [list the fields].I want to generate individual pages for each item on my website. Each page should: – Have a unique URL at [URL pattern, e.g. mysite.com/jobs/{slug}/] – Include [which fields to show and how] – Have proper SEO structure (title tag, meta description, H1) – Link back to the main listing page at [URL] – Be a child of [parent page] on my siteAlso generate category pages that group items by [field].When I add a new item to the database, all relevant pages should update automatically.

4.2 The “Guide Pages” Prompt

Creates informational pages around your categories for additional keyword targeting.

The thinking: Category pages list things. Guide pages explain things. “Generalist Jobs for Connectors” is a category page. “What is a Connector?” is a guide page. Both rank for different keywords and they link to each other.

For each [category type] in my [system], create a guide page that explains: – What is a [category]? – What skills do they have? – What kind of roles suit them? – Link to the category page showing all [items] in this categoryWrite these in [your brand voice]. The goal is to rank for “[what is a category]” searches and drive traffic to the main listing.

Category 5: Brand & Design Assets

5.1 The “On-Brand Everything” Prompt

Generates visual assets that match your brand perfectly.

The thinking: The key is giving Claude your EXACT brand specifications once (in the CLAUDE.md), then every asset comes out consistent. No more Canva templates that are “close enough.”

Create a [type of asset, e.g. LinkedIn banner / social graphic] for [what it’s promoting].Use my brand system: – Background: [colour] – Text colour: [colour] – Heading font: [font] – Body font: [font] – Accent colour: [colour] – Dimensions: [platform-specific size]The message: [what it should say] The vibe: [what feeling it should give]Build it as HTML so I can screenshot it at the right dimensions.

Why HTML?Claude can’t generate image files, but it can generate pixel-perfect HTML that you screenshot. This sounds hacky but it works brilliantly – you get exact brand colours, exact fonts, exact spacing, every time.

5.2 The “Design System in a File” Prompt

Captures your entire visual brand so you never have to describe it again.

I want to document my brand’s visual system so that every asset you create matches perfectly. Here are my brand elements:– Primary colour: [hex] – Secondary colour: [hex] – Accent colour: [hex] – Background colours: [hex for light, dark] – Heading font: [name] – [weight] – Body font: [name] – [weight] – Button style: [describe] – Border radius: [px]Save this as a brand system reference in my CLAUDE.md so you use it automatically for everything.

Category 6: The Meta-Prompts

6.1 The “Crawl My Own Files” Prompt

Has Claude analyse your own projects to find patterns, extract insights, or document what exists.

The thinking: This is literally how this product was made. I asked Claude to look through everything I’ve built and tell me what my process is. You can use this to audit your own business, find inefficiencies, or create documentation.

Go through all of my files and folders in [directory]. I want you to understand: – What I’ve built – How the pieces connect to each other – What’s working well – What’s incomplete or could be improvedThen [what you want to do with that information – create documentation, find gaps, suggest next steps, package it for someone else].

6.2 The “Teach Me What I Did” Prompt

Helps you understand and document your own systems.

The thinking: When you build things conversationally, you don’t always understand the infrastructure Claude created. This prompt makes it explain your own setup back to you.

Walk me through how [system/project] works, in plain English. Explain it like I didn’t build it (even though I did). What are the moving parts? What connects to what? If I wanted to explain this to someone else, what would I say?

6.3 The “What Should I Build Next?” Prompt

Uses your existing setup to suggest high-value next projects.

Look at everything I’ve built so far. Based on what exists, what infrastructure is already in place, and what my business does – what’s the highest-value thing I could build next? I want something that: – Uses what already exists (don’t start from zero) – Could be tested quickly – Would either make money, save time, or grow my audienceGive me 3 options ranked by impact.

Quick Reference: The Cheat Sheet

The Generalist’s Claude Code Cheat Sheet

1. Start here – Create a CLAUDE.md file. Put everything Claude needs to know about your business in it. This one file changes everything.

2. Describe outcomes, not steps – “I want a job board that connects Notion to WordPress” beats “write Python code that calls the REST API.” Let Claude figure out the how.

3. Ship, then stack – Build one thing. Then ask: what does this make possible? Build that next. Every project makes the next one easier.

4. Automate the gathering, keep the judgment – Let Claude search, sort, categorise, and present. You make the decisions.

5. Test in hours – When building costs a conversation instead of a contractor, you can test anything. Validate ideas with quick builds, not months of planning.

6. The compounding file – Every time you learn something Claude needs to know, add it to CLAUDE.md. Six months in, it knows your business better than any contractor you’ve hired.

Claude Code for Generalists:The Meta-Prompt Vault