ccg_skill

This skill orchestrates Claude, Codex, and Gemini to decompose, parallelize tasks, and synthesize a cohesive backend and frontend solution.
  • TypeScript

9.3k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill yeachan-heo/oh-my-claudecode --skill ccg

  • SKILL.md2.7 KB

Overview

This skill implements a Claude-Codex-Gemini tri-model orchestration pattern that decomposes developer requests, runs backend and frontend work in parallel, and synthesizes a unified implementation. It is teams-first and designed for multi-agent code workflows where Claude acts as conductor, Codex handles backend/code tasks, and Gemini handles UI/design tasks. The pattern emphasizes parallel execution, clear role assignment, and a final integration step to reconcile interfaces and cross-cutting concerns.

How this skill works

On trigger, Claude immediately announces CCG mode, decomposes the request into backend, frontend, and synthesis tasks, and fans out parallel jobs: Codex (backend) and Gemini (frontend) run in background mode via MCP tools. Claude waits for both outputs, reconciles conflicts (API shapes vs component props), applies cross-cutting concerns (typing, auth, error handling), and emits integration glue code and a cohesive deliverable. If an MCP is unavailable, defined fallback subagents are used to preserve flow.

When to use it

  • Building a full-stack feature that requires coordinated API and UI work
  • Adding endpoints, data models, or security changes alongside React/Vue components
  • Refactoring where API shapes and component props must be reconciled
  • Parallelizing work to speed delivery while keeping a single orchestrator
  • Generating design-forward UI with large-context needs plus backend code

Best practices

  • Clearly describe backend vs frontend responsibilities in the initial prompt
  • Include relevant source files for context so Codex/Gemini can run independently
  • Choose appropriate agent roles (architect, designer, security-reviewer) for each task
  • Use background execution and wait_for_job to avoid blocking the orchestration
  • Review synthesized output for edge cases like auth flows, types, and error boundaries

Example use cases

  • Add a REST endpoint and a React user profile page with matching props and types
  • Create a new database model, migration, endpoint, and admin UI component in parallel
  • Perform a security audit on APIs while iterating on component styling and layout
  • Refactor API responses and update consuming UI components with a single integration pass
  • Produce design assets and long-context documentation for a complex UI while wiring backend services

FAQ

Fallback subagents are used: an oh-my-claudecode executor for backend or designer for frontend; if both are unavailable, Claude handles tasks directly.

How are conflicts between API shapes and component props resolved?

Claude synthesizes both outputs, reconciles types and shapes, and emits glue code such as adapters, fetch hooks, or prop transformations.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
ccg skill by yeachan-heo/oh-my-claudecode | VeilStrat