Skip to content
Skills Library
Design & UX · Building & coding

spectre-prototype

/spectre-prototype

Create one self-contained HTML prototype to resolve ambiguity, validate flows, or render UX before planning. Use for prototype/mockup/preview requests and UX Stage 1→2; not for production code, multi-file apps, scope, or planning.

Repository
spectre ↗
Licence
MIT
Last repository change
02.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create one self-contained HTML prototype to resolve ambiguity, validate flows, or render UX before planning. Use for prototype/mockup/preview requests and UX Stage 1→2; not for production code, multi-file apps, scope, or planning.

Original author description

Create one self-contained HTML prototype to resolve ambiguity, validate flows, or render UX before planning. Use for prototype/mockup/preview requests and UX Stage 1→2; not for production code, multi-file apps, scope, or planning.

How it works

  1. Purpose
  2. Inputs
  3. Working Set
  4. Outputs + DONE
  5. Method / guardrails
  6. Handoff
  7. Escalate-If
Original SKILL.md headings · 66 lines, 648 words
SKILL.md preview
---
name: "spectre-prototype"
description: "Create one self-contained HTML prototype to resolve ambiguity, validate flows, or render UX before planning. Use for prototype/mockup/preview requests and UX Stage 1→2; not for production code, multi-file apps, scope, or planning."
user-invocable: true
disable-model-invocation: true
---

# prototype

## Purpose

Produce one HTML prototype at `{FEATURE_ROOT}/prototypes/{slug}_{MMDDYY}.html`. The primary owns it; agents provide evidence only.

## Inputs

- `$ARGUMENTS`: feature root/name or descendant, description, optional `--explore`; marker `FROM_UX=true`.
- Read existing `concepts/scope.md`, `specs/prd.md`, `ux.md`, then legacy `specs/ux.md` fully before questions.
- Silently read repo-root `product.md` when present, plus `design.md` or fallback `design/design.md`; apply them; do not mention missing files.

| Mode | Signal | Fidelity | Contract |
|---|---|---|---|
| `post-ux` | complete `ux.md`: Screens, Layouts, Components, Interactions, States, Content | high | render faithfully; exact documented copy; no invented screens |
| `flows-only ux` | `FROM_UX=true` or flows without complete Stage 2 | mid | preserve approved flows; choose UI details |
| `explore` | `--explore` | low, grayscale/layout-only | visualize an unvalidated concept |
| `post-scope` | scope, no UX | mid | validate scope |
| `standalone` | no artifact | mid | establish what to prototype |

## Working Set

- Reuse a managed `FEATURE_ROOT` only when explicit/current-thread evidence ties it to this work (physical directory wins; never branch/recency/lifecycle/scans); distinct work ignores ambient roots. Otherwise, including on collision, standalone MUST first load and follow `@skill-spectre:spectre-feature-root` through DONE; orchestrated calls escalate. Keep writes beneath it and pass it unchanged.
- Repair stale feature/root metadata in artifacts this workflow touches.

## Outputs + DONE

The single HTML file contains:

- `<!DOCTYPE html>`, viewport metadata, inline CSS, and inline end-of-body JavaScript.
- A top-of-head comment beginning `Feature:` and `Feature Root:`, followed by Fidelity, Generated, Flow covered, Screens/states, Visual anchor, Source spec, Key assumptions, post-UX Filled assumptions, NOT included, and Next step.
- A design-token comment for Primary, Accent, Surface, Text, Font, Border-radius, Spacing, mirrored as `:root` custom properties.
- If multi-screen, vanilla-JS `display:block/none` navigation; one ordered `<section>` per screen, each with happy path plus an empty, error, or loading state.

DONE when mode/fidelity/anchor are explicit; available context and research preceded generation; the primary authored and validated the file; documented UX is faithful; content is realistic; components reuse named classes; interactions have no console errors; and states, reuse, and portability pass. Surface failures as caveats.

## Method / guardrails

1. Reply before tools, except `FROM_UX=true` may begin by reading `ux.md`; if no arguments or context, ask what to prototype.
2. Ask 2–4 focused questions. Confirm fidelity and a visual anchor (colors, fonts, URL, or named aesthetic); if skipped, declare one. **Gate: wait unless `FROM_UX=true`.**
3. After the gate, dispatch in parallel; each returns ≤2,000 tokens in-thread and writes no files:
   - `@spectre:web-research`: 2–3 current references, interaction convention, and concrete palette/type/layout values; <400 words with citations.
   - `@spectre:analyst`: post-UX extracts required sections and copy verbatim, marking spec-silent details as filled assumptions; otherwise synthesizes flow, screen states, realistic content, and components.
   - `@spectre:patterns`: only for an existing app; return actual tokens and interaction conventions.
4. After all findings return, the primary alone creates, edits, and validates the HTML; not even `@spectre:dev` modifies it.

Use inline SVG/data URIs/CSS shapes only: no remote images, relative assets, custom WOFF, filler, Inter/Roboto defaults, purple-on-white gradients, broken `href="#"`, happy-path-only screens, or inline restyling of recurring components. Use one Google family (≤2 weights) or system fonts. Tailwind CDN is mid/high-fi only.

## Handoff

| Handoff | Details |
|---|---|
| 🧭 **Current phase** | Done |
| 📦 **What was just done** | Result |
| ▶️ **Proposed next step** | Render resolved action. |

Return path/screens/fidelity/anchor/assumptions/NOT included; opens/shareable; revalidate edits/research; promote post-UX to `ux.md`. explore → Scope; flows-only UX → Stage 2; post-UX contradiction/assumption → UX, else Plan; post-scope unresolved UX → UX, post-scope validated scope → `/spectre:spectre-plan`; standalone no scope → Scope, else reclassify as `post-scope`. One route/conditional/pause.

## Escalate-If

- A post-UX contradiction exists: ask which is authoritative, update `ux.md` and HTML together, then revalidate.
- A required mode artifact is missing/unreadable, or neither the user nor context supplies a usable visual anchor/aesthetic.

Next step: follow the mode-specific handoff above.

Versions

RepositoryScoreLicence
This page · joenandez/spectre90MIT
joenandez/spectre90MIT

Database snapshot: 13.11.2026 · package version 70a0a99fa467 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 89prototype
    Render a proposed redesign of a page on the current website as a self-contained static HTML file, then iterate via the impeccable craft loop. Per-page, idempotent, stale-aware. Use when the user asks for a redesign prototype, a before/after comparison, a design preview, a page…
  • 100prototype
    HTML mockup of a UI change in the project's own look, one proposal or three variants. Use when the user wants to see or compare a UI change before planning it.
  • 100mockup-builder
    Use when creating a visual mockup, UI prototype, or HTML reference for your project's UI. Triggers on "mockup", "prototype", "UI reference", "design a panel", "mock up", or any task producing a visual HTML file for later Unity UI Toolkit implementation.
  • 100build-prototype
    Use when the user wants a prototype, mockup, clickable demo, design options or "something to show" for an item with approved behaviour trees. Step 4 of the pipeline - builds one self-contained clickable HTML file with two or three hypothesis-led design variants, where every tree…
  • 90prototype
    Build a throwaway HTML or in-app prototype that answers one design question. Use when the user wants to try a state model or UI idea before committing, or says "mock it up", "prototype", "what should this look like".
  • 90prototype
    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.