This guide provides comprehensive instructions for creating *cs- prefixed agents** that seamlessly integrate with the 42 production skills in this repository. *cs- agents** are specialized Claude Code agents that orchestrate the 177 existing skills. Each agent: - References skills via relative paths (../../marketing-skill/) - Executes Python automation tools from skill packages - Follows established workflows and templates - Maintains skill portability and independence Key Principle: Agents ORCHESTRATE skills, they don't replace them. Skills remain self-contained and portable. When skills are…
This is a comprehensive skills library for Claude AI and Claude Code - reusable, production-ready skill packages that bundle domain expertise, best practices, analysis tools, and strategic frameworks. The repository provides modular skills that teams can download and use directly in their workflows. Current Scope: 177 production-ready skills across 9 domains with 254 Python automation tools, 357 reference guides, 16 agents, and 17 slash commands. Key Distinction: This is NOT a traditional application. It's a library of skill packages meant…
A complete virtual board of directors: 28 skills covering 10 executive roles, orchestration, cross-cutting capabilities, and culture & collaboration frameworks. The only skill with a plugin.json (namespace: em) because it has slash commands. Other skills are invoked by name through the Chief of Staff router or directly by the user. This is intentional — only add plugin.json when a skill has dedicated slash commands that need a namespace.
This directory contains 43 marketing skills organized into specialist pods. 32 scripts, all stdlib-only. Run directly: No pip install needed. Scripts include embedded samples for demo mode (run with no args). ❌ Don't read all 43 SKILL.md files ❌ Don't skip marketing-context.md if it exists ❌ Don't use content-creator (deprecated → use content-production) ❌ Don't install pip packages for Python tools
This guide explains the template system for agents, commands, and standardized workflows. Location: templates/ Purpose: Reusable templates for consistent agent development, slash command creation, and workflow automation across all domains. Location: templates/agent-template.md (when created) Usage: Starting point for creating new cs-* agents Contains: - YAML frontmatter structure - Required markdown sections - Workflow documentation format - Integration examples pattern When to Use: Creating any new agent in agents/ directory Location: templates/command-template.md (when created) Usage: Creating new slash commands Contains: -…
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.
zhangzhang-111-iCLAUDE.md