Documenting Project History
This skill maintains a living knowledge base of prompts, decisions, and architectural evolution for StickerNest. It helps future AI sessions understand context and continue work seamlessly.
When to Use This Skill
- End of session: Document what was accomplished
- Major feature complete: Record the approach taken
- Architecture decision: Capture the why behind choices
- Starting new session: Review history for context
- User explicitly asks: "document this", "add to history", "record what we did"
How to Document
When documenting, add entries to prompt-history.md in this skill folder:
## [Category] Brief Title
**Date**: YYYY-MM-DD
**Summary**: 1-2 sentence overview
**Key Decisions**:
- Decision 1 and why
- Decision 2 and why
**Files Changed**: List of main files
**Related**: Links to related entries
Categories
| Category |
Description |
Examples |
ARCHITECTURE |
System design, patterns, structure |
Parallel rendering, state management |
WIDGETS |
Widget system, creation, pipelines |
New widget types, Protocol changes |
SPATIAL |
VR/AR, 3D rendering, WebXR |
XR entry, coordinate systems |
UI/UX |
Components, panels, interactions |
Toolbars, modals, gestures |
AI |
AI features, prompts, generation |
Widget generation, reflection |
INFRA |
Build, deploy, testing, CI/CD |
Vite config, Playwright tests |
FIX |
Bug fixes, debugging sessions |
XR issues, rendering bugs |
SKILL |
Claude Code skills created |
Meta-documentation |
Documentation Template
When the user asks to document, use this format:
---
## [CATEGORY] Title of Work Done
**Date**: [Today's date]
**Session Summary**:
[2-3 sentences describing what was accomplished]
**User's Original Request**:
> [Quote or paraphrase the user's initial prompt]
**Approach Taken**:
1. [Step 1]
2. [Step 2]
3. [Step 3]
**Key Decisions**:
- **[Decision]**: [Why this choice was made]
**Files Created/Modified**:
- `path/to/file.ts` - [brief description]
**Lessons Learned**:
- [Any insights for future sessions]
**Related Entries**: [Links to related history]
---
Viewing History
To help users understand project evolution:
- Read
prompt-history.md for full history
- Summarize by category if requested
- Find related past work for current tasks
- Identify patterns in user requests
Maintaining the Archive
- Keep entries concise but complete
- Link related entries together
- Update if decisions are reversed
- Archive outdated approaches
Quick Reference Commands
When user says:
- "document this" → Add entry for current session
- "what did we do last time?" → Read recent history
- "show widget history" → Filter by WIDGETS category
- "update the history" → Append to prompt-history.md
1---2name: documenting-project-history3description: Documenting and categorizing project prompts and decisions for StickerNest. Use when the user asks to document a session, record what was built, update project history, add to the prompt archive, or when starting a new session and needing context. Covers prompt categorization, decision history, and architectural evolution.4---5
6# Documenting Project History
7
8This skill maintains a living knowledge base of prompts, decisions, and architectural evolution for StickerNest. It helps future AI sessions understand context and continue work seamlessly.
9
10## When to Use This Skill
11
121. **End of session**: Document what was accomplished
132. **Major feature complete**: Record the approach taken
143. **Architecture decision**: Capture the why behind choices
154. **Starting new session**: Review history for context
165. **User explicitly asks**: "document this", "add to history", "record what we did"
17
18## How to Document
19
20When documenting, add entries to `prompt-history.md` in this skill folder:
21
22```markdown
23## [Category] Brief Title
24**Date**: YYYY-MM-DD
25**Summary**: 1-2 sentence overview
26**Key Decisions**:
27- Decision 1 and why
28- Decision 2 and why
29**Files Changed**: List of main files
30**Related**: Links to related entries
31```
32
33## Categories
34
35| Category | Description | Examples |
36|----------|-------------|----------|
37| `ARCHITECTURE` | System design, patterns, structure | Parallel rendering, state management |
38| `WIDGETS` | Widget system, creation, pipelines | New widget types, Protocol changes |
39| `SPATIAL` | VR/AR, 3D rendering, WebXR | XR entry, coordinate systems |
40| `UI/UX` | Components, panels, interactions | Toolbars, modals, gestures |
41| `AI` | AI features, prompts, generation | Widget generation, reflection |
42| `INFRA` | Build, deploy, testing, CI/CD | Vite config, Playwright tests |
43| `FIX` | Bug fixes, debugging sessions | XR issues, rendering bugs |
44| `SKILL` | Claude Code skills created | Meta-documentation |
45
46## Documentation Template
47
48When the user asks to document, use this format:
49
50```markdown
51---
52
53## [CATEGORY] Title of Work Done
54**Date**: [Today's date]
55**Session Summary**:
56[2-3 sentences describing what was accomplished]
57
58**User's Original Request**:
59> [Quote or paraphrase the user's initial prompt]
60
61**Approach Taken**:
621. [Step 1]
632. [Step 2]
643. [Step 3]
65
66**Key Decisions**:
67- **[Decision]**: [Why this choice was made]
68
69**Files Created/Modified**:
70- `path/to/file.ts` - [brief description]
71
72**Lessons Learned**:
73- [Any insights for future sessions]
74
75**Related Entries**: [Links to related history]
76
77---
78```
79
80## Viewing History
81
82To help users understand project evolution:
83
841. Read `prompt-history.md` for full history
852. Summarize by category if requested
863. Find related past work for current tasks
874. Identify patterns in user requests
88
89## Maintaining the Archive
90
91- Keep entries concise but complete
92- Link related entries together
93- Update if decisions are reversed
94- Archive outdated approaches
95
96## Quick Reference Commands
97
98When user says:
99- "document this" → Add entry for current session
100- "what did we do last time?" → Read recent history
101- "show widget history" → Filter by WIDGETS category
102- "update the history" → Append to prompt-history.md
majiayu000