Agent skill

Component Preview Usage

by Dinil-Thilakarathne in Dinil-Thilakarathne/sona-ui

Instructions and guidelines for using the component-preview and component-preview-server components within the Sona-UI repository.

MITAuto-check passedFrontend & Design

Install Component Preview Usage

skills CLI
$ npx skills add Dinil-Thilakarathne/sona-ui --skill component-preview-usage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Dinil-Thilakarathne/sona-ui component-preview-usage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Dinil-Thilakarathne/sona-ui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/component-preview .claude/skills/component-preview-usage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
component-preview-usage
GitHub stars
118
Token cost
~891 tokens
SKILL.md length
301 words
Files
4
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Instructions and guidelines for using the component-preview and component-preview-server components within the Sona-UI repository.

  • Works in 2 steps: Manual Usage (ComponentPreview) → Registry Usage (ComponentPreviewServer)
  • Frontend & Design work in your project
  • SKILL.md covers Core Components, Usage Guidelines, How Registry Fetching Works and Reference Files
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Component Preview Usage is an agent skill from Dinil-Thilakarathne/sona-ui. Instructions and guidelines for using the component-preview and component-preview-server components within the Sona-UI repository. Includes details on registry fetching.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `reference/component-preview-server.md`, `reference/component-preview.md` and `reference/component-wrapper.md`).

It sits in Frontend & Design. The repository describes itself as: A modern UI component library built with React and TailwindCSS to help you build beautiful and accessible web applications faster. The licence is MIT.

When your agent uses it

  • Frontend & Design work in your project

Example prompts

  • “Use the component-preview-usage skill to instruction and guidelines for using the component-preview and component-preview-server components within…”
  • “/component-preview-usage”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Manual Usage (ComponentPreview)
  2. Registry Usage (ComponentPreviewServer)

What it can do on your machine

Read from SKILL.md and the folder at commit 9a72ffe. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Component Preview Usage loads about 891 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 301 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~891

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Dinil-Thilakarathne/sona-ui at commit 9a72ffe, republished under its MIT licence (© Dinil-Thilakarathne). 301 words, ~891 tokens.

Download SKILL.mdSave it as .claude/skills/component-preview-usage/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
component-preview-usage
description
Instructions and guidelines for using the component-preview and component-preview-server components within the Sona-UI repository. Includes details on registry fetching.

Component Preview in Sona-UI

This skill covers the usage of the Component Preview ecosystem in the sona-ui repository. The preview system handles displaying live React components alongside their raw source code in an interactive tabbed interface.

Core Components

The system relies on three primary files:

  1. ComponentPreview (src/components/common/component-preview.tsx): The client-side UI wrapper providing the Tabs (Preview / Code) and invoking CodeBlock under the hood. It takes raw component and code nodes.
  2. ComponentPreviewServer (src/components/common/component-preview-server.tsx): A server component wrapper that automatically resolves a component and its source code from a global registry map.
  3. ComponentWrapper (src/components/common/component-wrapper.tsx): The visual layout shell that adds the standard background, padding, and centered layout to the actual rendered component.

Usage Guidelines

1. Manual Usage (ComponentPreview)

If you already have the component node and its raw string code, you can use ComponentPreview directly. This is generalized and can be used on any path or any arbitrary block of UI.

tsx
import ComponentPreview from "@/components/common/component-preview";
import MyButton from "./my-button";

const codeString = `
export default function MyButton() {
  return <button>Click</button>
}
`;

export default function Page() {
  return (
    <ComponentPreview 
      component={<MyButton />} 
      code={codeString} 
    />
  )
}
2. Registry Usage (ComponentPreviewServer)

To build scalable documentation (like a UI library docs site), rely on ComponentPreviewServer. This abstracts away importing explicit components and parsing raw strings by reading from a central registry.

tsx
import { ComponentPreviewServer } from "@/components/common/component-preview-server";

// Auto fetches the "default" example from the "button" category
// in the exampleRegistry
<ComponentPreviewServer 
  component="button" 
  name="default" 
/>

How Registry Fetching Works

The ComponentPreviewServer component integrates tightly with the @/registry/index file (specifically exampleRegistry). When you pass component="button" and name="default":

  1. It queries exampleRegistry["button"] to get an array of button examples.
  2. It .find()s the specific example where e.name === "default".
  3. If found, it passes the example's lazy-loaded/imported functional component <example.component /> and its literal string example.code down to ComponentPreview.
  4. If it fails, it gracefully handles the error by returning an inline message: Example default not found in registry for component button.

