reflect
Reflect Skill
Review the current conversation and analyze:
Analysis Questions
- Tasks Completed: What features/bugfixes were implemented?
- Errors Encountered: What issues came up and how were they resolved?
- User Feedback: What did the user like/dislike?
- Patterns Discovered: Any reusable patterns or workflows?
- Skill Gaps: What skills are missing that would help?
Output Format
# Session Reflection
## Summary
[Brief overview of what was accomplished]
## Key Learnings
- [Learning 1]
- [Learning 2]
## Improvement Opportunities
- [Opportunity 1]
- [Opportunity 2]
## Skill Recommendations
- [New skill to create?]
- [Existing skill to improve?]
## Action Items
- [ ] Create new skill: [name]
- [ ] Update existing skill: [name]
- [ ] Add to memory: [pattern]
Present findings to the user and ask what to implement or save
Examples
Example 1: After Bug Fix Session
User says: "reflect on what we did" Actions:
- Review conversation history
- Identify: bug root cause, solution approach, key learnings
- Note: skill gaps discovered (e.g., missing debugging patterns)
- Generate reflection report Result: Structured learnings for future sessions
Example 2: After Feature Development
User says: "what did we learn from this sprint" Actions:
- Analyze completed tasks
- Identify patterns: repeated code structures, useful utilities
- Discover improvement opportunities: better testing, refactoring candidates
- Generate actionable recommendations Result: Actionable improvement list
Example 3: After Complex Debugging
User says: "review session and summarize" Actions:
- Trace problem identification flow
- Document hypothesis-validation pattern used
- Note tools/approaches that worked well
- Extract reusable debugging strategy Result: Debugging pattern for future reference
More from jochenyang/jochen-ai-rules
ui-ux-pro-max
UI/UX design-system reasoning and UX quality audit skill. Use when user needs style direction, palette/typography selection, UX review, or design optimization before implementation. Do NOT use for backend logic or database design.
24claude-audit
Audit all .claude/*.md files for redundant instructions, verbose phrasing, and content that could move to memory. Use when user wants to optimize their Claude configuration rules.
1miloya-codebase
Project context engine for repo orientation, cached handoff, and task-focused code retrieval.
1phaser-build
Build 2D HTML5 games for the web using Phaser with WebGL/Canvas rendering. Use when creating Phaser game scaffolds, scenes, core loops, or deployment guidance for web-based releases.
1threejs-builder
>
1agent-teams
Create agent teams for parallel collaboration. Use when user mentions team, parallel, multi-agent, coordinate, collaborate, review team, multiple perspectives, or says "agent-teams".
1