# AI use cases for Sepia (Nanako0129/sepia) Repo: [Nanako0129/sepia](https://github.com/Nanako0129/sepia) | Use cases: 5 | Page: https://dedupedai.com/use-cases/nanako0129-sepia/ sepia is a portable Agent Skill that de-AI-fies writing, repairing narrative structure in fiction and applying venue-matched rules to professional documents. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Repair a story draft's narrative structure in Claude Code: https://dedupedai.com/use-cases/nanako0129-sepia/repair-fiction-narrative-structure/ - Check release notes and PR replies against venue rules: https://dedupedai.com/use-cases/nanako0129-sepia/review-release-notes-venue-rules/ - Draft a blameless postmortem with the Codex plugin: https://dedupedai.com/use-cases/nanako0129-sepia/write-postmortem-with-codex/ - Rebuild a rough draft from its facts and intent: https://dedupedai.com/use-cases/nanako0129-sepia/recreate-draft-from-facts-and-intent/ - Write or revise fiction with the Hemingway voice profile: https://dedupedai.com/use-cases/nanako0129-sepia/write-fiction-in-hemingway-voice/ ## How to repair a story draft's narrative structure in Claude Code with Sepia Repo: [Nanako0129/sepia](https://github.com/Nanako0129/sepia) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Diagnose and minimally fix AI tells in a story's architecture before touching word choice. **Who it is for:** A fiction writer with a finished chapter who suspects it reads as AI-generated and wants targeted edits. **The problem:** Surface-level humanizers rewrite word choice but leave the architecture that detectors key on, such as a narrator who explains the theme. **The outcome:** A diagnosis of structural tells followed by minimal in-place edits that leave the rest of the chapter alone. ### Steps 1. Install the complete Sepia plugin package for Claude Code, not the bare skill file. 2. Use the install route described under Install in the README to add the plugin. (inferred, check the README) 3. Run `/sepia-review` on the chapter to get a diagnosis without any edits. 4. Run `/sepia-refactor` on the same chapter to make minimal in-place edits. 5. Read the diff and keep only the edits that change structure you want changed. ### Prompt to paste into your agent ```text Using the sepia repo, run its review operation on and then its refactor operation with minimal edits. Expected output: a list of structural diagnoses followed by an edited copy of the file. Verify that no narrator states the theme outright and that the plot's causal chain is still intact. ``` ### Caveat The README describes the plugin install route in its Install section, which was truncated in the source, so the exact install steps must be taken from the full README. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nanako0129-sepia/repair-fiction-narrative-structure/ ## How to check release notes and PR replies against venue rules with Sepia Repo: [Nanako0129/sepia](https://github.com/Nanako0129/sepia) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Review a professional draft against the rules for its document type before publishing. **Who it is for:** A maintainer about to publish release notes, a blog post, or replies to contributors on a pull request. **The problem:** Professional drafts pick up filler, marketing inflation, and reflex praise that carry no information. **The outcome:** A diagnosis that flags venue mismatches, such as missing user impact or unsupported claims, without rewriting the draft. ### Steps 1. Install the Sepia plugin package or load the skill in an Agent Skills-compatible agent. 2. Run the review operation on the draft, such as `/sepia-review` in Claude Code. 3. Check each flag against the domain rule for the document type, such as user impact first for release notes. 4. Run the refactor operation to fix only the flagged lines. 5. Confirm that every number and artifact the draft cites still matches its source. ### Prompt to paste into your agent ```text Using the sepia repo, run its review operation on as release notes. Expected output: a diagnosis that names each venue mismatch with its line. Verify that every number in the diagnosis matches the source notes. ``` ### Caveat The professional rules come from the studies digested in the research folder, and the README describes the professional structure finding as drawn from a preprint whose features are LLM-scored. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nanako0129-sepia/review-release-notes-venue-rules/ ## How to draft a blameless postmortem with the Codex plugin with Sepia Repo: [Nanako0129/sepia](https://github.com/Nanako0129/sepia) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Write a postmortem that names mechanisms, timestamps, and owned action items. **Who it is for:** An engineer on call who must write an incident postmortem from timeline notes and wants the venue rules applied. **The problem:** Postmortem drafts often blame people, skip dead ends, or leave action items unowned. **The outcome:** A first draft that is blameless toward people, direct about mechanisms, and lists timestamps and owned action items. ### Steps 1. Install the complete Sepia plugin package for Codex. 2. Use the install route described under Install in the README to add the plugin. (inferred, check the README) 3. Run `$sepia-write` with the incident timeline and the postmortem brief as input. 4. Run `$sepia-review` on the result to check it against the postmortem rules. 5. Add owners and dates to any action item the review flags as unowned. ### Prompt to paste into your agent ```text Using the sepia repo, run its write operation to draft a postmortem from . Expected output: a postmortem with timestamps, dead ends, and owned action items. Verify that every timestamp matches the timeline notes. ``` ### Caveat The postmortem rules are one domain in the professional rule set, and the README gives no example postmortem to check output against. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nanako0129-sepia/write-postmortem-with-codex/ ## How to rebuild a rough draft from its facts and intent with Sepia Repo: [Nanako0129/sepia](https://github.com/Nanako0129/sepia) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Rewrite a flat draft from its source facts and stated purpose instead of editing it. **Who it is for:** A writer or team member whose AI-generated draft is so stiff that editing it line by line would take longer than starting over. **The problem:** Line-level edits keep the skeleton of the original draft, including its structure. **The outcome:** A full rewrite that keeps the facts and intent of the source and drops the original skeleton. ### Steps 1. Install the Sepia plugin package or load the skill in an Agent Skills-compatible agent. 2. Collect the source facts and the intent of the piece in one file. 3. Run the recreate operation, such as `/sepia-recreate` in Claude Code, on that file. 4. Compare the result against the source facts and fix any mismatch by hand. 5. Run the review operation on the result as a final check. ### Prompt to paste into your agent ```text Using the sepia repo, run its recreate operation on . Expected output: a full rewrite that keeps only the facts and intent from the source. Verify that every number and name in the rewrite appears in the source file. ``` ### Caveat Recreate rewrites from the source facts, so any fact missing from the source file will be missing from the output. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nanako0129-sepia/recreate-draft-from-facts-and-intent/ ## How to write or revise fiction with the Hemingway voice profile with Sepia Repo: [Nanako0129/sepia](https://github.com/Nanako0129/sepia) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Apply the built-in Hemingway voice to a story with an opt-in direct entry. **Who it is for:** A fiction writer who wants a spare, omission-driven style on a new scene or a revision. **The problem:** Generic de-AI passes do not give a fiction draft a distinct voice to follow. **The outcome:** A scene or revision written under the Hemingway profile, with Sepia stating the profile and how to decline it. ### Steps 1. Install the complete Sepia plugin package for your agent. 2. Run `/sepia-hemingway` on the scene or draft, or `$sepia-hemingway` in Codex. 3. Read the profile notice Sepia prints and decline it if you did not want the voice applied. 4. Run the review operation to see the voice's known costs that Sepia reports. 5. Keep the moves you want and revert the rest by hand. ### Prompt to paste into your agent ```text Using the sepia repo, run its hemingway operation on . Expected output: the scene with the Hemingway voice applied and a review of the profile's known costs. Verify that the story's facts and character names are unchanged. ``` ### Caveat The voice-skills interface rests on one blind review experiment that the README calls a worked example rather than measured evidence. Risk, voice cloning: The profile imitates a named author's published style, so use it as a technique and do not present the output as that author's writing. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nanako0129-sepia/write-fiction-in-hemingway-voice/