5.1천건 · 관련도순
Verifies build output integrity after code changes. Runs builds, validates artifact structure, checks for regressions in bundle size, asset references, and static export completeness. The last line of defense before a bad deploy ships.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs. NOT for GraphQL schema evolution, gRPC/Protobuf wire compatibility, database schema migrations, or library/SDK semver.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design low-friction UX, interaction patterns, and comeback loops for AI coding assistant apps, agent consoles, background coding agents, and Port Daddy swarm/operator surfaces. Use when creating flows like prompt-to-diff, context attach, plan/apply/review, checkpoint rollback, background-agent dashboards, visual proof, or multi-agent invocation. NOT for generic landing pages, static dashboards, or implementation-only changes without product flow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a Coval adversarial / red-team testing report and turn it into an agent-hardening plan. Use when a user provides a Coval report URL, report export, run IDs, screenshots, or a per-scenario scorecard from an adversarial sweep and wants evidence-backed next steps such as prompt/guardrail changes, refusal hardening, verification fixes, escalation routing, or expanded attack coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a Coval accent testing report from runs across different speaker accents. Use when a user provides a Coval report URL, report export, run IDs, screenshots, or metric summary and wants evidence-backed next steps such as prompt changes, STT/confirmation adjustments, accent-robust routing, or expanded accent coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a Coval audio-quality testing report from runs across different voice, speaking-style, volume, interruption, and background-noise scenarios. Use when a user provides a Coval report URL, report export, run IDs, screenshots, or metric summary and wants evidence-backed next steps such as prompt changes, tool handling fixes, STT/TTS adjustments, trace setup, or expanded audio-scenario coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the full static analysis suite — ruff lint, ruff format check, pyright type check, auth analysis, license headers, example.env check. Use before committing or to verify code quality after changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the pytest test suite with coverage. Accepts optional filter flags. Use after making changes to verify nothing broke.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Doctrine for all Supabase realtime: postgres_changes, broadcast, presence. Use before writing a `.channel(`/useChannel subscription, echo suppression, reconnect logic, an autosave loop beside realtime, or replacing polling with live updates, or when the tab freezes, messages duplicate, or a subscription delivers nothing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Entry point and shared rules for structural changes to the live Matrx database. Use before any DDL: dropping, merging, or renaming a table, changing a function, RPC, trigger, or policy, hunting straggler tables, or starting a deprecated, schema move, or canonicalization (it routes to those skills).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find and patch the water jump velocity inside CCSPlayer_MovementServices_CheckJumpButton in CS2 binary using IDA Pro MCP. This patch changes the water jump velocity from 100.0f to 145.0f by modifying the immediate operand of a mov instruction. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate and patch the water jump height value. Trigger: water jump patch, CheckJumpButton water velocity, jump height patch, water jump 145
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically creates user-facing changelogs from git commits by analyzing history, categorizing changes, and transforming technical entries into customer-friendly release notes. Use when preparing release notes from commit logs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when starting creative work (features, components, functionality, or behavior changes) to clarify user intent, requirements, and design before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "ドキュメントを更新して", "sync the docs", "update CLAUDE.md after this change", "実装に合わせてドキュメントを直して", or notices that docs have drifted from the codebase. Diffs git history to identify what changed, proposes targeted updates to CLAUDE.md, docs/architecture.md, docs/requirements.md, and README.md, then applies only approved changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Fagsak (case) domain in melosys-api. Use when: (1) Understanding the fagsak lifecycle and status transitions, (2) Working with actors (aktører) - citizens, employers, authorities, (3) Debugging case creation, closure, or type/theme changes, (4) Understanding relationship between fagsak and behandling, (5) Working with EU/EEA authorities or bilateral treaty authorities. Triggers: "fagsak", "saksnummer", "MEL-", "aktør", "sakstype", "sakstema", "avslutt sak".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Behandling (case treatment) domain in melosys-api. Use when: (1) Understanding the behandling lifecycle and status transitions, (2) Debugging issues with behandling creation, status changes, or closure, (3) Understanding relationships between Fagsak, Behandling, and Behandlingsresultat, (4) Investigating why a behandling is stuck or has wrong status, (5) Understanding Behandlingstyper, Behandlingstema, Behandlingsstatus enums, (6) Debugging journalføring or SED-triggered behandling creation, (7) Understanding behandling creation via saksflyt sagas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Modular monolith architecture overview for melosys-api. Use when needing to understand module structure, dependencies between modules, where to place new code, or when changes in one module might affect others. Triggers: "architecture", "module dependencies", "where should I put", "which modules", "dependency graph".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing a Spark feature or writing or materially revising a design proposal that needs repository-first research, user input on unresolved key choices, and an owner-aligned implementation plan before code changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full-stack Convex development guidelines covering React, Vite, TypeScript, mutations, auth, design system, and documentation practices. Use when building features, writing Convex functions, or making code changes in this project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and execute Convex schema migrations safely, including adding fields, creating tables, and data transformations. Use when schema changes affect existing data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.