Reference Files

If you need to bootstrap these preview block wrapper components into another standalone project, full source code for the components is provided in the reference/ block of this skill.

  • component-preview.tsx
  • component-preview-server.tsx
  • component-wrapper.tsx

© Dinil-Thilakarathne, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in .agents/skills/component-preview of Dinil-Thilakarathne/sona-ui.

  • SKILL.md
  • reference/component-preview-server.md
  • reference/component-preview.md
  • reference/component-wrapper.md

Open the folder on GitHubat commit 9a72ffe

Compare with similar skills

Component Preview Usage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Component Preview Usage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Component Preview Usage this skillDinil-Thilakarathne/sona-ui118—~891Automated safety check: PassMIT
Web Artifacts Builderanthropics/skills180k41 repos~769Automated safety check: PassApache-2.0
React Doctormakeplane/plane61k12 repos~657Automated safety check: PassAGPL-3.0
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone

Similar skills

  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 41 repos~769 tokens
    Frontend & DesignAuto-check passed
  • React Doctor

    makeplane/plane

    Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.

    61k GitHub starsUsed in 12 repos~657 tokens
    Frontend & DesignAuto-check passed
  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 97 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Frontend & DesignAuto-check passed

More from Dinil-Thilakarathne/sona-ui

All 10 skills in this repo
  • Oklch Skill

    Dinil-Thilakarathne/sona-ui

    OKLCH color space for web projects. An agent skill from Dinil-Thilakarathne/sona-ui.

    118 GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Sona UI

    Dinil-Thilakarathne/sona-ui

    Discover and integrate Sona UI registry components. An agent skill from Dinil-Thilakarathne/sona-ui.

    118 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Smooth Shadow Ring

    Dinil-Thilakarathne/sona-ui

    A skill your agent uses when styling any elevated surface (card, dialog, popover, dropdown, menu, tooltip, sheet, toast) in a Tailwind project that has shadow-plugin installed.

    118 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Add Sona Component

    Dinil-Thilakarathne/sona-ui

    Integrate a new component into the Sona UI library end to end — the full per-component pipeline of writing the component, demo, docs, registry entry, nav link, playground controls, regenerating the…

    118 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed
  • Component Anatomy

    Dinil-Thilakarathne/sona-ui

    Create a source-backed Inspection Board around an existing Sona UI component for social demonstrations and later documentation experiments.

    118 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed
  • Design Motion Principles

    Dinil-Thilakarathne/sona-ui

    Motion and interaction design expert based on Emil Kowalski, Jakub Krehel, and Jhey Tompkins' techniques.

    118 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Questions about Component Preview Usage

What does Component Preview Usage do?

Instructions and guidelines for using the component-preview and component-preview-server components within the Sona-UI repository. Component Preview Usage is an agent skill from Dinil-Thilakarathne/sona-ui. Instructions and guidelines for using the component-preview and component-preview-server components within the Sona-UI repository.

When should I use Component Preview Usage?

Component Preview Usage fits situations like: frontend & Design work in your project.

How do I install Component Preview Usage in Claude Code?

Run `npx skills add Dinil-Thilakarathne/sona-ui --skill component-preview-usage -a claude-code`. Or copy the skill folder (.agents/skills/component-preview in Dinil-Thilakarathne/sona-ui) into .claude/skills/component-preview-usage in your project. Claude Code loads it when a task matches its description.

How do I install Component Preview Usage in Codex?

Run `npx skills add Dinil-Thilakarathne/sona-ui --skill component-preview-usage -a codex`. Or copy the skill folder (.agents/skills/component-preview in Dinil-Thilakarathne/sona-ui) into .agents/skills/component-preview-usage in your project. Codex loads it when a task matches its description.

Can I use Component Preview Usage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Dinil-Thilakarathne/sona-ui --skill component-preview-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/component-preview-usage, .gemini/skills/component-preview-usage, .github/skills/component-preview-usage and .opencode/skills/component-preview-usage in your project.

What does Component Preview Usage need to run?

SKILL.md names no scripts, command-line tools or credentials: Component Preview Usage is instructions for the agent only.

Does Component Preview Usage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Component Preview Usage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Component Preview Usage use?

Component Preview Usage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Component Preview Usage use?

About 891 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Component Preview Usage?

Skills that share tags, products or a category with Component Preview Usage: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Component Preview Usage?

Dinil-Thilakarathne (a GitHub user) maintains it in Dinil-Thilakarathne/sona-ui, which has 118 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.

Source: Dinil-Thilakarathne/sona-ui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.