개발 스킬

Prepare bug reports for chengfeng-videocut by organizing reproduction steps, expected behavior, and minimal diagnostic evidence. Review a draft with sensitive information removed, then submit a GitHub Issue only after explicit confirmation, with checks for existing matching reports.

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

• Report a reproducible editing bug
• Review a bug report for sensitive information
• Submit a previously reviewed bug report

Write JSX, an HTML-like syntax within JavaScript, for Vue by checking how it differs from React JSX. Covers attribute conventions and JSX plugin configuration, with guidance for code migration and attribute type errors.

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

• Migrating React JSX code to Vue
• Investigating JSX attribute type errors
• Checking class and className usage

Guides Vue 3 development with TypeScript, covering state, component responsibilities, and data flow. Helps organize implementation and refactoring, then review performance once the required behavior works.

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

• Building Vue 3 screens with TypeScript
• Refactoring large components
• Clarifying state ownership and data flow

Create reusable Vue composables, functions that share reactive logic, accepting plain values, refs, or getters. Choose input types for reading or writing and normalize values so reactive effects track changes consistently.

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

• Build reusable Vue composables
• Update a document title when its input changes
• Create a counter with writable input

Helps troubleshoot Vue Router 4 navigation, including checks before changing pages, URL parameter changes, and component cleanup. Use it to investigate redirect loops, stale data, and asynchronous work during navigation.

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

• Investigating infinite redirect loops
• Reviewing data updates when URL parameters change
• Checking asynchronous API calls during navigation

Guides maintenance of Vue 3 components written with Options API. Covers TypeScript typing, access to component data through this, lifecycle methods, and accidental sharing of state between component instances.

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

• Adding types to Options API components
• Investigating this binding in methods
• Reviewing access to data in lifecycle hooks

Set up Pinia stores, the shared data containers used in Vue applications, and troubleshoot state updates. Covers startup errors, destructuring that breaks screen updates, method context, and using URLs for temporary filters.

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

• Investigating Pinia startup errors
• Fixing screen updates after destructuring store values
• Checking state returned by setup stores

Diagnose Vue 3 problems through symptom-based references covering state updates, component events, asynchronous failures, and rendering errors. Includes server-rendered pages whose HTML does not match what the browser expects when it takes over.

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

• Investigating a screen that no longer updates
• Tracking duplicate or missing component events
• Diagnosing asynchronous loading failures

Helps separate business rules from frameworks, databases, user interfaces, and infrastructure. Uses Robert C. Martin-inspired architecture rules to guide decisions about responsibilities, dependency direction, and boundaries when technologies change.

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

• Separating business rules from database code
• Reviewing dependency direction between layers
• Organizing use cases and entities

Plan safer changes to hard-to-test existing code using rules inspired by Michael Feathers. Consider tests that capture current behavior, ways to separate dependencies, and techniques for adding or wrapping methods while reducing risk incrementally.

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

• Planning changes to existing code without tests
• Capturing current behavior in tests
• Separating dependencies to make testing easier

Support engineering decisions with practical rules for reducing duplicated knowledge, keeping components independent, automating work, and getting fast feedback. Use these perspectives to assess design choices, prototypes, and code changes that need to accommodate future change.

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

• Reviewing design choices for future changes
• Reducing duplicated knowledge across code
• Considering automation for repeated work

Identify structural problems in code and choose focused refactoring techniques while preserving behavior. Drawing on Refactoring.Guru-inspired rules, this skill helps match problems to appropriate changes and keep cleanup from expanding into uncontrolled redesign.

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

• Diagnosing structural problems in code
• Choosing focused refactoring techniques
• Keeping cleanup from expanding into uncontrolled redesign

Support business application design with rules inspired by Martin Fowler. Compare ways to organize application layers, place business logic, manage database interactions, and transfer data, using established patterns to reason through structural choices.

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

• Reviewing layers in a business application
• Choosing how to organize business logic
• Considering patterns for database interactions

Guide domain-driven design implementation, which organizes code around business concepts. Apply Vaughn Vernon-inspired rules to aggregate boundaries, business constraints, domain events, repositories, application services, and integration between distinct business contexts.

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

• Define aggregate boundaries and business constraints
• Review domain events and repositories
• Design application services

Model complex business domains using domain-driven design, an approach that organizes software around business concepts. Inspired by Eric Evans, this skill guides shared terminology, model boundaries, aggregates, and the relationships between different contexts.

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

• Modeling complex business domains
• Aligning shared terminology and model boundaries
• Considering aggregates, repositories, and domain services

Apply domain-driven design, an approach to modeling software around business concepts, without excessive ceremony. Inspired by Vaughn Vernon, this skill guides domain boundaries, relationships between models, aggregates, and events representing business occurrences.

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

• Organizing business areas and model boundaries
• Mapping relationships between bounded contexts
• Considering aggregates and domain events

Apply construction rules inspired by Steve McConnell when designing routines, variables, classes, and control flow. The skill guides implementation decisions, defensive programming to handle unexpected conditions, coding standards, and implementation testing.

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

• Designing routines and classes
• Reviewing variables and control flow
• Handling unexpected inputs and conditions

Review module boundaries, APIs, and abstractions using John Ousterhout-inspired design rules. Use it to reduce software complexity, decide which implementation details to hide, and reconsider interfaces that leave too much work to their callers.

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

• Review module boundaries
• Reconsider API responsibilities
• Decide which implementation details to hide

Improve existing code structure without changing observable behavior. Drawing on Martin Fowler-inspired rules, this skill guides small refactoring steps, cleanup supported by tests, and separation of structural improvements from feature changes.

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

• Cleaning up code without changing behavior
• Improving code in small steps supported by tests
• Separating refactoring from feature changes

Guide data system design with Martin Kleppmann-inspired rules. Review reliability, growth, data consistency, replication, transactions, and schema changes, including decisions about data ownership and how events, streams, and batch jobs move and process information.

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

• Clarify data ownership and consistency requirements
• Review data replication and partitioning
• Design event flows, streams, and batch processing

Review everyday code for readability and testability using rules inspired by Robert C. Martin. Examine names, small functions, control flow, responsibilities, comments, error handling, and tests to guide practical improvements to implementation quality.

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

• Reviewing variable and function names
• Reconsidering large functions and their responsibilities
• Making control flow easier to read

Create or update reusable skills for Codex by organizing task instructions, scripts, reference documents, and templates. The workflow covers defining use cases, writing SKILL.md, validating the structure, and packaging files for distribution.

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

• Turn recurring work into a reusable agent skill
• Organize scripts, reference documents, and templates
• Revise an existing skill after practical use

Find the GJC SDK reference documents for understanding session commands, embedding GJC within a process, and building applications. This advisory index points to background reading without running workflows or changing configuration.

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

• Finding an overview of the GJC SDK
• Understanding the gjc sdk session commands
• Reading about embedding GJC within a process

Manage live GJC SDK sessions from the command line: list sessions, inspect activity, send prompts, follow results and transcripts, or close a session. Connections go through the SDK broker, which keeps connection credentials out of output.

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

• Find sessions within a repository or working directory
• Send a prompt to a live session
• Follow results and saved transcripts