Open source CapCut alternative.
TypeScript
chore: point the agent rules at the writing style guide
David Le0c78bd0ffe75
diff --git a/AGENTS.md b/AGENTS.mdindex f384acc2..181e6953 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -46,7 +46,7 @@ Every Cut change has to hold on all four surfaces, and the plan for it says how:- Do not touch repository-root `prototype/` unless the user explicitly asks for that filesystem path. By default, assume requested product changes are for the Mac app or the site/landing page.- Ask before creating any new plan document.- Code reviews run on the latest Opus model; fixes and implementation run on the latest Fable model. Make the switch yourself: a review request (`/review`, "review this") runs in the `code-reviewer` agent (`.claude/agents/code-reviewer.md`, which pins `model: opus`) whatever the session model is, and a fix runs on Fable, spawned in an agent with `model: "fable"` when the session is on something else. A forked skill runs on the session model, so a review never goes through a fork. Never ask the user to `/model`.-- All writing follows `docs/guides/writing-style.md`: docs, guides, articles and blog posts, landing page and marketing copy, release notes, emails, UI copy, commit messages, code comments, and chat replies. The voice is a thoughtful engineer explaining what they learned while building real software: conversational, calm, precise, why before what, concrete examples, starting from a real problem. Engineering docs under `docs/` also follow the structure in `docs/guides/eng-doc-style.md`.+- All writing follows `docs/guides/writing-style.md` exactly, for documentation, marketing, and every other writing surface. Read it before writing. Engineering docs under `docs/` also follow the structure in `docs/guides/eng-doc-style.md`.- Write straight up — in prompts, docs, commits, code comments, summaries, and UI copy. State what a thing is, once, and stop. Never frame it against what it is not: no "X, not Y", no "X rather than Y", no "instead of Z", no "…, which is exactly what not to do". Cut filler.- Keep replies short and action-oriented. For implementation questions, give the recommendation first, then one to three short bullets on why; when the answer is obvious, just say what to do. Skip long explanations, caveats, and "one last thing" sections; flag a real blocker or risk with "One issue:" and explain it briefly.- Never dress a fact up as an aside. No "worth knowing", "worth flagging", "worth calling out", "one thing to note", "for future reference", "the part that matters here" — and no other phrase that announces information as bonus insight. This holds anywhere in a reply, not just at the end. If it matters, state it plainly as part of the work; if it does not, cut it. A problem gets fixed in the same turn it is found, and anything that changes what the user does belongs in the body of the summary, said once.diff --git a/CLAUDE.md b/CLAUDE.mdindex f384acc2..181e6953 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -46,7 +46,7 @@ Every Cut change has to hold on all four surfaces, and the plan for it says how:- Do not touch repository-root `prototype/` unless the user explicitly asks for that filesystem path. By default, assume requested product changes are for the Mac app or the site/landing page.- Ask before creating any new plan document.- Code reviews run on the latest Opus model; fixes and implementation run on the latest Fable model. Make the switch yourself: a review request (`/review`, "review this") runs in the `code-reviewer` agent (`.claude/agents/code-reviewer.md`, which pins `model: opus`) whatever the session model is, and a fix runs on Fable, spawned in an agent with `model: "fable"` when the session is on something else. A forked skill runs on the session model, so a review never goes through a fork. Never ask the user to `/model`.-- All writing follows `docs/guides/writing-style.md`: docs, guides, articles and blog posts, landing page and marketing copy, release notes, emails, UI copy, commit messages, code comments, and chat replies. The voice is a thoughtful engineer explaining what they learned while building real software: conversational, calm, precise, why before what, concrete examples, starting from a real problem. Engineering docs under `docs/` also follow the structure in `docs/guides/eng-doc-style.md`.+- All writing follows `docs/guides/writing-style.md` exactly, for documentation, marketing, and every other writing surface. Read it before writing. Engineering docs under `docs/` also follow the structure in `docs/guides/eng-doc-style.md`.- Write straight up — in prompts, docs, commits, code comments, summaries, and UI copy. State what a thing is, once, and stop. Never frame it against what it is not: no "X, not Y", no "X rather than Y", no "instead of Z", no "…, which is exactly what not to do". Cut filler.- Keep replies short and action-oriented. For implementation questions, give the recommendation first, then one to three short bullets on why; when the answer is obvious, just say what to do. Skip long explanations, caveats, and "one last thing" sections; flag a real blocker or risk with "One issue:" and explain it briefly.- Never dress a fact up as an aside. No "worth knowing", "worth flagging", "worth calling out", "one thing to note", "for future reference", "the part that matters here" — and no other phrase that announces information as bonus insight. This holds anywhere in a reply, not just at the end. If it matters, state it plainly as part of the work; if it does not, cut it. A problem gets fixed in the same turn it is found, and anything that changes what the user does belongs in the body of the summary, said once.