26 lines
1.2 KiB
Markdown
26 lines
1.2 KiB
Markdown
# Source Priority
|
|
|
|
Use the closest source type first. Do not average all examples together.
|
|
|
|
Priority by task:
|
|
|
|
- Agent instructions: use `EXAMPLES/spec-direction` first, then `technical-review`, then `debugging-help`.
|
|
- Code/architecture criticism: use `EXAMPLES/technical-review` first, then `ANTI_STYLE.md`.
|
|
- Bug reports and operational debugging: use `EXAMPLES/debugging-help` first.
|
|
- Short product/design takes: use `EXAMPLES/casual-opinion` first.
|
|
- Company updates and Popdog-style roundups: use `EXAMPLES/formal-public` first, especially roundup bullets.
|
|
- Blog posts and public arguments: use `EXAMPLES/formal-public` first, especially blunt thesis and conversational explainer examples.
|
|
|
|
Conflict rules:
|
|
|
|
- Curated examples beat generated held-out examples.
|
|
- Mode files beat global rules when the task clearly belongs to that mode.
|
|
- `PRESERVE_DRAFT.md` beats everything when the user supplies a rough draft.
|
|
- `ANTI_STYLE.md` beats positive style rules when a sentence sounds AI/corporate.
|
|
- Do not copy slang, swearing, or irritation into text unless the draft already has it or the context clearly supports it.
|
|
|
|
Evidence quality:
|
|
|
|
- High: spec-direction, technical-review, casual-opinion, debugging-help.
|
|
- Medium: formal-public.
|