菜单
Guide an end-of-session reflection to capture learnings and feelings. Use when finishing a work session, after completing a challenging task, when wanting to consolidate what was learned, or to build a personal learning log over time.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Find UI components from screenshots, route paths, or component names. Use when a designer asks "where does this live?", shares a screenshot and wants to find the code, needs to locate a component by its visual appearance, or wants to understand how a UI element is built. Works with React, Vue, Angular, and other component-based frameworks.
Improve UI copy using proven frameworks (JTBD, benefit-first, error patterns). Use when a designer wants to improve button text, error messages, empty states, or audit copy in a component. Supports interactive walkthrough mode for reviewing changes one-by-one, or batch mode for quick fixes.
Use when writing or reviewing UI copy - rewrites labels, CTAs, helpers, and placeholders through a Jobs to Be Done lens so every element reflects the user's actual goal, not the system's internal model.
Use when defining a feature, writing a PRD, or scoping work - reframes requirements around the user's job instead of the feature or team that owns it. Use before design or development begins.
Analyze a work session to identify repeatable patterns that could become reusable skills or commands. Use at the end of a productive session to capture workflows worth automating, when noticing repetitive multi-step tasks, or when wanting to improve personal productivity with Claude Code.
| name | dcode:reflect-session |
| description | Guide an end-of-session reflection to capture learnings and feelings. Use when finishing a work session, after completing a challenging task, when wanting to consolidate what was learned, or to build a personal learning log over time. |
Pause. Notice what you learned. Capture it before it fades.
For designers who want to grow: Learning happens in the doing—but sticks in the reflecting.
Most learning evaporates within hours. A 5-minute reflection:
Review what was accomplished:
Show the user what you noticed, numbered for easy editing:
Based on this session, here's what I think you learned:
**Technical:**
1. [specific technical learning]
2. [another technical insight]
**Process/Soft Skills:**
3. [workflow or communication learning]
**Patterns Established:**
4. [reusable patterns or approaches discovered]
**Mistakes → Lessons:**
5. [what went wrong and what it taught]
Ask: "Want to keep, edit, or add? (e.g., 'drop 2', 'edit 3: [new text]', 'add: [learning]')"
After learnings are confirmed, ask:
"How do you feel about the work? (e.g., empowered, frustrated, curious, accomplished, drained)"
Let them express freely—one word or a whole paragraph. Feelings are data about sustainability and engagement.
Create a structured reflection entry:
# Session: [Descriptive Title]
**Date:** [Today's date]
**Duration:** [Approximate time spent]
## What I Learned
### Technical
- [Learning 1]
- [Learning 2]
### Process
- [Learning about how I work]
### From Mistakes
- [What went wrong → what I'll do differently]
## How I Feel
[Their feeling and any elaboration]
## Session Context
[1-2 sentence summary of what was built/fixed/explored]
## Tags
[Relevant tags: project names, technologies, skill areas]
Options for saving the reflection:
If they have a preferred journaling setup, use it.
Specific over generic:
align-self: stretch only works when the parent has explicit height"Actionable over vague:
Honest about feelings:
One reflection: mildly useful. Weekly reflections over a year: a personal knowledge base of how you learn and what you know.
"We do not learn from experience. We learn from reflecting on experience." — John Dewey