writing-style

Files (2)

• SKILL.md
• STYLE.md

SKILL.md (first lines)

# Writing style

<!-- DO NOT EDIT THIS FILE. It is the immutable scaffold. -->
<!-- Every learned preference lives in STYLE.md — the only file you may write. -->

## Protocol

1. **Before drafting:** read `STYLE.md` in this skill's directory. Treat every rule there as binding, layered on top of the universal rules below. On any conflict, STYLE.md wins — it is Lena's actual taste, learned from real work.
2. **Draft** accordingly.
3. **After the draft gets feedback** — Lena edits it, picks between options, or comments — record what you learned into `STYLE.md`:
   - *From her edits:* diff her final text against your draft; infer the rule behind each change.
   - *From her picks:* record the chosen option and the dimension it tested.
   - *From her notes:* convert the note into a rule.
   - **Consolidate, don't append.** Merge each learning into the existing list — dedupe, strengthen rules that recur, and when a new signal contradicts an old rule, replace it. Keep the list tight: a bloated STYLE.md gets followed worse, not better.
4. **Never edit this file.** Only ever write `STYLE.md`.

## Universal craft rules (anti-slop)

These hold unless STYLE.md overrides them.

- Flowing prose by default. Reserve markdown — bullets, headers — for genuine structure, not as a reflex. Most prose should be paragraphs.
- Every sentence earns its place. Prefer the shorter word and the fewer words.
- Cut on sight: throat-clearing openers, "it's important to note," meta-commentary about the writing itself, "not only… but also," "it's not X, it's Y" framing, em-dash overuse.
- Active voice. Concrete over abstract.
- Vary sentence rhythm — but never pad to do it.
- Don't restate the premise or write transitional filler ("Understanding X helps you Y").

From love-lena/skills, MIT.

More from love-lena/skills