Prompt Patterns¶
This repository maintains reusable prompts for common tasks, so agents (and humans directing them) don't reinvent the same instructions each time.
Where prompts live¶
prompts/— company-level reusable prompts. Seeprompts/README.mdfor the index.ventures/digital-products/prompts/— Digital Products venture-specific prompts. Seeventures/digital-products/prompts/README.md.- Other ventures may maintain their own
prompts/directory following the same convention. .claude/commands/— tool-specific (Claude Code) slash-command definitions, which may wrap or reference the reusable prompts above.
How to use them¶
Before writing a one-off prompt for a recurring kind of task (e.g. "draft a product specification,"
"run a research pass with evidence classification"), check whether an existing reusable prompt
already covers it. Reuse and adapt rather than rewriting from scratch — this keeps outputs
consistent with the standards referenced throughout docs/governance/ and docs/ai/.
Relationship to this directory¶
Prompts are operational tooling, not policy. If a prompt seems to encode a rule that belongs in
docs/governance/ or docs/ai/ (e.g. a new mandatory check), that rule should live in the
appropriate governance/AI document and the prompt should reference it — not the other way around.
See prohibited-behaviors.md, item 21, on avoiding scattered, drifting
copies of the same rule.