// Prompts & Examples

Based on our conversation, create a pocket reference card summarising the key points.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Extract the most actionable information
- Organise into 3-5 logical sections
- Include a final **Do next** checklist (5-9 bullets)
- Use em dash (—) not hyphen
- Add <!-- columnbreak --> between major section groups
- Target 400-500 words total

Begin output now:

Create a pocket shopping checklist template.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Checkbox format: - [ ] Item — optional note
- Use em dash (—) not hyphen for notes
- Add <!-- columnbreak --> between major section groups
- Target 300-350 words total

STRUCTURE:

# Shopping Checklist

## Produce
[8-10 common vegetables and fruits with checkboxes]

## Dairy & Proteins
[6-8 items: eggs, milk, cheese, meat, fish]

<!-- columnbreak -->

## Pantry Staples
[8-10 items: bread, rice, pasta, oils, spices]

## Household
[6-8 items: cleaning supplies, paper goods]

<!-- columnbreak -->

## Personal Care
[5-6 items]

## Weekly Specials
[3-4 blank lines for handwritten additions]

## Notes
[2-3 tips for efficient shopping]

Begin output now:

Create a pocket packing checklist for a weekend trip.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Checkbox format: - [ ] Item — optional note
- Use em dash (—) not hyphen for notes
- Add <!-- columnbreak --> between major section groups
- Target 300-350 words total

STRUCTURE:

# Weekend Packing

## Clothing
[8-10 essential clothing items with checkboxes]

## Toiletries
[6-8 personal care items]

<!-- columnbreak -->

## Electronics
[5-6 items: phone, charger, headphones]

## Documents
[4-5 items: ID, tickets, reservations]

## Medications
[3-4 items including first aid basics]

<!-- columnbreak -->

## Before Leaving
[5-6 home security checks]

## Notes
[2-3 tips for light packing]

Begin output now:

Create a pocket training handout for [TOPIC/PROCESS].

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Bullet points for steps and key points
- Use em dash (—) not hyphen
- Add <!-- columnbreak --> between major section groups
- Target 400-450 words total

STRUCTURE:

# [Topic] Quick Reference

## Overview
[2-3 sentences: what this covers and why it matters]

## Key Steps
[6-8 numbered steps for the main process]

<!-- columnbreak -->

## Common Mistakes
[4-5 mistakes to avoid]

## Quick Tips
[4-5 practical tips]

## Troubleshooting
[3-4 common issues and solutions]

<!-- columnbreak -->

## Resources
[3-4 where to get help: contacts, documentation]

## Checklist
- [ ] Step 1 complete
- [ ] Step 2 complete
[4-5 checkboxes for verification]

Begin output now:

Create a pocket SOP card for [PROCEDURE NAME].

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Numbered steps for procedures
- Checkbox format for verification steps: - [ ] Item
- Use em dash (—) not hyphen
- Add <!-- columnbreak --> between major section groups
- Target 350-400 words total

STRUCTURE:

# [Procedure] SOP

## Purpose
[1-2 sentences: why this procedure exists]

## Before You Start
- [ ] Check: [prerequisite 1]
- [ ] Verify: [prerequisite 2]
[3-4 pre-checks]

## Procedure
1. [Step with specific action]
2. [Step with specific action]
[8-10 numbered steps]

<!-- columnbreak -->

## Safety Notes
[3-4 critical safety points]

## Quality Checks
- [ ] [Verification point]
[4-5 checkboxes]

<!-- columnbreak -->

## If Something Goes Wrong
[3-4 escalation steps and contacts]

## Sign-off
- Completed by: _____________
- Date: _____________

Begin output now:

Create a pocket meeting checklist for professionals.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- No links, citations, or URLs
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Checkbox format: - [ ] Item — optional note (keep notes under 6 words)
- Use em dash (—) not hyphen for notes
- Add <!-- columnbreak --> between phases
- Target 350-400 words total

STRUCTURE:

# Meeting Checklist

[1 sentence: reusable checklist for productive meetings]

## Before (1 day prior)
- [ ] Review agenda — confirm objectives clear
- [ ] Prepare materials — slides, docs, data
[4-5 more prep items]

<!-- columnbreak -->

