개발 스킬

Investigate bugs, failing tests, and unexpected behavior by reproducing the issue, narrowing where it originates, and testing a specific hypothesis. Then verify that the proposed fix addresses the proven cause, rather than only hiding the symptom.

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

• Investigating a failing test
• Tracing an error after a code change
• Finding the cause of intermittent behavior

Use this skill to assess architecture, technology choices, delivery capacity, infrastructure, and technical debt in business terms. It helps compare build and buy options, surface costs and assumptions, and judge a technical plan before committing.

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

• Comparing whether to build or buy a capability
• Reviewing an architecture or technology choice
• Assessing delivery capacity and project risk

Design and review APIs around the concepts their users need. Shape resources, errors, pagination, and versioning, and assess whether a proposed change could break existing consumers so teams can plan compatibility and deprecation clearly.

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

• Design a new API interface
• Review an API before release
• Assess whether a change breaks consumers

Use a red, green, refactor workflow: write a test that fails for the intended behavior, make the smallest change that passes, then clean up. Apply it to features, bug fixes, regression tests, and decisions about what behavior needs coverage.

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

• Starting feature implementation with a failing test
• Reproducing a bug before fixing it
• Changing difficult code with behavior checks

Turn a specification or requirement into a step-by-step implementation plan with explicit changes, proof of completion, and review checkpoints. Then track execution in order, updating the plan when real conditions differ from expectations.

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

• Planning a change that spans several files
• Preparing a task for another agent or teammate
• Keeping a growing implementation within scope

Use this skill to isolate repository work in a separate branch or worktree, keep it aligned with its base, and prepare it for review. It guides clean integration through merging, rebasing, or splitting work into smaller branches.

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

• Isolating a feature from current work
• Running parallel efforts in one repository
• Preparing a finished change for review

Assess code and systems to separate deliberate technical debt from accumulated mess, outdated assumptions, or personal taste. Measure where debt costs delivery time or causes incidents, then prioritize incremental fixes and explain their business value to decision makers.

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

• Prioritizing technical debt by its ongoing cost
• Deciding whether to fix or accept an awkward system
• Explaining remediation value to non-engineers

Clarify the outcome behind a request before implementation, then compare genuinely different approaches by cost, tradeoffs, and assumptions. It helps teams make a reasoned recommendation for a feature or behavior change, especially when the request is ambiguous.

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

• Clarifying an ambiguous feature request
• Comparing approaches before implementation
• Pressure-testing a design decision

Design a repository’s multi-agent structure by assigning exclusive file areas, defining builder and reviewer roles, and checking ownership rules with a CI script. Use it to divide work, prevent overlapping edits, and decide whether another agent is needed.

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

• Dividing repository work among agents
• Defining agent roles and file ownership
• Auditing overlapping agent responsibilities

Review specified files for design system usage, replace legacy @trycompai/ui components and lucide-react icons with available @trycompai/design-system equivalents, and run the app type check to verify the migration.

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

• Migrating legacy UI components
• Replacing lucide-react icons with Carbon icons
• Checking specified files for design system compliance

Use this skill to investigate failed SDK generation from an OpenAPI spec. It helps classify errors, identify likely root causes, and outline whether an overlay can address them, the spec needs changes, or a human decision is required.

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

• Finding the cause of a failed Speakeasy SDK run
• Sorting OpenAPI errors by likely fix strategy
• Preparing action items for a generation failure

Write Trigger.dev v4 tasks with validated inputs, scheduled runs, retries, waits, and task-to-task triggers. The skill explains how to handle Result values returned by waiting for tasks and highlights patterns that the v4 SDK does not support.

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

• Creating a task with input validation
• Scheduling a task with a cron pattern
• Triggering one task from another and handling its result

Get guidance for package and dependency work in a bun-based monorepo. It covers package boundaries, cross-package imports, build commands, type checks, linting, and the structure for adding a new package.

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

• Adding a dependency to one monorepo package
• Choosing whether code belongs in a shared package
• Running builds and checks across packages

Review specified files for outdated hook and API patterns, then replace them with the prescribed SWR hooks, API clients, or server API calls. The guidance covers data fetching, mutations, cache updates, and response handling, followed by a typecheck command.

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

• Auditing files for disallowed API and hook patterns
• Replacing raw fetch calls with the API client
• Migrating server actions and database mutations to API hooks

Build React forms with React Hook Form and Zod. The skill shows how to define validation schemas, connect fields, display errors, handle submission state, and manage complex or dynamic inputs.

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

• Building a validated sign-up or profile form
• Adding cross-field checks such as password confirmation
• Handling selectable or dynamically repeated fields

Structure data fetching so server pages provide initial data to client components, while SWR refreshes it and handles mutations through an API client. The guidance covers cache keys, server and client responsibilities, and URL based organization context.

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

• Building pages that render with server-fetched initial data
• Creating SWR hooks for API reads and mutations
• Keeping cached data separate by organization

Use this skill to define recurring Trigger.dev tasks with cron schedules, set time zones and environments, and manage schedules through code or the dashboard. It also explains schedule payloads and common conditions that prevent a task from running.

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

• Defining a recurring cron task
• Scheduling runs for a particular time zone
• Creating per-user schedules with external IDs

Keep Prisma schema changes, database migrations, and generated client types in sync across applications. The guidance also sets conventions for readable, prefixed CUID IDs, including short unique prefixes and the required database function cast.

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

• Updating a Prisma schema and creating its migration
• Regenerating Prisma client types across apps
• Choosing prefixed IDs for new data models

Set up Better Auth for TypeScript applications, including server and client configuration, database adapters, sessions, email and social sign-in, and plugins. The guide also highlights environment variables, schema generation, and security settings to review.

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

• Configuring Better Auth in a TypeScript app
• Connecting an ORM or database adapter
• Setting up sessions and cookie storage

Use these guidelines for visible UI changes to plan layouts across mobile, tablet, desktop, and large screens. They cover mobile-first breakpoints, design-system components, overflow, touch targets, long content, and checks at four screen widths.

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

• Building a responsive page or component
• Updating a table, toolbar, or form
• Checking a layout at several screen widths

Review changed code after implementation for readability, repeated logic, inconsistent patterns, unsafe boundary handling, redundant casts, and dead code. The checklist guides cleanup and calls for a TypeScript type check after fixes.

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

• Reviewing files after implementing a feature
• Cleaning up code after a bug fix
• Checking changed files before committing

Build interfaces that follow Trigger.dev v4 task runs as they happen. The skill covers subscriptions to run status, metadata, tagged runs, and streamed data from backend code or React hooks, using scoped access tokens for reads and triggers.

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

• Showing task status and progress in a React interface
• Subscribing to runs by ID, tag, or batch
• Displaying streamed task output as it arrives

Apply advanced Trigger.dev task patterns for concurrency, retries, idempotency, progress tracking, machine sizing, and run management. The guidance helps structure resilient tasks and monitor execution details, including cost, duration, logs, and child task progress.

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

• Limiting task concurrency with queues
• Configuring retries and fatal error handling
• Preventing duplicate payment or critical operations

Prepare an isolated worktree for a feature, ticket, or bugfix by following the repository’s setup conventions for environment files, databases, dependencies, and development servers. It also explains how to avoid conflicts when multiple worktrees are active.

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

• Starting a feature in a new worktree
• Setting up a branch for a Linear ticket
• Running development servers across worktrees