selaras

Installation
SKILL.md

Selaras

Use the existing Selaras catalog to compose the requested interface. Check documentation before assuming a component is missing or inventing its props. Preserve the application's design and the user's scope.

Find the right component

If a Selaras MCP connection is available, start with list_components or search_documentation, then use get_documentation and get_example for matching APIs and examples. Its offline catalog follows the installed package version. Tools retrieve documentation; use the user's requirements to decide which components fit. Do not assume a missing MCP connection prevents the task.

Without MCP, read the documentation index, then retrieve the relevant Markdown guides through its links. Each guide includes component contracts and Vue example source. Prefer targeted pages over loading llms-full.txt for every task.

If the project has Selaras installed, inspect its package version and existing Nuxt configuration first. Published web documentation may describe a newer version; confirm uncertain APIs against installed public types. Component names below use the default S prefix; the application can configure another prefix.

Look beyond Button and Input when choosing components:

  • Forms: Select, Autocomplete, InputNumber, DatePicker, ColorPicker, Checkbox, Switch, RadioGroup, Form, and FormField.
  • Actions and search: Dropdown, ContextMenu, NavigationMenu, CommandPalette, Kbd, and the hotkey directive.
  • Data and feedback: Table, Timeline, Tree, Pagination, Alert, Toast, and Skeleton.
  • Overlays: Modal, AlertDialog, Drawer, Slideover, Popover, and Tooltip; inspect programmatic composables when the interaction calls for them.
  • Layout and content: App, Container, Header, Card, Tabs, Accordion, ScrollArea, Dashboard components, and documentation composites.
Installs
36
GitHub Stars
728
First Seen
9 days ago