개발 스킬

The official Skill Base CLI client. Use the `skb` (Skill Base CLI) command to search, install (single skill or collection), update, delete, publish, and import-from-GitHub skills from Skill Base, as well as configure skb. Triggered when users say "publish skill to skill base", "install collection", "import skill from github", "download/update/delete skill from skill base", "configure skb", "am I logged in", "check skb login", or "configure skill-base-cli".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user wants a written, reviewable plan or spec produced before coding starts. Triggers on: mapping out changes without implementing, thinking through risks of upgrades or migrations, evaluating approaches before committing to one, writing specs for team review, phasing work into stages, or any request that explicitly defers coding ('don't implement yet', 'before we build'). The distinguishing signal is that the user wants a plan artifact — not implementation, not a conversational answer. MUST activates inside Claude's native plan mode to have a better planning behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a web browser — whether building, fixing, or refactoring — use this skill. Not for backend APIs, databases, infrastructure, or DevOps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review code for quality, correctness, and fit. Use when the user wants judgment on code that already exists — their own changes, a teammate's patch, a PR, branch, commit, diff, staged changes, or one or more files to look over. Activate on requests like review, look over, sanity check, critique, code review, or 'is this good?' The key signal is that the user wants evaluation of existing code and its tradeoffs, not implementation, debugging, or explanation. This skill works independently, but when plans, specs, task artifacts, or prior discussion exist, use them to understand why the code exists before judging it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill for any Python backend work in this project: building FastAPI endpoints, writing service functions, defining Pydantic/SQLModel schemas, running Alembic migrations, or debugging 422 errors. Essential for authentication and authorization patterns — setting up get_current_user, is_superuser checks, admin-only guards, role-based access, and dependency injection chains like Depends(). Also covers middleware, background tasks, async SQLAlchemy sessions, ORM relationship loading, and request/response design. Activate whenever the question involves Python API code, FastAPI patterns, or backend architecture in this codebase. Not for frontend, Docker, CI/CD, or infrastructure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MUST use for ANY query mentioning packages, monorepo, workspace, catalog, turbo, turborepo, or pnpm in a multi-package context. MUST use when sharing config (ESLint, tsconfig, prettier) across packages, fixing build order between packages, adding new packages, scoping CI installs/caching to changed packages, or debugging pnpm catalog version resolution. This skill OWNS all cross-package coordination problems — even when they look like build, CI, config, or dependency issues. If two or more packages interact in the query, this skill applies. Takes priority over other skills when the problem spans package boundaries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when an "enable observability" card asks for crash reporting on a mobile (iOS, Android, React Native, Flutter) or desktop app - adding Sentry or Firebase Crashlytics with release and environment tags, symbol upload, and session tracking so crash-free users can be read

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the repository keeps its alerting in code, or a person asks for alerts outside TaskTrooper - PrometheusRule YAML, a Cloud Monitoring alert policy in Terraform, a Datadog monitor, each routed to TaskTrooper's alert ingest URL so it opens an incident here

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building or extending a Rust service - axum on tokio (or the repository's actix-web / rocket), typed errors with IntoResponse, serde at the boundary, sqlx queries and migrations, never blocking the runtime, tracing, clippy

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when starting a backend task that could be built in more than one language - follow the repository's stack, or for a greenfield service choose between Go, Java, C#/.NET, TypeScript on Node.js and Rust from the task's shape

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building or extending a TypeScript service on Node.js - Fastify, NestJS, Express or Hono, runtime validation at the boundary, strict types, the repository's ORM and migrations, async error handling, graceful shutdown

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the diff adds or changes a gRPC service or interceptor, a GraphQL resolver or subscription, a protobuf/Thrift schema, a queue or pub/sub producer or consumer, an event handler or an inbound webhook - peer identity vs claimed principal, interceptor gaps, per-item and stream authorization, webhook signatures, untrusted producers, enum defaults, replay, duplicate delivery and ordering

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the diff changes C, C++ or Objective-C, Rust unsafe blocks, Go unsafe or cgo, JNI, Python ctypes/cffi or C extensions, Swift unsafe pointers, C# unsafe or Marshal code, or a native plugin, parser or loader that sees untrusted bytes - bounds, integer overflow before allocation, unit confusion, lifetimes, uninitialized memory, format strings, FFI ownership and library search order

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the diff reads Host or X-Forwarded-* headers, configures trusted proxies, builds absolute URLs or response headers from input, sets cache headers or CDN/reverse-proxy cache rules, or changes an ingress, auth proxy or custom HTTP parser - host and forwarded-header trust, cache poisoning and deception, header injection, trusted-proxy bypass and request framing

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before writing any new function, helper, component or module - find what the repository, the standard library and the installed dependencies already provide, and use an established library instead of hand-rolled code for a non-trivial problem

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when an analiz question needs the human, not the code, to decide - recording it with record_open_questions, judging blocking vs non-blocking, and resuming the report after an answer

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a task is in code_review - how to read the diff, which findings block, and the verdict move

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building native iOS with SwiftUI - small composable views, observable state models, atomic components, Swift 6.2+ concurrency, and system styling over hardcoded values

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before and after calling rollback_release - what a rollback restores per delivery mode, when a schema change makes a code rollback unsafe, how to work and report manual_steps, and what to do when rollback_release refuses

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when changing the database schema - detect the repo's migration tool, ship a new migration in its layout, never edit an applied one, and avoid lock-unsafe DDL on a live table

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before handing off any change to an endpoint, job or migration — start the service from the task branch and exercise the change with real requests, real logs and real DB side effects

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a Java service reads or writes the database - JPA/Hibernate and Panache/Spring Data mapping, transaction boundaries, pagination and avoiding N+1 and entity-over-the-wire leaks

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Root-cause debugging discipline. Use when a test, build or pipeline fails, behaviour does not match expectations, a bug task arrives, or a task comes back in need_revision — before proposing any fix.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a component talks to the backend - go through the typed api client, type every response, and handle loading, success, and error states explicitly

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.