sero-prototype
Create and review interactive Sero UX prototypes in the styleguide. Use when the user asks for a prototype, mockup, interaction concept, design exploration, UX review with a reviewable artifact, or a proposed Sero UI before production implementation. Trigger for work in `apps/styleguide/public/prototypes/` and for requests that say "prototype before implementing", "show me first", or "make this match Sero".
sero-labs · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add sero-labs/sero --skill sero-prototypeAbout this skill
name: sero-prototype
description: |
Create and review interactive Sero UX prototypes in the styleguide. Use when
the user asks for a prototype, mockup, interaction concept, design
exploration, UX review with a reviewable artifact, or a proposed Sero UI
before production implementation. Trigger for work in
apps/styleguide/public/prototypes/ and for requests that say "prototype
before implementing", "show me first", or "make this match Sero".
Creating Sero prototypes
Build a reviewable design artifact that matches the current Sero desktop UI. Do not treat a prototype as production implementation.
Non-negotiable rules
- Store every deliverable under
apps/styleguide/public/prototypes/. - Link every interactive prototype from
apps/styleguide/src/PrototypeArchive.tsx. - Never deliver a prototype from
/tmp, a clipboard path, or another protected directory. - Inspect the closest existing prototype before creating a new one. Reuse its useful structure and interaction patterns, but verify them against the current product source because archived prototypes can be outdated.
- Do not edit production UI while the user is still reviewing the prototype.
- Show only controls and behavior supported by the proposed design. Do not add decorative controls that imply unsupported functionality.
- Use ASD-STE100 Simplified Technical English for labels and explanatory copy.
Workflow
1. Define the review question
State what the prototype must help the user decide. Extract these items from the request and screenshots:
- target workflow and entry point
- behavior that must match an existing Sero surface
- supported and unsupported actions
- key states the user must compare
- unresolved product choices
Ask focused questions before building only when different answers would change the interaction model. If the user asked to discuss before implementation, stop after the prototype and review notes.
2. Inspect Sero before drawing
Read the smallest relevant set of sources:
- The current production components for the feature and the Sero surface it must match.
packages/ui/src/styles/globals.cssfor current tokens, typography, focus, radii, and status colors.- Related shared components under
packages/ui/src/components/. - The closest prototype in
apps/styleguide/public/prototypes/. apps/styleguide/src/PrototypeArchive.tsxto understand current names and avoid duplicate entries.
For changes to an existing concept, inspect its saved prototype first. Create a new descriptive prototype file unless the user explicitly asks to replace the historical artifact.
3. Choose the artifact
Use an interactive standalone HTML prototype by default. Name it with a short, lowercase kebab-case slug:
apps/styleguide/public/prototypes/<concept>.html
Use prototypes/<concept>/index.html with adjacent CSS, JavaScript, or image
assets when a single HTML file would become hard to review or exceed the
repository file-size rules. Do not depend on a CDN or remote runtime. The
prototype must work through the styleguide Vite server without network access.
Use static images only when interaction adds no review value. Put persistent review captures in:
apps/styleguide/public/prototypes/screenshots/<concept>/
4. Match the product
- Copy semantic token names and current values from the Sero design system. Do not invent a second palette.
- Match the current desktop layout, density, spacing, border treatment, typography, active states, and control placement.
- Use standard Sero font sizes. In React or Tailwind prototypes, use utilities
such as
text-xs,text-sm, andtext-baseinstead of arbitrary sizes. - Use inline Lucide SVG geometry or repository-owned assets. Do not substitute emoji or unrelated Unicode glyphs for product icons.
- Use realistic, sanitized Sero data. Keep names and copy short.
- Preserve the hierarchy and interaction language of the product surface being matched. A different runtime or backend must not create a different visual system without a product reason.
- Use clear focus, hover, selected, disabled, loading, streaming, success, and error states where they affect the proposed workflow.
- Respect
prefers-reduced-motion. Avoid animation that does not explain a state change.
If the prototype explores alternatives, label each option and keep the data and viewport consistent so the user can compare the design rather than the content.
5. Make the important behavior real
Implement the interactions needed for review, not every product feature. Common examples include:
- opening and closing menus, popovers, and dialogs
- search and filtering
- keyboard focus, Enter, arrow keys when applicable, and Escape
- adding, selecting, renaming, or deleting prototype rows
- changing empty, loading, connected, disconnected, or streaming states
- preserving user overrides such as expansion and scroll position
Use semantic HTML. Every icon-only button needs an accessible name. Every field needs a label or accessible name. Keep the DOM state and visible state in sync.
6. Add the archive entry
Add a concise label and prototype path to interactivePrototypes in
apps/styleguide/src/PrototypeArchive.tsx. Keep the label specific enough to
distinguish revisions of the same feature.
The archive is a design history. Do not describe a prototype as current product behavior or overwrite an older concept without an explicit reason.
7. Serve and review it
Run the styleguide from the repository root:
pnpm styleguide
Open the prototype through the server, never through a file:// URL:
http://127.0.0.1:5176/prototypes/<concept>.html
Use the agent-browser skill when browser automation is available. Check:
- The archive link opens the prototype.
- Every review interaction works from the served URL.
- Keyboard focus order and Escape behavior are correct.
- The d