What is design-review?

A frontend review that checks whether a user interface still contains sample values from a mockup instead of data that can change.

It helps inspect a component against its mockup and report values that should come from the application’s data.

It catches fixed emails, dates, prices, and similar placeholders that could appear incorrectly for real users.

How rakovi4/continue-framework configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/skills/design-review/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/rakovi4/continue-framework

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rakovi4/continue-framework/design-review.svg)](https://agentmods.dev/skills/rakovi4/continue-framework/design-review)

Your own site

<a href="https://agentmods.dev/skills/rakovi4/continue-framework/design-review"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/design-review.svg" alt="Measured on agentmods" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 480 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00043	$0.00480
Opus 5	$0.00022	$0.00240
Sonnet 5	$0.00009	$0.00096
Haiku 4.5	$0.00004	$0.00048

Measured 6d ago against content hash 983eb25f07a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

design-review scanned grade B with 1 finding 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 6d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

1. **By story number**: Read `ProductSpecification/stories.md` to resolve story name → find `ProductSpecification/stories/NN-story-name/mockups/desktop/*.html` for the mockup, falling back to `ProductSpecification/storie

.claude/skills/design-review/SKILL.md · 43 lines

What it actually says

/design-review - Mockup Placeholder Data Review

Usage

/design-review                           # Interactive — find component from current story progress
/design-review 12                        # By story number
/design-review BoardPage.tsx             # By component file

File Resolution

By story number: Read ProductSpecification/stories.md to resolve story name → find ProductSpecification/stories/NN-story-name/mockups/desktop/*.html for the mockup, falling back to ProductSpecification/stories/done/NN-story-name/mockups/desktop/*.html for a story in the Done table (.claude/rules/workflow.md, "Resolving a story folder"), and frontend/src/features/{feature}/components/*.tsx for the component
By component path: Find the component directly, locate the matching mockup from the story directory
Interactive: Read current story's progress.md, find the active align-design step, resolve from there

Workflow

Load .claude/agents/design-review-agent.md
Locate the component TSX file(s) and the mockup HTML
Run the agent's review workflow against the component
Output the review table and verdict

Available Templates

Template	Purpose
`.claude/tech/{browser-testing}/templates/design-review-patterns.md`	Anti-patterns (BAD → GOOD), output format, verdict examples

Gate Behavior

PASS → proceed to /refactor as normal
FAIL → do NOT proceed to /refactor. Fix the flagged violations in the component first, then re-run /design-review

In a staged frontend design-alignment lane, review only the component files in that lane's manifest. A flagged fix outside the manifest or in a frozen Stage 1 interface is an ownership conflict: return FAIL with the path and finding, and let the coordinator reconcile it. Do not edit files, stage, commit, or advance progress.

Changes

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.

6d ago First seen · 43 lines · 43 tokens per session scan B 983eb25f07a2

Subscribe to this mod's changes

design-review is a skill published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 4d ago), licensed MIT. It adds 43 tokens to every session and 480 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Design and UX Frontend

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

frontend-visual-qa

Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…

daymade/claude-code-skills · 145 tokens

prototype-web

可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.

nexu-io/html-anything · 24 tokens

animation-principles

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.

Owl-Listener/designer-skills · 59 tokens

refactoring-ui

Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…

wondelai/skills · 132 tokens

moai-ref-ui-polish

UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…

modu-ai/moai-adk · 98 tokens

continue-framework: Skill for Claude Code