product-demo-director
CLAUDE.md38 starsChanged 4 months agoMITView on GitHub
Treat AGENTS.md as the canonical repository contract. Follow it for both production work and code changes; do not duplicate or weaken its rules here. - For a request to create, recut, capture, render, or judge a demo, read SKILL.md completely before editing files or running provider-backed stages. - Read only the task-relevant production references named in AGENTS.md. - Inspect existing product evidence before proposing a story. Ask a focused question only when the audience, intended change, or required evidence cannot…
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- product-demo-directorSkill
The file
We split this CLAUDE.md into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Treat AGENTS.md as the canonical repository contract.
- Distinctive: line 12
Read only the task-relevant production references named in AGENTS.md.
- Very specific: line 15
Keep new working projects under projects/<slug>/ so footage, narration, renders, and QA outputs remain local and ignored.
- Very specific: line 17
Prefer the ./pdd commands in AGENTS.md.
- Distinctive: line 19
Do not invoke paid providers, capture authenticated pages, or render media merely to explore the repository.
- Distinctive: line 28
Never paste provider keys into chat or shell history.
- Distinctive: line 31
Do not declare a film complete from a visual impression or model score.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Code instructions
@AGENTS.md
Treat AGENTS.md as the canonical repository contract. Follow it for both production work and code
changes; do not duplicate or weaken its rules here.
Starting a task
- For a request to create, recut, capture, render, or judge a demo, read
SKILL.mdcompletely before editing files or running provider-backed stages. - Read only the task-relevant production references named in
AGENTS.md. - Inspect existing product evidence before proposing a story. Ask a focused question only when the audience, intended change, or required evidence cannot be discovered safely.
- Keep new working projects under
projects/<slug>/so footage, narration, renders, and QA outputs remain local and ignored. - Prefer the
./pddcommands inAGENTS.md. Use individualtools/*.pystages when diagnosing or intentionally controlling one stage of the documented pipeline. - Do not invoke paid providers, capture authenticated pages, or render media merely to explore the repository. Run those stages only when the user's requested production requires them.
Claude-specific behavior
- This root file loads automatically in Claude Code. Use
/memoryif you need to verify which instruction files are active. ./pdd install-skill --target claudeis optional and only needed to expose Product Demo Director while Claude works from another repository. Do not install it without the user's request.- Never paste provider keys into chat or shell history. Read local configuration through the documented environment variables without printing values; verify a required key exists before a provider-backed stage.
- Do not declare a film complete from a visual impression or model score. Report the exact final
media path and the deterministic preflight/QA result required by
AGENTS.md.
For a typical launch request, interpret “make a demo” as: inspect evidence, identify one meaningful change, author a source-bound single-focus story, capture missing states, synthesize or stage narration, pace cuts between thoughts, render, finish, run strict QA, and then optionally judge.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

