FunnyEnough

Engineering notes & expertise

Reading

Size
Theme
Motion
For long-form reading
Type
Width
Space
Aids

Prompts

Prompts I actually use, shared as is — from my own work and from the community. Each one says when to reach for it and how it breaks. Start from a job below, or read the whole library by machine at /prompts.json.

Press / to search here, or ⌘K anywhere on the site to copy a prompt without leaving the page.

Start from the job, not the list

These are the jobs people actually arrive with. Run the steps in order; where a step has a fork, take the branch that matches your situation.

  1. Turn a vague ask into a change you can defend

    A one-line request, and every expensive decision still unmade.

  2. Change old code without breaking it

    No tests, real users, and something that has to get faster or cleaner.

  3. Make a change other code depends on

    A bounded edit in a living codebase, with neighbours you can break.

  4. Let an agent touch something you cannot undo

    A delete, a migration, a force-push, a deploy.

  5. Run an agent overnight and wake up to proof

    You will not be watching, and optimistic prose is not evidence.

  6. Decide whether to believe a green result

    Everything passed, and you cannot say what any of it proved.

  7. Ship a screen that does not feel machine-made

    It builds, it ships, and it still feels like a machine made it.

  8. Recover stranded work and leave the repo clean

    Stashes, stale branches, orphaned worktrees, and a pile of open PRs.

  9. Write something that reads human and survives a fact-check

    Technically right, and it still sounds like a model wrote it.

The full index

38 prompts, each with receipts

Shared as is, for reference. Read a prompt and decide what it will do before you run it; using it is your responsibility, under the terms.