Coding standards, frameworks, refactoring, and code review (16.6K skills)
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.