Skip to content

Open source CapCut alternative.

TypeScript

docs: a guide edit deletes 1.5 words per word added

David Le182517aac7b5
diff --git a/AGENTS.md b/AGENTS.md
index d3a087d5..17610ee5 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -55,7 +55,7 @@ Every Cut change has to hold on every surface, and the plan for it says how:
- Never ship a known gap. Finding a case that does not work — another type, another surface, another shelf — means fixing it in the same turn, before the summary. A line explaining what still fails is the work left undone; do the work. Ask only when closing it is a scope fork or a destructive action.
- Make the decision and do it. Implement the obvious next step; never end with "if you want, I can…" or ask the user to say the word. Save questions for genuine scope forks and destructive actions.
- Update guides in `docs/guides/` only for major features or durable supported-behavior changes. Do not update guide docs for small styling tweaks, layout adjustments, copy changes, or implementation-only refactors.
-- Guide edits remove text before they add it. A change earns one or two sentences; a paragraph is a rewrite of what was there, shorter.
+- A guide edit is a net deletion, at a hard ratio: every word you add costs 1.5 words cut from what is already there. A change earns one sentence; a paragraph is a rewrite of what was there, shorter.
- Keep guides explanatory. They should teach what the system is, how it works, and which boundaries matter; do not turn guides into feature inventories, implementation logs, duplicated code, or long file lists.
- Optimize guides for readability: use plain language, short sections, and only the detail a maintainer needs to understand the supported boundary. Prefer trimming outdated or repetitive detail over adding more paragraphs.
- Keep guide source entrypoints short and readable. Do not write exhaustive file inventories. Prefer a small maintainer map by subsystem or one to seven high-signal paths, and link to a source path only when it gives someone a clear place to start.
diff --git a/CLAUDE.md b/CLAUDE.md
index d3a087d5..17610ee5 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -55,7 +55,7 @@ Every Cut change has to hold on every surface, and the plan for it says how:
- Never ship a known gap. Finding a case that does not work — another type, another surface, another shelf — means fixing it in the same turn, before the summary. A line explaining what still fails is the work left undone; do the work. Ask only when closing it is a scope fork or a destructive action.
- Make the decision and do it. Implement the obvious next step; never end with "if you want, I can…" or ask the user to say the word. Save questions for genuine scope forks and destructive actions.
- Update guides in `docs/guides/` only for major features or durable supported-behavior changes. Do not update guide docs for small styling tweaks, layout adjustments, copy changes, or implementation-only refactors.
-- Guide edits remove text before they add it. A change earns one or two sentences; a paragraph is a rewrite of what was there, shorter.
+- A guide edit is a net deletion, at a hard ratio: every word you add costs 1.5 words cut from what is already there. A change earns one sentence; a paragraph is a rewrite of what was there, shorter.
- Keep guides explanatory. They should teach what the system is, how it works, and which boundaries matter; do not turn guides into feature inventories, implementation logs, duplicated code, or long file lists.
- Optimize guides for readability: use plain language, short sections, and only the detail a maintainer needs to understand the supported boundary. Prefer trimming outdated or repetitive detail over adding more paragraphs.
- Keep guide source entrypoints short and readable. Do not write exhaustive file inventories. Prefer a small maintainer map by subsystem or one to seven high-signal paths, and link to a source path only when it gives someone a clear place to start.