From vibe-to-prod-skills
Capture learnings after tasks. Triggers on task completion, repeated mistakes, retrospective requests, or "what did I learn".
npx claudepluginhub shimyth/vibe-to-prod --plugin vibe-to-prod-skillsThis skill uses the workspace's default tool permissions.
After completing a task, briefly reflect and capture learnings.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
After completing a task, briefly reflect and capture learnings.
Ask yourself:
| Learning Type | Action |
|---|---|
| Pattern/gotcha | Store in Memory MCP |
| Missing automation | Create issue/TODO |
| Repeated mistake | Update .claude/rules/ |
| Complex process | Create .claude/skills/ |
When storing a learning in Memory MCP:
mcp__memory__create_entities({
entities: [{
name: "Learning_TOPIC",
entityType: "development_learning",
observations: [
"Context: What was happening",
"Learning: What was learned",
"Application: How to apply it"
]
}]
})
| Issue | Solution |
|---|---|
| Same mistake twice | Add rule to .claude/rules/ |
| Manual process > 5 min | Create skill or hook |
| New tool/pattern | Store in Memory MCP |
| Missing documentation | Update docs |
When you make the same mistake twice:
# .claude/rules/my-rules.md
---
paths: relevant/path/**
description: Rules for this area
---
## Critical Rules
| Rule | Why |
|------|-----|
| Don't do X | Because Y happens |
When a process is complex and repeated:
.claude/skills/my-skill/# .claude/skills/my-skill/SKILL.md
---
name: my-skill
description: When this skill should activate
---
# My Skill
## When to Activate
[Trigger conditions]
## Process
[Steps to follow]
/improve-claude-config for major configuration updates.