개발 스킬

Plan major framework and library upgrades by reviewing compatibility, peer dependencies, and breaking changes. Get an incremental upgrade path, testing guidance, automation options, and rollback considerations to reduce surprises during modernization.

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

• Planning a framework major-version upgrade
• Checking compatibility and peer dependency conflicts
• Modernizing legacy libraries incrementally

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

Investigate errors, failed tests, and unexpected behavior by gathering messages, logs, and reproduction steps. The skill helps isolate the failure, test likely causes, propose a focused fix, explain the evidence, and suggest verification and prevention steps.

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

• Tracing the cause of a test failure
• Investigating unexpected application behavior
• Reproducing and isolating an error

Use this skill to investigate slow database workloads and plan improvements to queries, indexes, caching, and scaling. It helps analyze performance bottlenecks, consider migration options, and outline monitoring and benchmarking steps across common database systems.

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

• Investigating slow queries and database bottlenecks
• Planning indexes for frequently used queries
• Reducing repeated ORM or GraphQL queries

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

Use this skill to check whether a Conductor project has its expected files and track structure, and whether status markers and track IDs follow the documented patterns. It helps verify project context after setup, during troubleshooting, or before implementation.

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

• Checking required Conductor project files
• Reviewing track folders after project setup
• Finding inconsistent status markers

Set up a project’s foundational Conductor documents through guided questions. Capture its purpose, product guidelines, technology stack, workflow preferences, and selected code style guides, with an option to resume an unfinished setup.

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

• Starting Conductor documentation for a new project
• Recording the goals and users of an existing project
• Agreeing on workflow and code review practices

Plan and implement CQRS, a pattern that separates models for changing data from models for reading it. Use it to handle different read and write workloads, build event-sourced systems, shape projections, and check performance, consistency, recovery, and failure behavior.

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

• Separating read and write models
• Scaling reads independently from writes
• Building an event-sourced system

Choose a database approach and design its data model, schema, indexes, and scaling strategy around application needs. The skill supports new systems and re-architecture, and helps plan migrations, backups, and rollout or rollback steps.

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

• Choosing a database for a new application
• Designing a schema for a multi-tenant service
• Planning a low-downtime database migration

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

Develop and optimize Django 5.x applications with guidance on architecture, async views, ORM queries, and ecosystem tools such as DRF, Celery, and Django Channels. The skill also covers testing, security, performance, and deployment decisions.

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

• Optimizing Django ORM queries
• Designing a scalable Django application
• Adding async views or real-time features

Write and refactor modern C++ using features such as RAII, smart pointers, templates, move semantics, and STL algorithms. Get guidance on memory safety, exception safety, concurrency, and performance, with code and supporting project artifacts shaped around the requested task.

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

• Refactoring legacy C++ code
• Reviewing memory ownership and safety
• Applying move semantics or templates

Use Conductor’s context-driven development approach to set up and maintain project context alongside code. Understand how product.md, tech-stack.md, and workflow.md fit together, and keep project guidance current across planning, implementation, and AI-assisted sessions.

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

• Set up context artifacts for a new project
• Understand how Conductor context files relate
• Review project context before implementation

Use this skill to identify high impact cleanup opportunities, remove duplication, and simplify modules while keeping changes small and reviewable. It produces a prioritized refactoring plan, explains risks, and outlines targeted checks for stability.

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

• Reducing duplication across a large codebase
• Simplifying modules before adding features
• Planning a staged cleanup of accumulated code debt

Review code changes for security flaws, performance concerns, configuration risks, and maintainability. Combine automated analysis with contextual review, then provide prioritized, actionable feedback and examples to help teams improve reliability before changes reach production.

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

• Reviewing an API for security and performance issues
• Assessing a database migration for production risks
• Checking deployment configuration for reliability concerns

Review system designs and major code changes for architectural risks and tradeoffs. Get guidance on service boundaries, scalability, resilience, security, and maintainability, along with concrete improvement ideas and validation steps.

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

• Review a microservice design
• Assess event sourcing tradeoffs
• Check service boundaries

Use this skill to plan and build blockchain applications, including smart contracts, DeFi protocols, NFT platforms, and DAOs. It covers Web3 frontends, blockchain infrastructure, security review, and integrations across several blockchain ecosystems.

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

• Designing a DeFi lending protocol
• Building an NFT marketplace
• Planning DAO governance contracts

Assess technical debt across code, architecture, tests, documentation, and infrastructure. Estimate maintenance costs, delivery impact, and risks, then create a measurable remediation roadmap with quick wins, longer-term work, and prevention measures.

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

• Finding code duplication and complexity hotspots
• Estimating the cost of recurring maintenance problems
• Prioritizing refactoring work by risk and impact

Plan and carry out AngularJS-to-Angular migrations, from choosing a rewrite or gradual hybrid approach to updating components, services, routing, and forms. Use it to assess risks, organize milestones, and validate an incremental transition.

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

• Planning an AngularJS-to-Angular migration
• Running AngularJS and Angular side by side
• Rewriting directives and controllers as components

Use this skill to coordinate complex feature delivery across services and teams, from requirements and architecture through implementation, testing, rollout, and monitoring. It structures the work into phases and prepares deployment, rollback, and documentation plans.

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

• Coordinating a feature across multiple services
• Planning requirements, architecture, and implementation phases
• Preparing a gradual rollout and rollback plan

Design asynchronous Python systems for APIs and I/O-heavy work such as network or database calls. Choose task, queue, or pool patterns, and account for timeouts, cancellation, backpressure, errors, testing, and debugging.

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

• Handling multiple API requests concurrently
• Designing an async web service
• Processing database or network I/O without blocking

Plan or refactor backend systems using Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Define domain boundaries, modules, interfaces, and dependency rules, then outline migration steps and checks for maintainable, testable code.

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

• Designing a new complex backend system
• Refactoring a tightly coupled application
• Defining modules and dependency rules

Turn component documentation into a deployment view of a system. Map components to containers such as applications, databases, and queues, then document their interfaces, dependencies, infrastructure needs, and communication in Mermaid diagrams and API specifications.

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

• Mapping components to deployment containers
• Documenting container APIs with OpenAPI or Swagger
• Creating a Mermaid C4 container diagram

Design backend services and APIs by defining service boundaries, contracts, and communication patterns. Get guidance on REST, GraphQL, or gRPC, resilience, security, observability, testing, and rollout planning for systems that need to scale and remain maintainable.

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

• Designing an API contract for a new service
• Planning a microservices structure for a SaaS product
• Choosing event-driven service communication