For Cursor

Cursor Agent Instructions

This file tells Cursor agents how to write or revise Thinking Bugs articles with the playbook framework.

Read the smallest set of files needed for the pass. Do not invent a third house style.

1. Source files

Do not outline a new article until playbook/briefs/<slug>.md is filled.

2. New or rewritten article workflow

1. Pick the slug and article shape.
2. Fill the brief: belonging test, nearby bugs, sources, examples, prevention, reframing, related links.
3. Draft or rewrite content/<slug>.php.
4. Add sources to data/article-references.json when the article cites verified research.
5. Update metadata and integration files when adding a new specimen.
6. Run a fact-check pass.
7. Run a voice pass.
8. Run the publish checklist and validation.
9. Update data/article-credits.json with the pass log.

For existing articles, inventory what already works before editing. Preserve useful examples, sources, reframes, and related links unless the pass note explains why they changed.

3. Prompt packs

Concept / brief pass

Model for credits: <exact name from playbook/data/authors.json>
Pass: research

Read playbook/docs/cursor-prompts.md, playbook/docs/writing-system.md sections 1-3 and 9, and playbook/docs/brief-template.md.
Create playbook/briefs/<slug>.md for <candidate>. Check whether it belongs in the catalog, how it differs from nearby bugs, and which sources support it.
Stop after the brief. Do not draft the article.

Draft a new article

Model for credits: <exact name from playbook/data/authors.json>
Pass: draft

Read playbook/docs/cursor-prompts.md, playbook/docs/writing-system.md, playbook/docs/style-guide.md, and playbook/briefs/<slug>.md.
Draft content/<slug>.php from the brief. Follow the Thinking Bugs section order. Do not invent sources, studies, DOIs, or effect sizes. Keep tone simple, practical, and non-shaming.
Update data/article-credits.json with this pass.

Improve an existing article

Model for credits: <exact name from playbook/data/authors.json>
Pass: rewrite | fact-check | voice | publish check

Read playbook/docs/cursor-prompts.md, playbook/docs/writing-system.md sections 1, 4-10, playbook/docs/style-guide.md, content/<slug>.php, data/article-credits.json, and data/article-references.json.
Inventory the current article before editing: sections, examples, sources, reframes, related links, credits, and distinctive wording. Improve the article without thinning it or changing unrelated files.
Append one pass-log entry to data/article-credits.json.

Fact-check pass

Model for credits: <exact name from playbook/data/authors.json>
Pass: fact-check

Check content/<slug>.php against playbook/docs/writing-system.md sections 5 and 10. Verify exact claims, source names, years, links, and hedges. Add verified source metadata to data/article-references.json when needed. Remove or soften unsupported claims.
Append a pass-log entry that says what changed and what was flagged.

Voice pass

Model for credits: <exact name from playbook/data/authors.json>
Pass: voice

Read content/<slug>.php cold as a reader who wants help recognizing the pattern. Remove shame, overstatement, repeated template cadence, and generic advice. Keep examples concrete and reframes realistic. Do not add new factual claims unless needed for clarity.
Append a pass-log entry.

Publish check

Model for credits: <exact name from playbook/data/authors.json>
Pass: publish check

Run playbook/docs/writing-system.md section 10. Open /playbook/made/<slug> or run the equivalent checks. Fix obvious mechanical misses only. Confirm credits and validation.
Append a pass-log entry.

4. Credit rules

The model name comes from the human's Model for credits: line. If it is missing, ask before editing article credits. Never write Cursor Agent, Thinking Bugs Editorial, or a guessed model name.

Keep old {author, at, message} rows. For new framework passes, prefer {date, pass, model, note}. The playbook receipt page understands both.