Design & frontend
15,938 rows, by stacks then stars
1,697 of these skill files have been read, by 1,179 distinct authors, and what they tell an agent counted. What Design & frontend authors agree on, and what they forbid
Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/ux-research Skill
0★ repoWhen to activate: user research, UX research, user interviews, usability testing, surveys, diary studies, research plan, synthesis, insight
Punpun1643/claude-skills/product-designer Skill
no license0★ repoProduce and refine product-design briefs — the document that turns a rough product idea into a buildable MVP spec: vision, personas, jobs-to-be-done, goals/non-goals, numbered functional requirements, key screens, data model, user stories with acceptance criteria, user journeys, success metrics, risks, and milestones, all grounded in human-centered-design principles. Use this skill WHENEVER the user wants to write, expand, critique, or restructure a product brief, MVP plan, PRD, feature spec, or set of user stories — including phrasings like "write a product spec for X", "turn this idea into an MVP plan", "draft the requirements", "write user stories with acceptance criteria", "design this feature", "what should the MVP scope be", "critique this product plan", or "make a PRD". Also use it proactively when a user describes a product idea and asks how to scope or structure it. The skill enforces HCD principles (visible constraints, reversibility, informative feedback, traceability) and that every requirement is testable and tied to a real user need.
SkillMedev/solo-founder-stack/skills/landing-page-copy Skill
0★ repoWrite landing-page copy section by section - hero, social proof, features-as-benefits, objections, CTA - leading with one promise and proving it down the page. Use when someone asks "write my landing page", "improve my hero headline", "what should the homepage say", "turn these features into benefits", or is shipping a new page for a launch or campaign. Do NOT use for testing and optimizing an existing page's conversion rate - use landing-page-cro instead; for the one-line claim itself use positioning-statement; for the full message ladder use messaging-hierarchy.
The same file is in 4 other repositories
jaballer/react-claude-skills/react-component-design Skill
0★ repoReact component architecture and API design — composition, compound components, headless patterns, prop interfaces, controlled vs uncontrolled, polymorphic components, TypeScript prop typing, slot patterns. Use when designing component APIs, building reusable components, structuring a component library, or refactoring component structure. Triggers on "component API", "reusable", "compound component", "headless", "polymorphic", "props", "design a component".
jaballer/react-claude-skills/react-forms-validation Skill
0★ repoComprehensive form patterns for React 19 / Next 15 — Zod schemas with type inference, Server Actions + useFormStatus + useActionState, useOptimistic for instant feedback, react-hook-form when Server Actions aren't on the table, multi-step forms with useReducer + persistence, async validation, file upload with progress, error messages with full a11y wiring (aria-invalid, aria-describedby, role=alert, focus management on errors). Use for any form-heavy interview build — newsletter signup, contact form, login, signup, multi-step onboarding, settings page, file upload. Triggers on "form", "validation", "zod", "react-hook-form", "Server Action", "useFormStatus", "useActionState", "useOptimistic", "controlled vs uncontrolled", "multi-step form", "file upload", "form a11y", "form errors", "newsletter signup".
jaballer/react-claude-skills/react-marketing-patterns Skill
0★ repoMarketing-site React patterns — hero sections, CTAs, pricing tables, testimonial carousels, lead-capture forms, sticky navigation, scroll-triggered animations, FAQ accordions, feature comparison tables, newsletter signups. Use when building landing pages, marketing components, conversion-focused UI, or Jamstack marketing sites. Triggers on "landing page", "hero", "CTA", "pricing", "testimonial", "lead form", "marketing site", "newsletter", "FAQ".
jaballer/react-claude-skills/react-resources Skill
0★ repoCurated authoritative documentation URL library for React 19, accessibility (WAI-ARIA APG, WebAIM), performance (web.dev Core Web Vitals), HTML/CSS platform (MDN), forms (Zod, react-hook-form), testing (Testing Library, Playwright), Next.js App Router, TypeScript, and tooling — indexed by problem keyword for quick lookup during interview builds. Claude can WebFetch any of these URLs for current authoritative content when inline knowledge isn't enough. Use when you need to verify a pattern, look up a spec, or pull in primary-source docs mid-build. Triggers on "where to find", "documentation for", "spec for", "look up", "research", "reference", "WAI-ARIA", "MDN", "web.dev", "React docs", "Next docs", "Tailwind docs", "what does X say about", "authoritative".
jaballer/react-claude-skills/react-senior-ux Skill
0★ repoSenior UX Engineer-level React orchestrator — opening moves, decision framework, and routing to specialized React skills (component design, a11y, styling, performance, marketing patterns, onboarding/docs, interview narration). Use when starting any React component build, UI feature, technical interview task, marketing-site work, product onboarding, or documentation site work. Triggers on "React", "component", "UX engineer", "interview build", "landing page", "onboarding", "docs site", or any prompt that mixes UI + code judgment.
jaballer/react-claude-skills/react-styling Skill
0★ repoReact styling, design tokens, responsive layout, and motion — Tailwind, CSS Modules, CSS-in-JS, design tokens (CSS custom properties), breakpoints, container queries, CSS animations, Framer Motion, dark mode. Use when styling React components, implementing responsive design, building from Figma, adding animations, or setting up a design token system. Triggers on "Tailwind", "CSS", "styling", "responsive", "animation", "motion", "design tokens", "dark mode".
jaballer/react-claude-skills/react-utility-snippets Skill
0★ repoPaste-ready React hooks and helpers that other react-* skills reference but don't define — cn (clsx + tailwind-merge), useMediaQuery (SSR-safe), usePrefersReducedMotion, useFocusTrap, useAnnouncer + LiveRegion, useOnClickOutside, useLocalStorage (SSR-safe), useIsomorphicLayoutEffect, useDebounce, useThrottle, useEventListener, useInterval, useId patterns. Every snippet is SSR-safe and dependency-light. Load this skill at the start of any interview build. Triggers on "useMediaQuery", "focus trap", "cn helper", "clsx", "tailwind-merge", "live region", "useAnnouncer", "useLocalStorage", "useDebounce", "useThrottle", "snippet", "utility hook", "paste-ready", "click outside", "prefers reduced motion".
SkillMedev/performance-marketing/skills/landing-page-copy Skill
0★ repoWrite landing-page copy section by section - hero, social proof, features-as-benefits, objections, CTA - leading with one promise and proving it down the page. Use when someone asks "write my landing page", "improve my hero headline", "what should the homepage say", "turn these features into benefits", or is shipping a new page for a launch or campaign. Do NOT use for testing and optimizing an existing page's conversion rate - use landing-page-cro instead; for the one-line claim itself use positioning-statement; for the full message ladder use messaging-hierarchy.
The same file is in 4 other repositories
SkillMedev/performance-marketing/skills/landing-page-cro Skill
0★ repoImproves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.
The same file is in 2 other repositories
roedyrustam/claudevibeskills/src/saas-mvp-launcher Skill
no license0★ repoRoadmap and technical design for bootstrapping high-performance multi-tenant B2B/B2C SaaS MVPs. Use whenever the user wants to start a new SaaS product, plan architecture, choose a tech stack, or needs a launch checklist. Trigger on phrases like "build a SaaS", "SaaS MVP", "multi-tenant app", "launch a product", "Next.js SaaS boilerplate", or any product that needs auth, billing, and a dashboard. Covers Next.js 15, Tailwind CSS v4, Drizzle/Prisma, Stripe, Clerk, and Vercel AI SDK.
roedyrustam/claudevibeskills/src/senior-frontend Skill
no license0★ repoExpert frontend engineering skill for React 19, Next.js 15, and Tailwind CSS v4. Use this skill whenever the user is building, debugging, or reviewing frontend code — React components, server components, client components, hooks, forms, routing, layouts, data fetching, bundle optimization, or anything related to the modern React/Next.js ecosystem. Trigger on any mention of React, Next.js, Tailwind, useActionState, useOptimistic, useFormStatus, Server Components (RSC), Turbopack, App Router, or frontend performance. Also trigger for questions about component architecture, hydration errors, code-splitting, or image/font optimization.
roedyrustam/claudevibeskills/src/tailwind-expert Skill
no license0★ repoTailwind CSS v4 styling rules, CSS-first design, theme customization, and utility optimization. Use whenever the user is writing or reviewing Tailwind CSS code, configuring themes, or migrating from Tailwind v3 to v4. Trigger on any mention of Tailwind, @theme, utility classes, CSS-first config, or Tailwind v3-to-v4 migration. Also trigger for questions about Tailwind performance, purging, or custom design tokens.
roedyrustam/claudevibeskills/src/ui-ux-pro-max Skill
no license0★ repoComprehensive UI/UX and Human Interface Guidelines consistency skill. Use whenever the user is designing interfaces, reviewing UX flows, building design systems, or wants feedback on visual hierarchy, spacing, accessibility, or interaction patterns. Trigger on mentions of UI/UX design, design systems, accessibility (a11y), visual hierarchy, micro-interactions, design tokens, or when the user asks "does this look good" or "how should this be designed". Also trigger for Human Interface Guidelines (HIG) consistency across platforms.
saurabhshuklagrowisto/saurabh-ai-systems/production-systems/landing-page-engine Skill
0★ repoTurns a one-paragraph event/webinar brief into a publish-ready landing page, either a WordPress/Elementor section structure or a standalone custom-HTML page, plus a matching set of marketing collaterals. Reads a brand kit on every run so every output is on-brand. A human reviews and publishes; the skill never publishes on its own.
Fldicoahkiin/agent-skills-card/.claude/skills/minimalist-skill Skill
no license0★ repoClean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.
The same file is in 16 other repositories
Fldicoahkiin/agent-skills-card/.claude/skills/soft-skill Skill
no license0★ repoTeaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
The same file is in 18 other repositories
muxammadmamajonov/dot-claude/.claude/skills/ui-ux-design Skill
0★ repoUse when designing user-facing surfaces — information architecture, user/data flows, screens or command surfaces, design-system baseline. Triggers — new web page, mobile screen, CLI command.
SkillMedev/qa-test-automation/skills/flaky-test-detangler Skill
0★ repoRoot-causes intermittently failing tests and eliminates the hidden dependency at its source instead of retrying around it. Use when a test passes locally but fails in CI, goes green on a CI re-run, fails roughly one run in ten, or is already tagged "flaky." Do NOT use when the task is to design the fake or stub that replaces a real dependency - use mock-stub-designer instead.
The same file is in 1 other repository
SkillMedev/qa-test-automation/skills/mock-stub-designer Skill
0★ repoDesigns the minimal set of test doubles for a unit or integration test and decides, per dependency, whether to stub, fake, spy, mock, or exercise the real thing. Use when someone asks "should I mock this", "how do I test code that calls Stripe or S3 or the clock", "why do our tests pass while production is broken", or when a test touches an HTTP API, payment or email/SMS SDK, database, filesystem, system clock, or randomness. Do NOT use for fabricating valid domain fixture data (a User with defaults, an Order with line items) - use test-data-builder instead; for driving a red-green implementation loop, use tdd-expert.
The same file is in 1 other repository
cody-hutson/pmo-platform/operations/skills/pmo-process-designer Skill
no license0★ repoConverts business context into structured, traceable requirements and process documentation. Modes: Requirements definition · Workflow documentation · Gap analysis · Traceability matrix · Compliance mapping. Use when uploading business requirements, FDDs, or Jira exports. Triggers: "document this process", "build the requirements", "build the traceability matrix", "write the FRD", "trace from requirement to Jira", "what's the gap."
rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-feature Skill
0★ repoSpecialist skill for documenting features (backend + frontend) in an Obsidian vault. Normally invoked by the obsidian-documentation orchestrator, but also use it directly when the user asks to document a feature, a new capability, an endpoint, a UI flow, or "what I just built" — including from a git diff or PR. Produces feature notes under Features/ with backend/frontend sub-notes, ready for the tagging and linking pass.
vipincode/exr-agent-skills/.claude/skills/figma-to-component Skill
no license0★ repoTurn a Figma frame or node (via the Figma MCP) into production-grade Next.js + TypeScript + Tailwind + shadcn/ui components, WITHOUT creating duplicates — it scans MODULE_REGISTRY.md and the shared/feature trees first and reuses or extends what exists, places each new piece correctly (generic/reusable → components/shared, domain-specific → features/<name>/components), styles with Tailwind utilities + theme tokens, animates with Tailwind/CSS or framer-motion, exports assets, and registers new shared components. Use this whenever the user wants to build/implement/convert a Figma design, frame, screen, section, or component into React/Next.js code — phrases like "turn this figma frame into a component", "build this design", "implement this figma node", "code this screen from figma", "figma to react/next", or pasting a figma.com link and asking for components. This is the Figma design-to-code component builder — when the design source is an HTML file/URL use html-to-component, and when it is another existing codebase/repo on disk use project-to-component. It does NOT set up the global theme/colors/fonts (that is font-theme-setup) and does NOT scaffold a project (that is nextjs-bootstrap). Requires the Figma MCP connected, a node-specific Figma URL, and an existing Next.js + shadcn project with the contract files.
vipincode/exr-agent-skills/.claude/skills/font-theme-setup Skill
no license0★ repoExtract a design system's tokens from a Figma file (via the Figma MCP) and apply them to a Next.js + Tailwind v4 + shadcn/ui project's THEME — rewriting globals.css color tokens in oklch, wiring fonts in layout.tsx (next/font Google + local custom fonts), and setting radius, shadows, spacing, line-heights, gradients, and background images. Use this whenever the user wants to set up or update the theme / design tokens / colors / typography / fonts from a Figma link — phrases like "set up the theme from this figma", "apply these design tokens", "update the colors and fonts from figma", "convert the palette to oklch", "configure the shadcn theme", or "wire up the fonts". This is the frontend theming skill — it edits globals.css + layout.tsx + tailwind theme, it does NOT build pages or components from a frame (that is figma-to-component) and does NOT scaffold the project (that is nextjs-bootstrap). Runs once per project (re-run to refresh tokens). Requires the Figma MCP to be connected and a Figma file/frame URL.
vipincode/exr-agent-skills/.claude/skills/frontend-code-review Skill
no license0★ repoReview frontend / client-side code (Next.js App Router, React, TypeScript, Tailwind + shadcn/ui, axios + Zod + TanStack Query + RHF) for correctness, component duplication, API-binding conformance, convention adherence, accessibility, and performance. Use whenever the user asks to review, audit, critique, or sanity-check frontend code — "review this component", "code review the products binding", "review my changes / this PR / the diff", "is this screen production-ready", "check this React code for issues". It reads the frontend ARCHITECTURE.md + MODULE_REGISTRY.md so it reviews against THIS project's conventions and flags components/hooks/utils that duplicate existing shared pieces or registry entries (DRY), plus bindings that bypass the BFF/axios/Zod/Query standard. Standalone and read-only — run anytime, never auto-chained, and it does not modify source unless explicitly asked to apply fixes. Tuned for frontend; NOT for backend/Express/Mongoose review (that is backend-code-review). This is static code review only — it does NOT run the app or confirm behavior at runtime; requests like "verify it works", "does it render", or "check my change actually works" are run/verify intent (/verify or /run), not review. Frontend / Next.js / React / component / API-binding scope only.
vipincode/exr-agent-skills/.claude/skills/frontend-feature-planner-workspace/skill-snapshot-v1 Skill
no license0★ repoPlan how an already-designed Next.js/React frontend feature will BIND to a backend API — before any binding code is written. Use this whenever the user has a built (or in-progress) design and wants to wire it to an endpoint: "plan the products API binding", "wire up the orders screen to the API", "bind this design to the auth endpoints", "how do I connect this page to the backend", "make this design functional with the API", or simply names an API/endpoint to hook a frontend feature to. Its signature move: it reads the REAL backend (monorepo source first, then the backend's contract files, then an OpenAPI/Swagger spec, then a user-pasted sample) to learn the actual endpoints, request/response envelope, auth, and validation — so the plan binds to ground truth instead of a guessed contract. It reads the frontend ARCHITECTURE.md + MODULE_REGISTRY.md, maps which existing design components consume which fields, and writes an editable _docs/FEATURE_PLAN_<name>.md (types, Zod schemas, BFF routes, axios api fns, TanStack Query hooks, data-binding map). It does NOT write binding code (that is frontend-module-builder), does NOT build the design/components (that is figma-to-component / html-to-component), does NOT write tests (frontend-test-writer), and is NOT for backend/server planning (that is backend-feature-planner). Frontend / Next.js / React / API-binding scope only.
vipincode/exr-agent-skills/.claude/skills/frontend-feature-planner Skill
no license0★ repoAgent Skills for building production-grade Express + TypeScript + Mongoose backends with Claude Code
vipincode/exr-agent-skills/.claude/skills/frontend-module-builder Skill
no license0★ repoBuild the API binding for an already-designed Next.js/React feature from an approved FEATURE_PLAN — wiring the existing design to a real backend endpoint and making it functional, while enforcing reuse so no duplicate components, hooks, schemas, or utils get created. Use this whenever the user wants to implement/build/execute a planned frontend binding — "build the products binding", "implement FEATURE_PLAN_products.md", "now make this design functional", "wire up the orders screen", "bind it to the API". It reads the frontend ARCHITECTURE.md + MODULE_REGISTRY.md + the feature plan, searches for existing reusable code BEFORE creating anything, writes the feature-module binding layer (types/schema/api/hooks) and edits the built design to consume it (dropping hardcoded samples), unwraps the response envelope + validates with Zod, uses TanStack Query for server state, then updates the registry. It does NOT plan the binding (that is frontend-feature-planner), does NOT build/redesign components from Figma or HTML (that is figma-to-component / html-to-component), and does NOT write tests (that is frontend-test-writer). It is NOT for backend/server code (that is backend-module-builder). Frontend / Next.js / React / API-binding scope only.
vipincode/exr-agent-skills/.claude/skills/frontend-onboard Skill
no license0★ repoMake any existing frontend ready for the frontend toolkit (frontend-feature-planner, frontend-module-builder, frontend-test-writer, frontend-code-review) by establishing its contract files. Use this as the entry point whenever the user points the frontend toolkit at a directory — "set up my existing Next.js app for these skills", "onboard this React frontend", "I want to use these skills on my current UI", "get this client ready", or starting work in a frontend folder that has no ARCHITECTURE.md / MODULE_REGISTRY.md yet. For an EXISTING frontend it scans the repo and generates a DESCRIPTIVE ARCHITECTURE.md plus a MODULE_REGISTRY.md seeded with all existing reusable components, hooks, schemas, lib utils, and feature modules, so feature work reuses what's there instead of duplicating it (DRY). For an EMPTY directory it hands off to nextjs-bootstrap. It is non-destructive — it never refactors existing code, only writes the contract files. After onboarding, plan/build/test/review happen through the dedicated frontend skills. This is the FRONTEND twin of backend-onboard — do NOT use it on an Express/Mongoose API (that is backend-onboard).
vipincode/exr-agent-skills/.claude/skills/frontend-test-writer Skill
no license0★ repoWrite tests for frontend Next.js/React code on demand — components, hooks (incl. TanStack Query hooks), Zod schemas, and API-binding behavior. Use this ONLY when the user explicitly asks to test frontend code — "write tests for the products grid", "test the useProductsQuery hook", "add component tests for product-card.tsx", "cover the create-product form", "test this binding". It is a standalone utility, run manually whenever the user wants — never auto-chained from frontend-feature-planner or frontend-module-builder. It reads ARCHITECTURE.md (conventions), MODULE_REGISTRY.md (what to mock vs use), the target file(s), and the FEATURE_PLAN's testing checklist if present, detects the test framework + RTL setup from package.json, and writes matching test files. It never modifies source files and never touches the registry. It is NOT for backend tests (that is backend-test-writer). Frontend / Next.js / React / Vitest+RTL scope only.
vipincode/exr-agent-skills/.claude/skills/html-to-component Skill
no license0★ repoTurn an HTML file, a pasted HTML section, or a live URL into a production-grade Next.js + TypeScript + Tailwind + shadcn/ui design — in two phases. (1) THEME — extract the design's tokens (colors → oklch, typography, fonts, radius, shadows, spacing, gradients, background images) and apply them to globals.css + wire fonts in layout.tsx. (2) COMPONENTS — turn the markup into components WITHOUT creating duplicates, scanning MODULE_REGISTRY.md and the shared/feature trees first and reusing/extending what exists, placing generic pieces (header, navbar, hero, small-hero, carousel, charts, sidebar, avatar, logo, banner …) in components/shared and domain-specific ones in features/<name>/components, styling with Tailwind utilities + theme tokens, animating with Tailwind/CSS or framer-motion, and registering new shared components. Use this whenever the user wants to convert/implement/build HTML into React/Next.js — phrases like "turn this HTML into a component", "build this html section", "convert design.html to next.js", "code this markup", "html to react/next", or when they point at an .html file (often in _docs/designs/) or paste a chunk of HTML/CSS and want components. Looks for design files in _docs/designs/ by default. Builds INTO an existing Next.js + shadcn project (scaffold first with nextjs-bootstrap; this skill does NOT scaffold). It is the HTML counterpart to figma-to-component (source = Figma) and project-to-component (source = an existing codebase/repo on disk) — reach for those when the source isn't an HTML file/section/URL.
vipincode/exr-agent-skills/.claude/skills/nextjs-bootstrap Skill
no license0★ repoScaffold a new production-grade Next.js (App Router) + TypeScript + Tailwind + shadcn/ui frontend from scratch, wired to a separate API backend (e.g. Express) via a BFF proxy, with axios, Zod, TanStack Query, and React Hook Form. Use this whenever the user wants to start a new Next.js / React frontend, bootstrap a web client/UI, set up a shadcn starter, or initialize a frontend project — even if they only say "new frontend", "Next.js starter", "React app", "admin dashboard UI", or name the stack loosely. It scaffolds the infrastructure ONCE per project and emits the two source-of-truth files (ARCHITECTURE.md and MODULE_REGISTRY.md) that the future frontend-* skills depend on. Do NOT use this to add a feature/page to an existing project (that is frontend-feature-planner + frontend-module-builder) or to write tests. This scaffolds a Next.js + React frontend specifically — do NOT use it to bootstrap a backend/API (that is express-ts-bootstrap) or projects in other frontend stacks (Vite/CRA/Remix/Vue/Svelte/Angular); those are out of scope.
vipincode/exr-agent-skills/.claude/skills/project-to-component Skill
no license0★ repoPort a page, screen, or design language from ANY existing codebase into a production-grade Next.js + TypeScript + Tailwind + shadcn/ui page in the current project — the source being another repo/folder on disk (a static design mock, an old app, a legacy frontend — CSS Modules, styled-components, SCSS, plain CSS, Vue, older React/Next, or a Tailwind app with different conventions). Use this whenever the user points at an existing project as the design source — "copy the dashboard from <path/repo>", "port /admin/orders from our old app", "make this route match <project>", "rebuild this screen from <codebase>", "migrate these pages into the new frontend", "make our page look like project X". It reads the source READ-ONLY, derives a reusable translation map (source colors/fonts/spacing → the target's oklch theme tokens; source custom UI → shadcn/ui + shared components), lifts the source theme first when the target still has the stock shadcn theme, then builds dedup-first — scanning ARCHITECTURE.md + MODULE_REGISTRY.md and the shared/feature trees, reusing/extending before creating, placing generic pieces in components/shared and domain-specific ones in features/<name>/components, and registering new shared pieces. It is the codebase counterpart to figma-to-component (source = Figma) and html-to-component (source = a single HTML file/URL) — reach for those when the source isn't a project. Builds INTO an existing Next.js + shadcn project with the contract files; it does NOT scaffold (nextjs-bootstrap) and does NOT bind APIs (frontend-module-builder).
scoobydrew83/skills/plugins/coordinated-skills/skills/experiment-designer Skill
0★ repoDesign a single falsifiable experiment with its pass/fail threshold fixed BEFORE the run, so a result can't be rationalized after the fact. Use whenever someone has a hypothesis or risky assumption and is about to just try it and see — "how do I test whether X", "design an experiment for this", "is this optimization worth it", "how would I prove or disprove this", "what would falsify this", or any "let me just run it and look at the numbers" with no threshold named. The method isolates the one decisive question, states the hypothesis and its negation, fixes a numeric metric and a PASS/FAIL/KILL rule up front, picks the cheapest decisive design, controls the confound that would make the result lie (optimization-before-correctness especially), and emits a dated pre-registration plus a falsifiability check. Distinct from reality-check (verifies an existing plan's claims), goal-builder (writes Claude Code /goal conditions), and hemlock (whole-idea GO/NO-GO); this designs one test and locks its bar.
SkillMedev/motion-video-direction/skills/motion-design-principles Skill
0★ repoThe craft layer for motion: pick the right easing (ease-in / ease-out / ease-in-out / spring), get timing and spacing right, build the anticipationâactionâfollow-through arc, and apply Disney's 12 principles to UI and product video. Use when animating any UI transition, modal, button, page load, or product-video scene, or when someone says "make this feel less janky", "smoother", "more polished", "more alive", "the animation feels off", "why does this look cheap", or asks "ease-in or ease-out" / "spring or interpolate". Do NOT use to plan shots, scene order, or beat lists â use video-storyboard instead; do NOT use to direct a full product demo (cursor moves, screen captures, callouts) â use product-demo-director instead; do NOT use to animate text/letterforms â use kinetic-typography instead; do NOT use to time motion to a beat or score â use sound-and-music-sync instead; do NOT use to crop/reframe for a platform â use social-video-formatter instead; do NOT use for light/exposure/color motion â use motion-color-and-light instead.
The same file is in 1 other repository
SkillMedev/motion-video-direction/skills/product-demo-director Skill
0★ repoDirect the craft of putting a real software UI on screen - cursor choreography, zoom/pan/callout language, screen-recording vs recreated-UI, and making state changes legible with highlights, focus pulls, and slow-downs. Use when filming or recreating an app for a product demo, feature walkthrough, onboarding clip, or release reel and asking "how do I show this click", "where should the camera zoom", "should I screen-record or rebuild the UI", "why does my demo feel confusing", "how do I make the state change readable", or "how do I move the cursor". Do NOT use for the underlying motion grammar (easing, timing) - use motion-design-principles; for the beat-by-beat plan - use video-storyboard; for animating words on screen - use kinetic-typography; for the color/light of highlights and glows - use motion-color-and-light; for sound design or a click/whoosh hit - use sound-and-music-sync; for reframing the demo to 9:16 or 1:1 - use social-video-formatter; for the React/MP4 mechanics of building it - use remotion-compose and remotion-render.
The same file is in 1 other repository
SkillMedev/motion-video-direction/skills/social-video-formatter Skill
0★ repoReframe and export a finished video for social platforms - 9:16 ↔ 16:9 cropping, burned-in captions, a platform-native first frame, loop design, and per-platform specs (aspect, length, safe areas) for TikTok, Reels, Shorts, X, and LinkedIn. Use when someone says "make this vertical", "crop to 9:16", "format for TikTok/Reels/Shorts", "add captions/subtitles", "why is my video cut off on mobile", "resize for Instagram", or "export for social". Do NOT use when the question is about the storyboard or shot order before any video exists (use video-storyboard); the animation craft of how elements move (use motion-design-principles); animated word-by-word caption styling (use kinetic-typography); palette, contrast, or lighting (use motion-color-and-light); directing the product-demo content and screen choreography (use product-demo-director); or scoring, beat-syncing, or audio (use sound-and-music-sync) - this is the craft layer that decides WHAT to format for the feed, then hands a concrete spec to remotion-compose / remotion-render to author and export.
The same file is in 1 other repository
SkillMedev/motion-video-direction/skills/video-storyboard Skill
0★ repoPlan a product demo, feature announcement, or launch video as a beat sheet and shot list BEFORE animating - hook in the first 3s, problem, reveal, proof, CTA - with target duration and pacing per scene type, output as a JSON scene plan that remotion-compose consumes directly. Use when someone says "storyboard my demo", "plan the video", "what scenes do I need", "plan my launch video", "map out the demo", or "break this feature into scenes" before any code. Do NOT use when the request is the animation mechanics - writing the .tsx, using interpolate/spring, registering the Composition - that is remotion-compose; do NOT use for the easing and choreography craft of a single scene - use motion-design-principles instead.
The same file is in 1 other repository
lroolle/skills/skills/kiln Skill
0★ repoPrecision UX design instrument: perceptual principles, composable patterns, parameterized material kits, anti-AI-slop detection. Fires on three branches: designing or restyling any frontend surface (layout, typography, color, spacing, responsive, dark mode, accessibility); auditing or critiquing an existing interface; and rescuing output that looks generic or AI-made ("make it look better", "needs more taste"). Animation design decisions live here (motion.md); implementing the animation is animate-it's job.
MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-design-graphic Skill
0★ repoDefine the graphic design specification for an approved mockup. Uses impeccable-inspired design laws to establish color system, typography, layout, and motion. Updates the mockup HTML with the visual system. Triggers include "karvey design-graphic", "diseño gráfico", "graphic design", "especificación visual", "visual specification", "sistema de diseño", "design system".
SkillMedev/project-management/skills/notion-database Skill
0★ repoDesigns Notion databases that scale - one entity per database, deliberate property types, two-way relations with rollups, audience-specific views, and row templates - with explicit decision rules for relation vs rollup vs formula. Use when someone asks "design a Notion database for my projects", "should this be a relation or a rollup", "my Notion workspace is a junk drawer", or "set up a tasks and projects system in Notion". Do NOT use for building a full personal knowledge-management method with capture and review habits - use second-brain instead. For SQL or application database schemas, use database-schema.
The same file is in 1 other repository
SkillMedev/product-manager-stack/skills/user-persona Skill
0★ repoSynthesizes interview notes, surveys, support tickets, and analytics into evidence-based user personas that drive design decisions, with every claim traced to source data. Use when someone asks "build personas from our research", "turn these interview notes into personas", "how many personas do we need", or "are our personas evidence-based". Do NOT use for sales-targeting ideal customer profiles with filterable firmographics and buying committees - use icp-persona-builder instead. Do NOT use for extracting jobs-to-be-done from research - use jtbd-extractor instead.
The same file is in 2 other repositories
SkillMedev/lifecycle-marketing/skills/email-drip-builder Skill
0★ repoDesigns automated onboarding and activation drip sequences with behavior-gated sends, exit triggers on conversion, and per-email jobs and timing. Use when someone asks "build an onboarding email sequence", "design a drip campaign for new signups", "why isn't our onboarding flow activating users", or is extending an existing drip series. Do NOT use for recurring content newsletters - use email-newsletter-pro; for recovering abandoned checkouts use abandoned-cart-sequence; for re-engaging dormant users use win-back-campaign; for cold outreach to prospects use outreach-sequence-designer or cold-email-craft.
The same file is in 2 other repositories
x77jh8gvrn-alt/staqd-skills/skills/editorial Skill
0★ repoUse when building or styling a UI in the Editorial aesthetic — A magazine-grade design system that makes typography the hero, pairing structured grids with generous whitespace and confident headlines. For Claude Code, Cursor, and Codex.
waseemnasir2k26/skynetlabs-all-claude-code/skills/client-delivery-and-planning/skynet-site Skill
no license0★ repoBuild a premium client website end-to-end — competitor research, niche-tuned design system, conversion funnel, SEO/AEO base, Vercel deploy, GitHub repo, speculative pitch with 5-8 scope-unlocking questions. Distilled from 9 shipped client wins (wedding, wellness, medical, luxury rental, clinic pitch, indie event, coach funnel, 20-niche demos, agency theme rebuild). Trigger when user says: "build a site for", "design website", "spec build for client", "/skynet-site", pastes a client brief / Upwork JD asking for a website, or wants a landing page / agency demo / niche site.
LaoitdevOpen/laoitdev-skills/skills/frontend/frontend-i18n Skill
0★ repoTranslation and i18n rules for the AMIS admin project. Use this whenever writing any user-visible string, building a form with validation messages, handling API or business errors, or adding new translation keys. Also use when the user asks 'how do I translate X', 'add translation for Y', 'don't hardcode this string', or 'add an error message'. Covers: useTranslation usage, Zod schema factory pattern, validation key structure, API error translation via useAPIErrorTranslator, and adding new error codes to both translation files.
LaoitdevOpen/laoitdev-skills/skills/frontend/mui-theme Skill
0★ repoMUI theme configuration, color palette, typography, dark/light mode, and shared UI building blocks. Use this when working with colors, spacing, typography, component styling, adding theme overrides, or using SectionCard/InfoRow shared components for consistent UI. Also covers how ThemeContext and LocalizationProvider are wired up.
SkillMedev/ux-research-discovery/skills/usability-test-plan Skill
0★ repoPlans a usability study - research questions, realistic task scenarios with success criteria, metrics (completion rate, time on task, SEQ, SUS), a recruiting screener, and moderated vs. unmoderated guidance. Use when someone says "plan a usability test", "write task scenarios for our prototype", "how many participants do we need", or is about to put an interface or prototype in front of users. Do NOT use for open-ended discovery interview guides - use interview-guide-builder instead; for analyzing quantitative A/B experiments, use ab-test-analyzer.
The same file is in 1 other repository
SkillMedev/ux-research-discovery/skills/user-persona Skill
0★ repoSynthesizes interview notes, surveys, support tickets, and analytics into evidence-based user personas that drive design decisions, with every claim traced to source data. Use when someone asks "build personas from our research", "turn these interview notes into personas", "how many personas do we need", or "are our personas evidence-based". Do NOT use for sales-targeting ideal customer profiles with filterable firmographics and buying committees - use icp-persona-builder instead. Do NOT use for extracting jobs-to-be-done from research - use jtbd-extractor instead.
The same file is in 2 other repositories
Drvivek34/Skill-Bazaar/coding-development/web-artifacts-builder Skill
no license0★ repoSuite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
The same file is in 33 other repositories
Drvivek34/Skill-Bazaar/design-creative/canvas-design Skill
no license0★ repoCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
The same file is in 38 other repositories
Drvivek34/Skill-Bazaar/design-creative/frontend-design Skill
no license0★ repoGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
The same file is in 19 other repositories
Drvivek34/Skill-Bazaar/design-creative/theme-factory Skill
no license0★ repoToolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
The same file is in 46 other repositories
Drvivek34/Skill-Bazaar/testing-qa/webapp-testing Skill
no license0★ repoToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
The same file is in 45 other repositories
aarshsharma2803-stack/optimusprime/skills/ui-ux-pro-max Skill
0★ repoDesign intelligence for frontend work — component critique, layout review, accessibility checks, dark mode, responsive design, UX patterns. Trigger: /ui-ux-pro-max, "design review", "ux check", "accessibility audit", "review my UI", "is this accessible", "dark mode", files contain .tsx/.jsx/.css/.vue
digitaldreams/tuhin/skills/design-system Skill
0★ repoAnalyzes the project and generates a custom, opinionated design system with Tailwind CSS CSS-first configuration (@theme), writing tasks/design_system.md from requirements, wireframes, information architecture, and the frozen architecture. Use whenever the user says "design system", "design tokens", or "set up the Tailwind theme".
digitaldreams/tuhin/skills/user-journey-map Skill
0★ repoDesigns the intended user journeys for an unbuilt product: personas, current workarounds, step-by-step flows with screens and expected friction, writing tasks/user_journeys.md. Use whenever the user says "user journey", "journey map", or "map the user flows".
digitaldreams/tuhin/skills/wireframe Skill
0★ repoCreates clean, focused wireframes showing layout and content structure for a named page, driven by tasks/information_architecture.md and tasks/user_journeys.md. Use whenever the user says "wireframe", "wireframe the X page", or "layout sketch". Pass the page name as the argument.