npx claudepluginhub ai-builder-team/ai-builder-plugin-marketplace --plugin mThis skill uses the workspace's default tool permissions.
The user wants to load feature documentation into context. Their hint is: **$ARGUMENTS**
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.
The user wants to load feature documentation into context. Their hint is: $ARGUMENTS
! find features -type d | sort
Identify the feature. Using the feature tree above and the hint "$ARGUMENTS", determine which feature directory the user is referring to. Use judgment — the hint may be partial, misspelled, or colloquial. If genuinely ambiguous between multiple candidates, list them and ask. Otherwise, pick the best match and proceed.
Read the FEATURE.md. Read the FEATURE.md inside the identified feature directory in full. It will tell you the purpose and reference any connected specs.
Discover and read specs. ls the specs/ subfolder inside the feature directory (if it exists). Apply this filter:
spec.md or matching spec-*.md — these are primary specs.checklist.md, research.md, design.md, and any other auxiliary files.Present a summary.
All primary spec files are now in context for follow-up questions.