mcpField
R
reuse

reuse

github.com/raphaelsalajaDevelopment5362 installsUpdated today
Repository

About reuse

reuse is a skill that sets reuse as the first consideration when building UI, for developers maintaining project components and styles. It directs them to check existing components, icons, and tokens before maintained libraries or platform features, with custom code as a last resort.

Key features

  1. 01Search shared project components first
  2. 02Use shipped component variants and attributes
  3. 03Standardize patterns for the same UI element
  4. 04Fix issues in shared primitives
  5. 05Prefer maintained libraries or platform features
  6. 06Follow documentation for current APIs

Use cases

  1. 01Finding reusable components before building UI
  2. 02Avoiding multiple styles for the same control
  3. 03Consolidating repeated fixes in shared components
  4. 04Replacing custom formatters or icons

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/raphaelsalaja/skills --skill reuse

After installing, type/reusein Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

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.

Comments

Markdown supported