lynx-api-docs — Claude Code skill: what it does, how to install
lynx-api-docs — a skill for Claude Code and Codex that routes Lynx engine docs during TSX or TTML development. Prevents AI from assuming browser defaults.
Apache-2.0 183 installs ★ 28 updated 2026-11-15
npx skills add lynx-community/skills --skill lynx-api-docs -a claude-codeWhat lynx-api-docs does
The skill instructs the agent to read authoritative Lynx documentation before generating or changing code. Layout, sizing, and styling tasks route through lynx-vs-web/css-differences.md. For specific tags and selectors, it pulls documents from elements/ and css/.
Lynx differs significantly from standard browser runtime. The engine uses <view>, <text>, and <image> instead of HTML tags, applies Linear layout by default, and keeps margins uncollapsed.
Repair rules force minimal edits. The agent diagnoses the defect on the smallest selector first and keeps unrelated markup, asset paths, and element properties untouched.
What it helps with
- migrate Web HTML and CSS components to Lynx TSX or TTML
- debug layout bugs caused by non-collapsing margins or linear flow
- verify supported CSS properties, pseudo-classes, and units in Lynx
- configure Lynx grid, flex, or relative layouts following engine specs
Example prompts for the agent
- Convert this React component into Lynx TSX markup
- Debug layout stacking differences on this Lynx TTML template
- Check why box-sizing behaves differently in this Lynx stylesheet
How to install lynx-api-docs
1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-api-docs -a claude-code2Manually: put the files in place
~/.claude/skills/lynx-api-docs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/lynx-api-docs/
1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-api-docs -a codex2Manually: put the files in place
.agents/skills/lynx-api-docs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-api-docs -a cursor2Manually: put the files in place
.cursor/skills/lynx-api-docs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install lynx-community/skills skills/lynx-api-docs2Manually: put the files in place
.github/skills/lynx-api-docs/SKILL.md1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-api-docs -a gemini-cli2Platform CLI
gemini skills install https://github.com/lynx-community/skills --path skills/lynx-api-docsManually: put the files in place
.devin/skills/lynx-api-docs/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-api-docs -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-api-docs
How to install lynx-api-docs in Claude Code?
Run npx skills add lynx-community/skills --skill lynx-api-docs -a claude-code in your terminal.
What does lynx-api-docs do?
It guides the agent through Lynx engine references for CSS, layout structures, and tags, preventing standard HTML assumptions.
What critical defaults does lynx-api-docs enforce?
It requires <view> and <text> elements, uses Linear layout as the default, and accounts for uncollapsed margins.
Source text
SKILL.md · Apache-2.0
--- name: lynx-api-docs description: Authoritative Lynx engine references for generating, reviewing, migrating, or debugging Lynx TSX/TTML pages, CSS, layouts, selectors, and elements. Use for Lynx-specific styling and Web-to-Lynx differences; always retrieve the relevant installed docs before changing code. --- # Using Lynx API Docs **MUST read the relevant API docs before writing or editing Lynx code.** Lynx elements and CSS differ from the Web; do not fill gaps with HTML or browser assumptions. **For repair tasks, diagnose and route each symptom before reading element documentation.** For layout, sizing, wrapping, or stacking symptoms, read the CSS differences index first. Do not infer element-prop defects from visual differences alone. ## Route the Task | Task | Read first | | --- | --- | | **Generate or edit Lynx CSS; migrate Web HTML/CSS; debug a Lynx/Web style difference** | **`lynx-vs-web/css-differences.md`**, then only the linked topic files needed for the diagnosed task | | Check a CSS property, value, unit, or function | `css/supported-properties.md` and `css/values-and-units.md`; also check the CSS differences index when Web compatibility matters | | Write or debug selectors | `css/selectors.md` and `css/pseudo-classes.md` | | Choose or debug a layout | `layout/linear-layout.md` (default), `layout/flex-layout.md`, `layout/grid-layout.md`, or `layout/relative-layout.md` | | Use or debug an element | `elements/<element-name>.md` | | Apply theming, responsive design, or animation | `patterns/theming.md`, `patterns/responsive.md`, or `patterns/animation.md` | | Look for a complete example or performance guidance | `examples/`, `quick-reference.md`, or `best-practices.md` as needed | For CSS work, the differences index is the generation entry point, not only a migration reference. Follow its exact topic links instead of loading the entire documentation bundle. ## Generation-Critical Defaults - Use `<view>`, `<text>`, and `<image>`, not HTML elements; wrap text in `<text>`. - Lynx defaults to Linear layout, not Web block flow. - `box-sizing` initially uses `auto`, normally with border-box sizing; set an explicit value when compatibility settings may differ. - Margins do not collapse. These defaults are shortcuts, not a substitute for the task-specific references above. ## Repair Scope and Output For debugging and visual-repair tasks: - Diagnose before expanding retrieval. Read only topics tied to the observed defect; do not survey unrelated element, animation, or visual-effect documentation. - Start from the observed defect and the smallest affected element or selector. Change only what is required for that defect; do not repair speculative differences or normalize unrelated code. - Preserve unrelated styles, component props and behavior, content, assets, fonts, and routing. Do not apply a relevant rule, such as `box-sizing`, to other elements unless they share the diagnosed defect. - Before answering, compare the result with the original and remove every edit not required by the diagnosis. - Follow the user's output contract exactly. When complete files only are requested, return those files without retrieval notes, status updates, explanations, or other prose.
© lynx-community · Apache-2.0 · lynx-community/skills