메뉴
Launch DevFlare and actually look at it — walk the key routes in a browser, screenshot them, and check the shell renders correctly at desktop and mobile widths. Use after any change to the layout, sidebar, navbar, styles.css or a Volt component.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/Andersseen/devflare --skill ui-check명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Verify a Cloudflare deploy will actually succeed before merging to main — token account and scopes, D1 bindings, required secrets, pending migrations, and a dry-run of both workers.
Add a D1 schema migration to dev-auth or devflare — pick the right app, number the file, write replayable SQL, sync the Drizzle schema when it applies, and verify locally before it ever touches production.
Scaffold a new DevFlare browser tool end to end — @org/core service + spec, the page component, and all four registration points (barrel export, router, shell navigation catalog, lucide icon).
SOC 직업 분류 기준
SKILL.md 표시 중
| name | ui-check |
| description | Launch DevFlare and actually look at it — walk the key routes in a browser, screenshot them, and check the shell renders correctly at desktop and mobile widths. Use after any change to the layout, sidebar, navbar, styles.css or a Volt component. |
| disable-model-invocation | true |
pnpm check passing tells you nothing about whether the app looks right. The
VoltUI regression of 2026-07-28 shipped with format, lint, typecheck, test and
build all green, while the sidebar rendered on top of the main content. This
skill is the missing step.
Needs the Playwright MCP server (.mcp.json → playwright). If no
mcp__playwright__* tools are available, stop and tell the user to restart
Claude Code — MCP servers are only loaded at startup. Do not fall back to
guessing from the HTML.
pnpm dev:app
Run it in the background. Wait for the port rather than sleeping:
curl -s --retry-connrefused --retry 40 --retry-delay 2 -o /dev/null \
-w '%{http_code}\n' http://localhost:4200/
Use pnpm dev:all instead if the change touches auth — that also brings up
dev-auth on :8787. Test account: test@devflare.com / TestPass123
(pnpm seed:user if it does not exist yet).
Always stop the server before finishing, even if the check fails.
Minimum set — add any route the change actually touched:
| Route | What must be true |
|---|---|
/ | Hero + card grid; sidebar shows Platform group |
/tools | Tool grid; sidebar switches to the Tools group |
/tools/qr-generator | Canonical two-column tool page |
/settings | Volt tabs, form fields |
/login | Renders standalone, without the app shell |
At each route take a screenshot and look at it. Then check the console:
mcp__playwright__browser_console_messages
Report any error or warning. A clean console is part of passing.
Shell integrity — this is where the known failure mode lives:
md:relative, w-72) — see the @source trap in
.claude/skills/volt-ui/SKILL.md.<main>
scrolls.Volt components: cards have background and padding, focus rings are visible when tabbing, no unstyled flashes of raw markup.
Check at least 1440×900 and 390×844. At mobile width:
The app follows prefers-color-scheme (there is no in-app toggle). Emulate both
and confirm text stays readable and no element keeps a hardcoded colour that
only works in one theme.
Say plainly what you saw at each route, and attach the screenshots. If something is wrong, describe the visual symptom and name the suspected cause, then stop — do not fix it in the same pass unless the user asked you to.
If you could not check something (route needs auth, a browser API is unavailable), say so explicitly. Never report a route as verified when you did not look at it.