Purpose
Prompts that work, written down once.
Patterns
Role + task + constraints + output format. "You are reviewing a Revit add-in for transaction safety. List each issue with file:line and a fix. Markdown table."
Give examples — one good and one bad example beats three paragraphs of description.
Ask for the plan before the code on anything over a few files.
Make it verify — "run the tests, then summarize what changed and what's untested."
Say what not to do — "don't add dependencies", "don't touch migrations".
Library
Reusable prompts live in [TEAM: org]/prompts as Markdown, and as Claude Code slash commands (.claude/commands/*.md) in repos where they apply. Current set:
/review-pr— checklist review per 03.05/write-migration— Supabase migration with RLS scaffold per 09.03 / 08.03/rhino-tool— scaffold a RhinoPython tool per 10.03/wiki-page— draft a page in the wiki template[TEAM: add]
Owner: Matt · Last reviewed: 2026-09