3.3천건 · 관련도순
Route a PR review request to the correct tool — code-review plugin (quick parallel scan across all dimensions) or pr-review-toolkit (deep-dive on a specific quality dimension such as type design, error handling, test quality, comments, or simplification). Use when the user asks for a code review, PR review, or mentions a specific quality concern before creating a PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug Keel agent command or validation failures under Keel's selected OpenSpec task contract. Use when `/opsx:apply` or a selected task reports failed commands, failing tests, validation errors, retry-fuse decisions, or needs an evidence-bound failure report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writes and cleans up messages and docs for their channel and reader (email, Slack, a text, release notes, store pages, READMEs, Claude Docs) in a plain voice that never moves a fact. Trigger to write, rewrite, shorten, line-edit, retell or change the tone of any message, even a two-line text; to strip dashes or AI tells; to fix UI wording (a dialog, button or error); to score text without rewriting; to plan release comms; to write a store page, launch post or listing title, blurb and tags; to write in a voice or learn one; or say commscribe (draft, reshape, humanize, audit, retell, formats, cadence, voice, docs). It never sends. A skill's own files (SKILL.md, references) are skillwright's; brand voice and layout brandscribe's; sourced write-ups researchscribe's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug and troubleshoot WorkOS AuthKit authentication issues with Convex. Use when authentication fails, JWT validation errors occur, user identity returns null, email claims are missing, admin access checks fail, or sign in button does not work. Supports Netlify deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run convex-doctor static analysis, interpret findings, and fix issues across security, performance, correctness, schema, and architecture categories. Use when running convex-doctor, fixing convex-doctor warnings or errors, improving the convex-doctor score, or when asked about Convex code quality, static analysis, or linting Convex functions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Watch for the next dev/prod error or request in a Convex app and react to it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up Sentinel production error capture in your own Convex deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create Convex queries, mutations, and actions with proper validation, authentication, and error handling. Use when implementing new API endpoints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ably real-time messaging patterns, WebSocket channel management, message validation and processing, staleness filtering, error recovery strategies, collaborative editing with drag-and-drop, optimistic updates for voting, real-time board collaboration, and Ably integration best practices for ree-board project
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing GraphQL resolvers with Absinthe. Covers resolver patterns, dataloader integration, batching, and error handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[61] VALIDATE. Comprehensive code quality check combining ESLint, TypeScript compilation, and unused code detection. Runs full lint suite with detailed error reporting and fix suggestions. Use before commits, after major changes, or when ensuring code quality standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[71] CLOSE. Quick, safe cleanup after completing a milestone. Fix objective issues only (syntax errors, dead code, poor naming). Must be <5% of main task time, <30 seconds per fix, and reversible. Use after key points, not after every small change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Kotlin Coroutines and Flow patterns for Android and KMP — structured concurrency, Flow operators, StateFlow, error handling, and testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds production-ready REST API endpoints with validation, error handling, authentication, and documentation. Follows best practices for security and scalability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design spec with 98 rules for building CLI tools that AI agents can safely use. Covers structured JSON output, error handling, input contracts, safety guardrails, exit codes, and agent self-description.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when declaring or manually triggering route-level TanStack Query prefetches with nuxt-ui-tools. Covers page macros, staged dependencies, NuxtLink integration, and error-safe navigation behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.