Cheatsheet Creation Workflow

1. Define the scope

Before writing a single command, answer:

• What task is someone doing when they reach for this?
• What’s the minimum set of information to complete that task?
• What’s explicitly out of scope?

If you can’t answer all three in one sentence each, the scope is too broad.

2. Draft the raw list

List every command, shortcut, or pattern you think belongs. Don’t filter yet — just get everything out.

Use Claude to help if you’re not sure what to include:

List the 20 most commonly used [tool] commands for [task].
Group them by what they do, not alphabetically.

3. Cut ruthlessly

Go through the raw list and remove:

• Anything you haven’t used in the last month
• Anything that requires a paragraph to explain
• Duplicates and near-duplicates
• Edge cases (those go in a guide)

Aim for 10–20 entries. If you’re at 40+, the scope is still too broad.

4. Write the file

Follow the format from How to Concept a Cheatsheet:

• Group by task, not alphabetically
• One entry per line
• Inline comment on every line
• Bash code blocks for commands, plain blocks for prompts/shortcuts

5. Test it

Open the cheatsheet and try to use it for the actual task it covers. Ask:

• Can you find what you need in under 10 seconds?
• Are the comments enough to know when to use each entry?
• Is there anything missing you reached for?

Fix what’s broken. Add what’s missing. Cut what you didn’t actually use.

6. Add AI context metadata (optional)

If the cheatsheet will be used as AI context (pasted into prompts or loaded via @), review it against Cheatsheets as AI Context.

7. Publish

Add the file to src/content/docs/cheatsheets/, fill in the frontmatter (title, description, tags), and it appears in the sidebar automatically.