From compound-engineering
This skill should be used when the user asks about "knowledge debt", "spec staleness", "cleanup subsystem specs", "stale discoveries", or when Claude notices during work that subsystem specs seem outdated, hot-patch comments are accumulating, or friction logs are large. Provides awareness of knowledge system decay patterns.
npx claudepluginhub mberto10/mberto-compoundThis skill uses the workspace's default tool permissions.
Recognize and flag knowledge system decay during normal engineering work. This skill provides the **diagnostic lens** — `/gc` provides the systematic remediation.
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.
Recognize and flag knowledge system decay during normal engineering work. This skill provides the diagnostic lens — /gc provides the systematic remediation.
| Signal | What It Means | Severity |
|---|---|---|
helpful_skills entry fails to resolve | Broken reference — skill deleted or renamed | High |
recently_fixed entry is very old | Stale data — no longer "recent" | Low |
| Invariant seems wrong based on current code | Spec drift — code evolved past the spec | Medium |
| Multiple hot-patch comments on one spec | Comment noise — cluttering the spec | Medium |
| Friction log has 20+ entries | Extraction backlog — patterns going unnoticed | High |
Gap marked addressed but fix seems missing | Premature closure — gap reopened silently | Medium |
| Harness guardrail never triggers in 20+ issues | Component may be unnecessary — model improved past it | Low |
| Harness guardrail triggers every single issue | Component doing heavy lifting — keep and possibly strengthen | Info |
| ORCHESTRATOR.md lesson has no recent references | Stale knowledge — may no longer apply | Low |
| Signal | What It Means | Severity |
|---|---|---|
| Discovery artifact is months old | Forgotten finding — consolidate or reject | Medium |
| Deferred discovery has been deferred 2+ times | Decision avoidance — force a decision | High |
| Same friction point logged 3+ times | Unextracted pattern — encode it or accept it | High |
| Signal | What It Means | Severity |
|---|---|---|
paths.owned glob matches no files | Stale ownership — files moved or deleted | High |
| Milestone says "prototype" but tests pass | Milestone drift — evidence exceeds stated level | Low |
| Description doesn't match actual code | Narrative drift — spec tells wrong story | Medium |
/gc./gc.| Category | Mechanical (can script) | Narrative (needs judgment) |
|---|---|---|
| Broken references | helpful_skills, stale dependencies | — |
| Stale dates | recently_fixed age | — |
| Artifact accumulation | Discovery backlog, friction log size | — |
| Spec drift | paths.owned globs, hot-patch comment count | Milestone drift, description accuracy |
| Missing knowledge | — | Invariant completeness, gap status accuracy |
| Comment noise | Hot-patch comment count | — |
Mechanical items can become architecture invariant check scripts. Narrative items require Claude's judgment — they're the unique value of /gc.
/gc command provides action — scan, report, and fix/review and /harness/discover processes friction patterns into component specs/consolidate processes discovery artifacts into plugin componentsThe full maintenance cycle: notice (this skill) → scan (/gc) → extract (/discover) → encode (/consolidate).