Agent skill
sketch-devtools-qa
Chrome DevTools QA workflow for the Sketch Magic kid-first UI. Use when validating Console/Network/Performance, investigating “tap doesn’t work”, /api/convert failures, mobile touch issues, or when a proof video must be backed by DevTools evidence.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/sketch-devtools-qa-joelklabo-markdowntown-cli-2
SKILL.md
Sketch DevTools QA
Overview
Run a repeatable DevTools QA pass for the upload → prompt → convert → result flow, with explicit log review and kid-first UX checks.
Quick Start
- Start the dev server and open Chrome DevTools.
- Enable Preserve log + Log XMLHttpRequests in Console.
- Run through the full flow (upload → prompt → convert → result).
- Record findings using the checklists in
references/.
Workflow (required)
1) DevTools setup
- Console: enable Preserve log and Group similar.
- Network: filter by
/api/convertand check for 4xx/5xx. - Performance: verify no frozen UI during convert.
2) Happy-path run
- Use a real upload or sample.
- Confirm Convert starts loading within ~300ms.
- Confirm result image renders and download works.
3) Log review
- Dev server logs: tail or use
pnpm dev:logsif available. - Confirm no server errors and no console errors.
4) Kid-first UX pass
- Validate tap targets, spacing, readability, and motion at 320/390 widths.
- Use the kid-first checklist from
references/ux-qa-checklist.md.
5) Report outcome
- If any error exists (Console, Network, or logs), do not claim done.
- Create follow-up issues for any UX or stability gaps.
- Use
qa-verificationfor the standard evidence format.
References
references/devtools-checklist.md— Console/Network/Performance QA list + log rubric.references/ux-qa-checklist.md— Kid-first UX checklist (tap targets, motion, copy).
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?