Explore skills

Use when the user asks for root-cause-first debugging of bugs, test failures, flaky behavior, build issues, or integration defects with tracked verification and regression lock-down.

Use after planning and before execution to verify approved current work is reality-fit, feasibility-ready, and explicitly approved at Gate 3.

Reviews product specs, requirements docs, RFCs, PRDs, and policy documents from text, markdown, or Figma. Use for completeness, consistency, edge-case coverage, ambiguity, policy conflicts, or compliance gaps. Triggers on "이 기획서 검토해줘", "스펙 리뷰", "정책 검토", "review this PRD", "is this complete?", "이 기획대로 구현하면 빠진게 뭐가 있을까", "스펙 갭", "요구사항 누락", or whenever a Figma URL is shared in a planning context. Trig

Use at the start of every conversation that touches a non-trivial code or design task. Establishes the ssep skill-matching matrix (4 specialized skills — reviewing-spec-and-policy, reviewing-design-fidelity, improving-feature-completeness, running-integration-tests) and requires the matrix to be evaluated BEFORE any other action, including clarifying questions, file reads, or implementation. Trigg

Read-only static analysis of SAP CAP Node.js code (a Pull Request, a branch comparison, or a specific file list). Classifies findings as Critical / High / Medium / Low, lists each finding with file:line, function/class, evidence and a *suggested* fix (always flagged as needing human validation), and writes the result to `CAP-CODE-REVIEW.md` at the project root. Use when the user asks to: - "analis

Test-only skill for SAP CAP Node.js projects. Its sole purpose is to scaffold and run automated tests using `cds test` (Node.js test runner wrapper) and, when (and only when) explicitly requested by the user, produce coverage with `c8`. The skill writes test files under `test/` (or the project's existing test folder), executes them, and emits two possible report files at the project root: - `CAP-T

Single-page SEO analysis and scoring. Use when user wants to audit a page for SEO, check meta tags, validate schema, review hreflang, or optimize on-page elements. Triggers on "SEO audit", "page SEO", "check my SEO", "meta tags", "schema markup", "hreflang", or /seo commands.

Help a backend engineer gather cross-repo context from browser DevTools network calls, trace API ownership to the right microservice, understand frontend data expectations, and determine exactly what backend changes are needed. Use when user pastes a DevTools network call, asks "which service owns this", wants to understand FE dependencies, or says "be-api-trace" or "trace this API".

Domain-Driven Design reference for pure Java domain modules. Enforces ubiquitous language, strong typing, tactical patterns, and hexagonal architecture boundaries. Consult when writing or reviewing domain-layer Java code.

Claude Code skills for Domain-Driven Design in Java. Opinionated coaching from decades of software engineering.

Scenario-based price selector that turns a price range into a single, intentional final number using real-world context. Use when the user already has a price range or rough estimate and needs to pick a specific price, or when they describe their situation (pipeline status, client type, competition) and want a strategically grounded number. Trigger on: "which price should I pick", "what do I actua

Use when creating a new pulse skill, editing an existing pulse skill, or verifying a skill works under pressure before deploying. Use when you need an agent skill to be bulletproof against rationalization. Do NOT use for project-specific AGENTS.md conventions or one-off solutions.