AGENT SKILL

team-configurator

Use when team configurator expertise is needed to unblock implementation decisions.

License 许可
MIT
最近更新
2026-04-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
team-configurator
metadata
{ "hermes": { "tags": [ "codex-agent", "architecture-orchestration" ], "source": "codex-field-kit/architecture-orchestration" } }
description
Use when team configurator expertise is needed to unblock implementation decisions.

03 SKILL.md 正文

Team Configurator

team-configurator – AI Team Setup & Update

Mission

Analyse the code‑base, pick the right specialists, and keep CLAUDE.md current.

Workflow

  1. Locate CLAUDE.md

    • If present: read it and preserve everything outside “AI Team Configuration”.
    • If absent: plan to create it.
  2. Detect stack

    • Inspect package.json, composer.json, requirements.txt, go.mod, Gemfile, and build configs.
    • Record backend framework, frontend framework, DB, build tools, test tools.
  3. Discover agents

    • List files under ~/.claude/agents/**/**.md for system level subagents and .claude folder for project level subagents.
    • Build a table: agent → tags (use the first heading line of each file).
  4. Pick specialists

    • Prefer a framework‑specific agent; otherwise use the nearest universal agent.
    • Always include code-reviewer and performance-optimizer.
  5. Write / update CLAUDE.md

    • Insert (or replace old) section headed
      ## AI Team Configuration (autogenerated by team-configurator, YYYY‑MM‑DD)
      followed immediately by the bold line:
      **Important: YOU MUST USE subagents when available for the task.**
    • Bullet list the detected stack.
    • Markdown table: Task | Agent | Notes.
    • Preserve all user prose outside this section.
  6. Report to user

    • Show detected stack.
    • List the agents added or updated.
    • Provide one sample command, e.g.

      Try: “@laravel-api-architect build a Posts endpoint”.

Delegations

Trigger Delegate Goal
No CLAUDE.md code-archaeologist Full stack report
Large mono‑repo tech-lead-orchestrator Split work across domains

Output rules

  • Append a timestamp to the configuration section.
  • Never delete user prose.
  • Use markdown tables for assignments.
  • Keep sentences short and plain.

04 同仓库更多 Skills

0xharryriddle
0xharryriddle/codex-field-kit

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

前端开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

swarm-planner

[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

super-swarm-spark

Only to be triggered by explicit super-swarm-spark commands.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

role-creator

Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

read-github

Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo

Skill与智能体开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

planner

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

★ 3