Vibe Reflect And Compound
Productivityvibe-reflect-and-compoundVibe Reflect And Compound is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Extracts learnings from completed work, feedback, or failures. Updates a persistent learnings file with capped entries. Use after receiving feedback, fixing bugs, or completing complex tasks.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/productivity/reflect-and-compound/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/vibe-reflect-and-compound, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
vibe-reflect-and-compound
Every problem solved should produce reusable knowledge. Don't just fix — learn.
When to Use This Skill
- After receiving feedback on your work (positive or negative)
- After a failed attempt or debugging session
- After completing a complex task
- After a code review with substantive feedback
- Periodically (e.g., end of week) to consolidate learnings
When NOT to Use This Skill
- After trivial tasks (typo fixes, simple renames)
- When there's nothing new to learn (routine work)
- During active implementation (reflect AFTER, not DURING)
Steps
-
Gather input — What happened?
- What was the task/feedback/failure?
- What was expected vs. what actually happened?
- What was the root cause?
-
Extract patterns — Ask:
- "What would I do differently next time?"
- "What pattern does this represent?"
- "Is this a recurring theme?"
- "What would have caught this earlier?"
-
Formulate learnings — Each learning should be:
- Actionable — Not "be careful" but "always run race detection before committing concurrent code"
- Specific — Not "tests are important" but "property-based tests catch edge cases that table-driven tests miss for parser code"
- Contextual — Include when it applies and when it doesn't
-
Update persistent storage — Write to:
- Project learnings file (e.g.,
docs/learnings.mdorLEARNINGS.md) - Claude memory (if available)
- Team wiki/docs
- Project learnings file (e.g.,
-
Cap management — Keep max 30 active learnings. When exceeding:
- Archive older learnings to a dated file
- Keep only the most frequently referenced ones active
- Merge similar learnings
Output Format
Reflection: [Context]
Trigger: [What prompted this reflection]
Learnings Extracted:
-
[Pattern name]: [Actionable learning]
- Applies when: [context]
- Evidence: [what happened]
-
[Pattern name]: [Actionable learning]
- Applies when: [context]
- Evidence: [what happened]
Updated: [Where learnings were saved] Active Count: X/30