rogee/superpowers
1
0
Fork 0
mirror of https://github.com/obra/superpowers.git synced 2026-04-21 00:49:06 +08:00
Code Issues Packages Projects Releases Wiki Activity

Show skills list and getting-started at session start

Browse Source 
Session start hook now:
- Inlines full getting-started/SKILL.md content (no @ links in hooks)
- Runs find-skills and shows complete skills list
- Shows tool paths after the guide

Getting-started improvements:
- Removed "Just Read This Guide?" section (redundant with hook)
- Removed "Last thing" announcement requirement
- Tightened intro from ~80 to ~35 words
- Simplified "How to Load Skills" section
- Updated Workflow 2 to reference skills list shown at session start
- Removed redundant find-skills path examples

This eliminates friction - agents see all available skills immediately without
needing to search first. No excuse for "I didn't want to spend time searching."
This commit is contained in:
Jesse Vincent
2025-10-10 22:59:26 -07:00
parent 33622d710e
commit 015a07f7d7
2 changed files with 16 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
skills/getting-started/SKILL.md
View File

@@ -7,32 +7,11 @@ version: 3.1.0
# Getting Started with Skills
Two skill libraries work together:
- **Core skills** at `${CLAUDE_PLUGIN_ROOT}/skills/` (from plugin)
- **Personal skills** at `~/.config/superpowers/skills/` (yours to create and share)
Skills live in two places:
- **Core:** `${CLAUDE_PLUGIN_ROOT}/skills/` (from plugin)
- **Personal:** `~/.config/superpowers/skills/` (yours to create)
Personal skills shadow core skills when names match.
## Just Read This Guide?
**RIGHT NOW**: Check out all the skills you've got!
`find-skills` with no args will show all your skills
**THEN**: Follow the workflows below based on what your partner is trying to do.
## How to Reference Skills
- Format: `skills/category/skill-name` (no @ prefix, no /SKILL.md suffix)
- Example: `skills/collaboration/brainstorming` or `skills/testing/test-driven-development`
- Load with your Read tool when you need them.
**When you see skill references in documentation:**
- `skills/path/name` → Check personal first (`~/.config/superpowers/skills/path/name/SKILL.md`)
- If not found, check core (`${CLAUDE_PLUGIN_ROOT}/skills/path/name/SKILL.md`)
- Load supporting files only when you need them
Personal skills shadow core when names match. To load `skills/path/name`, check personal first, then core.
## Mandatory Workflow 1: Brainstorming Before Coding
@@ -49,11 +28,7 @@ Personal skills shadow core skills when names match.
## Mandatory Workflow 2: Before ANY Task
**1. Find skills** (shows all, or filter by pattern):
```bash
find-skills [PATTERN] # Filter by grep-compatible pattern
```
**1. Check the skills list** shown at session start, or run `find-skills [PATTERN]` to filter.
**2. Check if historical context would help:**
Review Workflow 3 conditions. If applicable, dispatch subagent to search past work.
@@ -155,8 +130,3 @@ Your human partner's specific instructions describe WHAT to do, not HOW.
**Skill has checklist?** TodoWrite for every item.
**Skills are mandatory when they exist, not optional.**
## Last thing
In the first response after reading this guide, you MUST announce to the user that you have read the getting started guide