agentleFS
VercelKnown publishervercel-labs/ui/.agents/skills/ui-sdk-unslop/SKILL.md

ui-sdk-unslop

Skill4.8k starsChanged 18 days agoApache-2.0View on GitHub

Removes generated-looking code from a ui-sdk diff or files, like comments that restate the code, filler JSDoc, defensive checks for impossible cases, one-caller helpers and vague names, without changing behavior. Use as the last step of any change, or when asked to clean up, trim comments or remove slop.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 23 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the vercel-labs/ui repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about vercel-labs/ui

The biggest 5 of 23 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 23

Talked about on GitHub and Bluesky (23 times).

On GitHub · 17

12 more on GitHub

On Bluesky · 6

1 more on Bluesky

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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. Distinctive:

    A comment that says what the next line does: Delete it. If the line isn't clear without it, rename something.

    line 16
  2. Distinctive:

    Logs, probes and commented-out code: Delete them.

    line 65
  3. Very specific:

    In examples, any comment at all: Only tool directives stay (svelte-ignore, eslint-disable, @__PURE__).

    line 67
  4. Very specific:

    Run pnpm lint, pnpm format, pnpm typecheck and the unit tests for the packages you touched.

    line 79
  5. Distinctive:

    Delete each comment left in the diff and reread the code.

    line 80
  6. Distinctive:

    Read the diff once more. Revert any change that doesn't make the code easier to read.

    line 81
  7. Very specific:

    If one pattern showed up in three or more files, propose a lint rule for it in scripts/check-code.mjs or scripts/check-comments.mjs.

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Unslop

Scope is the diff (git diff against the base) unless you're given files. Behavior never changes: the same tests pass before and after, and nothing public is renamed.

What goes

Each pattern, with what replaces it.

A comment that says what the next line does. Delete it. If the line isn't clear without it, rename something.

// Close the popup when Escape is pressed.
if (event.key === "Escape") close()

A comment on every declaration. Most constants, fields and functions need none: the name and the type say what they are. Delete each one that doesn't stop a reader from getting the code wrong.

A comment that explains the design. What a value holds, where it's kept, which attribute it lands on, who reads it. The code says that. Keep the one fact it can't show, in a line, or delete the comment.

// Before
// The site's color scheme, shown on <html> as `data-color-scheme`, which the
// stylesheet's colors follow. It's kept under "theme", the key the site used
// before, so readers keep what they chose.
const colorScheme = createColorScheme({
  storage: createLocalStorage("theme"),
  global: true,
})

// After
// "theme" is the key the site used before, so readers keep their choice.
const colorScheme = createColorScheme({
  storage: createLocalStorage("theme"),
  global: true,
})

A comment longer than three lines. Cut it to the reason. An explanation that needs more goes in the docs page, a test title or contributing/. pnpm lint flags it (comment-length).

A comment that narrates history or the task. "Now we", "Updated to", "Fixed the bug where", "As requested". Delete it. Git holds the history.

A section banner. // ---- Helpers ----, // State. Delete it. Split the file if it needs signposts.

JSDoc that repeats the name. /** The value. */ value. Say what the reader can't see: the default, the unit, when it's called, what happens on change. pnpm lint catches field docs that only repeat the name; write the rest the same way.

A hedge or a sales word in a comment or a doc. "Robust", "seamless", "comprehensive", "simply", "just", "easily", "ensure", "leverage", "utilize", "note that", "it's important to". Cut the word; if nothing is left, cut the comment.

A defensive check the types already rule out. if (!items) return on items: Item[], ?? [] on a value that's never undefined, try around code that can't throw. Delete it. Narrow unknown at a boundary instead.

A cast or ! with no reason. Make the type right, or say why in a comment.

A one-caller helper, or a wrapper that only renames. Inline it, unless its name explains something the call can't.

A name that says nothing. data, result, item2, handleClick2, temp, flag, isValid2. Name what it is: highlightedItem, isOpen, onTriggerPress.

An option nobody passes, a parameter with one value, a config object for one setting. Delete it.

Logs, probes and commented-out code. Delete them.

In examples, any comment at all. Only tool directives stay (svelte-ignore, eslint-disable, @__PURE__).

What stays

  • A comment that says why, in three lines at most: a browser bug and the browser, an APG rule, a trade-off, a link to the spec or test that pins the behavior.
  • The word "primitive", and parentheses that hold code names, like "the trigger (MenuTrigger)".
  • JSDoc on every public field and export. Make it say more; don't delete it.

Steps

  1. List what you'll change, by file, before touching anything.
  2. Make the changes.
  3. Run pnpm lint, pnpm format, pnpm typecheck and the unit tests for the packages you touched. Check exit codes.
  4. Delete each comment left in the diff and reread the code. If it still reads right, leave it deleted.
  5. Read the diff once more. Revert any change that doesn't make the code easier to read.
  6. If one pattern showed up in three or more files, propose a lint rule for it in scripts/check-code.mjs or scripts/check-comments.mjs.

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.