Claude Code ecosystem expertise. Modules: CLI tool (setup, slash commands, MCP servers, hooks, plugins, CI/CD), extensibility (agents, skills, output styles creation), CLAUDE.md (project instructions, optimization). Actions: configure, troubleshoot, create, deploy, integrate, optimize Claude Code. Keywords: Claude Code, Anthropic, CLI tool, slash command, MCP server, Agent Skill, hook, plugin, CI/CD, enterprise, CLAUDE.md, agentic coding, agent, skill, output-style, SKILL.md, subagent, Task tool, project instructions, token optimization. Use when: learning Claude Code features, configuring settings, creating skills/agents/hooks, setting up MCP servers, troubleshooting issues, CI/CD integration, initializing or optimizing CLAUDE.md files.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
npx agent-skills-cli listSkill Instructions
name: claude-ecosystem description: "Claude Code ecosystem expertise. Modules: CLI tool (setup, slash commands, MCP servers, hooks, plugins, CI/CD), extensibility (agents, skills, output styles creation), CLAUDE.md (project instructions, optimization). Actions: configure, troubleshoot, create, deploy, integrate, optimize Claude Code. Keywords: Claude Code, Anthropic, CLI tool, slash command, MCP server, Agent Skill, hook, plugin, CI/CD, enterprise, CLAUDE.md, agentic coding, agent, skill, output-style, SKILL.md, subagent, Task tool, project instructions, token optimization. Use when: learning Claude Code features, configuring settings, creating skills/agents/hooks, setting up MCP servers, troubleshooting issues, CI/CD integration, initializing or optimizing CLAUDE.md files."
Claude Ecosystem
Comprehensive guide for Claude Code CLI tool, extensibility (agents/skills/output styles), and CLAUDE.md architecture.
Module Selection
| Need | Module | Reference |
|---|---|---|
| Setup/Configuration | CLI | references/getting-started.md, references/configuration.md |
| Slash Commands | CLI | references/slash-commands.md |
| MCP Servers | CLI | references/mcp-integration.md |
| Hooks & Plugins | CLI | references/hooks-and-plugins.md |
| Create Agents | Extensibility | references/agent-development.md |
| Create Skills | Extensibility | references/skill-development.md |
| Output Styles | Extensibility | references/skill-development.md |
| Init CLAUDE.md | Architecture | references/initialization-workflow.md |
| Optimize CLAUDE.md | Architecture | references/optimization-patterns.md |
| Enterprise/CI-CD | CLI | references/enterprise-features.md, references/cicd-integration.md |
| Troubleshooting | CLI | references/troubleshooting.md |
Quick Reference
Extension Types
| Type | Invocation | Purpose | Location |
|---|---|---|---|
| Agents | Task tool | Specialized sub-processes | .claude/agents/ |
| Skills | Model-invoked | Domain knowledge | .claude/skills/{name}/ |
| Output Styles | /output-style | Modify main agent | .claude/output-styles/ |
Model Selection (Agents)
| Model | Use When | Target Time |
|---|---|---|
haiku | Fast tasks, exploration | < 3s |
sonnet | Balanced, most use cases | < 10s |
opus | Complex reasoning | < 30s |
CLAUDE.md Token Budget
| Complexity | Target Tokens |
|---|---|
| Simple | 100-200 |
| Medium | 200-400 |
| Complex | 400-800 |
| Maximum | 1000 |
Extensibility Principles
Core Truths
| Truth | Meaning |
|---|---|
| Expertise Transfer | Make Claude think like expert, not follow steps |
| Flow, Not Friction | Produce output, not intermediate work |
| Voice Matches Domain | Sound like practitioner, not documentation |
| Focused Beats Comprehensive | Constrain ruthlessly |
Decision Heuristics
| Rule | Guidance |
|---|---|
| 3-File Rule | 3+ files → agent. Enhances YOUR work → skill. |
| Delegation Test | Runs independently? Agent. Guides you? Skill. |
| Activation Breadth | Trigger on 80% of relevant requests |
| Tool Constraint | Start with 2-3 essential tools |
Activation Keywords
The description field is your activation gate. Include:
- Task verbs: create, build, debug, fix, deploy
- Problem descriptions: slow, broken, failing
- Artifact types: component, API, database
- Casual synonyms: "make it faster" → optimize
Common Workflows
Create Agent
---
name: agent-name
description: "Use when [use case]. PROACTIVELY for [triggers].\n\nExamples:\n<example>\nContext: [situation]\nuser: [request]\nassistant: [response]\n</example>"
tools: Grep, Glob, Read, Bash
model: haiku
---
# Agent Name
Mission statement.
## Strategy
[Approach]
## Does NOT Do
- [boundary] (use X instead)
Create Skill
---
name: skill-name
description: "[Core purpose]. [Technologies]. Capabilities: [list].
Actions: [verbs]. Keywords: [triggers]. Use when: [scenarios]."
allowed-tools: Read, Grep, Glob
---
# Skill Name
## Patterns
### [Pattern Name]
**When you see:** [Observable trigger]
**This indicates:** [Expert insight]
**Therefore:** [Action]
**Watch out:** [Pitfall]
Initialize CLAUDE.md
- Analyze codebase (language, framework, structure)
- Extract code style, commands, patterns
- Generate with template, customize
- Validate commands, check token count
- Target <400 lines, prefer <250
Detailed: references/initialization-workflow.md
Optimize CLAUDE.md
- Evaluate token efficiency
- Find redundancy, outdated info
- Apply token reduction techniques
- Target 40%+ reduction
- Verify critical info retained
Detailed: references/optimization-patterns.md
Anti-Patterns
| Pattern | Problem | Fix |
|---|---|---|
| Kitchen Sink Agent | 10+ tools, handles "everything" | Constrain to 3-5 tools |
| Echo Skill | Restates docs without insight | Add expert layer |
| Invisible Trigger | Description uses only formal terms | Include user language |
| Procedure Manual | Step 1, 2, 3... | Teach patterns, not steps |
| Over-Documentation | CLAUDE.md > 400 lines | Document project-specific only |
Quality Signals
Good Signs
- Frontmatter reads like "when to use" guide
- First 10 lines provide actionable guidance
- Expert would nod "yes, that's how I think"
- Explicit constraints on what it does NOT handle
Warning Signs
-
50% reference tables or field definitions
- No mention of "when NOT to use"
- Generic language for any domain
- Body exceeds 600 lines
References
CLI Tool
references/getting-started.md- Installation, setup, authreferences/slash-commands.md- Complete command catalogreferences/mcp-integration.md- MCP server configurationreferences/hooks-and-plugins.md- Hook types, plugin structurereferences/configuration.md- Settings hierarchyreferences/enterprise-features.md- IAM, SSO, sandboxingreferences/cicd-integration.md- GitHub Actions, GitLab CIreferences/ide-integration.md- VS Code, JetBrainsreferences/advanced-features.md- Extended thinking, cachingreferences/troubleshooting.md- Common issuesreferences/api-reference.md- Admin, Messages, Skills APIsreferences/best-practices.md- Project organization, securityreferences/agent-skills.md- Creating skills via CLI
Extensibility
references/agent-development.md- Full YAML structure, system promptsreferences/skill-development.md- Structure, triggers, hooks
CLAUDE.md
references/initialization-workflow.md- Creating new CLAUDE.mdreferences/optimization-patterns.md- Token reduction techniquesreferences/integration-strategies.md- Global config, MCP toolsreferences/output-templates.md- Standard output formats
Related Skills
IMPORTANT: When creating/editing prompts, use prompt-architect skill.
Skill("prompt-architect") → Create/enhance skill/agent prompt content
Documentation:
More by samhvw8
View all3D web graphics with Three.js (WebGL/WebGPU). Capabilities: scenes, cameras, geometries, materials, lights, animations, model loading (GLTF/FBX), PBR materials, shadows, post-processing (bloom, SSAO, SSR), custom shaders, instancing, LOD, physics, VR/XR. Actions: create, build, animate, render 3D scenes/models. Keywords: Three.js, WebGL, WebGPU, 3D graphics, scene, camera, geometry, material, light, animation, GLTF, FBX, OrbitControls, PBR, shadow mapping, post-processing, bloom, SSAO, shader, instancing, LOD, WebXR, VR, AR, product configurator, data visualization, architectural walkthrough, interactive 3D, canvas. Use when: creating 3D visualizations, building WebGL/WebGPU apps, loading 3D models, adding animations, implementing VR/XR, creating interactive graphics, building product configurators.
Search GitHub for repos, code, and usage examples using gh CLI. Capabilities: repo discovery, code search, finding library usage patterns, issue/PR search. Actions: search, find, discover repos/code/examples. Keywords: gh, github, search repos, search code, find examples, how to use library, stars, language filter. Use when: finding repositories, searching code patterns, discovering how libraries are used, exploring open source.
UI/UX design system for dashboards, admin panels, SaaS interfaces, and web apps. Stack: React, Tailwind, CSS, styled-components. Capabilities: spacing systems (4px grid), color palettes, typography hierarchy, shadows/elevation, card layouts, dark mode, component styling. Actions: design, style, beautify, fix, improve, refactor UI components. Keywords: ugly, inconsistent, cluttered, unprofessional, spacing, padding, margin, colors, fonts, shadows, cards, buttons, forms, navigation, sidebar, layout. Use when: building new UI, fixing ugly interfaces, making things look professional/modern/clean, implementing design systems, styling components, choosing colors/fonts/spacing.
Git workflow management with atomic commit principles. Capabilities: commit organization, branching strategies, merge/rebase workflows, PR management, history cleanup, staged change analysis, single-responsibility commits. Actions: commit, push, pull, merge, rebase, branch, stage, stash git operations. Keywords: git commit, git push, git pull, git merge, git rebase, git branch, git stash, atomic commit, commit message, conventional commits, branching strategy, GitFlow, trunk-based, PR, pull request, code review, git history, cherry-pick, squash, amend, interactive rebase, staged changes. Use when: organizing commits, creating branches, merging code, rebasing, writing commit messages, managing PRs, cleaning git history, analyzing staged changes.
