Explore skills

Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

Finds companies matching the ICP that are showing buying signals right now, then finds contacts at the best ones. Builds a scored prospect list for outreach. Triggers: /prospect, "find companies", "build a list", "find prospects". Reads: ./gtm/icp.md, ./gtm/signals.md, ./gtm/company.md. Writes: ./gtm/prospects.md. Standalone: yes.

Create distinctive, production-grade frontend interfaces. Rejects generic AI aesthetics (purple gradients, Inter font, glassmorphism). Design direction first, then implementation.

Save and restore session state for continuity across Claude Code sessions. Captures tasks, changed files, context, and decisions. Use when ending a session, preserving progress, or running /checkpointing.

Generate distinctive, production-grade frontend UI code that avoids generic AI aesthetics. Follows opinionated design principles for unique visual identity. Use when building web UIs, components, or running /frontend-design.

Generate native-quality iOS/macOS mockup PNGs using SwiftUI Preview rendering. Use when designing Apple platform UIs, creating native app mockups, or running /mockup-swift.

Reviews implemented UI against design source-of-truth (Figma frames, mockup images, design tokens) for visual fidelity — spacing, typography, color, responsive behavior, interaction states, accessibility. Use when comparing built pages to design specs, when a Figma URL is shared alongside a live URL/screenshot, or for "디자인 검수", "퍼블리싱 검토", "compare with figma", "픽셀 비교", "design QA", "피그마대로 되어있나", "

Authors and runs tests across the test pyramid — unit, FE↔BE integration, and end-to-end browser scenarios — using Playwright MCP and runners (jest, vitest, mocha). Use when verifying multi-layer behavior or for "e2e 테스트", "integration 테스트", "통합 테스트", "playwright로 검증", "브라우저에서 직접 확인", "백엔드-프론트 연동", "API 통합 테스트", "staging 검증", "배포 후 검증", "smoke test", or when a feature crosses boundaries (API + UI

Use when the original plan needs to flex mid-flight in response to new information / changed inputs / discovered constraints — but flexibility WITHOUT defined scope degenerates into either rigid plan-sticking or unbounded winging-it. CRITICAL Step 0 (mirror of chengyu-close-door-catch-thief): scope MUST be defined before any deviation. If operator hasn't given a flexibility-scope tier, agent must

Use when the operator has explicitly authorised an indirect / non-causal move — when frontal attack is blocked AND chengyu-remove-firewood-from-cauldron has been exhausted, requiring attention-redirect or incentive-shift rather than technical root-fixing. Default to chengyu-remove-firewood-from-cauldron unless the operator has told the agent how to 圍魏.

Use when designing a migration — graceful transition where the old interface stays as a thin stub/proxy/shim, real implementation moves underneath, consumers keep working through the transition, eventual cleanup of the shell once consumer count reaches zero. The schema of every good rename / endpoint move / library v1→v2 / database schema migration / monorepo split.