개발 스킬

Plan a feature that spans database, backend, frontend, testing, and deployment. The workflow organizes API-first design, implementation, integration and security checks, and operations work into phases with expected artifacts and success criteria.

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

• Planning a feature that spans application layers
• Defining API contracts before implementation
• Coordinating implementation, integration, and end-to-end testing

Plan an incremental modernization of a legacy system using the strangler fig pattern, which replaces parts gradually while old and new systems coexist. The workflow covers risk assessment, test and integration contracts, rollout, and migration documentation.

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

• Assessing risks in a legacy system modernization
• Planning a gradual replacement of system components
• Preserving integration behavior during migration

Get practical guidance for Haskell design and implementation, from expressive types and pure functions to concurrency and performance. It helps structure reliable programs, handle effects clearly, and improve project organization with examples and verification steps.

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

• Designing domain rules with strong types
• Separating pure logic from input and output
• Choosing safe concurrency patterns

Use this skill to plan and build Flutter applications with Dart across mobile, web, desktop, and embedded platforms. It covers architecture, widgets, state management, animations, testing, native integrations, and performance, helping shape implementation and deployment for the target platforms.

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

• Planning a Flutter app architecture with Riverpod
• Building responsive Flutter interfaces and animations
• Integrating native iOS or Android features

Investigate production incidents and recurring errors by organizing logs, timestamps, and affected services. Narrow down causes with targeted checks, validate findings with evidence, and propose fixes, tests, and prevention measures.

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

• Investigating a production incident
• Finding the cause of recurring errors
• Reviewing logs and traces across services

Use this skill to design, build, or review C#/.NET backends such as APIs and MCP servers. It covers async code, dependency injection, Entity Framework Core, Dapper, configuration, caching, error handling, and xUnit testing patterns.

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

• Designing a .NET Web API
• Reviewing C# backend code
• Choosing EF Core or Dapper data access

Use this skill to start a Python backend with FastAPI. It provides project structure and implementation patterns for asynchronous REST APIs, dependency injection, middleware, and error handling, including setups that use PostgreSQL or MongoDB.

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

• Starting a new FastAPI backend project
• Structuring an asynchronous Python REST API
• Setting up a FastAPI service with PostgreSQL

Supports GraphQL API architecture, from schema and federation design to resolver performance, caching, authorization, and real-time subscriptions. It helps plan scalable systems, integrate services, test schema changes, and evolve APIs while considering security and client compatibility.

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

• Designing a federated GraphQL architecture
• Reducing N+1 queries and improving API speed
• Planning authorization for GraphQL fields

Build and improve Go services, command-line tools, and microservices using Go 1.21 and later. Get guidance on concurrency, architecture, testing, profiling, and production readiness, including ways to investigate latency, memory use, and reliability.

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

• Designing a concurrent Go worker pool
• Improving a Go service's memory use or speed
• Planning a Go microservice architecture

Use this skill to investigate unclear software failures systematically. It combines error reports, logs, metrics, and traces with ranked cause hypotheses, targeted instrumentation, and a validation plan, so you can narrow down what is failing and decide how to test a proposed fix.

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

• Investigating an intermittent production error
• Ranking possible causes from logs and traces
• Choosing where to add debugging instrumentation

Create a tailored onboarding plan for a new technical team member, covering environment setup, codebase orientation, team integration, learning resources, and 30-, 60-, and 90-day milestones. The plan can account for the role, seniority, location, and team context.

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

• Planning a developer’s first 90 days
• Preparing a new hire’s first-week checklist
• Adapting onboarding for a remote team

Build Godot 4 games with practical GDScript patterns for signals, scene architecture, game state, and performance. The skill helps design and implement game systems while following explicit typing and other stated code style conventions.

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

• Building a game in Godot 4
• Designing scene architecture
• Implementing game systems in GDScript

Design systems that store changes as immutable events, with separate models for writing and reading data. Use it to plan audit histories, time based queries, projections, and multi step workflows that may need compensation when a step fails.

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

• Keeping a complete audit history
• Querying what a system state was at a past time
• Separating read and write models

Coordinate a Git workflow from change review and testing through commit preparation, branch checks, and pull request drafting. Get structured guidance for verifying collaboration readiness, including Conventional Commit messages and feature branch or trunk-based workflows.

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

• Preparing reviewed changes for a pull request
• Creating Conventional Commit messages
• Choosing a feature branch or trunk-based workflow

Handle complex Git histories and branch workflows with rebase, cherry-pick, bisect, worktrees, and reflog. The skill helps clean up commits, move selected changes, find the commit that introduced a bug, work across branches, and recover lost work.

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

• Cleaning up commits before a pull request
• Applying a fix to multiple branches
• Finding which commit introduced a bug

Use this skill to plan or improve .NET APIs and backend systems. It helps apply modern C#, ASP.NET Core, data access, caching, performance, testing, and architecture patterns, with practical guidance for maintainable production code.

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

• Planning an ASP.NET Core API architecture
• Reviewing asynchronous C# code
• Choosing EF Core or Dapper data access patterns

Plan incremental package upgrades by assessing breaking changes, compatibility, and risk. Get a prioritized update plan, migration steps for major changes, regression test guidance, and rollback procedures to help keep a project stable while dependencies are updated.

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

• Prioritizing package updates by risk and importance
• Reviewing breaking changes before an upgrade
• Planning regression tests for dependency updates

Plan event storage for event-sourced applications by comparing technologies and shaping schemas and access patterns. The guidance covers appending and reading event streams, ordering, concurrency checks, subscriptions, snapshots, and scaling considerations, with examples for common storage options.

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

• Choosing an event store for a new event-sourced system
• Designing a schema for event streams and snapshots
• Planning reliable event subscriptions and checkpoints

Carry out incomplete tasks from a Conductor track plan. Follow the project workflow for test-driven development, verification checkpoints, commits, and progress updates, with task and phase status recorded as implementation proceeds.

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

• Implementing the next task in a Conductor track
• Following a project’s configured TDD workflow
• Tracking task and phase completion

Improve pull request descriptions by explaining the change, its intent, tests, risks, and rollout notes. The skill also helps organize reviewer guidance and checklists, and suggests ways to make a change easier to understand and review.

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

• Drafting a clear pull request description
• Summarizing a change set for reviewers
• Organizing test results and rollout risks

Assess a codebase for technical debt such as duplication, complexity, weak tests, and outdated dependencies. Estimate maintenance and delivery impact, rank risks, and create a measurable remediation roadmap with practical short- and long-term actions.

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

• Assessing code health and maintenance costs
• Prioritizing refactoring work
• Planning a technical debt roadmap

Investigate unclear software failures by collecting observability data such as logs, traces, and performance metrics, then ranking possible causes. It helps choose targeted instrumentation, propose a fix, and outline validation and prevention steps.

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

• Investigating failures with unclear causes
• Correlating logs, traces, and performance changes
• Ranking hypotheses before testing a fix

Use Solidity examples and guidance to build common DeFi protocol components, including staking rewards, automated market makers, governance, lending, and flash loans. The skill helps shape implementation steps and verification practices for smart contract projects.

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

• Starting a staking rewards contract
• Exploring an automated market maker design
• Planning governance or lending contract components

Turn a feature, bug fix, maintenance task, or refactor into a reviewed specification and a phased implementation plan. The skill gathers requirements, checks the project's Conductor context, and organizes the approved work as a track.

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

• Planning a new feature with acceptance criteria
• Recording bug reproduction steps and expected behavior
• Breaking maintenance or refactoring into verifiable phases