From compound-engineering
This skill should be used when the user invokes "/consolidate", asks to "process discoveries", "implement compound improvements", "review pending patterns", or wants to turn discovered patterns into actual project plugin components and subsystem knowledge updates. Provides methodology for reviewing, approving, and implementing discovery artifacts.
npx claudepluginhub mberto10/mberto-compoundThis skill uses the workspace's default tool permissions.
Process pending discovery artifacts and implement approved changes into the local project plugin and subsystem knowledge. Consolidation is the second half of the compound loop — where discovered patterns become permanent improvements.
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.
Process pending discovery artifacts and implement approved changes into the local project plugin and subsystem knowledge. Consolidation is the second half of the compound loop — where discovered patterns become permanent improvements.
Load references/compounding-methodology.md for the underlying philosophy — where learnings land, the heuristics format, and anti-patterns to avoid.
Check the project's discovery directory:
./compound-discoveries/*.md
If user provides filter text, focus on matching discoveries.
For each discovery, present:
Group by subsystem when multiple discoveries affect the same area.
Before presenting for approval, evaluate each proposed change:
Evolvability Check:
If a change reduces evolvability, flag it. Sometimes worth it, but should be conscious.
Cross-Pollination Check:
For each discovery, user can:
Wait for explicit approval before making changes. Never auto-implement.
Based on component type:
Skill → Create in local plugin:
skills/{skill-name}/SKILL.md with proper frontmatterplugin.jsonCommand → Create in local plugin:
commands/{name}.md with proper frontmatterplugin.jsonAgent → Create in local plugin:
agents/{name}.md with proper frontmatterplugin.jsonHook → Update local plugin:
hooks/hooks.jsonAfter creating a component:
Add to helpful_skills:
helpful_skills:
- name: "{skill name}"
plugin: "{local plugin name}"
when: "{when this skill is relevant}"
Mark addressed gaps:
gaps:
- id: GAP-XXX
status: addressed
addressed_by: "{component name}"
./compound-discoveries/archived/After changes:
---
name: {Skill Name}
description: This skill should be used when [specific trigger phrases and contexts].
---
# {Skill Name}
## Purpose
[What this skill enables]
## Core Concepts
[Essential knowledge]
## Workflow
[How to apply it]
## Examples
[Concrete applications]
---
description: [What this command does]
argument-hint: [What arguments it accepts]
allowed-tools: [Tools needed]
---
# {Command Name}
[Implementation instructions...]
When adding helpful_skills:
when field for context on when the skill appliesAfter consolidation:
When changes are ready to commit:
compound: implement discoveries from [date range]
- [plugin]: create [component type] [name]
- [subsystem]: update helpful_skills
- [subsystem]: address GAP-XXX