Use cases
Configure outline + @system to match how you work.
Fiction / long-form narrative
Novel/
├── @system/
│ ├── style.md
│ ├── characters.md
│ ├── world.md
│ └── outline.md
├── vol1/
│ ├── 01-opening.md
│ └── ...
└── appendix/Put voice, cast, and world rules in @system so the Writing Agent stays consistent.
Academic writing
- One file per chapter or major section
- Use heading levels consistent with your school/style guide
- Keep citations, definitions, and notation in
@systemor dedicated files - Use Review Agent for logic and terminology passes
See also: Showcases — academic.
Technical documentation
- Mirror your product map: Overview → Setup → API → FAQ
@systemfor terminology, code style, and audience level- Export Markdown ZIP for Git/GitHub; see Export
See: Showcases — tech docs.
Creative shorts / columns
- Lighter
@system(tone + taboos) - Smaller file granularity for faster AI diffs
Marketing / long-form web
- Separate facts (sources in
@webor references) from draft - Review stage for claims and compliance
Next steps
- Template creation
- Pricing for AI usage