| name | learning-loop-capture |
| description | Use at task handoff, milestone review, or after implementation when project lessons may be reusable for future apps, toolkit docs, AGENTS/CLAUDE instructions, skills, or templates. |
Learning Loop Capture
Use this skill to decide whether a project lesson should improve the toolkit.
Capture Triggers
- A pattern worked well and should be reused.
- A setup mistake caused friction.
- An instruction rule prevented or caused a problem.
- A service, feature, config, UX, testing, or deployment pattern became clearer.
- A workflow or token-use practice should influence future projects.
Workflow
- Read
references/continuous-learning-loop.md; fall back to docs/foundation/continuous-learning-loop.md when installed.
- Decide whether the learning is project-specific or reusable.
- Classify it: Product, UX, Architecture, Data, Testing, Security, Workflow, Tooling, or Token Use.
- Promote only lessons likely to apply to at least two future projects or prevent repeated setup mistakes.
- Propose updates to Notion, docs, skills, templates, or custom agents.
- Keep private/project-specific details out of public toolkit material.
Handoff Snippet
Reusable toolkit learning:
- Learning:
- Applies to future projects:
- Suggested toolkit update: