Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/skills/design-preview/SKILL.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rakovi4/continue-framework/design-preview)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/design-preview"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/design-preview/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rakovi4/continue-framework/design-preview"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/design-preview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.01993 |
| Opus 5.5 | $0.00025 | $0.00797 |
| Sonnet 5.5 | $0.00013 | $0.00399 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
design-preview scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 29d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-preview - Scenario Design Preview
Usage
/design-preview 10 "Filter by date range" # Story 10, named scenario
/design-preview 10 9 # Story 10, scenario 9
/design-preview # Detect from progress.md
Purpose
Before writing any test code, present the planned implementation design to the user for approval. This catches design disagreements early — before red-usecase locks in the approach.
This is also the design gate for a scenario invented mid-cycle (see .claude/guidelines/workflow-detail.md "Net-New Scenarios Introduced Mid-Cycle").
Workflow
Whole-Story Stage 1 Mode
When invoked by .claude/templates/workflow/story-stages.md, design for the complete
story scope while acceptance RED proceeds. The coordinator interviews the user about
material cross-layer choices, reuses settled answers, and waits for required decisions;
workers return open questions to the coordinator instead of assuming agreement.
Freeze the agreed contracts and lane boundaries together. Reuse the concurrent modes'
interface/skeleton and boundary checks, but their infer-without-questions instruction
and ordinary preview's per-scenario approval/stop rules do not apply here. The
coordinator owns existing progress checkboxes and commits; after the joined freeze,
return for immediate implementation without a new invocation or approval round.
Concurrent Contract-Design Mode
When Stage 1 of parallel-backend-stages.md dispatches this skill beside acceptance
RED, do not ask questions or wait for the acceptance lane. Infer the design from the
scenario, existing architecture, and acceptance criterion; discover every adapter;
create the use-case, port, and adapter skeletons; and commit only the declared files.
Record a material choice in an ADR when needed. The coordinator presents the test
and frozen interfaces together for user review after both lanes join.
The acceptance test is optional input in this mode: inspect its committed form when available, but never make either lane depend on the other's completion.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +1 lines · -25 tokens per session 721072ca73ff
- 1mo ago Changed · +5 lines c28a71164b04
- 1mo ago Changed · +12 lines f4df0548c0cb
- 1mo ago Changed · -36 lines 80431ad2016f
- 2mo ago First seen · 179 lines · 63 tokens per session scan A dce72a0d8c8b
design-preview is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 63 tokens to every session and 1,993 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…