Abyss Documentation Skill

Fetches Abyss Design System documentation to help build frontend applications.

Checklist-driven workflow

- [ ] Step 1: Fetch documentation index
- [ ] Step 2: Determine platform (web/mobile)
- [ ] Step 3: Select specific documentation URLs
- [ ] Step 4: Fetch and apply documentation

When to use

Invoke this skill when:

• User asks about Abyss components (Button, Input, Card, etc.)
• User needs form inputs, layouts, or UI patterns
• User asks "how do I use Abyss [component]"
• User needs Abyss styling or theming guidance

Do NOT invoke if:

• User asks about migrating to v2 (use abyss-v2-migration skill)
• User asks about non-Abyss libraries

Workflow

Documentation Index URL: https://abyss.uhc.com/llms/llms.txt

Step 1: Fetch the Documentation Index

Use fetch_webpage to read the documentation index URL above. This returns a structured list of all available documentation grouped by platform and category.

Step 2: Determine Platform

Check the project's package.json for dependencies:

• If @uhg-abyss/web is present → Use Web documentation
• If @uhg-abyss/mobile is present → Use Mobile documentation

Step 3: Select Specific Documentation URLs

Important for token efficiency: Be selective when fetching documentation. Prioritize:

• Component-specific docs for the exact component needed
• Implementation guides for the specific feature being built
• When fetching, focus only on relevant sections (props, examples, specific use cases)
• Skip broad overview pages, full example galleries, or unrelated sections

Step 4: Fetch and Apply

Use fetch_webpage on your selected URLs, then apply the documentation to complete the user's request.

Skill feedback

If user says "Report skill issue" or "This isn't working, help me report it":

1. Read references/feedback.md and follow its workflow