[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CJE5SXSW14APAS204QDNCS":3,"skill-same:01M7CJE5SXSW14APAS204QDNCS":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M7CJE5SXSW14APAS204QDNCS","turborepo",null,"Turborepo expert guidance. Use when setting up or optimizing monorepo builds, configuring task caching, remote caching, parallel execution, or the --affected flag for incremental CI.","rossboyd\u002Fquickque","rossboyd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3195729?v=4","01M7CG99NTNRFV0TWTZX9JY9CQ","rbyd","01M7CG99PH4WEP5P45VTBNPDB0",0,"MIT","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fturborepo\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: turborepo\ndescription: Turborepo expert guidance. Use when setting up or optimizing monorepo builds, configuring task caching, remote caching, parallel execution, or the --affected flag for incremental CI.\nmetadata:\n  priority: 5\n  docs:\n    - \"https:\u002F\u002Fturborepo.dev\u002Fdocs\"\n  sitemap: \"https:\u002F\u002Fturborepo.dev\u002Fsitemap.xml\"\n  pathPatterns: \n    - 'turbo.json'\n    - 'turbo\u002F**'\n  bashPatterns: \n    - '\\bturbo\\s+(run|build|test|lint|dev)\\b'\n    - '\\bnpx\\s+turbo\\b'\n    - '\\bbunx\\s+turbo\\b'\n---\n\n# Turborepo\n\nYou are an expert in Turborepo v2.8 — \"the build system for agentic coding\" — a high-performance build system for JavaScript\u002FTypeScript monorepos, built by Vercel with a Rust-powered core.\n\n## Key Features\n\n- **Task caching**: Content-aware hashing — only rebuilds when files actually change\n- **Remote caching**: Share build caches across machines and CI via Vercel\n- **Parallel execution**: Uses all CPU cores automatically\n- **Incremental builds**: `--affected` flag runs only changed packages + dependents\n- **Pruned subsets**: Generate minimal monorepo for deploying a single app\n- **Dependency graph awareness**: Understands package relationships\n- **Git worktree cache sharing**: Automatically shares local cache across worktrees (2.8+)\n- **Devtools**: Visual package and task graph explorer via `turbo devtools` (2.8+)\n- **Composable configuration**: Extend `turbo.json` from any package, not just root (2.7+)\n- **AI-enabled docs**: `turbo docs` returns markdown responses optimized for AI agents (2.8+)\n\n## Setup\n\n```bash\nnpx create-turbo@latest\n# or add to existing monorepo:\nnpm install turbo --save-dev\n# upgrade existing Turborepo:\nnpx @turbo\u002Fcodemod migrate\n```\n\n## turbo.json Task Pipeline\n\nThe `turbo.json` file defines your task dependency graph. Here are comprehensive examples:\n\n### Basic pipeline\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Fturborepo.dev\u002Fschema.json\",\n  \"tasks\": {\n    \"build\": {\n      \"description\": \"Compile TypeScript and bundle the application\",\n      \"dependsOn\": [\"^build\"],\n      \"outputs\": [\".next\u002F**\", \"dist\u002F**\"]\n    },\n    \"test\": {\n      \"description\": \"Run the test suite\",\n      \"dependsOn\": [\"build\"]\n    },\n    \"lint\": {\n      \"description\": \"Lint source files\"\n    },\n    \"dev\": {\n      \"cache\": false,\n      \"persistent\": true\n    }\n  }\n}\n```\n\n### Advanced pipeline with environment variables and inputs\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Fturborepo.dev\u002Fschema.json\",\n  \"globalDependencies\": [\".env\"],\n  \"globalEnv\": [\"CI\", \"NODE_ENV\"],\n  \"tasks\": {\n    \"build\": {\n      \"dependsOn\": [\"^build\"],\n      \"outputs\": [\".next\u002F**\", \"dist\u002F**\"],\n      \"env\": [\"DATABASE_URL\", \"NEXT_PUBLIC_API_URL\"],\n      \"inputs\": [\"src\u002F**\", \"package.json\", \"tsconfig.json\"]\n    },\n    \"test\": {\n      \"dependsOn\": [\"build\"],\n      \"outputs\": [\"coverage\u002F**\"],\n      \"env\": [\"TEST_DATABASE_URL\"]\n    },\n    \"test:unit\": {\n      \"dependsOn\": [],\n      \"outputs\": [\"coverage\u002F**\"]\n    },\n    \"lint\": {\n      \"inputs\": [\"src\u002F**\", \".eslintrc.*\"]\n    },\n    \"typecheck\": {\n      \"dependsOn\": [\"^build\"],\n      \"inputs\": [\"src\u002F**\", \"tsconfig.json\"]\n    },\n    \"db:generate\": {\n      \"cache\": false\n    },\n    \"dev\": {\n      \"cache\": false,\n      \"persistent\": true\n    },\n    \"clean\": {\n      \"cache\": false\n    }\n  }\n}\n```\n\n### Key Configuration\n\n- `dependsOn: [\"^build\"]` — Run `build` in dependencies first (`^` = topological)\n- `dependsOn: [\"build\"]` — Run `build` in the same package first (no `^`)\n- `outputs` — Files to cache (build artifacts)\n- `inputs` — Files that affect the task hash (default: all non-gitignored files)\n- `env` — Environment variables that affect the task hash\n- `cache: false` — Skip caching (for dev servers, codegen)\n- `persistent: true` — Long-running tasks (dev servers)\n- `globalDependencies` — Files that invalidate all task caches when changed\n- `globalEnv` — Env vars that invalidate all task caches when changed\n\n## Workspace Filtering\n\nRun tasks in specific packages or subsets of your monorepo:\n\n```bash\n# Single package\nturbo build --filter=web\n\n# Package and its dependencies\nturbo build --filter=web...\n\n# Package and its dependents (what depends on it)\nturbo build --filter=...ui\n\n# Multiple packages\nturbo build --filter=web --filter=api\n\n# By directory\nturbo build --filter=.\u002Fapps\u002F*\n\n# Packages that changed since main\nturbo build --filter=[main]\n\n# Combine: changed packages and their dependents\nturbo build --filter=...[main]\n\n# Exclude a package\nturbo build --filter=!docs\n\n# Packages matching a pattern\nturbo build --filter=@myorg\u002F*\n```\n\n### Filter syntax reference\n\n| Pattern | Meaning |\n|---------|---------|\n| `web` | Only the `web` package |\n| `web...` | `web` and all its dependencies |\n| `...web` | `web` and all its dependents |\n| `...web...` | `web`, its dependencies, and its dependents |\n| `.\u002Fapps\u002F*` | All packages in the `apps\u002F` directory |\n| `[main]` | Packages changed since `main` branch |\n| `{.\u002Fapps\u002Fweb}[main]` | `web` only if it changed since `main` |\n| `!docs` | Exclude the `docs` package |\n\n## CI Matrix Strategies\n\n### GitHub Actions — parallel jobs per package\n\n```yaml\nname: CI\non: [push, pull_request]\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 0 # Required for --affected\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: 22\n      - run: npm ci\n      - run: turbo build test lint --affected\n        env:\n          TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}\n          TURBO_TEAM: ${{ vars.TURBO_TEAM }}\n\n  deploy-web:\n    needs: build\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - run: npm ci\n      - run: turbo build --filter=web\n        env:\n          TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}\n          TURBO_TEAM: ${{ vars.TURBO_TEAM }}\n```\n\n### Dynamic matrix from workspace list\n\n```yaml\njobs:\n  detect:\n    runs-on: ubuntu-latest\n    outputs:\n      packages: ${{ steps.list.outputs.packages }}\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - id: list\n        run: |\n          PACKAGES=$(turbo ls --affected --output=json | jq -c '[.[].name]')\n          echo \"packages=$PACKAGES\" >> \"$GITHUB_OUTPUT\"\n\n  test:\n    needs: detect\n    if: needs.detect.outputs.packages != '[]'\n    runs-on: ubuntu-latest\n    strategy:\n      matrix:\n        package: ${{ fromJson(needs.detect.outputs.packages) }}\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - run: npm ci\n      - run: turbo test --filter=${{ matrix.package }}\n```\n\n### Remote caching in CI\n\n```bash\n# Set in CI environment\nTURBO_TOKEN=your-vercel-token\nTURBO_TEAM=your-vercel-team\n\n# Builds automatically use remote cache\nturbo build\n```\n\n## Watch Mode\n\nRun tasks in watch mode for development — re-executes when source files change:\n\n```bash\n# Watch a specific task\nturbo watch test\n\n# Watch with a filter\nturbo watch test --filter=web\n\n# Watch multiple tasks\nturbo watch test lint\n```\n\nWatch mode respects the task graph — if `test` depends on `build`, changing a source file re-runs `build` first, then `test`.\n\n### Persistent tasks vs watch\n\n- `persistent: true` in turbo.json: The task itself is long-running (e.g., `next dev`). Turbo starts it and keeps it alive.\n- `turbo watch`: Turbo re-invokes the task on file changes. Use for tasks that run and exit (e.g., `vitest run`, `tsc --noEmit`).\n\n## Boundary Rules\n\nEnforce architectural constraints across your monorepo with `boundaries` in turbo.json:\n\n```json\n{\n  \"boundaries\": {\n    \"tags\": {\n      \"apps\u002F*\": [\"app\"],\n      \"packages\u002Fui\": [\"shared\", \"ui\"],\n      \"packages\u002Futils\": [\"shared\"],\n      \"packages\u002Fconfig\": [\"config\"]\n    },\n    \"rules\": [\n      {\n        \"from\": [\"app\"],\n        \"allow\": [\"shared\"]\n      },\n      {\n        \"from\": [\"shared\"],\n        \"deny\": [\"app\"]\n      }\n    ]\n  }\n}\n```\n\nThis enforces:\n- Apps can import shared packages\n- Shared packages cannot import from apps\n- Violations produce build-time errors with `turbo boundaries`\n\n```bash\n# Check boundary compliance\nturbo boundaries\n\n# Add to your pipeline\n{\n  \"tasks\": {\n    \"check\": {\n      \"dependsOn\": [\"lint\", \"typecheck\", \"boundaries\"]\n    },\n    \"boundaries\": {}\n  }\n}\n```\n\n## Graph Visualization\n\nInspect your task dependency graph:\n\n```bash\n# Print graph to terminal\nturbo build --graph\n\n# Output as DOT format (Graphviz)\nturbo build --graph=graph.dot\n\n# Output as JSON\nturbo build --graph=graph.json\n\n# Open interactive graph in browser\nturbo build --graph=graph.html\n```\n\n### Dry run — see what would execute\n\n```bash\n# Show tasks that would run without executing them\nturbo build --dry-run\n\n# JSON output for programmatic use\nturbo build --dry-run=json\n```\n\nThe dry run output shows:\n- Each task that would execute\n- Cache status (HIT or MISS)\n- Dependencies and dependents\n- File hash used for caching\n\n## Devtools & Docs (2.8+)\n\n```bash\n# Visual package\u002Ftask graph explorer (hot-reloads on changes)\nturbo devtools\n\n# Search Turborepo docs from the terminal (returns agent-friendly markdown)\nturbo docs\n\n# Upgrade to latest Turborepo\nnpx @turbo\u002Fcodemod migrate\n```\n\n> **Note**: `turbo docs` output is optimized for AI coding agents — markdown format preserves context windows. The docs site also includes sample prompts for common tasks you can copy directly into your agent.\n\n## Composable Configuration (2.7+)\n\nPackage configs can now extend from any workspace package, not just the root:\n\n```json\n\u002F\u002F packages\u002Fui\u002Fturbo.json\n{\n  \"extends\": [\"@myorg\u002Fconfig\"],\n  \"tasks\": {\n    \"build\": {\n      \"outputs\": [\"dist\u002F**\"]\n    }\n  }\n}\n```\n\n## Common Commands\n\n```bash\n# Run build across all packages\nturbo build\n\n# Run only affected packages (changed since main branch)\nturbo build --affected\n\n# Run specific tasks in specific packages\nturbo build --filter=web\n\n# Run with remote caching\nturbo build --remote-cache\n\n# Prune monorepo for a single app deployment\nturbo prune web --docker\n\n# List all packages\nturbo ls\n\n# List affected packages\nturbo ls --affected\n```\n\n## Remote Caching\n\n```bash\n# Login to Vercel for remote caching\nturbo login\n\n# Link to a Vercel team\nturbo link\n\n# Now builds share cache across all machines\nturbo build  # Cache hits from CI, teammates, etc.\n```\n\n## Monorepo Structure\n\n```\nmy-monorepo\u002F\n├── turbo.json\n├── package.json\n├── apps\u002F\n│   ├── web\u002F           # Next.js app\n│   │   └── package.json\n│   ├── api\u002F           # Backend service\n│   │   └── package.json\n│   └── docs\u002F          # Documentation site\n│       └── package.json\n├── packages\u002F\n│   ├── ui\u002F            # Shared component library\n│   │   └── package.json\n│   ├── config\u002F        # Shared configs (eslint, tsconfig)\n│   │   └── package.json\n│   └── utils\u002F         # Shared utilities\n│       └── package.json\n└── node_modules\u002F\n```\n\n## --affected Flag\n\nThe most important optimization for CI pipelines:\n\n```bash\n# Only build\u002Ftest packages that changed since main\nturbo build test lint --affected\n```\n\nThis performs intelligent graph traversal:\n1. Identifies changed files since the base branch\n2. Maps changes to affected packages\n3. Includes all dependent packages (transitively)\n4. Runs tasks only for the affected subgraph\n\n## Microfrontends & Multi-App Composition\n\nTurborepo is the recommended orchestration layer for Vercel's Microfrontends architecture — composing multiple independently-deployed apps behind a single URL.\n\n### Monorepo Structure for Microfrontends\n\n```\nmy-platform\u002F\n├── turbo.json\n├── package.json\n├── apps\u002F\n│   ├── shell\u002F          # Layout \u002F shell app (owns top-level routing)\n│   ├── dashboard\u002F      # Micro-app: dashboard features\n│   ├── settings\u002F       # Micro-app: settings features\n│   └── marketing\u002F      # Micro-app: public marketing site\n└── packages\u002F\n    ├── ui\u002F             # Shared component library\n    ├── auth\u002F           # Shared auth utilities\n    └── config\u002F         # Shared tsconfig, eslint\n```\n\n### Independent Deploys\n\nEach micro-app is a separate Vercel project with its own build and deploy lifecycle:\n\n```bash\n# Deploy only the dashboard micro-app\nturbo build --filter=dashboard\n\n# Deploy all micro-apps in parallel\nturbo build --filter=.\u002Fapps\u002F*\n\n# Deploy only micro-apps that changed since main\nturbo build --filter=.\u002Fapps\u002F*...[main]\n```\n\n### Shared Packages Across Micro-Apps\n\nUse Turborepo's dependency graph to share code without coupling deploys:\n\n```json\n{\n  \"tasks\": {\n    \"build\": {\n      \"dependsOn\": [\"^build\"],\n      \"outputs\": [\".next\u002F**\", \"dist\u002F**\"]\n    }\n  }\n}\n```\n\nShared packages (`ui`, `auth`, `config`) are built first via `^build`, then each micro-app builds against the latest shared code. Remote caching ensures shared package builds are never repeated across micro-app deploys.\n\n### Multi-Zone Patterns\n\nNext.js multi-zones let each micro-app own a URL path prefix while sharing a single domain:\n\n```ts\n\u002F\u002F apps\u002Fshell\u002Fnext.config.ts\nimport type { NextConfig } from 'next'\n\nconst nextConfig: NextConfig = {\n  async rewrites() {\n    return [\n      { source: '\u002Fdashboard\u002F:path*', destination: 'https:\u002F\u002Fdashboard.example.com\u002Fdashboard\u002F:path*' },\n      { source: '\u002Fsettings\u002F:path*', destination: 'https:\u002F\u002Fsettings.example.com\u002Fsettings\u002F:path*' },\n    ]\n  },\n}\n\nexport default nextConfig\n```\n\nCombine with Turborepo boundary rules to enforce architectural isolation:\n\n```json\n{\n  \"boundaries\": {\n    \"tags\": {\n      \"apps\u002F*\": [\"micro-app\"],\n      \"packages\u002Fui\": [\"shared\"],\n      \"packages\u002Fauth\": [\"shared\"]\n    },\n    \"rules\": [\n      { \"from\": [\"micro-app\"], \"allow\": [\"shared\"] },\n      { \"from\": [\"shared\"], \"deny\": [\"micro-app\"] }\n    ]\n  }\n}\n```\n\n### When to Use Turborepo for Microfrontends\n\n| Scenario | Recommended? |\n|----------|-------------|\n| Multiple teams owning independent features | Yes — independent deploys + shared packages |\n| Single team, single app | No — standard Next.js is simpler |\n| Shared component library across apps | Yes — `packages\u002Fui` with boundary rules |\n| Gradual migration from monolith | Yes — extract features into micro-apps incrementally |\n| Need version-skew protection | Yes — isolated builds per micro-app |\n\n### Related Documentation\n\n- [Vercel Microfrontends](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fmicrofrontends)\n- [Next.js Multi-Zones](https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fapp\u002Fbuilding-your-application\u002Fdeploying\u002Fmulti-zones)\n\n## Bun Support & Lockfile Detection\n\nTurborepo 2.6+ has **stable Bun support** with granular lockfile analysis:\n\n- **Lockfile format**: Turborepo requires `bun.lock` (text format). If only `bun.lockb` (binary) is found, it errors with a prompt to generate a text lockfile. Generate with `bun install --save-text-lockfile`.\n- **Granular cache invalidation**: Turborepo parses `bun.lock` to detect which specific packages changed and only invalidates caches for affected tasks — not the entire monorepo.\n- **Pruning**: `turbo prune` works with Bun workspaces, generating a minimal lockfile for single-app deploys.\n- **Skip-builds detection**: On Vercel, monorepo workspace detection automatically skips unaffected projects when `bun.lock` changes don't touch a project's dependencies. Combined with `--affected`, only changed packages and their dependents rebuild.\n\n```bash\n# Ensure text lockfile for Turborepo compatibility\nbun install --save-text-lockfile\n\n# Run only affected packages (works with Bun lockfile detection)\nturbo build --affected\n```\n\n> **Known issue**: `turbo prune` with Bun 1.3+ may produce lockfiles with formatting differences that break `bun i --frozen-lockfile`. Track fixes in [turborepo#11007](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fturborepo\u002Fissues\u002F11007).\n\n## Deploying to Vercel\n\nVercel auto-detects Turborepo and optimizes builds. Each app in `apps\u002F` can be a separate Vercel project with automatic dependency detection.\n\n## When to Use Turborepo\n\n| Scenario | Use Turborepo? |\n|----------|----------------|\n| Single Next.js app | No — Turbopack handles bundling |\n| Multiple apps sharing code | Yes — orchestrate builds |\n| Shared component library | Yes — manage dependencies |\n| CI taking too long | Yes — caching + affected |\n| Team sharing build artifacts | Yes — remote caching |\n| Enforcing architecture boundaries | Yes — boundary rules |\n| Complex multi-step CI pipelines | Yes — task graph + matrix |\n\n## Official Documentation\n\n- [Turborepo Documentation](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs)\n- [Getting Started](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs\u002Fgetting-started)\n- [Crafting Your Repository](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs\u002Fcrafting-your-repository)\n- [Task Configuration](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs\u002Freference\u002Fconfiguration)\n- [Filtering](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs\u002Fcrafting-your-repository\u002Frunning-tasks#using-filters)\n- [GitHub: Turborepo](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fturborepo)\n","# Turborepo\n\nYou are an expert in Turborepo v2.8 — \"the build system for agentic coding\" — a high-performance build system for JavaScript\u002FTypeScript monorepos, built by Vercel with a Rust-powered core.\n\n## Key Features\n\n- **Task caching**: Content-aware hashing — only rebuilds when files actually change\n- **Remote caching**: Share build caches across machines and CI via Vercel\n- **Parallel execution**: Uses all CPU cores automatically\n- **Incremental builds**: `--affected` flag runs only changed packages + dependents\n- **Pruned subsets**: Generate minimal monorepo for deploying a single app\n- **Dependency graph awareness**: Understands package relationships\n- **Git worktree cache sharing**: Automatically shares local cache across worktrees (2.8+)\n- **Devtools**: Visual package and task graph explorer via `turbo devtools` (2.8+)\n- **Composable configuration**: Extend `turbo.json` from any package, not just root (2.7+)\n- **AI-enabled docs**: `turbo docs` returns markdown responses optimized for AI agents (2.8+)\n\n## Setup\n\n```bash\nnpx create-turbo@latest\n# or add to existing monorepo:\nnpm install turbo --save-dev\n# upgrade existing Turborepo:\nnpx @turbo\u002Fcodemod migrate\n```\n\n## turbo.json Task Pipeline\n\nThe `turbo.json` file defines your task dependency graph. Here are comprehensive examples:\n\n### Basic pipeline\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Fturborepo.dev\u002Fschema.json\",\n  \"tasks\": {\n    \"build\": {\n      \"description\": \"Compile TypeScript and bundle the application\",\n      \"dependsOn\": [\"^build\"],\n      \"outputs\": [\".next\u002F**\", \"dist\u002F**\"]\n    },\n    \"test\": {\n      \"description\": \"Run the test suite\",\n      \"dependsOn\": [\"build\"]\n    },\n    \"lint\": {\n      \"description\": \"Lint source files\"\n    },\n    \"dev\": {\n      \"cache\": false,\n      \"persistent\": true\n    }\n  }\n}\n```\n\n### Advanced pipeline with environment variables and inputs\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Fturborepo.dev\u002Fschema.json\",\n  \"globalDependencies\": [\".env\"],\n  \"globalEnv\": [\"CI\", \"NODE_ENV\"],\n  \"tasks\": {\n    \"build\": {\n      \"dependsOn\": [\"^build\"],\n      \"outputs\": [\".next\u002F**\", \"dist\u002F**\"],\n      \"env\": [\"DATABASE_URL\", \"NEXT_PUBLIC_API_URL\"],\n      \"inputs\": [\"src\u002F**\", \"package.json\", \"tsconfig.json\"]\n    },\n    \"test\": {\n      \"dependsOn\": [\"build\"],\n      \"outputs\": [\"coverage\u002F**\"],\n      \"env\": [\"TEST_DATABASE_URL\"]\n    },\n    \"test:unit\": {\n      \"dependsOn\": [],\n      \"outputs\": [\"coverage\u002F**\"]\n    },\n    \"lint\": {\n      \"inputs\": [\"src\u002F**\", \".eslintrc.*\"]\n    },\n    \"typecheck\": {\n      \"dependsOn\": [\"^build\"],\n      \"inputs\": [\"src\u002F**\", \"tsconfig.json\"]\n    },\n    \"db:generate\": {\n      \"cache\": false\n    },\n    \"dev\": {\n      \"cache\": false,\n      \"persistent\": true\n    },\n    \"clean\": {\n      \"cache\": false\n    }\n  }\n}\n```\n\n### Key Configuration\n\n- `dependsOn: [\"^build\"]` — Run `build` in dependencies first (`^` = topological)\n- `dependsOn: [\"build\"]` — Run `build` in the same package first (no `^`)\n- `outputs` — Files to cache (build artifacts)\n- `inputs` — Files that affect the task hash (default: all non-gitignored files)\n- `env` — Environment variables that affect the task hash\n- `cache: false` — Skip caching (for dev servers, codegen)\n- `persistent: true` — Long-running tasks (dev servers)\n- `globalDependencies` — Files that invalidate all task caches when changed\n- `globalEnv` — Env vars that invalidate all task caches when changed\n\n## Workspace Filtering\n\nRun tasks in specific packages or subsets of your monorepo:\n\n```bash\n# Single package\nturbo build --filter=web\n\n# Package and its dependencies\nturbo build --filter=web...\n\n# Package and its dependents (what depends on it)\nturbo build --filter=...ui\n\n# Multiple packages\nturbo build --filter=web --filter=api\n\n# By directory\nturbo build --filter=.\u002Fapps\u002F*\n\n# Packages that changed since main\nturbo build --filter=[main]\n\n# Combine: changed packages and their dependents\nturbo build --filter=...[main]\n\n# Exclude a package\nturbo build --filter=!docs\n\n# Packages matching a pattern\nturbo build --filter=@myorg\u002F*\n```\n\n### Filter syntax reference\n\n| Pattern | Meaning |\n|---------|---------|\n| `web` | Only the `web` package |\n| `web...` | `web` and all its dependencies |\n| `...web` | `web` and all its dependents |\n| `...web...` | `web`, its dependencies, and its dependents |\n| `.\u002Fapps\u002F*` | All packages in the `apps\u002F` directory |\n| `[main]` | Packages changed since `main` branch |\n| `{.\u002Fapps\u002Fweb}[main]` | `web` only if it changed since `main` |\n| `!docs` | Exclude the `docs` package |\n\n## CI Matrix Strategies\n\n### GitHub Actions — parallel jobs per package\n\n```yaml\nname: CI\non: [push, pull_request]\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 0 # Required for --affected\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: 22\n      - run: npm ci\n      - run: turbo build test lint --affected\n        env:\n          TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}\n          TURBO_TEAM: ${{ vars.TURBO_TEAM }}\n\n  deploy-web:\n    needs: build\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - run: npm ci\n      - run: turbo build --filter=web\n        env:\n          TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}\n          TURBO_TEAM: ${{ vars.TURBO_TEAM }}\n```\n\n### Dynamic matrix from workspace list\n\n```yaml\njobs:\n  detect:\n    runs-on: ubuntu-latest\n    outputs:\n      packages: ${{ steps.list.outputs.packages }}\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - id: list\n        run: |\n          PACKAGES=$(turbo ls --affected --output=json | jq -c '[.[].name]')\n          echo \"packages=$PACKAGES\" >> \"$GITHUB_OUTPUT\"\n\n  test:\n    needs: detect\n    if: needs.detect.outputs.packages != '[]'\n    runs-on: ubuntu-latest\n    strategy:\n      matrix:\n        package: ${{ fromJson(needs.detect.outputs.packages) }}\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - run: npm ci\n      - run: turbo test --filter=${{ matrix.package }}\n```\n\n### Remote caching in CI\n\n```bash\n# Set in CI environment\nTURBO_TOKEN=your-vercel-token\nTURBO_TEAM=your-vercel-team\n\n# Builds automatically use remote cache\nturbo build\n```\n\n## Watch Mode\n\nRun tasks in watch mode for development — re-executes when source files change:\n\n```bash\n# Watch a specific task\nturbo watch test\n\n# Watch with a filter\nturbo watch test --filter=web\n\n# Watch multiple tasks\nturbo watch test lint\n```\n\nWatch mode respects the task graph — if `test` depends on `build`, changing a source file re-runs `build` first, then `test`.\n\n### Persistent tasks vs watch\n\n- `persistent: true` in turbo.json: The task itself is long-running (e.g., `next dev`). Turbo starts it and keeps it alive.\n- `turbo watch`: Turbo re-invokes the task on file changes. Use for tasks that run and exit (e.g., `vitest run`, `tsc --noEmit`).\n\n## Boundary Rules\n\nEnforce architectural constraints across your monorepo with `boundaries` in turbo.json:\n\n```json\n{\n  \"boundaries\": {\n    \"tags\": {\n      \"apps\u002F*\": [\"app\"],\n      \"packages\u002Fui\": [\"shared\", \"ui\"],\n      \"packages\u002Futils\": [\"shared\"],\n      \"packages\u002Fconfig\": [\"config\"]\n    },\n    \"rules\": [\n      {\n        \"from\": [\"app\"],\n        \"allow\": [\"shared\"]\n      },\n      {\n        \"from\": [\"shared\"],\n        \"deny\": [\"app\"]\n      }\n    ]\n  }\n}\n```\n\nThis enforces:\n- Apps can import shared packages\n- Shared packages cannot import from apps\n- Violations produce build-time errors with `turbo boundaries`\n\n```bash\n# Check boundary compliance\nturbo boundaries\n\n# Add to your pipeline\n{\n  \"tasks\": {\n    \"check\": {\n      \"dependsOn\": [\"lint\", \"typecheck\", \"boundaries\"]\n    },\n    \"boundaries\": {}\n  }\n}\n```\n\n## Graph Visualization\n\nInspect your task dependency graph:\n\n```bash\n# Print graph to terminal\nturbo build --graph\n\n# Output as DOT format (Graphviz)\nturbo build --graph=graph.dot\n\n# Output as JSON\nturbo build --graph=graph.json\n\n# Open interactive graph in browser\nturbo build --graph=graph.html\n```\n\n### Dry run — see what would execute\n\n```bash\n# Show tasks that would run without executing them\nturbo build --dry-run\n\n# JSON output for programmatic use\nturbo build --dry-run=json\n```\n\nThe dry run output shows:\n- Each task that would execute\n- Cache status (HIT or MISS)\n- Dependencies and dependents\n- File hash used for caching\n\n## Devtools & Docs (2.8+)\n\n```bash\n# Visual package\u002Ftask graph explorer (hot-reloads on changes)\nturbo devtools\n\n# Search Turborepo docs from the terminal (returns agent-friendly markdown)\nturbo docs\n\n# Upgrade to latest Turborepo\nnpx @turbo\u002Fcodemod migrate\n```\n\n> **Note**: `turbo docs` output is optimized for AI coding agents — markdown format preserves context windows. The docs site also includes sample prompts for common tasks you can copy directly into your agent.\n\n## Composable Configuration (2.7+)\n\nPackage configs can now extend from any workspace package, not just the root:\n\n```json\n\u002F\u002F packages\u002Fui\u002Fturbo.json\n{\n  \"extends\": [\"@myorg\u002Fconfig\"],\n  \"tasks\": {\n    \"build\": {\n      \"outputs\": [\"dist\u002F**\"]\n    }\n  }\n}\n```\n\n## Common Commands\n\n```bash\n# Run build across all packages\nturbo build\n\n# Run only affected packages (changed since main branch)\nturbo build --affected\n\n# Run specific tasks in specific packages\nturbo build --filter=web\n\n# Run with remote caching\nturbo build --remote-cache\n\n# Prune monorepo for a single app deployment\nturbo prune web --docker\n\n# List all packages\nturbo ls\n\n# List affected packages\nturbo ls --affected\n```\n\n## Remote Caching\n\n```bash\n# Login to Vercel for remote caching\nturbo login\n\n# Link to a Vercel team\nturbo link\n\n# Now builds share cache across all machines\nturbo build  # Cache hits from CI, teammates, etc.\n```\n\n## Monorepo Structure\n\n```\nmy-monorepo\u002F\n├── turbo.json\n├── package.json\n├── apps\u002F\n│   ├── web\u002F           # Next.js app\n│   │   └── package.json\n│   ├── api\u002F           # Backend service\n│   │   └── package.json\n│   └── docs\u002F          # Documentation site\n│       └── package.json\n├── packages\u002F\n│   ├── ui\u002F            # Shared component library\n│   │   └── package.json\n│   ├── config\u002F        # Shared configs (eslint, tsconfig)\n│   │   └── package.json\n│   └── utils\u002F         # Shared utilities\n│       └── package.json\n└── node_modules\u002F\n```\n\n## --affected Flag\n\nThe most important optimization for CI pipelines:\n\n```bash\n# Only build\u002Ftest packages that changed since main\nturbo build test lint --affected\n```\n\nThis performs intelligent graph traversal:\n1. Identifies changed files since the base branch\n2. Maps changes to affected packages\n3. Includes all dependent packages (transitively)\n4. Runs tasks only for the affected subgraph\n\n## Microfrontends & Multi-App Composition\n\nTurborepo is the recommended orchestration layer for Vercel's Microfrontends architecture — composing multiple independently-deployed apps behind a single URL.\n\n### Monorepo Structure for Microfrontends\n\n```\nmy-platform\u002F\n├── turbo.json\n├── package.json\n├── apps\u002F\n│   ├── shell\u002F          # Layout \u002F shell app (owns top-level routing)\n│   ├── dashboard\u002F      # Micro-app: dashboard features\n│   ├── settings\u002F       # Micro-app: settings features\n│   └── marketing\u002F      # Micro-app: public marketing site\n└── packages\u002F\n    ├── ui\u002F             # Shared component library\n    ├── auth\u002F           # Shared auth utilities\n    └── config\u002F         # Shared tsconfig, eslint\n```\n\n### Independent Deploys\n\nEach micro-app is a separate Vercel project with its own build and deploy lifecycle:\n\n```bash\n# Deploy only the dashboard micro-app\nturbo build --filter=dashboard\n\n# Deploy all micro-apps in parallel\nturbo build --filter=.\u002Fapps\u002F*\n\n# Deploy only micro-apps that changed since main\nturbo build --filter=.\u002Fapps\u002F*...[main]\n```\n\n### Shared Packages Across Micro-Apps\n\nUse Turborepo's dependency graph to share code without coupling deploys:\n\n```json\n{\n  \"tasks\": {\n    \"build\": {\n      \"dependsOn\": [\"^build\"],\n      \"outputs\": [\".next\u002F**\", \"dist\u002F**\"]\n    }\n  }\n}\n```\n\nShared packages (`ui`, `auth`, `config`) are built first via `^build`, then each micro-app builds against the latest shared code. Remote caching ensures shared package builds are never repeated across micro-app deploys.\n\n### Multi-Zone Patterns\n\nNext.js multi-zones let each micro-app own a URL path prefix while sharing a single domain:\n\n```ts\n\u002F\u002F apps\u002Fshell\u002Fnext.config.ts\nimport type { NextConfig } from 'next'\n\nconst nextConfig: NextConfig = {\n  async rewrites() {\n    return [\n      { source: '\u002Fdashboard\u002F:path*', destination: 'https:\u002F\u002Fdashboard.example.com\u002Fdashboard\u002F:path*' },\n      { source: '\u002Fsettings\u002F:path*', destination: 'https:\u002F\u002Fsettings.example.com\u002Fsettings\u002F:path*' },\n    ]\n  },\n}\n\nexport default nextConfig\n```\n\nCombine with Turborepo boundary rules to enforce architectural isolation:\n\n```json\n{\n  \"boundaries\": {\n    \"tags\": {\n      \"apps\u002F*\": [\"micro-app\"],\n      \"packages\u002Fui\": [\"shared\"],\n      \"packages\u002Fauth\": [\"shared\"]\n    },\n    \"rules\": [\n      { \"from\": [\"micro-app\"], \"allow\": [\"shared\"] },\n      { \"from\": [\"shared\"], \"deny\": [\"micro-app\"] }\n    ]\n  }\n}\n```\n\n### When to Use Turborepo for Microfrontends\n\n| Scenario | Recommended? |\n|----------|-------------|\n| Multiple teams owning independent features | Yes — independent deploys + shared packages |\n| Single team, single app | No — standard Next.js is simpler |\n| Shared component library across apps | Yes — `packages\u002Fui` with boundary rules |\n| Gradual migration from monolith | Yes — extract features into micro-apps incrementally |\n| Need version-skew protection | Yes — isolated builds per micro-app |\n\n### Related Documentation\n\n- [Vercel Microfrontends](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fmicrofrontends)\n- [Next.js Multi-Zones](https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fapp\u002Fbuilding-your-application\u002Fdeploying\u002Fmulti-zones)\n\n## Bun Support & Lockfile Detection\n\nTurborepo 2.6+ has **stable Bun support** with granular lockfile analysis:\n\n- **Lockfile format**: Turborepo requires `bun.lock` (text format). If only `bun.lockb` (binary) is found, it errors with a prompt to generate a text lockfile. Generate with `bun install --save-text-lockfile`.\n- **Granular cache invalidation**: Turborepo parses `bun.lock` to detect which specific packages changed and only invalidates caches for affected tasks — not the entire monorepo.\n- **Pruning**: `turbo prune` works with Bun workspaces, generating a minimal lockfile for single-app deploys.\n- **Skip-builds detection**: On Vercel, monorepo workspace detection automatically skips unaffected projects when `bun.lock` changes don't touch a project's dependencies. Combined with `--affected`, only changed packages and their dependents rebuild.\n\n```bash\n# Ensure text lockfile for Turborepo compatibility\nbun install --save-text-lockfile\n\n# Run only affected packages (works with Bun lockfile detection)\nturbo build --affected\n```\n\n> **Known issue**: `turbo prune` with Bun 1.3+ may produce lockfiles with formatting differences that break `bun i --frozen-lockfile`. Track fixes in [turborepo#11007](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fturborepo\u002Fissues\u002F11007).\n\n## Deploying to Vercel\n\nVercel auto-detects Turborepo and optimizes builds. Each app in `apps\u002F` can be a separate Vercel project with automatic dependency detection.\n\n## When to Use Turborepo\n\n| Scenario | Use Turborepo? |\n|----------|----------------|\n| Single Next.js app | No — Turbopack handles bundling |\n| Multiple apps sharing code | Yes — orchestrate builds |\n| Shared component library | Yes — manage dependencies |\n| CI taking too long | Yes — caching + affected |\n| Team sharing build artifacts | Yes — remote caching |\n| Enforcing architecture boundaries | Yes — boundary rules |\n| Complex multi-step CI pipelines | Yes — task graph + matrix |\n\n## Official Documentation\n\n- [Turborepo Documentation](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs)\n- [Getting Started](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs\u002Fgetting-started)\n- [Crafting Your Repository](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs\u002Fcrafting-your-repository)\n- [Task Configuration](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs\u002Freference\u002Fconfiguration)\n- [Filtering](https:\u002F\u002Fturborepo.dev\u002Frepo\u002Fdocs\u002Fcrafting-your-repository\u002Frunning-tasks#using-filters)\n- [GitHub: Turborepo](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fturborepo)\n",{"name":5,"metadata":24,"description":7},{"docs":25,"sitemap":27,"priority":28,"bashPatterns":29,"pathPatterns":33},[26],"https:\u002F\u002Fturborepo.dev\u002Fdocs","https:\u002F\u002Fturborepo.dev\u002Fsitemap.xml",5,[30,31,32],"\\bturbo\\s+(run|build|test|lint|dev)\\b","\\bnpx\\s+turbo\\b","\\bbunx\\s+turbo\\b",[34,35],"turbo.json","turbo\u002F**","main","907b1d897cc6743f7f133f8ea2021e1331b0b020",".codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fturborepo","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque","https:\u002F\u002Fgithub.com\u002Frossboyd","www.bigideasgroup.co.uk","2026-09-22 02:03:50",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add rossboyd\u002Fquickque --skill turborepo",{"tool":49,"command":50},"bunx","bunx skills add rossboyd\u002Fquickque --skill turborepo",{"tool":52,"command":53},"pnpm","pnpm dlx skills add rossboyd\u002Fquickque --skill turborepo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fturborepo\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"agents\u002Fopenai.yaml","REFERENCE","参考文档",88,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fturborepo\u002Fagents\u002Fopenai.yaml",[64,73,81,88,95,103],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CJSS21K09H3ZQZMPFR4ZAG","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-installer\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CJSM1F4E7RBXCS3C18EFBY","skill-creator","Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CJSGF2PJM504Q6TZCNT27C","review-agent","Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Freview-agent\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7CJSBQTPFEQYZF4VWS7QZ3N","plugin-creator","Create and scaffold plugin directories for Codex with a required `.codex-plugin\u002Fplugin.json`, optional plugin folders\u002Ffiles, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7CJS5BHJZKA16353PVZGC50","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7CJRY1FC048P3RF4YQZ6J8B","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fimagegen\u002FSKILL.md",[],[]]