agentleFS
sanmidablesanmidable/skills/skills/raphaelsalaja/reuse/SKILL.md

reuse

Skill2 starsChanged 4 months agoMITView on GitHub

This skill sets the order for building anything new. The project's own parts come first, then a maintained library or a platform feature. Custom code comes last. A new component, style or icon that duplicates one the project already has is a finding. Adding a primitive to the shared package and then using it is not. A project with no shared package is judged on the libraries it already depends on. Cutting what nobody asked for belongs to restraint. Copying…

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Search the shared component package, the icon set and the tokens before writing UI.

    line 20
  2. Very specific:

    Use a component's variants and data-* attributes.

    line 24
  3. Very specific:

    Keep one menu, one table and one dialog shell.

    line 28
  4. Very specific:

    When a fix applies to every instance, make it inside the shared component.

    line 32
  5. Very specific:

    When the project has nothing, use a maintained library or a platform feature before custom code.

    line 36
  6. Very specific:

    Check that a library is maintained.

    line 38
  7. Very specific:

    Read a primitive's documentation before using it, and use its current APIs.

    line 42
  8. Very specific:

    Use the project's icon set at the size it was drawn for.

    line 46
  9. Distinctive:

    Every check is a pair. The broken line sits beside the line that replaces it.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

---name: reuse description: Reaches for the project's own components, then a maintained library, then a native feature, before writing new code. author: raphaelsalaja source: https://github.com/raphaelsalaja/skill homepage: https://github.com/raphaelsalaja/skill/blob/main/skills/reuse/SKILL.md

Reuse

This skill sets the order for building anything new. The project's own parts come first, then a maintained library or a platform feature. Custom code comes last.

A duplicate is a finding

A new component, style or icon that duplicates one the project already has is a finding. Adding a primitive to the shared package and then using it is not. A project with no shared package is judged on the libraries it already depends on.

Cutting what nobody asked for belongs to restraint. Copying an outside app belongs to match.

The project's parts come first

Search the shared component package, the icon set and the tokens before writing UI. Name what you found. A raw <input> beside the project's Input is reuse-house-component-first.

Shipped components stay as shipped

Use a component's variants and data-* attributes. Restyling it with a local className is reuse-no-local-restyle.

One style per kind of thing

Keep one menu, one table and one dialog shell. A second dropdown style is reuse-one-standard.

Fix it once, in the primitive

When a fix applies to every instance, make it inside the shared component. Patching five call sites is reuse-fix-in-the-primitive. Then search for every sibling, remove its local fix and list the files. Fixing only the cited line is reuse-sweep-siblings.

Then a library or the platform

When the project has nothing, use a maintained library or a platform feature before custom code. Intl formats dates and numbers. The native context menu handles right-click. A hand-written formatter is reuse-library-before-custom.

Check that a library is maintained. When it is not, port the pattern instead of installing it. That is reuse-no-stale-dependency.

Read the docs before the props

Read a primitive's documentation before using it, and use its current APIs. A guessed prop is reuse-read-the-docs.

Icons from the set, at native size

Use the project's icon set at the size it was drawn for. A generated SVG, or an 18px icon scaled to 12px, is reuse-icon-set-native-size.

The pair

Every check is a pair. The broken line sits beside the line that replaces it.

RuleBrokenReplacement
reuse-house-component-first<input className={styles.search} />The project's <Input />
reuse-no-local-restyle.menu { border-radius: 6px } beside the shared MenuMenu as shipped
reuse-one-standardThree dropdown styles on three screensOne Menu
reuse-fix-in-the-primitiveA scroll fade added at five call sitesThe fade inside ScrollArea
reuse-sweep-siblingsThe cited line fixed, its siblings leftEvery sibling fixed, files listed
reuse-library-before-customA hand-written relative date formatterIntl.RelativeTimeFormat
reuse-no-stale-dependencyAn unmaintained package installedIts pattern ported into the project
reuse-read-the-docsrender={<button />} on a trigger that is already a buttonThe prop the docs describe, or none
reuse-icon-set-native-sizeAn 18px icon at width: 12pxThe 12px icon from the set

Reporting

Severity. HIGH is a duplicate of an existing shared component, or a hand-built control a primitive covers. MEDIUM is a local restyle, an icon from outside the set or a shared fix applied at one call site. LOW is a library chosen without checking that it is maintained.

Format. One finding per root cause:

file:line - [rule-id] what is wrong

Then a Rule | Count | Severity summary. Block when any HIGH remains, Approve otherwise. Never Approve a file you did not read. Mark every check you could not run as Not verified.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.