lynx-ui — Claude Code skill: what it does, how to install
A skill for building with lynx-ui: it picks the component, checks the public API in the repo's reference files and keeps the agent from inventing props.
Apache-2.0 326 installs ★ 28 updated 2026-10-24
npx skills add lynx-community/skills --skill lynx-ui -a claude-codeWhat lynx-ui does
The skill keeps lynx-ui work anchored to a set of reference files. A request is routed first: component choice goes to references/component-overview.md, setup limits to references/foundation.md, Luna themes to references/theming-and-tokens.md, animation to references/motion.md, screen layouts to references/component-composition.md.
For the component in play, the agent opens guide.md, api.md and examples.md under references/components/<component>/. Others get loaded only when the task touches them. Imports default to @lynx-js/lynx-ui unless the API reference asks for a package-specific one.
Before code goes out, props, methods and exports are looked up in api.md; examples count as patterns to verify, not to copy. Where the references have no answer, the skill asks the agent to flag the gap. That is the part that matters: on a component the docs do not cover you get a question, not plausible-looking code.
What it helps with
- pick the right lynx-ui component for a screen
- check a component's props and methods in
api.md - wire up Luna themes and design tokens
- choose a motion package for a transition
- combine several components into one screen the documented way
Example prompts for the agent
- Build a settings screen from lynx-ui components and show me their props from
api.mdfirst. - Set up a Luna theme with dark tokens.
- Which motion package in
references/motion.mdfits a screen transition?
How to install lynx-ui
1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-ui -a claude-code2Manually: put the files in place
~/.claude/skills/lynx-ui/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/lynx-ui/
1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-ui -a codex2Manually: put the files in place
.agents/skills/lynx-ui/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-ui -a cursor2Manually: put the files in place
.cursor/skills/lynx-ui/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install lynx-community/skills skills/lynx-ui2Manually: put the files in place
.github/skills/lynx-ui/SKILL.md1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-ui -a gemini-cli2Platform CLI
gemini skills install https://github.com/lynx-community/skills --path skills/lynx-uiManually: put the files in place
.devin/skills/lynx-ui/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-ui -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about lynx-ui
How do I install lynx-ui in Claude Code?
Run npx skills add lynx-community/skills --skill lynx-ui -a claude-code. The skill lands at ~/.claude/skills/lynx-ui/SKILL.md.
What does the lynx-ui skill do?
It sorts a lynx-ui task into the repo's reference files and pulls the docs for the components involved. Themes, motion and screen composition each have their own reference.
Where do the component props come from?
api.md for that component is the place to check which props, methods and exports really exist. Patterns taken from examples.md get verified against it before use.
Source text
SKILL.md · Apache-2.0
--- name: lynx-ui description: "Use when building with lynx-ui: select components, verify public APIs, adapt examples, configure Luna themes, choose motion packages, compose screens, or troubleshoot lynx-ui usage." --- # lynx-ui Use the smallest relevant reference set. ## Workflow 1. Route the task: - Component selection: `references/component-overview.md` - Setup or troubleshooting boundaries: `references/foundation.md` - Luna themes and tokens: `references/theming-and-tokens.md` - Animation choice: `references/motion.md` - Common component combinations: `references/component-composition.md` 2. After selecting a component, inspect: - `references/components/<component>/guide.md` when available - `references/components/<component>/api.md` for exact public props, methods, and exports - `references/components/<component>/examples.md` for implementation patterns 3. Load additional component references only for components used by the task. ## Rules - Import from `@lynx-js/lynx-ui` unless the API reference requires a package-specific import. - Preserve documented component composition and state handling. - Verify props, methods, and exports in `api.md`. - Treat examples as usage patterns; verify their APIs in `api.md`. - Report missing coverage instead of guessing.
© lynx-community · Apache-2.0 · lynx-community/skills