Skip to content

Commit e00042b

Browse files
sgx-labsclaude
andcommitted
Add Skills and Flywheels documentation
New welcome note covers: Skills: - /document-decision — Create well-formatted decision notes - /create-handoff — Generate session summaries - /create-hub — Create central reference notes - /search-deep — Trigger comprehensive search Flywheels explained: - Usage Flywheel (notes that help get boosted) - Documentation Flywheel (value → more documentation) - Quality Flywheel (good notes → better results → better notes) - Handoff Flywheel (compound productivity) Includes kickstart guide and flywheel health metrics. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent 2fdc611 commit e00042b

1 file changed

Lines changed: 228 additions & 0 deletions

File tree

Lines changed: 228 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,228 @@
1+
---
2+
title: "SAME — Skills and Flywheels"
3+
tags: [same, reference, skills, automation]
4+
content_type: hub
5+
---
6+
7+
# Skills and Flywheels
8+
9+
Supercharge SAME with reusable skills and self-reinforcing flywheels.
10+
11+
## What Are Skills?
12+
13+
Skills are reusable prompts that automate common workflows. In Claude Code, they live in `.claude/skills/` and are invoked with slash commands.
14+
15+
## Recommended SAME Skills
16+
17+
### /document-decision
18+
19+
Create a well-formatted decision note:
20+
21+
```markdown
22+
# .claude/skills/document-decision.md
23+
24+
Create a decision note with this structure:
25+
26+
---
27+
title: "Decision: [Topic]"
28+
tags: [decision, <relevant-tags>]
29+
content_type: decision
30+
date: <today>
31+
---
32+
33+
# Decision: [Topic]
34+
35+
## Context
36+
What problem or question prompted this decision?
37+
38+
## Decision
39+
What did we decide? Be specific.
40+
41+
## Rationale
42+
Why this approach? What alternatives were considered?
43+
44+
## Consequences
45+
What are the implications? Any follow-up needed?
46+
```
47+
48+
### /create-handoff
49+
50+
Generate a session summary:
51+
52+
```markdown
53+
# .claude/skills/create-handoff.md
54+
55+
Create a handoff note summarizing this session:
56+
57+
---
58+
title: "Session Handoff - <date>"
59+
tags: [handoff, session]
60+
content_type: handoff
61+
date: <today>
62+
---
63+
64+
# Session Handoff
65+
66+
## What We Worked On
67+
- Bullet points of main activities
68+
69+
## Decisions Made
70+
- Key decisions with brief rationale
71+
72+
## Current State
73+
Where did we leave off?
74+
75+
## Next Steps
76+
What should the next session pick up?
77+
78+
## Open Questions
79+
Anything unresolved?
80+
```
81+
82+
### /create-hub
83+
84+
Create a hub note for a topic:
85+
86+
```markdown
87+
# .claude/skills/create-hub.md
88+
89+
Create a hub note that serves as a central reference:
90+
91+
---
92+
title: "[Topic] Hub"
93+
tags: [hub, <topic>]
94+
content_type: hub
95+
---
96+
97+
# [Topic]
98+
99+
Central reference for [topic].
100+
101+
## Overview
102+
Brief description of this area.
103+
104+
## Key Decisions
105+
- [[Decision: ...]]
106+
107+
## Resources
108+
- Links to relevant notes
109+
- External documentation
110+
111+
## Current Status
112+
What's the state of this area?
113+
```
114+
115+
### /search-deep
116+
117+
Trigger a comprehensive search:
118+
119+
```markdown
120+
# .claude/skills/search-deep.md
121+
122+
Search the user's notes thoroughly:
123+
124+
1. Search with the exact query (top_k=15)
125+
2. Try 2-3 alternate phrasings
126+
3. Search for related concepts
127+
4. Report what you found or didn't find
128+
129+
If nothing found, offer to document the topic.
130+
```
131+
132+
## The SAME Flywheels
133+
134+
Flywheels are self-reinforcing loops. SAME has several:
135+
136+
### 1. The Usage Flywheel
137+
138+
```
139+
AI uses a note
140+
141+
Note gets "access boost"
142+
143+
Note ranks higher next time
144+
145+
AI uses it more
146+
147+
Better results over time
148+
```
149+
150+
Notes that actually help get surfaced more. Notes that don't help fade away.
151+
152+
### 2. The Documentation Flywheel
153+
154+
```
155+
User documents decision
156+
157+
AI references it in future
158+
159+
User sees value ("it remembered!")
160+
161+
User documents more
162+
163+
Richer knowledge base
164+
```
165+
166+
The more you document, the smarter your AI gets, which motivates more documentation.
167+
168+
### 3. The Quality Flywheel
169+
170+
```
171+
Well-structured note
172+
173+
Better search matches
174+
175+
AI produces better output
176+
177+
User learns what works
178+
179+
Writes better notes
180+
```
181+
182+
Good notes teach you what format works, leading to better notes.
183+
184+
### 4. The Handoff Flywheel
185+
186+
```
187+
Session ends with handoff
188+
189+
Next session starts with context
190+
191+
Faster ramp-up
192+
193+
More productive session
194+
195+
Better handoff for next time
196+
```
197+
198+
Handoffs compound — each one makes the next session more productive.
199+
200+
## Kickstarting the Flywheels
201+
202+
### Week 1: Foundation
203+
- Document your top 3 project decisions
204+
- Create one hub note for your main project
205+
- Let SAME generate handoffs automatically
206+
207+
### Week 2: Build Momentum
208+
- Document decisions as you make them
209+
- Notice when SAME surfaces something useful
210+
- Add context when SAME misses something
211+
212+
### Week 3+: Cruise
213+
- Flywheels are spinning
214+
- AI remembers your project
215+
- Documentation happens naturally
216+
217+
## Measuring Flywheel Health
218+
219+
```bash
220+
same status # How many notes indexed?
221+
same log # What's being surfaced?
222+
same budget # Is surfaced context being used?
223+
```
224+
225+
If surfaced context isn't being used, either:
226+
- Notes need better structure
227+
- Search profile needs tuning (`same profile use precise`)
228+
- Content isn't matching queries (try different terminology)

0 commit comments

Comments
 (0)