Claude Code plugins
2 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 2 plugins that match these filters. Clear filters
Scenario-driven UI development: a versioned design chain in docs/ux/ that runs product vision -> personas, JTBD, journeys and stories -> user flows -> a screens+states UI map with Figma frames -> traced use-case scenarios -> evidence-backed audits -> concrete fix plans. Skills: vision, ux-foundation, ux-flows, ux-scenarios, ux-audit, brand-voice, copywriting. /ux is the single plain-language entry point and reaches every skill; a stdlib linter fails on doc drift; a tag-indexed best-practices catalog, PRN heuristics and component guidelines guide design; one style pack (via the sheleg-design companion) locks the visual identity.
development
Briefs statutes and legislative Acts using the MAPS + RULES framework: a system-level map of the whole Act (citation and text status, purpose, structure, scope, definitions) plus operational rule-modules for each operative provision (elements, legal effect, exceptions, procedure, consequences, forum, interaction rules). Works from statutory text supplied by the user and never invents statutory language. Use when briefing a statute, analyzing legislative text, mapping statutory architecture, extracting the elements of a provision, or applying a statute to facts. Triggers on "brief this statute", "analyze this Act", "map the statute", "apply [statute] to [scenario]", "what are the elements of [provision]", "statutory analysis", and on references to codified sections such as 42 U.S.C. or the Texas Health and Safety Code. Two modes: (A) text-only briefing for structural analysis, and (B) scenario-driven briefing that applies provisions to specific facts with verbatim quotation and pinpoint