We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

• 0

  Common

  Most of the 133 edited versions we read keep these.

• 0

  Distinctive

  This author's own choices. Worth a look.

• 3

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Rebuild the SDK: after any change under sdk/ or third-party/.

   line 12
2. Very specific:

   Windows: check the prerequisites in notes/build.md first (symlink rights, long paths, short Hexagon toolchain path).

   line 13
3. Very specific:

   After building, verify the binary you run is the one you built (see the geniex skill: an installed CLI on PATH can shadow it).

   line 16

“Common” is measured: kept by at least 6 in 10 of the 133 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

• Other versions146 projects use a version of this.

  Word for word · 0

  None found.

  Edited · 0

  None found.

  Wrote their own version · 146

  1. FalkorDB/FalkorDB★ 11ksame name
  2. microsoft/microsoft-ui-xaml★ 8.6ksame name
  3. hathach/tinyusb★ 7.2ksame name
  4. parcadei/Continuous-Claude★ 3.9ksame name
  5. parcadei/Continuous-Claude-v2★ 3.9ksame name
  6. parcadei/Continuous-Claude-v3★ 3.9ksame name
  7. pytorch/TensorRT★ 3ksame name
  8. oxsecurity/megalinter★ 2.6ksame name
  9. iPlug2/iPlug2★ 2.4ksame name
  10. clice-io/clice★ 1.4ksame name

  136 more not listed

  How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

• Used alongsideProjects with it also use backprop, finances and 10 more.

  Other files people use alongside this one.

  How we pick theseFiles found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • GerardoRdz96Skill

    finances

    Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".

    Also in 3 projects that use this

  • cpiprintSkill

    favicon

    Generate favicons from a source image

    Also in 3 projects that use this

  • madeehahassanSkill

    Go-Live

    Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.

    Also in 3 projects that use this

  • TrevokeSkill

    define

    Use when a new feature request, bug report, or work request needs requirements defined before implementation

    Also in 3 projects that use this

  • JuliusBrusseeSkill

    deepen

    Optional design-improvement pass for when you have spare usage to drain. Finds the shallowest modules in the code the spec touches, researches a deeper design, and proposes refactors that shrink interfaces and hide decisions — behavior held constant, tests green before and after. Proposes §I/§V/§T edits, never silent rewrites. Triggers when the user says "deepen this", "improve the design", "this module feels shallow", "pull complexity down", "use spare budget on the codebase", or invokes /ck:deepen. Leans on the codebase-design skill's deep-module vocabulary when present.

    Also in 3 projects that use this

• In this repository3 other files it gives its agents.

  • CLAUDE.mdCLAUDE.md
  • geniexSkill
  • releaseSkill