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

ui-sdk-expert-review

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

Reviews a change with ui-sdk's framework experts (react, vue, svelte, solid, web), only the ones the change reaches, each from its last reviewed commit. Use before merging a branch that touches an adapter, core, specs, examples or framework docs, or when asked for an expert review. Pass a base ref, framework names, or nothing.

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Run the framework experts on what changed.

    line 10

≈ “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

ui-sdk: expert review

Run the framework experts on what changed. Each expert lives in .agents/experts/<framework>/: who it is in expert.md, what it knows in knowledge.md and what's decided in decisions.md. You orchestrate; the experts review.

1. Find the scope

node scripts/expert-scope.mjs --json            # each expert from its "Last reviewed" commit
node scripts/expert-scope.mjs --base origin/main --json   # a branch before merging

Arguments narrow it: a ref becomes --base; framework names keep only those experts. An empty plan means no expert is needed: say so and stop.

Then run each framework's own lint rules on what changed, so the experts spend their review on what a linter can't catch:

git diff --name-only <base>...HEAD | xargs npx eslint --no-warn-ignored

2. Ask the experts

Spawn one background agent per framework in the plan, all at once, as <framework>-expert (in a harness without named agents, a general-purpose agent told to read .agents/experts/<framework>/expert.md first and act as it). Prompt:

Review mode. Scope: git diff <base>...HEAD.
Your files: <own>. Shared files every adapter renders: <shared>.
Review your files, and the shared ones only for what a user of your framework would meet.
Don't report anything decisions.md lists, or these lint findings: <findings, or none>.

Each expert works in its own worktree when it writes throwaway tests (git worktree add ../ui-sdk-expert-<framework> HEAD), with its own ports.

3. Collect

  1. One table: framework, verdict, proven findings by rank, suspected, revisit.
  2. Dedupe across experts: a finding in core that several experts report is one item, listed once, with every framework it reaches.
  3. Hand the table to the user. Don't fix anything unless asked.

4. After triage

Each finding goes one of three ways, in the same turn:

  • Fix now: fix it with its proof as the test.
  • Later: one line under "Known and open" in that expert's decisions.md.
  • Won't do / decided otherwise: one line under "Settled" in decisions.md, with the reason, so no expert raises it again.

Then move Last reviewed: in each expert's decisions.md to the reviewed HEAD. If an expert said its knowledge.md was wrong, fix the file and its "Last checked" date.

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.