comparer
Compares an old and a new version of one Recursica knowledge file and lists every rule the new version lost, narrowed, widened, made stronger, made weaker or added. Dispatched by Edie after each rewrite. Reads only and never edits, so no edit can remove a finding before a person sees the finding.
- License 许可
- MIT
- 最近更新
- 2026-11-09
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- comparer
- tools
- Read, Grep, Glob
- targets
- claude-code
- description
- Compares an old and a new version of one Recursica knowledge file and lists every rule the new version lost, narrowed, widened, made stronger, made weaker or added. Dispatched by Edie after each rewrite. Reads only and never edits, so no edit can remove a finding before a person sees the finding.
02 资源文件 1
- 参考文档platform/session.md176 B
03 SKILL.md 正文
<!-- platform:role-line -->
Find every rule that changed between the old version and the new version of one file. The input is the two versions of the file. A change in wording is expected and is not a finding.
What counts as a rule
A rule is any requirement, prohibition, number, threshold, example, reason, open question or checklist item.
How to compare
- Read both versions in full.
- List every rule in the old version.
- For each rule, find the sentence in the new version that states the same rule, and quote the new sentence. When no sentence in the new version states the rule, the rule is lost.
- Compare the strength of each rule in the two versions. "Must", "never", "only" and a plain instruction are equally strong. "Should" is weaker than "must".
- Compare the scope of each rule. The scope is the set of cases the rule covers. A rule that covers fewer cases in the new version is narrowed. A rule that covers more cases in the new version is widened. For example, "goes somewhere" changed to "opens a different page" narrows the rule, because the new wording leaves out a change of URL on the same page.
- Read the new version for rules the old version did not have.
Report
Report four lists. Every item in a list quotes the old text, the new text, or both.
- Lost
- Narrowed or widened
- Stronger or weaker
- Added
Write "None" under an empty list. Comment on rules only, never on style.
04 同仓库更多 Skills
recursica-skill-template
Replace with a description of the skill and its purpose.
recursica-skill-working-memory
The research behind Recursica's item-count limits, with citations — Miller's 7 ± 2, Cowan's 4, chunking, and recognition versus recall. Use when a decision turns on how many options, navigation items, or chips to show at once, or to justify or challenge a count. Not for choosing a control — see recursica-skill-selection-controls.
recursica-skill-discoverability
The research behind Recursica's rule that rarely needed settings get a real but unpromoted entry point — the paradox of the active user, satisficing (settling for the first method that is good enough), and progressive disclosure, with citations. Use when deciding whether to hide, promote, or build a configuration or customization feature, or to justify that choice. Not for item counts — see recursica-skill-working-memory.
recursica-skill-design-router
Start here for any Recursica screen work. The router says what to decide in what order, which skill owns each decision, which rule wins when two rules conflict, and when to confirm with the user instead of guessing. Load the router first to design, build, review, or refactor a screen, page, panel, or flow, or when rules seem to disagree or no rule applies. The router routes, and the owning skill holds the rules.
recursica-skill-undo
House rules for undo — when an action gets an undo instead of a confirmation, where the undo goes (on the page, in place, or in a toast), when a toast is needed at all, and the Undo button's accessible name. Use whenever an action can be reversed, or when choosing between an undo and a confirmation. Not for building the toast that holds an Undo button — see recursica-skill-toast. Not for the confirmation modal — see recursica-skill-buttons-links.
recursica-skill-typography-semantics
House rules for type and semantic markup — real elements instead of styled divs, one H1 per page, type styles from tokens only, loading the brand typefaces, hidden headings, emphasis with em and strong, abbreviations, and AP style. Use for headings, body copy, emphasis, and the markup under a visual hierarchy. Not for naming — see recursica-skill-names-and-terms.