agentsclimarketplace
Sign in

Vercel composition patterns

Skill kimtth/agent-skill-100-lines-or-less/skills/vercel-composition-patterns

Use when: design composable React component APIs that scale without boolean prop sprawl.From its SKILL.md

Install
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill vercel-composition-patterns

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.1 KB, 203 tokens by cl100k_base, as published. Nobody here has run it

Goal: component APIs that stay flexible as features grow.

Use for:

  • components accumulating many boolean and config props
  • shared UI that each consumer needs to customize differently
  • replacing rigid components with composable ones

Workflow:

  1. Identify the variation points consumers actually need.
  2. Prefer composition (children, slots) over configuration flags.
  3. Use compound components for related, coordinated parts.
  4. Share state via context, not prop drilling.
  5. Expose render props or slots for true customization.
  6. Keep the default usage simple; advanced control opt-in.

Patterns:

  • compound components for grouped UI (Tabs, Tabs.List, Tabs.Tab)
  • context to coordinate without prop drilling
  • render props / slots for caller-controlled rendering
  • polymorphic as prop where appropriate

Rules:

  • favor children over a growing prop list
  • do not leak internal structure through booleans
  • keep each part single-purpose and replaceable
  • common case stays trivial; complexity is opt-in

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most containers cloud skills give in 203 tokens

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07

  • Run containers as a non-root userin 66 of 607, across 46 files
  • Use multi-stage buildsin 53 of 607, across 44 files
  • Use Promise.all for independent operationsin 47 of 607, across 13 files
  • Import directly instead of barrel filesin 46 of 607, across 12 files
  • Use ternary instead of AND for conditionalsin 45 of 607, across 12 files
  • Use Set or Map for O(1) lookupsin 42 of 607, across 10 files
  • Create a .dockerignore filein 41 of 607, across 31 files
  • Read individual rule files for detailsin 39 of 607, across 9 files
  • Copy dependency files before source codein 36 of 607, across 23 files
  • Authenticate server actions like API routesin 35 of 607, across 7 files
  • Use next/dynamic for heavy componentsin 34 of 607, across 9 files
  • Use React.cache for per-request deduplicationin 34 of 607, across 10 files

Said here and by no other author read

  • Identify variation points consumers need
  • Prefer composition over configuration flags
  • Use compound components for related parts
  • Share state via context not prop drilling
  • Expose render props or slots for customization
  • Keep default usage simple

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.