القائمة
Research a library and create comprehensive documentation in .claude/docs/libraries/.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Comprehensive onboarding for new or returning contributors. Scans repository artifacts (git history, CLAUDE.md / AGENTS.md, project rules, skill catalog, DESIGN.md, research & library notes, checkpoints, agent-team logs) and synthesizes a GUIDE.md at the repository root summarizing what has been worked on, why, and how to resume work.
Save full session context: git history, CLI consultations, Agent Teams activity, and discover reusable skill patterns — all in one run. No flags needed. Maintains a rolling PROGRESS.md (latest 5 checkpoint summaries) and ends with a compact phase that prunes stale CLAUDE.md Zone C work blocks and compacts the conversation (also available standalone via --compact-only, replacing the old /context-refresh skill). Run at session end, after major milestones, or when you want to capture learnings.
Codex CLI handles planning, design, and complex code implementation. Use for: architecture design, implementation planning, complex algorithms, debugging (root cause analysis), trade-off evaluation, code review. External research is NOT Codex's job — use general-purpose-opus instead. Explicit triggers: "plan", "design", "architecture", "think deeper", "analyze", "debug", "complex", "optimize".
Unified feature planning & implementation skill — replaces the old /add-feature and /start-feature skills (both trigger phrases still apply here). MODE=existing (formerly /add-feature): add a feature to an established codebase with Codex-first collaboration — Codex is consulted in every phase for scope analysis, architecture design, implementation planning, and validation. MODE=greenfield (formerly /start-feature): start a large or new feature that requires external research — Agent Teams (Researcher + Architect) do parallel research & design. Both modes share Phase 3 complexity routing (SIMPLE: Codex direct, MODERATE: Codex + /team-execute --review-only, COMPLEX: /team-execute).
Analyze project structure, write the thick requirements doc (.claude/docs/DESIGN.md), and populate the thin "Repository Identity" pointer in CLAUDE.md (Zone B).
Two-phase Agent Teams execution — replaces the old /team-implement and /team-review skills. Phase 1 IMPLEMENT (formerly /team-implement): parallel implementation with teammates per module/layer, file-ownership separation, and a shared task list with dependencies. Run after /feature plan approval. Phase 2 REVIEW (formerly /team-review): specialized reviewers (security, quality, test coverage) review the changes from different perspectives in parallel. Pass --review-only to skip Phase 1 and review existing changes (after manual or Codex implementation).
| name | research-lib |
| description | Research a library and create comprehensive documentation in .claude/docs/libraries/. |
| disable-model-invocation | true |
Research $ARGUMENTS and create documentation in .claude/docs/libraries/.
Use general-purpose-opus with WebSearch/WebFetch for comprehensive library research:
Agent tool:
subagent_type: "general-purpose-opus"
prompt: |
Research: {library}. Find latest version, official documentation,
key features, constraints, best practices, known issues, and usage patterns.
Use WebSearch and WebFetch to gather information.
Save results to .claude/docs/libraries/{library}.md
Return concise summary.
If the subagent is unavailable, verify via manual web search:
Basic Information
Core Features
Constraints & Notes
Usage Patterns in This Project
Troubleshooting
.claude/docs/libraries/$ARGUMENTS.md
# {Library Name}
## Overview
- **Version**: {version}
- **License**: {license}
- **Official URL**: {url}
- **Installation**: `{install command}`
## Core Features
{Description of main features}
## Basic Usage
```python
{Code example}
{Good pattern}
{Anti-pattern}
Cause: {cause} Solution: {solution}