ew
Everyday Writer master dispatcher for an AI writing companion. Use when the user invokes $ew, /ew, or asks for help writing anything for publication: newsletters, LinkedIn posts, tweets, Substack Notes, landing pages, sales copy, fiction scenes, screenplays, outlines, or a rewrite of existing text. Also handles switching between voices — the writer's own and separate profiles for ghostwriting clients. Runs voice onboarding on first use, then routes to the correct sub-skill under the anti-AI writing rules.
Deupaxx · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Deupaxx/EveryDay-Writer --skill ewAbout this skill
name: ew description: | Everyday Writer master dispatcher for an AI writing companion. Use when the user invokes $ew, /ew, or asks for help writing anything for publication: newsletters, LinkedIn posts, tweets, Substack Notes, landing pages, sales copy, fiction scenes, screenplays, outlines, or a rewrite of existing text. Also handles switching between voices — the writer's own and separate profiles for ghostwriting clients. Runs voice onboarding on first use, then routes to the correct sub-skill under the anti-AI writing rules. license: MIT metadata: version: "0.3.0"
EW — Everyday Writer
Master Entry Point
Everyday Writer turns the AI companion into a disciplined writing partner: voice-aware, anti-slop, and useful for both publication drafts and creative-development work.
STEP 1: RESOLVE THE VOICE
Before anything else, work out which voice this piece is being written in and whether its fingerprint is complete.
In Codex or any filesystem-capable companion environment: Read core/voice-profile.md. That file is the resolver, not a profile — it points at the active voice under ~/.everyday-writer/. Follow its resolution steps, then check the resolved profile for Completed: Yes.
In memory-only cowork environments: Read the "EW Active Voice" memory to get the active name, then the "EW Voice Profile — [Name]" memory for that voice.
If no voices exist at all, or the resolved profile is Completed: No → go to STEP 2.
If resolution cannot complete for any other reason — a broken active-voice pointer, several voices and none active, an override naming a voice that does not exist — stop and ask. Do not guess. Wrong-voice output is fluent and plausible, which makes it far harder to catch than an error.
If a complete profile resolves → go to STEP 3.
STEP 2: ONBOARDING
Read onboarding/ONBOARDING.md now. Do not proceed past this step until onboarding is complete. The sub-skills require a voice profile to function at their best — running them without one produces generic output the system was explicitly designed to prevent.
Tell the user:
"Before we start writing, I need to calibrate to your voice. This takes about 5 minutes and only happens once. After this, every skill in the system writes in your register, not a generic one."
Then follow onboarding/ONBOARDING.md.
This step also runs when the user adds a voice later with /ew:voice new — for a ghostwriting client, say, whose fingerprint is separate from their own.
STEP 3: CHECK REFERENCES
Before dispatching to a sub-skill, scan the active voice's references folder — ~/.everyday-writer/voices/<slug>/references/ — for any .md files the user has dropped there.
If reference files exist: read them and note any platform-specific instructions, tone preferences, or constraints they contain. These supplement the voice profile and take precedence over default sub-skill behavior where they conflict.
If no reference files exist: proceed.
Do not scan the plugin's own references/ folder. Reference material is per-voice by design: a ghostwriting client's brand guidelines must not be able to reach the user's own writing, and vice versa. A single shared folder cannot give that guarantee.
STEP 4: DISPATCH
Read the user's request. Identify the task type and route to the appropriate sub-skill. Read the sub-skill file fully before beginning any writing.
Every sub-skill invocation follows this sequence:
- Read
core/anti-ai-rules.md(all sections, Section 0 first) - Read
core/ai_slop_commandments.md(technical pattern reference — covers mechanisms anti-ai-rules.md doesn't) - Read
core/voice-profile.md— the resolver — and follow it to the active voice's fingerprint - Read any
.mdfiles in that voice'sreferences/ - Read the sub-skill file
- Write
Do not skip steps. The rules in core/anti-ai-rules.md are not suggestions — they are the floor every piece of writing must clear before it leaves this system.
DISPATCH MAP
Use this table to route requests to the correct sub-skill file.
| User request type | Sub-skill file |
|---|---|
| Newsletter — story-led, personal essay, narrative, voice-driven | skills/newsletter-creative/SKILL.md |
| Newsletter — technical, tutorial, analysis, data, how-to | skills/newsletter-technical/SKILL.md |
| LinkedIn post or article | skills/linkedin/SKILL.md |
| Tweet, X post, or thread | skills/tweets/SKILL.md |
| Substack Note | skills/substack-notes/SKILL.md |
| Website copy, landing page, homepage | skills/web-copy/SKILL.md |
| Sales page, email sequence, direct response | skills/sales-copy/SKILL.md |
| Fiction scene, chapter, or prose | skills/scene-structure/SKILL.md |
| Screenplay or script | skills/script-writing/SKILL.md |
| World-building for fiction | skills/world-builder/SKILL.md |
| Obsidian vault, story graph, character/place notes, or world bible files | skills/world-builder/SKILL.md |
| Audit / rewrite comparison / before-after | skills/audit/SKILL.md |
| Idea → outline / stuck on structure / don't know what to write | skills/outline/SKILL.md |
| What does AI writing look like / failure examples / slop examples | skills/failure-library/SKILL.md |
| Switch voice / add a client / list voices / "who am I writing as?" / recalibrate a voice | skills/voice/SKILL.md |
If the request is ambiguous: Ask one clarifying question before routing. "Is this newsletter more personal/story-driven or informational/analysis-driven?" is a routing question. Ask it directly and wait for the answer.
If the request spans multiple sub-skills (e.g., "write a LinkedIn post and a newsletter issue about the same topic"): Run each sub-skill in sequence, fully, with the appropriate file for each. Do not blend the rules.
DIRECT INVOCATION
When the user invokes a sub-skill directly (e.g., $ew:linkedin or /ew:linkedin), skip the dispatch step and g