## During
- [ ] Start on time — respect attendees
- [ ] Assign note-taker
[5-6 facilitation items]

## After (within 24 hours)
- [ ] Send summary — action items, owners, dates
[3-4 follow-up items]

<!-- columnbreak -->

## Quick Tips
[3-4 meeting best practices]

Begin output now:

Create a pocket new hire onboarding checklist for managers.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- No links, citations, or URLs
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Checkbox format: - [ ] Item — optional note (keep notes under 6 words)
- Use em dash (—) not hyphen for notes
- Add <!-- columnbreak --> between phases
- Target 400-450 words total

STRUCTURE:

# New Hire Onboarding

[1 sentence: reusable checklist for welcoming new team members]

## Day One
- [ ] Workspace ready — desk, equipment, access
- [ ] Welcome meeting — team introductions
[5-6 more first day items]

<!-- columnbreak -->

## Week One
- [ ] Training sessions — role-specific
- [ ] Buddy check-ins — daily
[5-6 learning and connecting items]

## First 30 Days
- [ ] First project assigned
- [ ] Feedback session completed
[3-4 milestone items]

<!-- columnbreak -->

## Success Indicators
[3-4 signs the onboarding worked]

Begin output now:

Create a pocket reference card for Git daily workflows.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- No links, citations, or URLs
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Command format: `command` — brief description (6-10 words max)
- Use em dash (—) not hyphen
- Add <!-- columnbreak --> between major section groups
- Use :danger: for destructive commands, :warn: for cautions
- Use :tip: for best practices, :info: for helpful notes
- Target 450-500 words total

STRUCTURE:

# Git Quick Reference

[1 sentence: what this covers]

## Setup & Config
[4-5 essential config commands]
:tip: [One best practice tip]

## Daily Workflow
[6-8 most common commands: status, add, commit, push, pull]
:info: [One helpful note]

<!-- columnbreak -->

## Branching
[5-6 branch operations: create, switch, merge, delete]
:warn: [One caution about force deleting]

## Viewing History
[4-5 log and diff commands]
:tip: [One tip about reflog]

<!-- columnbreak -->

## Undoing Changes
[3-4 commands: restore, reset, stash]
:warn: [Caution about discarding changes]
:tip: [Tip about stash]

## Dangerous Commands
:danger: `git reset --hard` — [why dangerous]
:danger: `git push --force` — [why dangerous]
:danger: `git clean -fd` — [why dangerous]

## Remote Operations
[3-4 remote commands]
:info: [Best practice about pulling]

Begin output now:

Create a pocket reference card for Vim daily workflows.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- No links, citations, or URLs
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Shortcut format: Key — Action (brief description)
- Group by: Navigation, Editing, Search/Replace, Visual Mode
- Use em dash (—) not hyphen
- Add <!-- columnbreak --> between groups
- Target 400-450 words total

STRUCTURE:

# Vim Quick Reference

[1 sentence: what this covers]

## Navigation
[8-10 motions: hjkl, w, b, 0, $, gg, G, etc.]

## Editing
[8-10 commands: i, a, o, d, c, y, p, u, etc.]

<!-- columnbreak -->

## Search & Replace
[5-6 patterns: /, n, N, :%s/old/new/g, etc.]

## Visual Mode
[4-5 commands: v, V, Ctrl+v, selection operations]

<!-- columnbreak -->

## Pro Tips
[3-4 power tips for daily use]

Begin output now:

Create a pocket reference card for a REST API.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- No links, citations, or URLs
- Start immediately with # heading

INPUT REQUIRED:
Tell me: What API? (e.g., "Stripe Payments API", "GitHub Issues API")

FORMAT:
- Use ## for sections
- Endpoint format: `METHOD /path` — Brief description
- Include common parameters in bullet points
- Use <!-- columnbreak --> between endpoint groups
- Target 400-450 words total

STRUCTURE:

# [API Name] Quick Reference

## Authentication
[1-2 sentences on auth method]

## Core Endpoints
`GET /resource` — List all
`GET /resource/:id` — Get one
`POST /resource` — Create new

<!-- columnbreak -->

## Common Parameters
- `limit` — Results per page
- `offset` — Pagination start
[3-4 more parameters]

