// Post-task lessons-learned review. Updates knowledge, instruction, and skill files to continuously improve future sessions.
Angular best practices and patterns for oilmod-web library development. USE WHEN writing new components, services, directives, pipes, or refactoring Angular code. Trigger words: component, service, directive, pipe, signal, inject, standalone, reactive, observable, change detection, performance, lazy, template, binding.
Build, publish, and locally link oilmod-web libraries. USE WHEN building libs, publishing to npm, setting up yalc, or troubleshooting build issues. Trigger words: build, publish, yalc, npm, release, version, deploy, link, clean, cache, troubleshoot.
Create new Angular components in the oilmod-web library. USE WHEN generating components, writing Storybook stories, or adding exports. Trigger words: new component, create component, add component, storybook story, export component.
| name | retrospective |
| description | Post-task lessons-learned review. Updates knowledge, instruction, and skill files to continuously improve future sessions. |
After any non-trivial task (feature, bugfix, refactor, debugging session), run this retrospective.
If the lesson is "this is unnecessarily hard," consider whether the root cause can be eliminated (rename, better default, small refactor). File an issue instead of (or in addition to) documenting the workaround.
If someone would need to leave the file to understand the code, the comment is missing.
knowledge/Route here when the lesson describes:
Use the structured notation (OWNS / READS FROM / WRITES TO / INVARIANT / FLOW / TENSION / DECIDED).
instructions/Conventions, naming rules, lint patterns, framework idioms. Add applyTo
glob frontmatter so it auto-loads for matching files.
skills/<name>/SKILL.mdA repeatable procedure with multiple steps (release prep, debugging flow, new-component scaffolding).
Make the documentation update in the same commit (or a follow-up) and reference it in the commit message.