Product design methods and version-aware ranui and ranuts skills in one plugin.

GitHub stars
270

Install

/plugin install ran@ran

Run it inside Claude Code after adding the marketplace with /plugin marketplace add chaxus/ran.

Contents

Discovered from source

Skills 3

Ran Design

Use the host's product goals, framework and visual language. This skill needs no npm package.

Read the design checklist. It is one page: before you start, the five-second and trunk tests, visual language, layout, interaction, motion, words and verification. A small correction stays small.

For a page or region you are building or restructuring, write the brief in the existing task note first, and update it before changing direction. Compare composed screens before adding motion.

When the direction is open, ask for a reference: a screenshot or a product the user likes moves the result more than any description. Ask before adding sections, pages or copy the request did not include; the user knows the audience.

Avoid unnecessary secondary labels and descriptions. Let the layout do the explaining. Preserve accessible names, useful constraints, errors and consequences.

Open the change in the real host: screenshots for layout, density and responsive states; continuous recordings for changed transitions, streaming, navigation and interruption. Say which revision you inspected, what you observed, what you only inferred and what you could not check. Do not mark your own review as accepted; the host project's approval rules still apply.

When the work touches glass menus, tabs, sidebar rows or shared menubar viewports, follow the checklist Motion and Surface · Interactive state on glass rules for sliding washes: one fill that travels, selected wash present on the first open frame (snap, no fade-in lag), full row width. Prefer the project's existing wash tokens and pilots over inventing a second hover grey.

Before handing back

Walk the checklist again, including the five-second and trunk tests on any page whose structure changed; skip lines that do not apply to the change.

When the project uses ranui or ranuts, load that library's sibling skill for installed-version contracts. These design references describe methods, not APIs or permission to install or upgrade dependencies.

ranui

Resolve ranui from the host project's dependency graph, not the plugin cache. Read its actual package.json version and exports. In a ran checkout, use packages/ranui/ and identify it as working-tree source; its version does not prove that code has been published.

package-contract.json beside this skill records the monorepo version the skill was authored against and states that API/token facts are not bundled here (bundledApi: false). Always prefer the host's installed docs for that version. If the installed version differs from authoredAgainst, say so and do not invent APIs from memory or from a newer checkout.

Resolve before you edit

  1. Locate the installed package root (node_modules/ranui, or packages/ranui in this monorepo).
  2. Read package.json version and compare it to package-contract.json authoredAgainst.
  3. Open docs/COMPONENTS.json for attributes, properties, events, slots and parts. If JSON is missing (older install), fall back to docs/COMPONENTS.md.
  4. Open docs/style-tokens-public.md only when theming. Open docs/CODING.md / CLAUDE.md / AGENTS.md only for lifecycle, form, SSR or testing contracts.
  5. Cross-check the host's exports / .d.ts for the subpath you will import. Do not use the website, training memory or an unreleased checkout as the attr source.

To validate markup against the installed JSON without MCP:

pnpm exec tsx node_modules/ranui/bin/check-component-attrs.ts path/to/file.html path/to/file.tsx
# monorepo: pnpm -F ranui check:attrs -- path/to/file.html

Read only the installed reference needed for the task:

TaskPackage-relative reference
Attributes, events, slots and partsdocs/COMPONENTS.json (preferred) or docs/COMPONENTS.md
Theme overridesdocs/style-tokens-public.md and shipped styles
Consumer quick startAGENTS.md
Component implementation and lifecycledocs/CODING.md and relevant CLAUDE.md sections
Form integration, submission and SSRRelevant CLAUDE.md sections and exported types

For product composition, interaction, motion and browser acceptance, use the sibling design skill. Generic design guidance does not depend on installing ranui. When ranui is installed, prefer its docs/DESIGN.md#ranui-implementation-adapter over remote links for token and tier mapping.

After confirming the installed exports, a minimal component setup can use:

import 'ranui/style';
import 'ranui/button';

For a host already using the builder entry, verify these exports in that same installed version:

import { Div, signal, createEffect } from 'ranui/builder';

Use supported public subpath exports; avoid internal aliases and source-only imports. Preserve the host's theme authority. Shadow labels, slots, parts and native form submission are separate contracts. Verify keyboard, focus and touch behavior in the actual host.

If installed documentation is missing, inspect matching declarations/source and report the gap. Do not infer an API from the latest website, assume unreleased components exist, or silently upgrade.

ranuts

Resolve ranuts from the host project, not the plugin cache. Read its package.json version and exports before selecting a utility. In a ran checkout use packages/ranuts/ and identify it as working-tree source; do not assume that source is already available from npm.

package-contract.json beside this skill records the monorepo version the skill was authored against and states that API facts are not bundled here (bundledApi: false). Prefer the host's installed docs/API.md for that version. If the installed version differs from authoredAgainst, say so and do not invent exports from memory or from a newer checkout.

Read package-relative docs/API.md for generated utility signatures, then relevant sections of CLAUDE.md and exported declarations for other subpaths. Prefer the smallest supported public entry. Do not copy a function inventory into the product or invent an export from a newer example.

Check each operation's browser, Node or SSR requirements. A package being importable in Node does not mean every function can run without DOM, storage, Canvas or GPU facilities. Verify the actual operation in its intended environment and preserve cleanup, cancellation and error handling.

For streaming consumers, preserve content identity and ordering, treat partial tool arguments as text until complete, and verify interruption and stale completion behavior against installed types. For product UI decisions use the sibling design skill; for ranui components use the sibling ranui skill.

If documentation is absent, inspect matching declarations/source and state the version gap. Do not silently install, upgrade, or claim that a working-tree capability has shipped.

Sponsors

Details

Marketplace
chaxus/ran
Source
plugins/ran
Author
chaxus
Category
Community