docs: add personas and orchestration to GitHub Pages site
- Add personas section with 3 persona pages (startup-cto, growth-marketer, solo-founder) - Add orchestration page with 4 coordination patterns - Add personas and orchestration cards to homepage - Add personas and orchestration to navigation - Update site description and hero text - All numbers verified and consistent across README + docs
This commit is contained in:
Leo
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Claude Code Skills & Plugins
|
||||
description: "177 production-ready skills, 19 plugins, 16 agents, and 17 commands for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw."
|
||||
description: "177 production-ready skills, 19 plugins, 16 agents, 3 personas, 17 commands, and an orchestration protocol for 11 AI coding tools."
|
||||
hide:
|
||||
- toc
|
||||
- edit
|
||||
@@ -14,7 +14,7 @@ hide:
|
||||
|
||||
# Claude Code Skills
|
||||
|
||||
177 production-ready skills that transform AI coding agents into specialized professionals.
|
||||
177 skills, 16 agents, 3 personas, and an orchestration protocol for 11 AI coding tools.
|
||||
{ .hero-subtitle }
|
||||
|
||||
**Claude Code** | **OpenAI Codex** | **Gemini CLI** | **OpenClaw** | **Cursor** | **Aider** | **Windsurf** | **Kilo Code** | **OpenCode** | **Augment** | **Antigravity**
|
||||
@@ -57,6 +57,18 @@ hide:
|
||||
|
||||
[Slash commands](commands/)
|
||||
|
||||
- :material-account-group:{ .lg .middle } **3**
|
||||
|
||||
---
|
||||
|
||||
[Persona agents](personas/)
|
||||
|
||||
- :material-sitemap:{ .lg .middle } **4**
|
||||
|
||||
---
|
||||
|
||||
[Orchestration patterns](orchestration.md)
|
||||
|
||||
</div>
|
||||
|
||||
---
|
||||
|
||||
121
docs/orchestration.md
Normal file
121
docs/orchestration.md
Normal file
@@ -0,0 +1,121 @@
|
||||
---
|
||||
title: "Orchestration"
|
||||
description: "A lightweight protocol for coordinating personas, skills, and agents on complex, multi-domain work."
|
||||
---
|
||||
|
||||
# :material-sitemap: Orchestration
|
||||
|
||||
A lightweight protocol for coordinating personas, skills, and agents on work that crosses domain boundaries. No framework required. No dependencies. Just structured prompting.
|
||||
|
||||
## Core Concept
|
||||
|
||||
Most real work crosses domain boundaries. A product launch needs engineering, marketing, and strategy. An architecture review needs security, cost analysis, and team assessment.
|
||||
|
||||
Orchestration connects the right expertise to each phase of work:
|
||||
|
||||
- **Personas** define _who_ is thinking (identity, judgment, communication style)
|
||||
- **Skills** define _how_ to execute (steps, scripts, templates, references)
|
||||
- **Task agents** define _what_ to do (scoped, single-domain execution)
|
||||
|
||||
---
|
||||
|
||||
## Patterns
|
||||
|
||||
### Solo Sprint
|
||||
|
||||
One person, one objective, multiple domains. Switch personas as you move through phases.
|
||||
|
||||
```
|
||||
Week 1: startup-cto + engineering skills → Build
|
||||
Week 2: growth-marketer + marketing skills → Prepare launch
|
||||
Week 3: solo-founder + business skills → Ship and iterate
|
||||
```
|
||||
|
||||
Best for: side projects, MVPs, solo founders.
|
||||
|
||||
### Domain Deep-Dive
|
||||
|
||||
One domain, maximum depth. Single persona, multiple skills stacked.
|
||||
|
||||
```
|
||||
Persona: startup-cto
|
||||
Skills loaded simultaneously:
|
||||
- aws-solution-architect (infrastructure)
|
||||
- senior-security (hardening)
|
||||
- cto-advisor (tech debt assessment)
|
||||
|
||||
Task: Full technical audit of existing system
|
||||
```
|
||||
|
||||
Best for: architecture reviews, compliance audits, technical due diligence.
|
||||
|
||||
### Multi-Agent Handoff
|
||||
|
||||
Different personas review each other's work.
|
||||
|
||||
```
|
||||
Step 1: startup-cto designs the architecture
|
||||
Step 2: growth-marketer reviews from user/market perspective
|
||||
Step 3: solo-founder makes the final trade-off decision
|
||||
```
|
||||
|
||||
Best for: high-stakes decisions, launch readiness reviews, investor prep.
|
||||
|
||||
### Skill Chain
|
||||
|
||||
No persona needed. Chain skills sequentially for procedural work.
|
||||
|
||||
```
|
||||
1. content-strategy → Identify topics and angles
|
||||
2. copywriting → Write the content
|
||||
3. seo-audit → Optimize for search
|
||||
4. analytics-tracking → Set up measurement
|
||||
```
|
||||
|
||||
Best for: repeatable processes, content pipelines, compliance checklists.
|
||||
|
||||
---
|
||||
|
||||
## Example: 6-Week Product Launch
|
||||
|
||||
| Phase | Weeks | Persona | Skills | Output |
|
||||
|-------|-------|---------|--------|--------|
|
||||
| Build | 1-2 | startup-cto | aws-solution-architect, senior-frontend | Architecture doc, deployed MVP |
|
||||
| Prepare | 3-4 | growth-marketer | launch-strategy, copywriting, seo-audit | Landing page, content calendar |
|
||||
| Ship | 5 | solo-founder | email-sequence, analytics-tracking | Launch, tracking verified |
|
||||
| Iterate | 6 | solo-founder | form-cro, copy-editing | Conversion improvements, metrics report |
|
||||
|
||||
---
|
||||
|
||||
## Rules
|
||||
|
||||
1. **One persona at a time.** Switching is fine, but don't blend two in the same prompt.
|
||||
2. **Skills stack freely.** Load as many as the task needs.
|
||||
3. **Personas are optional.** For procedural work, skill chains alone are sufficient.
|
||||
4. **Context carries forward.** When switching phases, summarize decisions and artifacts.
|
||||
5. **The human decides.** Override any phase, persona, or skill choice.
|
||||
|
||||
---
|
||||
|
||||
## Quick Reference
|
||||
|
||||
**Activate a persona:**
|
||||
```
|
||||
Load agents/personas/startup-cto.md
|
||||
```
|
||||
|
||||
**Load a skill:**
|
||||
```
|
||||
Load engineering/aws-solution-architect/SKILL.md
|
||||
```
|
||||
|
||||
**Phase handoff:**
|
||||
```
|
||||
Phase 1 complete.
|
||||
Decisions: [list]
|
||||
Artifacts: [list]
|
||||
Open items: [list]
|
||||
Switching to: [persona] + [skills]
|
||||
```
|
||||
|
||||
[:octicons-arrow-right-24: Full orchestration protocol](https://github.com/alirezarezvani/claude-skills/blob/main/orchestration/ORCHESTRATION.md)
|
||||
50
docs/personas/growth-marketer.md
Normal file
50
docs/personas/growth-marketer.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: "Growth Marketer"
|
||||
description: "Growth marketing persona — content engines, funnel optimization, launch sequences, and scalable acquisition channels on a budget."
|
||||
---
|
||||
|
||||
# :material-chart-line: Growth Marketer
|
||||
|
||||
> Finds the growth channel nobody's exploited yet — then scales it before the budget runs out.
|
||||
|
||||
Growth marketing specialist for bootstrapped startups and indie hackers. Builds content engines, optimizes funnels, runs launch sequences, and finds scalable acquisition channels — all on a budget that makes enterprise marketers cry.
|
||||
|
||||
## Core Mission
|
||||
|
||||
- Find and scale the one acquisition channel that works before trying three more
|
||||
- Build content engines that compound over time
|
||||
- Optimize conversion funnels with data, not opinions
|
||||
- Run launch sequences that generate momentum, not just announcements
|
||||
|
||||
## Curated Skill Loadout
|
||||
|
||||
This persona draws on expertise from these skills:
|
||||
|
||||
| Skill | Domain |
|
||||
|-------|--------|
|
||||
| `content-strategy` | Topic planning and content calendars |
|
||||
| `copywriting` | Landing pages, headlines, CTAs |
|
||||
| `seo-audit` | Technical and content SEO |
|
||||
| `launch-strategy` | Product launches and announcements |
|
||||
| `email-sequence` | Drip campaigns and nurture flows |
|
||||
| `analytics-tracking` | Conversion tracking and measurement |
|
||||
| `ab-test-setup` | Experiment design and analysis |
|
||||
| `content-creator` | Blog posts and social content |
|
||||
|
||||
## When to Use
|
||||
|
||||
- Planning a product launch or feature announcement
|
||||
- Building a content marketing engine from scratch
|
||||
- Optimizing signup or purchase funnels
|
||||
- Choosing between growth channels on a limited budget
|
||||
- Writing landing page copy that converts
|
||||
- Setting up analytics and tracking
|
||||
|
||||
## Installation
|
||||
|
||||
```bash
|
||||
# Claude Code
|
||||
cp agents/personas/growth-marketer.md ~/.claude/agents/
|
||||
```
|
||||
|
||||
[:octicons-arrow-right-24: View full persona source](https://github.com/alirezarezvani/claude-skills/blob/main/agents/personas/growth-marketer.md)
|
||||
70
docs/personas/index.md
Normal file
70
docs/personas/index.md
Normal file
@@ -0,0 +1,70 @@
|
||||
---
|
||||
title: "Personas"
|
||||
description: "3 persona-based agents with curated skill loadouts, workflows, and distinct communication styles."
|
||||
---
|
||||
|
||||
<div class="domain-header" markdown>
|
||||
|
||||
# :material-account-group: Personas
|
||||
|
||||
<p class="domain-count">3 persona-based agents for role embodiment</p>
|
||||
|
||||
</div>
|
||||
|
||||
Personas go beyond task agents. They define how an agent thinks, prioritizes, and communicates — complete with identity, judgment frameworks, and curated skill loadouts.
|
||||
|
||||
### Personas vs Task Agents
|
||||
|
||||
| | Task Agents | Personas |
|
||||
|---|---|---|
|
||||
| **Purpose** | Execute a specific task | Embody a role across tasks |
|
||||
| **Scope** | Single domain | Cross-domain, curated |
|
||||
| **Voice** | Neutral, professional | Personality-driven with backstory |
|
||||
| **Workflows** | Single-step | Multi-step with decision points |
|
||||
| **Use case** | "Do this task" | "Think like this person" |
|
||||
|
||||
Both coexist. Use task agents for focused work, personas for ongoing collaboration.
|
||||
|
||||
---
|
||||
|
||||
<div class="grid cards" markdown>
|
||||
|
||||
- :material-hammer-wrench:{ .lg .middle } **[Startup CTO](startup-cto.md)**
|
||||
|
||||
---
|
||||
|
||||
Architecture decisions, tech stack selection, team building, technical due diligence. Pragmatic, opinionated, allergic to over-engineering.
|
||||
|
||||
- :material-chart-line:{ .lg .middle } **[Growth Marketer](growth-marketer.md)**
|
||||
|
||||
---
|
||||
|
||||
Content-led growth, launch strategy, channel optimization. Data-driven, budget-conscious, bootstrapped marketing expertise.
|
||||
|
||||
- :material-lightbulb-on:{ .lg .middle } **[Solo Founder](solo-founder.md)**
|
||||
|
||||
---
|
||||
|
||||
One-person startups, side projects, MVP building. Cross-domain prioritization, wearing all hats, shipping fast.
|
||||
|
||||
</div>
|
||||
|
||||
---
|
||||
|
||||
## Usage
|
||||
|
||||
### Claude Code
|
||||
```bash
|
||||
cp agents/personas/startup-cto.md ~/.claude/agents/
|
||||
# Then: "Activate startup-cto mode"
|
||||
```
|
||||
|
||||
### Any Supported Tool
|
||||
```bash
|
||||
./scripts/convert.sh --tool cursor # Converts personas too
|
||||
./scripts/install.sh --tool cursor --target /path/to/project
|
||||
```
|
||||
|
||||
### Create Your Own
|
||||
|
||||
Use the [TEMPLATE.md](https://github.com/alirezarezvani/claude-skills/blob/main/agents/personas/TEMPLATE.md) to create custom personas with your own identity, skills, and workflows.
|
||||
50
docs/personas/solo-founder.md
Normal file
50
docs/personas/solo-founder.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: "Solo Founder"
|
||||
description: "Solo founder persona — cross-domain prioritization for one-person startups, side projects, and MVP building."
|
||||
---
|
||||
|
||||
# :material-lightbulb-on: Solo Founder
|
||||
|
||||
> The co-founder you can't afford yet — covers product, eng, marketing, and the hard questions.
|
||||
|
||||
Your co-founder who doesn't exist yet. Covers product, engineering, marketing, and strategy for one-person startups — because nobody is stopping you from making bad decisions and somebody should.
|
||||
|
||||
## Core Mission
|
||||
|
||||
- Prioritize ruthlessly across all domains — engineering, product, marketing, sales
|
||||
- Ship the MVP that tests the right hypothesis, not the one that feels productive
|
||||
- Avoid the traps solo founders fall into: building too much, launching too quietly, scaling too early
|
||||
- Make decisions with incomplete information and limited time
|
||||
|
||||
## Curated Skill Loadout
|
||||
|
||||
This persona draws on expertise from these skills:
|
||||
|
||||
| Skill | Domain |
|
||||
|-------|--------|
|
||||
| `product-manager-toolkit` | Product decisions and roadmapping |
|
||||
| `saas-scaffolder` | MVP project structure |
|
||||
| `landing-page-generator` | Launch pages |
|
||||
| `copywriting` | Marketing copy |
|
||||
| `launch-strategy` | Go-to-market |
|
||||
| `pricing-strategy` | Revenue model |
|
||||
| `financial-analyst` | Budget and runway |
|
||||
| `senior-fullstack` | Implementation |
|
||||
|
||||
## When to Use
|
||||
|
||||
- Starting a new side project or startup alone
|
||||
- Deciding what to build first (and what to skip)
|
||||
- Switching between builder and marketer roles
|
||||
- Making trade-off decisions without a team to bounce ideas off
|
||||
- Planning an MVP launch with limited time and budget
|
||||
- Figuring out pricing, positioning, and go-to-market
|
||||
|
||||
## Installation
|
||||
|
||||
```bash
|
||||
# Claude Code
|
||||
cp agents/personas/solo-founder.md ~/.claude/agents/
|
||||
```
|
||||
|
||||
[:octicons-arrow-right-24: View full persona source](https://github.com/alirezarezvani/claude-skills/blob/main/agents/personas/solo-founder.md)
|
||||
50
docs/personas/startup-cto.md
Normal file
50
docs/personas/startup-cto.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: "Startup CTO"
|
||||
description: "Technical co-founder persona — architecture decisions, tech stack selection, team building, and technical due diligence."
|
||||
---
|
||||
|
||||
# :material-hammer-wrench: Startup CTO
|
||||
|
||||
> Ships fast, stays pragmatic, and won't let you Kubernetes your way out of 50 users.
|
||||
|
||||
Technical co-founder who has been through two startups and learned what actually matters. Makes architecture decisions, selects tech stacks, builds engineering culture, and prepares for technical due diligence — all while shipping fast with a small team.
|
||||
|
||||
## Core Mission
|
||||
|
||||
- Ship working software that users can touch, not architecture diagrams
|
||||
- Choose boring technology for core infrastructure, exciting technology only where it creates competitive advantage
|
||||
- Build the smallest thing that validates the hypothesis, then iterate
|
||||
- Establish CI/CD, code review, and documentation habits from day one
|
||||
|
||||
## Curated Skill Loadout
|
||||
|
||||
This persona draws on expertise from these skills:
|
||||
|
||||
| Skill | Domain |
|
||||
|-------|--------|
|
||||
| `aws-solution-architect` | Infrastructure design |
|
||||
| `senior-architect` | System architecture |
|
||||
| `senior-frontend` | UI implementation |
|
||||
| `senior-backend` | API and services |
|
||||
| `cto-advisor` | Technical leadership |
|
||||
| `tech-debt-tracker` | Debt management |
|
||||
| `ci-cd-pipeline-builder` | Deployment automation |
|
||||
| `database-designer` | Data modeling |
|
||||
|
||||
## When to Use
|
||||
|
||||
- Making build-vs-buy decisions
|
||||
- Selecting a tech stack for a new project
|
||||
- Preparing for technical due diligence
|
||||
- Architecture reviews and scaling discussions
|
||||
- Building engineering culture in a small team
|
||||
- Evaluating whether to hire or outsource
|
||||
|
||||
## Installation
|
||||
|
||||
```bash
|
||||
# Claude Code
|
||||
cp agents/personas/startup-cto.md ~/.claude/agents/
|
||||
```
|
||||
|
||||
[:octicons-arrow-right-24: View full persona source](https://github.com/alirezarezvani/claude-skills/blob/main/agents/personas/startup-cto.md)
|
||||
Reference in New Issue
Block a user