Index of every page on this site: llms.txt
All skills
Run it yourself

Builds a temporary page that shows every variant and state of real components at once, each linked to its source.

Use this Skill: https://skilld.dev/gh/raphaelsalaja/skills/lab

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈30 tokens for metadata: the name and description. ≈1.5k when used: this file. ≈34 more on demand in 1 file.

How this Skill uses context

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

This Skill turns off automatic use in Claude Code. Its description stays out of the automatic Skill list by default.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Lab

This skill builds a page for inspecting components. Every variant and every state of the real components sits open on one screen, so the user can tune them without clicking through the app.

Every state open, nothing faked

The lab renders the real components, not copies. States that need a click, such as an open menu or a hover, are forced open. The lab is a development page and never ships.

Exploring new options for one idea belongs to prototype. Which states a screen needs belongs to states, and worst-case data inside an entry belongs to stress. The values on the page come from defaults, motion, color and the project's tokens.

1. Find the states

Read each component and list its variants, sizes and states: hover, pressed, focus, open, selected, checked, indeterminate, disabled, read-only, invalid, loading, empty and error. A lab that shows the resting state only is lab-every-state.

Read the list from the code, not from memory. Every value of a union prop and every boolean prop is an entry. So is every state selector in the component's styles, such as :hover, :active, :focus-visible, :disabled, [data-state="open"], [aria-expanded], [aria-invalid] and [aria-busy].

Cross the variants with the states, so every variant shows every state it can enter. Sizes show at rest, plus any state whose layout changes with size, such as loading. Primary in six states beside Secondary at rest only is lab-cross-the-axes.

2. Build one route

Add one development-only route, such as /lab, that imports the real components. Copy lab.js into the app and load it once on that route. A lab built from copied markup is lab-real-components.

Each entry renders from fixed props and fixture data, never a live request or the current time, so it looks the same on every load. A card entry that fetches its user and spins while the API is down is lab-fixed-props.

3. Force states open

Render menus, popovers, tooltips and submenus open with their controlled props or data-* attributes. Hold hover and focus with force on the entry, such as force="hover". A menu that needs a click to see is lab-states-open. Use the app's current theme unless the user asked for both. That is lab-one-theme.

Forced overlays must not close or block each other. Opening a second popover="auto" closes the first, and a dialog opened with showModal() makes the rest of the lab inert. On the lab page only, open dialogs non-modally with show() and popovers as popover="manual", through the component's own props where it has them. The component itself keeps the modal, auto and hint behaviour overlays sets. Render portals into their own entry. An open popover that lands outside its entry, such as one the browser centres, is moved under that entry's content by lab.js.

After load, count document.querySelectorAll(":popover-open, dialog[open]") against the overlays you forced. One menu open where six were forced, or a lab that ignores clicks behind a modal, is lab-overlays-stay-open.

force rewrites the app's same-origin style rules, so a browser default, such as the built-in focus ring, does not appear. Mark an entry that relies on one as Not verified, then check it with the real keyboard.

4. Link each entry to its source

Wrap each state in a lab-entry naming its component, state and source line, as the header comment in lab.js shows. An unlabelled grid is lab-link-the-source. When the user asked to tune values, add a lab-tune for each custom property with its range.

The grid, labels, filters and controls ship with the skill, so write entries only. A lab page with its own grid, labels or styles is lab-shipped-frame.

5. Open it

Start the dev server and open the lab. A route named in the reply but never opened is lab-open-it.

6. Keep it out of the release

Gate the route and lab.js to development, or delete both before release. A lab reachable in production is lab-not-in-production.

The pair

Every check is a pair. The broken line sits beside the line that replaces it.

Rule Broken Replacement
lab-every-state The resting button only Rest, hover, pressed, focus, disabled and loading
lab-cross-the-axes Primary in six states, Secondary and Ghost at rest only Primary, Secondary and Ghost each in all six states
lab-real-components Copied markup for each state The real Button imported
lab-fixed-props <UserCard id="42" /> fetching from the live API <UserCard user={fixtures.user} />
lab-states-open A menu behind a trigger <Menu open> with its submenu open
lab-one-theme Light and dark side by side, unasked The app's current theme
lab-overlays-stay-open Six popover="auto" menus forced open, one left showing Each menu as popover="manual", six counted open
lab-link-the-source An unlabelled grid Menu / Submenu Open linked to menu/index.tsx
lab-shipped-frame A lab grid and labels written from scratch lab.js loaded, only lab-entry elements written
lab-open-it "Added /lab" The lab opened for the user
lab-not-in-production /lab live on the production site The route gated to development

Reporting

Severity. HIGH is a lab built from copies, or a lab reachable in production. MEDIUM is a missing state, a state that still needs a click or a hand-written lab page. It is also a variant shown in fewer states than its siblings, or a forced overlay that closed another or made the lab inert. LOW is an unlabelled entry, or a lab that was not opened for the user. It is also an entry that reads a live request or the current time, or both themes shown unasked.

Format. One finding per root cause:

file:line - [rule-id] what is wrong

Then a Rule | Count | Severity summary. Block when any HIGH remains, Approve otherwise. Mark every state you could not render as Not verified.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alertstoday3 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    The skill is a developer tool designed to create a component inspection page ('Lab') by analyzing a project's source code. It is generally safe; however, its primary function—ingesting and processing untrusted source code—introduces a surface for indirect prompt injection. It also uses browser APIs like the clipboard for legitimate utility features.

  • Sockettoday

    No alerts

  • Snyktoday

    Risk: LOW · No issues

Signed by skilld at b2e4283. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 12 hours ago.

Activeupdated yesterday
disable-model-invocation
true

README badge

README badge for raphaelsalaja/skills/lab