Reference Contract Builder
Follow shared release-shell rules in:
postplus-sharedrelease-shell rules
Use this skill when references exist and the boundary between inspiration and copying must be explicit.
This skill is for:
- writing clean reference policies
- preventing identity copying
- deciding which references to exclude from early tests
- making later failure analysis easier
This skill is not for decoding the hook itself.
Core Rule
Every reference set should answer three questions:
- what may the model learn?
- what must not be copied?
- what references are intentionally not being used yet?
Method
Read references/contract-template.md.
Default Workflow
1. Inventory the reference set
Classify each input as:
- hook clip
- hook-first contact sheet
- style board
- product image
- persona image
- audio reference
2. Decide the test purpose
Examples:
- hook rhythm only
- camera realism
- product proof
- persona continuity
The purpose decides what references should stay out.
3. Print the contract before the final prompt
Do not bury the contract inside prose.
Failure Mode
If the prompt uses references but does not say what is intentionally excluded, the contract is incomplete.