From coordinator
Periodic maintenance of lessons files — trims stale entries, merges duplicates, and deletes exhausted feature-scoped files. Implements the 'Periodic trim' rule from CLAUDE.md's Self-Improvement Loop. This skill should be used when lessons.md is getting long, when a feature is complete and its lessons file should be cleaned up, or when periodic housekeeping is needed. Invoked by /update-docs (Phase 6) or standalone.
npx claudepluginhub oduffy-delphi/coordinator-claudeThis skill uses the workspace's default tool permissions.
Review `tasks/lessons.md` (global) and any `tasks/<feature>/lessons.md` files. This is the periodic safety net described in the Self-Improvement Loop guidelines in CLAUDE.md.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Review tasks/lessons.md (global) and any tasks/<feature>/lessons.md files. This is the periodic safety net described in the Self-Improvement Loop guidelines in CLAUDE.md.
Discovery: Find feature-scoped lessons files via tasks/*/lessons.md (glob). Each match is a feature-scoped file. Global lessons live at tasks/lessons.md (no subdirectory).
Skip if no lessons files exist.
For each lessons file:
tasks/<feature>/lessons.md) relates to completed work and all entries are either stale or promoted to the global file, delete itJudgment call: When in doubt, keep the entry. The cost of a slightly long file is lower than losing a lesson that would have prevented a future mistake. But be honest — most one-off debugging notes don't belong here.