mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
docs: Transform documentation to emphasize simplicity and auto-activation
Update all Docs/ guides to lead with "just start using it" approach while keeping comprehensive information available. Key changes: - Add prominent "Simple Truth" and "Just Start Here" sections - Emphasize intelligent routing and auto-activation throughout - Reframe detailed guides as optional curiosity rather than required study - Use casual, humble developer tone with emojis for clarity - Transform "learn first" to "discover through use" messaging - Make auto-expert selection and flag activation prominent - Remove any marketing language in favor of honest, straightforward content Files updated: superclaude-user-guide.md, commands-guide.md, flags-guide.md, personas-guide.md, installation-guide.md 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -1,23 +1,55 @@
|
||||
# SuperClaude Personas User Guide 🎭
|
||||
|
||||
## 🎭 Personas Auto-Activate - No Need to Choose!
|
||||
|
||||
**The simple truth**: You don't need to pick personas or memorize what they do. SuperClaude automatically brings in the right expert for each situation!
|
||||
|
||||
**Here's what actually happens:**
|
||||
- You type `/analyze auth.js` → Security expert automatically jumps in 🛡️
|
||||
- You work on React components → Frontend specialist takes over 🎨
|
||||
- You debug performance issues → Performance optimizer activates ⚡
|
||||
- You write documentation → Professional writer helps out ✍️
|
||||
|
||||
**It's like having a smart team** that knows when to jump in and help, without you managing who does what.
|
||||
|
||||
**Manual control available** when you want it (like asking specifically for a security review of frontend code), but most of the time you can just... let it work. 🪄
|
||||
|
||||
---
|
||||
|
||||
## 🚀 Just Try These (No Persona Knowledge Required)
|
||||
|
||||
```bash
|
||||
# These automatically activate the right experts:
|
||||
/analyze payment-system/ # → Security + backend experts auto-activate
|
||||
/build react-app/ # → Frontend specialist takes over
|
||||
/improve slow-queries.sql # → Performance optimizer jumps in
|
||||
/troubleshoot "auth failing" # → Debug specialist + security expert coordinate
|
||||
```
|
||||
|
||||
**See the pattern?** You focus on what you want to do, SuperClaude figures out who should help. Everything below is for when you get curious about who's on the team.
|
||||
|
||||
---
|
||||
|
||||
Think of SuperClaude personas as having a team of specialists on demand. Each persona brings different expertise, priorities, and perspectives to help you with specific types of work.
|
||||
|
||||
## What Are Personas? 🤔
|
||||
|
||||
**Personas are AI specialists** that change how SuperClaude approaches your requests. Instead of one generic assistant, you get access to 11 different experts who think and work differently.
|
||||
**Personas are AI specialists** that automatically adapt SuperClaude's behavior for different types of work. Instead of generic responses, you get expert-level help from the right specialist.
|
||||
|
||||
**How they work:**
|
||||
- **Auto-activation** - SuperClaude picks the right persona based on your request
|
||||
- **Manual control** - You can explicitly choose with `--persona-name` flags
|
||||
- **Different priorities** - Each persona values different things (security vs speed, etc.)
|
||||
- **Specialized knowledge** - Each has deep expertise in their domain
|
||||
- **Cross-collaboration** - Personas can work together on complex tasks
|
||||
**How they actually work in practice:**
|
||||
- **Auto-activation** - SuperClaude automatically picks the right expert (90% of the time this is all you need!)
|
||||
- **Smart detection** - Recognizes security work, frontend tasks, performance issues, etc.
|
||||
- **Seamless switching** - Different experts jump in as needed within the same conversation
|
||||
- **Team coordination** - Multiple experts collaborate automatically on complex tasks
|
||||
- **Manual override available** - You can explicitly choose with `--persona-name` flags when you want a different perspective
|
||||
|
||||
**Why use personas?**
|
||||
- Get expert-level advice for specific domains
|
||||
- Better decision-making aligned with your goals
|
||||
- More focused and relevant responses
|
||||
- Access to specialized workflows and best practices
|
||||
**Why this matters (automatically):**
|
||||
- Get expert-level advice without knowing which expert to ask
|
||||
- Better decision-making aligned with what you're actually working on
|
||||
- More focused and relevant responses based on the task
|
||||
- Access to specialized workflows that activate when useful
|
||||
|
||||
**The magic**: You just work on your stuff, and the right experts show up when needed. 🎯
|
||||
|
||||
## The SuperClaude Team 👥
|
||||
|
||||
@@ -788,47 +820,52 @@ Personas often work together automatically. Here are common collaboration patter
|
||||
|
||||
## Tips for Effective Persona Usage 💡
|
||||
|
||||
### Getting Started
|
||||
1. **Let auto-activation work** - It's usually right
|
||||
2. **Try manual activation** - Experiment with `--persona-*` flags
|
||||
3. **Watch the differences** - See how different personas approach the same problem
|
||||
4. **Use appropriate commands** - Some personas work better with specific commands
|
||||
### Getting Started (The Honest Way)
|
||||
1. **Just ignore personas completely at first** - Auto-activation handles everything
|
||||
2. **Use basic commands normally** - `/analyze`, `/build`, `/improve` work great without persona knowledge
|
||||
3. **Notice what happens** - You'll see different types of expertise emerge naturally
|
||||
4. **Trust the automation** - SuperClaude usually picks better experts than manual selection
|
||||
|
||||
### Getting Advanced
|
||||
1. **Learn persona priorities** - Understand what each values most
|
||||
2. **Use persona combinations** - Different perspectives on complex problems
|
||||
3. **Override when needed** - Don't be afraid to choose different personas
|
||||
4. **Match personas to phases** - Use different personas for different project phases
|
||||
### Getting Advanced (If You Want To)
|
||||
1. **Experiment with manual override** - Try `--persona-security` on frontend code for different perspectives
|
||||
2. **Learn the team members** - Read about individual personas when you get curious
|
||||
3. **Watch persona combinations** - See how multiple experts collaborate on complex problems
|
||||
4. **Use for learning** - Ask different personas the same question to see different approaches
|
||||
|
||||
### Best Practices
|
||||
- **Match persona to problem type** - Security persona for security issues
|
||||
- **Consider project phase** - Architect for planning, QA for testing
|
||||
- **Use multiple perspectives** - Complex problems benefit from multiple viewpoints
|
||||
- **Trust auto-activation** - It learns from patterns and usually gets it right
|
||||
### Best Practices (Keep It Simple)
|
||||
- **Let auto-activation work first** - Override only when you want different perspectives
|
||||
- **Don't overthink it** - The right experts show up when needed
|
||||
- **Use for experimentation** - Try different personas on the same problem for learning
|
||||
- **Trust the intelligence** - Auto-activation learns from patterns and keeps getting better
|
||||
|
||||
---
|
||||
|
||||
## Final Notes 📝
|
||||
|
||||
**Remember:**
|
||||
- Personas are like having specialists on your team
|
||||
- Auto-activation works well, but manual control gives you flexibility
|
||||
- Different personas have different priorities and perspectives
|
||||
- Complex problems often benefit from multiple personas
|
||||
**The real truth about personas** 💯:
|
||||
- **Auto-activation is usually better** than trying to pick the right expert yourself
|
||||
- **You can completely ignore this guide** and still get expert help automatically
|
||||
- **Personas exist to help you** - not to create complexity you need to manage
|
||||
- **Learning happens naturally** through use, not through studying persona descriptions
|
||||
|
||||
**Still evolving:**
|
||||
- Persona auto-activation is getting smarter over time
|
||||
- Collaboration patterns between personas are improving
|
||||
- New specialized knowledge is being added regularly
|
||||
**Don't feel overwhelmed by the team** 🧘♂️:
|
||||
- You don't need to know what each persona does
|
||||
- SuperClaude handles expert selection intelligently
|
||||
- The detailed descriptions above are for curiosity, not necessity
|
||||
- You're not missing anything by letting auto-activation work
|
||||
|
||||
**When in doubt:**
|
||||
- Let auto-activation do its thing first
|
||||
- Try the mentor persona for learning and understanding
|
||||
- Use specific personas when you know what expertise you need
|
||||
- Experiment with different personas on the same problem
|
||||
**When you might manually choose personas**:
|
||||
- **Curiosity** - "What would a security expert think about this frontend code?"
|
||||
- **Learning** - "How would different experts approach this problem?"
|
||||
- **Experimentation** - "Let me see this through a performance lens"
|
||||
- **Override** - "I want architectural advice on this small utility function"
|
||||
|
||||
**Happy persona-ing!** 🎭 Having specialists available makes development so much more effective when you know how to work with them.
|
||||
**Keep it simple** 🎯:
|
||||
- Use normal commands like `/analyze some-code/`
|
||||
- Let the right experts automatically show up
|
||||
- Manual persona control is available when you want it, not because you need it
|
||||
- Focus on your work, not on managing who helps you
|
||||
|
||||
---
|
||||
|
||||
*It's like having a whole development team in your pocket - just way less coffee consumption! ☕*
|
||||
*Behind all this apparent complexity of having 11 specialists, SuperClaude is actually simple to use. Just start coding and let the experts show up automatically! 🚀*
|
||||
Reference in New Issue
Block a user