From magic-powers
Transform code diffs (PRs, branches, files) into structured YAML briefs for analytics instrumentation planning. Minimal MCP usage — primarily code analysis.
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
- Starting an instrumentation workflow from a pull request URL or branch name
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.
Determine what the user has provided and select the right ingestion path:
github.com/.../pull/123) → fetch the diff via GitHub API or gh pr difffeat/checkout-v2) → run git diff main...feat/checkout-v2 to get full changesetOutput of classification: input_type + source_reference + list of files changed.
For each changed file, extract:
Focus on user-facing changes only. Skip internal refactors with no UX impact.
Filter parsed changes down to what matters for analytics:
page_viewed eventsbutton_clicked or action-specific eventsform_started, form_submitted, form_abandoned eventsOutput a YAML document consumed by discover-event-surfaces:
brief:
summary: "One sentence describing the feature change"
pr_reference: "<URL or branch>"
files_changed: 12
new_surfaces:
- type: screen
name: "Checkout Confirmation Page"
file: "src/pages/checkout/confirmation.tsx"
interactions:
- "Continue Shopping button"
- "View Order Details link"
- type: form
name: "Shipping Address Form"
file: "src/components/ShippingForm.tsx"
fields: ["street", "city", "zip", "country"]
removed_surfaces:
- type: screen
name: "Legacy Cart Page"
note: "Replaced by new unified checkout"
changed_behaviors:
- description: "Payment step now skipped for free orders"
files: ["src/flows/checkout.ts"]
impact: "high — affects conversion funnel"
technical_context:
stack: "React + TypeScript"
analytics_sdk: "Amplitude Browser SDK v2"
existing_tracking_file: "src/analytics/events.ts"
This skill uses minimal MCP — primarily local code analysis tools:
mcp__Amplitude__* tools required at this stagediscover-event-surfaces which uses Amplitude toolsA structured YAML brief with these top-level sections:
brief:
summary: <string>
pr_reference: <URL or branch name>
files_changed: <count>
new_surfaces: <list of {type, name, file, interactions}>
removed_surfaces: <list of {type, name, note}>
changed_behaviors: <list of {description, files, impact}>
technical_context: {stack, analytics_sdk, existing_tracking_file}
After producing the YAML, state: "Brief ready. Proceed to discover-event-surfaces to map these surfaces to candidate analytics events."