su-record
UserVerification harness for AI coding agents — completion judged by deterministic gates (tests, run-ledger, regression memory), not the model's self-report. Wraps Claude Code, Codex, Cursor.
Categories
Indexed Skills (41)
vibe.agents-md
Use when authoring or optimizing AGENTS.md or CLAUDE.md — create the context file or remove discoverable detail while preserving project-specific gotchas.
vibe.brand-assets
Auto-generate app icons (iOS/Android/PWA), favicons, and OG images from SPEC brand information using the Antigravity image backend. Use when the project needs visual brand assets, when user mentions 'icon', 'favicon', 'logo', or 'brand assets', or when a SPEC defines brand colors/identity but no assets exist yet. Outputs multiple sizes and formats ready for deployment. Not for complex illustration or marketing graphics — focused on app identity assets.
vibe.capability-loop
Use when the same agent or tool failure repeats, or a missing capability blocks progress, to reproduce the cause and build a permanent repository capability.
vibe.commerce-patterns
E-commerce domain patterns — cart management, payment processing (Toss/Stripe/PG), inventory tracking, and order state machines with transaction safety. Use when implementing any shopping cart, checkout flow, payment integration, stock management, or order lifecycle. Covers idempotency keys, double-charge prevention, stock reservation, and refund flows. Must use this skill when the codebase involves e-commerce — even for seemingly simple 'add to cart' features.
vibe.create-prd
Use when a product idea or research input must become an implementation-ready PRD covering the problem, objectives, segments, value propositions, solution, and release plan.
vibe.design-refine
Design refinement — distill (remove visual complexity), normalize (hardcoded values → design tokens), polish (pre-ship micro-details). Modifying passes. Use when design-refine, design-polish, design-normalize, token-align, simplify-ui, ship-ready.
vibe.design-review
Design quality review — technical audit (a11y, performance, responsive, theming, AI slop) + UX critique (Nielsen heuristics, persona red flags). Read-only report. Use when design-review, design-audit, ui-audit, a11y-check, ux-review.
vibe.devlog
Use when accumulated git commits must be turned into a devlog post or the configured N-commit publication threshold is reached.
vibe.e2e-commerce
E2E test scenarios for commerce checkout and payment flows. Provides ready-made Playwright test templates for cart→checkout→payment→confirmation flows, including PG sandbox testing (Toss/Stripe), error scenarios (payment failure, timeout, stock exhaustion), and idempotency verification. Use when writing E2E tests for any e-commerce feature — checkout, payment, order status, or refund flows.
vibe.parallel-research
Parallel research with 4 specialized agents (best-practices, framework-docs, codebase-patterns, security-advisory) running simultaneously. Use when facing unfamiliar technology, choosing between libraries/frameworks, designing architecture for a new feature, or investigating security implications. Must use this skill when user asks 'how should we build X', 'which library for Y', or when starting work on a complex feature with unknown requirements. Not for simple lookups — use web search directly for those.
vibe.presentation
소스 데이터(리서치/문서/지식그래프)를 16:9 HTML 슬라이드덱으로 생성한다. 디자인 시스템(타이포·색·그리드·1슬라이드1메시지)을 통째로 적용해 전문가 수준 결과를 뽑고, 1920×1080 PDF 로 발행한다. 사용자가 '슬라이드/PPT/프레젠테이션/덱 만들어줘' 라고 하면 이 스킬을 쓴다. 17종 스타일 프리셋은 references/style-presets.md 에서 style= 로 선택.
vibe.prioritization
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more.
vibe.react-best-practices
Use when implementing or reviewing React/Next.js code where Vercel performance pitfalls, rendering behavior, or bundle efficiency must be checked.
vibe.seo-checklist
SEO gotchas for web development — easy-to-miss items that hurt search ranking. Covers meta tags, Open Graph, structured data (JSON-LD), sitemap, robots.txt, canonical URLs, and Naver/Google-specific requirements. Use when building or reviewing any public-facing web page, landing page, or marketing site. Must use this skill when user mentions SEO, search ranking, meta tags, or when deploying a web app that needs to be discoverable.
vibe.tool-fallback
Use when a tool or provider returns API errors, search failures, timeouts, 429, 5xx, or overload responses and a circuit-breaker fallback is required.
vibe.ui-ux-pro-max
UI/UX design intelligence with bold aesthetic direction. Searchable database: 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, 25 chart types across 9 stacks (React, Vue, Svelte, Angular, Astro, Next.js, Flutter, Swift, Kotlin). Use when building any UI component, choosing color schemes, selecting typography, applying design patterns, or reviewing UX compliance. Must use this skill when user builds frontend — pages, components, dashboards, or landing pages — to ensure design quality beyond generic AI output.
vibe.user-personas
Use when research data must be synthesized into three evidence-based user personas with JTBD, pains, gains, and unexpected insights.
vibe.commit-push-pr
Use when the user asks to commit completed changes, push the branch, and open a pull request in one workflow.
vibe.git-worktree
Use when PR review, hotfix, parallel testing, or simultaneous branch work needs an isolated Git worktree.
vibe.analyze
Use when code, documents, websites, Figma, or project quality must be analyzed into an evidence-backed report.
vibe.clone
참조할 라이브 사이트 URL이 있고 그 마크업을 현재 스택으로 재현할 때 — 헤드리스 브라우저로 렌더된 DOM·computed CSS·에셋을 캡처해 픽셀 검증까지 루프
vibe.contract
Use when a SPEC API contract may differ from implementation or endpoint and schema drift must be detected.
vibe.design
UI 작업 전에 시각 품질 SSOT가 필요하거나 DESIGN.md를 생성·검증·동기화할 때 사용한다. Figma와 독립적으로 동작한다.
vibe.docs
Use when README, guides, architecture, release notes, agent instructions, diagrams, or codemaps must be generated or synchronized with the actual codebase.
vibe.educational-content
Create evidence-backed educational content from a subject, curriculum, source document, repository, product, expert interview, or demonstration. Use when Codex needs to research, design, script, verify, assess, or repurpose a lesson, course, tutorial, workshop, explainer, screencast, teaching article, presentation, worksheet, microlearning unit, or educational social content for any domain, including development and technical education. Especially useful when content needs observable learning outcomes, audience-appropriate scaffolding, practice and feedback, valid assessment, source traceability, or clear separation between verified facts and inference.
vibe.event
커뮤니티 행사 일정·홍보·운영을 준비하거나 D-Day 기준 자동화가 필요할 때 — event 유형을 판별하고 외부 발송 전 승인을 강제한다.
vibe.figma
Figma 디자인을 코드로 옮기거나 구현 계획을 Figma에 반영할 때 — READ(Figma→Code)와 WRITE(plan→Figma)를 라우팅한다.
vibe.harness
프로젝트의 Claude Code·Codex 하네스 품질과 병목을 진단하거나 6축 성숙도 점수가 필요할 때 사용한다.
vibe.loop
반복 작업을 자율 goal loop로 설계·설치·실행하고 결정론적 gate로 완료를 판정해야 할 때 사용한다.
vibe.reason
복잡한 문제에서 가설·근거·트레이드오프를 구조화해 결론을 내려야 할 때 체계적 reasoning framework를 적용한다.
vibe.regress
Use when a reproduced bug must be registered, turned into a preventive test, or clustered into a recurring root-cause pattern.
vibe.review
Use when changed code or a SPEC needs a pre-merge review for defects, security risks, boundary mismatches, and zero remaining P1 findings.
vibe.run
승인된 SPEC이 있고 구현을 시작할 때 — `.vibe/specs/<feature>.md`를 읽어 코드와 검증 산출물로 전개한다.
vibe.scaffold
새 프로젝트 구조를 만들거나 기존 폴더 구조가 AI-assisted development에 적합한지 감사할 때 사용한다.
vibe.spec
자연어 요구사항이나 첨부 자료로 승인 가능한 SPEC을 작성해야 할 때 — 단일 패스로 작성하고 1회 승인 후 vibe.run으로 넘긴다.
vibe.test
Use when verifying that a vibe install is intact or that CC and Codex are in sync — before a release, after changing skills/hooks/agents, or when a harness behaves inconsistently. Probes every shipped surface in the target install dir and writes a pass/fail report with STCV skill-quality verdicts.
vibe.verify
승인된 SPEC에 대한 구현 완료를 판정하거나 REQ→SPEC→Feature→Code 추적표가 필요할 때 검증 또는 trace mode로 실행한다.
vibe.continue
세션을 넘기거나 이전 작업을 계속해야 할 때 — reset 전 HANDOFF.md를 만들거나 최신 handoff/checkpoint에서 상태를 복원한다.
vibe.documentation-provider
Fetch current, authoritative library and API documentation through the best available provider. Use for external API/SDK implementation, migrations, version differences, official references, or deprecated API checks; routes between chub, Context7, and official web documentation.
vibe.image
아이콘·배너·목업 같은 래스터 이미지 산출물이 필요할 때 Antigravity 이미지 backend로 생성한다.
vibe.llm
provider별 사용 가능 모델이 바뀌었거나 현재 claude/openai/gemini/zai 모델 목록과 vibe model SSOT를 갱신할 때 사용한다.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.