lynx-community/skills

lynx-ui

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.

First seen Jun 2, 2026

Installation

$ npx skills add lynx-community/skills --skill lynx-ui

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from lynx-community/skills · top by installs.

npx skills add lynx-community/skills

Browse all from lynx-community/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 25
License LICENSE
Default branch release
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,310 B
  • docs README.md 2,799 B
  • docs SUMMARY.md 1,259 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 212 installs

SKILL.md

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

  1. 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

  1. 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.