## Response Codes
[5-6 common codes with meanings]

<!-- columnbreak -->

## Quick Examples
[2-3 curl examples]

Begin output now:

Create a pocket reference card for [COURSE NAME] golf course.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- No links, citations, or URLs
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Bullet points with dashes (-), NO tables
- Hole format: **N** Par X, Ym, SI Y — short tip (8-12 words max)
- Use em dash (—) not hyphen
- Add <!-- columnbreak --> between Front 9, Back 9, and final sections
- Target 520-560 words total

STRUCTURE:

# Course Name
[2 sentences: par, length in metres, slope/CR, defining character]

## Front 9
[Each hole: **N** Par X, Ym, SI Y — brief tip about key challenge]

<!-- columnbreak -->

## Back 9
[Same format as Front 9]

<!-- columnbreak -->

## Signature Holes
[3 bullets: hole number and one-sentence description]

## Course Strategy
[5 short bullets with key advice]

## Local Rules
- Preferred lies
- Stake colors
- Drop zones
- Cart rules

## On Course
- Halfway house
- Toilets
- Pro shop
- Lightning procedure

Begin output now:

Create a pocket exit-home checklist for busy professionals.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- No links, citations, or URLs
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Checkbox format: - [ ] Item — optional note (keep notes under 6 words)
- Use em dash (—) not hyphen for notes
- Add <!-- columnbreak --> between major section groups
- Target 350-400 words total

STRUCTURE:

# Exit Home Checklist

[1 sentence: purpose of this checklist]

## Essentials
- [ ] Phone — charged above 50%
- [ ] Wallet — cards, cash, ID
- [ ] Keys — house, car, office
[2-3 more essential items]

## Work Items
[5-6 work-related items with checkboxes]

<!-- columnbreak -->

## Weather & Season
[4-5 weather-dependent items]

## Personal Care
[4-5 items: glasses, meds, etc.]

## Before You Lock
[4-5 home security checks]

<!-- columnbreak -->

## Weekly Additions
[3-4 items you might need certain days]

## Monthly Check
[3-4 less frequent items to verify]

## Emergency Kit
[4-5 items to keep in bag/car]

## Notes
[3-4 bullet points with personalisation tips]

Begin output now:

Create a beginner-friendly pocket reference for Python basics.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Focus on: variables, loops, functions, common operations
- Add brief explanations for each item
- Use <!-- columnbreak --> between major sections
- Target 400-450 words total

Begin output now:

Create a keyboard shortcut reference for VS Code.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Shortcut format: Shortcut — Action (brief description)
- Group by: Navigation, Editing, Search, Debug
- Include Mac shortcuts (Cmd instead of Ctrl)
- Use <!-- columnbreak --> between groups
- Target 400-450 words total

Begin output now:

Create a pocket reference for Docker CLI commands.

STRICT OUTPUT RULES:
- Output ONLY raw Markdown, nothing else
- No introductions, explanations, or follow-up text
- Start immediately with # heading

FORMAT:
- Use ## for sections
- Command format: `command` — brief description (6-10 words max)
- Group by workflow: build, run, debug, cleanup
- Use <!-- columnbreak --> between groups
- Target 450-500 words total

Begin output now:

Use color markers at the start of lines to highlight text:

:danger: Never run as root — commands can damage your system
:warn: Check permissions before proceeding
:tip: Use tab completion to save time
:info: Default timeout is 30 seconds

The marker is removed and the text appears in the specified color.

# Git Quick Reference

## Undoing Changes

`git restore file` — Discard uncommitted changes
:warn: This permanently discards local changes

`git reset --hard HEAD~1` — Undo last commit
:danger: This deletes commit history — use with caution

`git stash` — Temporarily save changes
:tip: Use `git stash pop` to restore later

## Best Practices
:info: Always create a branch before risky operations

Add visual icons to your PDFs using relative URLs:

![Warning](/public/icons/warning.svg) Cautions, potential issues
![Info](/public/icons/info.svg) Additional information
![Tip](/public/icons/tip.svg) Best practices, pro tips
![Danger](/public/icons/danger.svg) Critical warnings

Also available: checklist, clock, code, folder, person, star

Icons are free for all users (no limits).