From magic-powers
Use when documenting architecture decisions, capturing the context and trade-offs behind technical choices
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
When making a significant technical decision that will be hard to reverse, affects multiple teams, or needs to be understood by future engineers.
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.
When making a significant technical decision that will be hard to reverse, affects multiple teams, or needs to be understood by future engineers.
Write one when:
Don't write one for: library patch versions, CSS changes, minor refactoring.
# ADR-[NNN]: [Short Title]
**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-NNN
**Deciders:** [names or teams]
## Context
[What situation are we in? What forces are at play? What is the problem?]
## Decision
[The decision we made. Use active voice: "We will use X because..."]
## Options Considered
### Option A: [Name]
**Pros:** ...
**Cons:** ...
### Option B: [Name]
**Pros:** ...
**Cons:** ...
## Consequences
**Positive:**
- [What becomes easier or better?]
**Negative:**
- [What becomes harder or worse? What do we give up?]
**Risks:**
- [What could go wrong?]
## References
- [Links to relevant docs, RFCs, benchmarks]
docs/adr/ in the repo (versioned with code)docs/adr/)