with one click
writer-memory
Writing style memory — stores voice/tone preferences
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Writing style memory — stores voice/tone preferences
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Diagnose and fix build/CI failures automatically
Concurrent code generation via multi-model picker
UI/UX design and frontend component generation
OMP self-improvement — analyse own skills/agents and propose improvements
Visual diff/screenshot comparison verdict
Clone and adapt a web page/design to the codebase
| name | writer-memory |
| description | Writing style memory — stores voice/tone preferences |
| trigger | writer-memory:, /writer-memory, /omp:writer-memory |
| autoinvoke | false |
| Field | Value |
|---|---|
| ID | writer-memory |
| Keywords | writer-memory:, /writer-memory |
| Tier | Memory Tool |
| Source | src/skills/writer-memory.mts |
Stores and retrieves writing style preferences, voice, and tone guidelines in .omp/writer-memory.md. Use omp writer-memory <style-note> to append a new style note, or omp writer-memory (no args) to print the current style guide. These preferences persist across sessions and are available to writer and document-specialist agents.
interface SkillInput { trigger: string; args: string[]; }
interface SkillOutput { status: "ok" | "error"; message: string; }
export async function activate(input: SkillInput): Promise<SkillOutput>
export function deactivate(): void
Real CLI logic: omp writer-memory <style-note> appends the note to .omp/writer-memory.md. omp writer-memory prints the current file content. Extension-side reads and injects the style guide into the agent context.
Note: Concurrent appends from multiple Copilot sessions are safe for entries ≤ 4KB (POSIX
O_APPENDatomicity), but may interleave for larger entries. Single-session usage is fully safe.
P3 scope: Full character/relationship/scene/theme tracking (as specified in SPEC-omp-2.0 §3) is deferred to P3. The current implementation provides voice/tone preference storage only.