This file provides domain-specific guidance for skills in business-operations/. The Business Operations domain ships skills that help internal operators (BizOps lead, COO direct reports, vendor management office, IT ops) run the company day-to-day. This is not strategy (that's c-level-advisor/) and not external sales (that's business-growth/). Path-B 11-file contract per skill (Matt Pocock-derived discipline preserved):
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: 388 production-ready skills across 20 domains with 727 Python automation tools, 842 reference guides, 118 agents (cs-* + 7 personas), and 150 slash commands, distributed as 99 marketplace plugins. Headline counters are derived from the…
A complete virtual board of directors: 28 skills covering 10 executive roles, orchestration, cross-cutting capabilities, and culture & collaboration frameworks — plus the new c-level-agents plugin layer that surfaces 8 cs-* persona agents and 17 /cs:* slash commands on top of the skills.
This file provides domain-specific guidance for skills in commercial/. The Commercial domain ships skills that help deal-desk operators, pricing teams, partner managers, RFP responders, and commercial forecasters make per-deal and packaging decisions. This is not strategy (c-level-advisor/cro-advisor), not sales execution (business-growth/sales-engineer), and not financial close (finance/financial-analysis). Path-B 11-file contract per skill. SKILL.md includes a "Forcing-question library" section that grills the user with cited canon (Skok, Tunguz, Bessemer, Ramanujam, ProfitWell, Winning by Design, Shipley, APMP).
This file provides domain-specific guidance for skills in markdown-html/. The markdown-html domain converts long markdown files (the actual artifacts produced inside a Claude project — specs, reports, RFCs, PR writeups, slide outlines) into world-class, single-file, lightly-interactive HTML. Inspired by Thariq Shihipar's argument (Medium, 2026): markdown collapses past ~100 lines because it lacks visual machinery for density and lateral navigation; HTML restores both. It is not an interactive prompt-tuning playground (/playground plugin owns that lane), not a landing-page generator (marketing/landing/), not…
This directory contains 44 marketing skills organized into 8 specialist pods (Content, SEO + AEO, CRO, Channels, Growth, Intelligence, Sales enablement, Marketing ops). 59 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 44 SKILL.md files ❌ Don't skip .claude/product-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 covers the 17 production-ready product management skills (13 bundled incl. the orchestrator + 4 standalone plugins) and their Python automation tools. skills/product-skills/ is the domain's context: fork orchestrator and agent harness adapter: Commands: /cs:product (router) · /cs:grill-product (canon-cited grilling) · /cs:product-loop (the discovery loop). Agent: cs-product-orchestrator. Build-scale goals compile through engineering/agent-harness with the product-team.json manifest. Hard rules: no roadmap cites a tree that fails the linter; single-participant claims are anecdotes; AI features ship with eval specs (see skills/product-skills/references/aiproductevals.md).
This file provides domain-specific guidance for skills in research-ops/. The Research Operations domain ships skills that help R&D leads, clinical study teams, R&D finance/controllers, market-research analysts, and product-research / ResearchOps teams plan, fund, scope, and synthesize research across enterprise workstreams. This is the enterprise / cross-functional counterpart to the academic research/ domain (litreview, grants, patent, syllabus, pulse, dossier, notebooklm). It is not regulatory submission (ra-qm-team), not corporate financial close/valuation (finance/financial-analysis), not funding discovery (research/grants), not persona/journey/live-experiment design (product-team), and not…
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 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 Not yet created. There is no command template or workflow template file in…
This is a curated collection of Claude Code subagent definitions - specialized AI assistants for specific development tasks. Subagents are markdown files with YAML frontmatter that Claude Code can load and use. Each subagent follows this template: When adding a new agent, update these files: Format for main README: - agent-name - Brief description Project subagents take precedence over global ones with the same name.
This file is a bridge — treat AGENTS.md as the source of truth. When asked to read, update, or add rules to CLAUDE.md, read from and write to AGENTS.md instead.
context-mode MCP tools available. Rules protect context window from flooding. One unrouted command dumps 56 KB into context. Analyze/count/filter/compare/search/parse/transform data: write code via ctxexecute(language, code), console.log() only the answer. Do…
CRITICAL: This project uses UV for all Python operations. Never use python -m, pip install, or python script.py directly. Current v4.3.0 Architecture: Python package with 30 commands, 20 agents, 7 modes SuperClaude integrates with Claude Code through these mechanisms: - Slash Commands: 30 commands installed to ~/.claude/commands/sc/ (e.g., /sc:pm, /sc:research) - Agents: 20 agents installed to ~/.claude/agents/ (e.g., @pm-agent, @system-architect) - Skills: Installed to ~/.claude/skills/ (e.g., confidence-check) - Hooks: Session lifecycle hooks in src/superclaude/hooks/ - Settings: Project settings in .claude/settings.json…
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.
alirezarezvaniCLAUDE.md
