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
Who's talking about vercel-labs/ui
- @druce.ai“Vercel Releases UI SDK: 50+ UI Behaviors for AI Coding Agents”Bluesky · Nov 15, 2026 · 2 likes
- @shun91.bsky.social“AIが生成するUIでアクセシビリティやインタラクション設計が欠落しやすい課題を解決するため、Vercel Labsがエージェント向けヘッドレスUIライブラリを公開。 vercel-labs/ui: A …”Bluesky · Nov 15, 2026 · 2 likes
- @yug1224.com“AIエージェントが新しいUIを構築するためのインタラクション動作を提供するライブラリっぽい 次世代のフロントエンド開発に応用できそうだから試したい yug1224 starred vercel-labs/ui …”Bluesky · Nov 13, 2026 · 2 likes
- @technews4869.bsky.social“github.com/vercel-labs/ui GitHub - vercel-labs/ui: A library of behaviors for agents to build the next …”Bluesky · Nov 13, 2026 · 1 likes
- @tech-trending.bsky.social“GitHub - vercel-labs/ui: A library of behaviors for agents to build the next generation of user interfaces.…”Bluesky · Nov 13, 2026 · 1 likes
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
- Nov 16, 2026U3756b, U3512d, U2580a: Move the desktop App to Solid 2 and ui-sdk — roundup-app/roundup0 reactions · 2 comments
- Nov 15, 2026Qué ofrece vercel-labs/ui y si sirve para una UI esqueuomórfica vectorial — itsmistermoon/plaid0 reactions · 1 comment
- Nov 15, 2026agent-skills.github.vercel-labs.ui: 0-unstable-2026-11-13 → 0-unstable-2026-11-15 — sudosubin/agents.nix0 reactions
- Nov 14, 2026[EPIC] UIBL — Universal Interface Behavior Layer: architecture, security, adapters, conformance — UniversalStandards/atlantis-ai-enhanced0 reactions
- Nov 14, 2026Add UI SDK (vercel-labs/ui) cheatsheet — luongnv89/awesome-cheatsheets0 reactions
12 more on GitHub
- Nov 14, 2026frontend-design, ux-ax-review: use UI SDK behaviors for interactive parts (beta) — luongnv89/skills0 reactions
- Nov 14, 2026[FEATURE] Index vercel-labs/ui (UI SDK) and its ui-sdk skill — luongnv89/asm0 reactions
- Nov 14, 2026Vercel Labs 'UI SDK' 베타 공개 — 완성 컴포넌트 대신 에이전트가 조립할 행동 50여 개를 주는 라이브러리 (11/12, Vercel 공식) — roomedia/ax-trend0 reactions
- Nov 14, 2026Resolve open design questions in order — asonas/native-ui-sdk0 reactions
- Nov 14, 2026agent-skills.github.vercel-labs.ui: 0-unstable-2026-11-12 → 0-unstable-2026-11-13 — sudosubin/agents.nix0 reactions
- Nov 13, 2026feat(ui): render json-render views in chat via app_ui tool — VinSpee/velvet-hammer0 reactions · 2 comments
- Nov 13, 2026spike(viewer): evaluate UI SDK behaviors for trace navigation and filters — open-ocpp-trace/viewer0 reactions
- Nov 13, 2026UI SDK をいれる — HayatoW/irreversible0 reactions
- Nov 13, 2026Plan documents build every component Astryx lacks on UI SDK, never by hand (owner instruction 29) — 416rehman/Guardrails0 reactions · 2 comments
- Nov 13, 2026agent-skills.github.vercel-labs.ui: init at 0-unstable-2026-11-12 — sudosubin/agents.nix0 reactions
- Nov 13, 2026Trending candidates 2026-11-13-04 — tayyabimam1/awesome-ai-agent-stack0 reactions · 1 comment
- Nov 12, 2026chore(agents): vendor ui-sdk skill as UI guidance (pinned) — tutur3u/platform0 reactions · 3 comments
On Bluesky · 6
- Nov 15, 2026Vercel Releases UI SDK: 50+ UI Behaviors for AI Coding Agents — @druce.ai2 likes and reposts
- Nov 15, 2026AIが生成するUIでアクセシビリティやインタラクション設計が欠落しやすい課題を解決するため、Vercel Labsがエージェント向けヘッドレスUIライブラリを公開。 vercel-labs/ui: A library of behaviors for agents to… — @shun91.bsky.social2 likes and reposts
- Nov 13, 2026AIエージェントが新しいUIを構築するためのインタラクション動作を提供するライブラリっぽい 次世代のフロントエンド開発に応用できそうだから試したい yug1224 starred vercel-labs/ui https://github.com/vercel-labs/ui — @yug1224.com2 likes and reposts
- Nov 13, 2026github.com/vercel-labs/ui GitHub - vercel-labs/ui: A library of behaviors for agents to build the next generation of user ... — @technews4869.bsky.social1 likes and repost
- Nov 13, 2026GitHub - vercel-labs/ui: A library of behaviors for agents to build the next generation of user interfaces.… — @tech-trending.bsky.social1 likes and repost
1 more on Bluesky
- Nov 13, 2026見てる: "vercel-labs/ui: A library of behaviors for agents to build the next generation of user interfaces." https://github.com/vercel-labs/ui — @azu.bsky.social1 likes and repost
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apps/docs/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ui-sdk-expert-reviewSkill
- ui-sdk-write-codeSkill
- ui-sdk-write-docsSkill
- ui-sdkSkill
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
- Distinctive: line 16
A comment that says what the next line does: Delete it. If the line isn't clear without it, rename something.
- Distinctive: line 65
Logs, probes and commented-out code: Delete them.
- Very specific: line 67
In examples, any comment at all: Only tool directives stay (svelte-ignore, eslint-disable, @__PURE__).
- Very specific: line 79
Run pnpm lint, pnpm format, pnpm typecheck and the unit tests for the packages you touched.
- Distinctive: line 80
Delete each comment left in the diff and reread the code.
- Distinctive: line 81
Read the diff once more. Revert any change that doesn't make the code easier to read.
- Very specific: line 82
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.
≈ “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.
Files
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
- List what you'll change, by file, before touching anything.
- Make the changes.
- Run
pnpm lint,pnpm format,pnpm typecheckand the unit tests for the packages you touched. Check exit codes. - Delete each comment left in the diff and reread the code. If it still reads right, leave it deleted.
- Read the diff once more. Revert any change that doesn't make the code easier to read.
- If one pattern showed up in three or more files, propose a lint rule for it in
scripts/check-code.mjsorscripts/check-comments.mjs.
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
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.

