メニュー
Unified router for development, infrastructure, and documentation tasks. Absorbs development-router + infrastructure-router + documentation-router.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill whenever the user wants high-quality semantic retrieval, cross-textbook synthesis, reference verification, or authority-ranked question answering over the PageIndex corpus. Trigger on requests like "find which texts cover X", "compare sources", "retrieve semantically", "verify this claim from my textbooks", "build a reading list from the corpus", "cluster by topic", or any PageIndex question where naïve filename search would miss relevant material. This skill teaches a state-of-the-art hybrid retrieval workflow over the PageIndex catalog and live MCP extraction surface.
Build complex AI systems with declarative programming, optimize prompts automatically, create modular RAG systems and agents with DSPy - Stanford NLP's framework for systematic LM programming. Use when you need to build complex AI systems, program LMs declaratively, optimize prompts automatically, create modular AI pipelines, or build RAG systems and agents.
Evaluate and improve Claude Code commands, skills, and agents. Use when testing prompt effectiveness, validating context engineering choices, or measuring improvement quality.
Real-time observability dashboard for multi-agent Claude Code sessions. Visualize agent interactions, tool usage, and session flows in real-time through a web dashboard. Track multiple agents running in parallel with swim lane visualization, event filtering, and live charts. **Key Features:** - 🔴 Real-time event streaming via WebSocket - 📊 Agent swim lanes showing parallel execution - 🔍 Event filtering by agent, session, event type - 📈 Live charts for tool usage patterns - 💾 Filesystem-based (no database required) **Inspired by [@indydevdan](https://github.com/indydevdan)**'s work on multi-agent observability. **Our approach:** Filesystem + in-memory streaming vs. indydevdan's SQLite database approach.
Track and optimize agent specialization during methodology development. Use when agent specialization emerges (generic agents show >5x performance gap), multi-experiment comparison needed, or methodology transferability analysis required. Captures agent set evolution (Aₙ tracking), meta-agent evolution (Mₙ tracking), specialization decisions (when/why to create specialized agents), and reusability assessment (universal vs domain-specific vs task-specific). Enables systematic cross-experiment learning and optimized M₀ evolution. 2-3 hours overhead per experiment.
Routes tasks to appropriate Task tool agents (subagents). Triggers on complex multi-step tasks, research, code review, exploration, or any task benefiting from specialized agent execution. Matches intent to agent types.
| name | build-router |
| description | Unified router for development, infrastructure, and documentation tasks. Absorbs development-router + infrastructure-router + documentation-router. |
Tier: unified Absorbs: development-router + infrastructure-router + documentation-router Purpose: All creation/building tasks (code, configs, docs)
patterns:
- build, implement, create, develop
- frontend, backend, fullstack, API
- mcp, server, hook, deploy
- document, readme, explain, changelog
- terminal, TUI, CLI interface
triggers: [UI, UX, component, styling, React, Vue, Svelte]
agent: frontend-engineer
skills:
- frontend-ui-ux (active)
- component patterns
- accessibility (WCAG)
- responsive design
triggers: [API, server, database, authentication]
patterns:
- RESTful API design
- GraphQL schemas
- Database modeling
- Authentication/authorization
triggers: [MCP, hook, config, deploy, tooling]
skills:
- mcp-builder (db/skill-db)
- hook development
- configuration management
workflows:
- MCP server: Research → Implement → Review → Evaluate
triggers: [document, readme, explain, changelog, API docs]
agent: document-writer
patterns:
- README creation
- API documentation
- Code comments
- Changelogs
standard_flow:
1. Analyze requirements
2. Plan implementation
3. Build incrementally
4. Test and validate
5. Document
sc_commands:
- sc:implement → Guided implementation
- sc:build → Build workflow
- sc:document → Documentation
package_managers:
package.json: pnpm | npm | yarn | bun
pyproject.toml: uv | poetry | pip
Cargo.toml: cargo
go.mod: go
build_commands:
typescript: "pnpm build" | "npm run build" | "bun build"
python: "uv run python -m build" | "poetry build"
rust: "cargo build --release"
test_runners:
typescript: vitest | jest | playwright
python: pytest
rust: cargo test
linting:
typescript: eslint | prettier | biome
python: ruff | black | mypy
Build/Create Request
│
├── Frontend?
│ ├── TUI/terminal? → terminal skill
│ ├── Component? → frontend-engineer agent
│ └── Feature → sc:implement
│
├── Backend?
│ ├── API design? → sc:design
│ └── Implementation → sc:build
│
├── Infrastructure?
│ ├── MCP server? → mcp-builder skill
│ ├── Hooks? → hookify skill
│ └── Config → component skill
│
└── Documentation?
├── README → document-writer agent
├── API docs → sc:document
└── Changelog → create-release-note