개발 스킬

Expand a structure outline into a detailed implementation plan grounded in research, design decisions, and source code. Specify changes, code examples, independently testable phases, runnable checks, and concrete criteria for automated and manual verification.

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

• Turn a structure outline into an implementation plan
• Specify code changes for each implementation phase
• Define verification commands and acceptance criteria

Prepare Git worktrees, separate working directories for task branches, using shared settings and local overrides. Copy configured files, run setup commands, and coordinate multiple repositories so implementation can begin in the prepared workspace.

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

• Prepare a separate working directory for a task
• Copy environment files and local settings
• Coordinate worktrees across multiple repositories

Refine an existing technical design document through focused feedback and one question at a time. Compare design options, resolve decisions, and update diagrams and explanations covering both component interactions and code structure.

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

• Revise a technical design document based on feedback
• Resolve open design decisions one at a time
• Clarify component interactions and code structure

Revise an existing implementation plan using feedback and related project documents. Check file paths and code examples, adjust phases, and clarify success criteria with runnable automated checks and specific manual verification steps where needed.

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

• Reorganizing implementation phases after review
• Correcting code examples and file paths in a plan
• Clarifying success criteria and verification steps

Create a Technical Design Document from tickets, research, or other product context through guided questions. It settles system architecture first, then code structure, recording agreed decisions with diagrams, signatures, and sketches in a coherent design document.

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

• Turning tickets and research into a technical design
• Comparing component interactions and data flows
• Planning code structure and function signatures

Turn existing product context into a technical design document through guided discussion. Settle system interactions first, then code structure, using diagrams and signatures to make decisions and tradeoffs clear for review.

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

• Turning a ticket or research document into a technical design
• Comparing system architecture options
• Agreeing on code structure before implementation

Review an existing design discussion without waiting for feedback. Check unstated assumptions against the codebase, examine implementation patterns, and add missing options or questions while preserving the agreed scope and resolved decisions.

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

• Checking unstated assumptions in a design discussion
• Verifying implementation patterns against existing code
• Finding missing options in design questions

Automate browser tasks from the terminal using the chrome-devtools-mcp CLI. Inspect page elements, click and fill forms, navigate tabs, capture screenshots, and investigate network requests, console messages, performance, and memory through shell commands.

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

• Automating form input and page navigation
• Capturing page or element screenshots
• Investigating network requests and console errors

Integrate Yjs collaborative editing with durable streams over HTTP. Configure document updates and participant presence, manage connection lifecycles, and handle synchronization events, with guidance on required dependencies, binary data formats, and cleanup.

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

• Adding HTTP synchronization to a Yjs collaborative editor
• Sharing participant presence alongside document updates
• Controlling connections and monitoring synchronization status

Prepare Riptide workspace settings by inspecting a project and proposing configuration files. Define Git worktrees, separate working directories for tasks, along with setup commands, copied files, and shared or machine-specific settings, then save approved configurations.

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

• Configure a task workspace for a single repository
• Coordinate workspaces across related repositories
• Separate shared settings from machine-specific overrides

Turn a task and its referenced materials into research questions about how an existing codebase works. Produce a document for another research agent, preserving relevant links, paths, and dependencies while focusing on current behavior.

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

• Preparing questions before investigating existing code
• Organizing research around a ticket and referenced files
• Handing research scope and source pointers to another agent

Revise an existing implementation outline using feedback, supporting documents, and codebase findings. Reorganize phases, adjust scope, incorporate answered questions, and define checks so each phase can be verified independently.

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

• Reorganizing implementation phases after feedback
• Updating scope and excluded work
• Incorporating answers to open questions

Review the changes made during a session and organize them into focused Git commits. The skill groups related files, writes messages explaining why changes were made, and stages specific files while excluding unrelated material.

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

• Commit the work completed during a session
• Split several changes into focused commits
• Write commit messages that explain the reasons for changes

Create and review Storybook examples using real production UI components. Separate display components from business logic, add local interaction demos when needed, and apply consistent rules for component composition, demo names, file placement, and navigation groups.

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

• Creating static Storybook examples for production UI components
• Adding dialog and toggle interaction demos
• Reviewing component boundaries in .stories.tsx pull requests

Repair conflicting Drizzle migrations after a rebase by inspecting migration history, SQL files, and schema snapshots. The skill guides cleanup, regeneration of database change scripts, local application, and verification against the upstream branch.

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

• Repairing conflicting migrations after a rebase
• Removing duplicate migration history entries
• Regenerating migrations for intended schema changes

Revise an existing codebase research document using feedback and additional investigation. Explain current behavior and component connections with file and line references, integrating findings into a coherent document rather than an edit log.

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

• Adding findings to an existing codebase research document
• Correcting explanations based on feedback
• Tracing data flow and component connections

Refine an existing technical design document through focused discussion. Compare design options with diagrams and code sketches, resolve one decision at a time, and update the relevant sections so the document consistently reflects agreed choices.

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

• Incorporating feedback into an existing technical design document
• Comparing unresolved architecture and code structure options
• Clarifying data flow and component responsibilities with diagrams

Tighten React component props, the inputs passed to components, to match real application usage. Remove unsupported states and unnecessary fallback logic, then adapt tests and Storybook examples to the stricter types.

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

• Review overly optional React component inputs
• Require handlers for visible buttons and menu items
• Remove fallback logic for unsupported states

Design, implement, review, and test Effect v4 applications with explicit dependencies and typed errors. Covers external service connections, data decoding, resource cleanup, concurrency, logging, and tests that replace dependencies at meaningful system boundaries.

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

• Design services with explicit dependencies
• Review error handling, logs, and traces
• Implement database and external API connections

Write and review React components by replacing direct useEffect calls with five purpose-specific patterns. It guides state calculations, data fetching, event handling, and component resets, with useMountEffect for external setup when a component first appears.

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

• Writing new React components
• Refactoring existing useEffect calls
• Reviewing PRs that introduce useEffect

Inspect GitHub pull requests, read review conversations, and investigate failed automated checks with dedicated scripts. Get consolidated status reports, unresolved discussion threads, and failing job or step logs, with full logs saved for further inspection.

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

• Checking pull request status in one report
• Reading unresolved review conversations
• Investigating failed CI jobs and steps

Turn a change request and research findings into a design discussion document. Compare the current and proposed behavior, explain architectural choices with focused visuals, and record decisions and their reasoning as the user provides feedback.

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

• Compare design options before implementation
• Clarify current behavior and the desired outcome
• Discuss architecture using diagrams and code examples

Compare function call structures across Git commits, branches, or working files to support code review. Display call trees and trace paths from an entry function to a target function, with support for 22 languages.

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

• Compare function calls before and after a change
• Review call structure changes between branches
• Trace paths from an entry function to a target

Review a codebase for modules whose interfaces expose too much complexity, then compare refactoring options in a visual HTML report. Explore a selected option through questions about constraints, dependencies, module design, and testing.

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

• Finding refactoring options in frequently changed code
• Comparing architecture options with before-and-after diagrams
• Exploring changes that make modules easier to test