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
bromso/metapowers/plugins/research/skills/design Skill
1★ repoGenerate and evaluate multiple solution concepts for the defined problem
adaptocms/adapto-cms-agent-skills/plugin/skills/adapto-microcopy Skill
1★ repoManage UI micro copy (nav, buttons, labels, errors) as Adapto key/value/language entries. Two modes — init seeds a curated, on-brand starter set; extract scans your frontend for hardcoded strings and creates entries + a replacement guide (no source rewrite). Plan-then-apply.
mkreindel/seo-toolkit-template/.claude/skills/wireframe Skill
1★ repoProduce a wireframe doc for a new page (blog post, service page, or catalog leaf) BEFORE content generation. Mandatory step per `CLAUDE.md` — `/blog` and `/service` invoke this in their flow. Output is a markdown wireframe in `_drafts/[slug]/wireframe.md` covering layout zones, heading hierarchy, internal-linking pattern slots, conversion elements (service pages), and image plan. Optionally produces a draw.io / AI-generated visual mockup for client presentation. Use when the user types `/wireframe` directly, or when a page-generating skill calls it.
tibichi/fast-preset/skills/fast-review Skill
1★ repoPolish pass for an Astro/Tailwind/DaisyUI prototype before sharing - visual quality, responsive behavior, interaction states, DaisyUI consistency, and unresolved assumptions still showing in the UI. Use after a build session, before showing the prototype to stakeholders, or when something feels off.
busyeugene/content-marketing-skills/landing-page-copy Skill
1★ repoUse when the user wants to draft landing page copy — product page, feature page, pricing page, lead magnet gate, or campaign page. Produces full copy for every standard section (hero, social proof, features, objections, FAQ, CTA) with optional variants.
SkillMedev/b2b-prospecting-engine/skills/icp-persona-builder Skill
1★ repoTurns a vague "who we sell to" into a weighted, filterable ICP scorecard - firmographics, technographics, and time-bound triggers expressed as literal Apollo or Sales Navigator filter values, built from closed-won and churned evidence, with hard disqualifiers and A/B/C account tiering - plus a buying-committee persona map covering economic buyer, champion, technical user, and blocker with each role's pains. Use when standing up outbound - FIRST, before any list-building or outreach - and someone asks "who is our ICP", "what filters do I put in Apollo", "we're targeting everyone and closing no one", or "score this account against our ICP". Do NOT use for pulling the actual prospect list - use prospect-list-builder instead - or for the messaging one-liner - use positioning-statement instead - or for end-user research personas - use user-persona instead.
The same file is in 1 other repository
SkillMedev/b2b-prospecting-engine/skills/outreach-sequence-designer Skill
1★ repoUse when you need to design the cadence/sequence structure that moves a cold prospect to a booked meeting across multiple channels - the orchestration of touches, not the copy of any one message. Trigger phrases "design an outreach sequence", "build a cold cadence", "how many touches should my sequence have", "multi-channel sequence", "what's a good follow-up cadence", "set up day-by-day steps", "how long should my sequence be", "add LinkedIn and calls to my email sequence", "design a breakup email sequence", "what's the spacing between touches". Workflow chooses channels and mix, sets length and step spacing, defines bump/follow-up logic, matches personalization tier to account tier, wires the "why now" signal hook, varies the message angle across steps, and sets exit/branch criteria. Do NOT use for writing the words of a single email - use [[cold-email-craft]]. Do NOT use for who to put in the sequence - use [[prospect-list-builder]]. Do NOT use for building the sequence inside a tool - use [[apollo-prospecting]].
The same file is in 1 other repository
jason0404/Jason-Android-Marketplace/plugins/android-localization-toolkit/skills/check-ui-overflow Skill
1★ repoCheck Android XML or Compose usage of translated strings for long-text, font scaling and RTL layout risks
lubochka/xiigen-general-skills/agent-skills/e2e-test-matrix Skill
1★ repoDesign end-to-end coverage across critical paths. Use for release readiness, user workflows, UI/API flows, and adapter validation.
lubochka/xiigen-general-skills/agent-skills/user-journey-testing Skill
1★ repoValidate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
lubochka/xiigen-general-skills/claude/skills/e2e-test-matrix Skill
1★ repoDesign end-to-end coverage across critical paths. Use for release readiness, user workflows, UI/API flows, and adapter validation.
lubochka/xiigen-general-skills/claude/skills/user-journey-testing Skill
1★ repoValidate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
lubochka/xiigen-general-skills/codex/skills/e2e-test-matrix Skill
1★ repoDesign end-to-end coverage across critical paths. Use for release readiness, user workflows, UI/API flows, and adapter validation.
lubochka/xiigen-general-skills/codex/skills/user-journey-testing Skill
1★ repoValidate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
lubochka/xiigen-general-skills/skills/universal/user-journey-testing Skill
1★ repoOpen-source AI agent skills for safer Claude, Codex and Cursor coding workflows
jajupmochi/agent-harness/skills/figma-authoring-constraints Skill
1★ repoUse when a designer asks how to structure a Figma file so it produces clean code, when a design keeps yielding pixel-snapshot output, or when get_variable_defs comes back empty — the 20 Figma-side authoring constraints that make a design cleanly code-able via the Figma MCP.
jajupmochi/agent-harness/skills/figma-design-fetch Skill
1★ repoUse when the user shares a figma.com URL, wants to implement/mock a UI from Figma, or do design-to-code — connect the Figma MCP, fetch the design (code/assets/screenshot) to disk, then rebuild with existing design-system components and visually self-verify against the Figma screenshot.
jajupmochi/agent-harness/templates/personal-cite-static/.claude/skills/verify-visual Skill
1★ repoUse chrome-devtools MCP to screenshot the local site (or a specific element) and visually verify it matches the design intent. Required after every UI-affecting change before marking work done.
royvergara/design-team-os/skills/design-system-enforcement Skill
1★ repoUse when auditing generated or drafted UI against a team's design system. Triggers on a screenshot, code, or spec plus a reference to the design system. Returns violations, not compliments.
royvergara/design-team-os/skills/design-system-extraction Skill
1★ repoUse when producing a design-system reference from a team's existing components, tokens, and patterns — the reference design-system-enforcement needs to audit against. Triggers on existing UI source (a component file, a codebase, exported tokens) plus a request to extract, document, or produce the design system. Returns an evidence-backed reference with its conflicts named, never an invented system.
royvergara/design-team-os/skills/user-journey-mapping Skill
1★ repoUse when drafting a user journey map from a brief or research inputs. Triggers on requests for a journey map, experience map, or end to end flow of a user's experience. Will not generate a map without a named customer pain and at least one real signal behind it.
ninnettesudanese653/claude-plugins/plugins/socials/commands/persona-guide Skill
1★ repoUse when the user asks about personas, wants to choose the right persona for their content, or needs help understanding how personas affect generated content. Covers both system personas and custom personas.
Marine-softdrink524/claude-skills/skills/ui-ux-advisor Skill
no license1★ repoUI/UX design expert providing actionable feedback on interfaces with focus on usability, accessibility (WCAG), visual hierarchy, and modern design patterns. Use when reviewing designs, creating wireframes, or improving user experience.
The same file is in 1 other repository
yugef3h/leo-skills/skills/sop-design Skill
1★ repoUse when starting a new feature or project, need to establish a spec→plan→task→code workflow, want AI to follow documentation-before-code discipline, or need to set up automated quality gates (Harness) for AI-generated code. Also use when AGENTS.md is growing too large, AI is drifting from spec, or you need to integrate BDD acceptance criteria into your development process. Applies to React frontend + Python/Go backend stacks.
alexngai/skill-tree/docs/demo/skills/react-component-testing Skill
1★ repoTest React components with Testing Library — render, query by role, and assert on user-visible behavior.
LaWebcapsule/d9-skills/skills/skillops/refine-skill-design Skill
1★ repoAudit and refactor existing SKILL.md files using meta-audit model for intent, logic, constraints, and examples. Align to spec v2.2.
svyatov/agent-toolkit/plugins/llms-visibility/skills/llms-visibility Skill
1★ repoMake websites, docs, blogs, or landing pages visible and readable to LLMs and AI agents — ChatGPT, Claude, Perplexity, Cursor, Claude Code, and other coding agents that fetch URLs. Use this for any request involving llms.txt, llms-full.txt, serving .md/Markdown versions of pages, Accept text/markdown content negotiation, Link rel="alternate" headers, Cloudflare Content-Signal in robots.txt, GEO (generative engine optimization), AI-friendly / AI-readable / LLM-discoverable sites, getting cited in ChatGPT or Perplexity answers, or fixing pages where AI tools fetch JavaScript bundles or empty React roots instead of content. Also use to push back on debunked patterns: ai.txt, AI meta tags, hidden HTML comments, AI toggle buttons, User-Agent sniffing, JSON-LD aimed at LLMs. Do NOT use for traditional Google SEO, sitemap.xml, schema.org rich snippets for search engines, WCAG/accessibility audits, or CSP/security headers.
SWEStash/swe-workflow-skills/plugins/backend/skills/test-suite-design Skill
1★ repoDesign comprehensive test suites for existing code — strategy across unit/integration/e2e, fixtures, factories, helpers. Triggers: add tests, write tests for, increase coverage, test this module, testing strategy, test plan, what tests do I need, test infrastructure, test helpers, this has no tests. Not for TDD — use tdd-workflow.
SWEStash/swe-workflow-skills/plugins/data/skills/data-pipeline-design Skill
1★ repoDesign batch and streaming data pipelines — ELT into a warehouse/lakehouse, dbt and analytics engineering (staging/intermediate/marts layers), orchestration with Airflow or Dagster, idempotent loads, incremental models, backfills, CDC ingestion. Triggers: data pipeline, ELT, ETL, dbt models, data warehouse, Snowflake, BigQuery, ingest into the warehouse, Airflow DAG, Dagster, Kafka streaming, backfill, incremental load, nightly job duplicates rows. ML training/feature pipelines → ml-pipeline-design; validating the data → data-quality.
SWEStash/swe-workflow-skills/plugins/data/skills/observability-design Skill
1★ repoDesign production observability — SLIs, SLOs, SLAs, error budgets, OpenTelemetry traces/metrics/logs, structured logging, alerting, dashboards. Triggers: SLO, SLI, SLA, error budget, observability, monitoring, OpenTelemetry, OTel, tracing, distributed tracing, structured logging, alerting, dashboard, metrics, correlation ID, alert fatigue.
SWEStash/swe-workflow-skills/plugins/designer/skills/accessibility-design Skill
1★ repoDesign and implement accessible web/mobile apps to WCAG 2.1/2.2 — semantic HTML, ARIA patterns, keyboard navigation, focus management, color contrast, screen readers, accessible forms. Triggers: accessibility, a11y, WCAG, screen reader, keyboard navigation, ARIA, focus management, color contrast, alt text, semantic HTML, tab order, focus trap, skip link, announce. Build it in, don't bolt it on.
SWEStash/swe-workflow-skills/plugins/designer/skills/frontend-architecture Skill
1★ repoDesign frontend architecture — React component hierarchy, state management, design tokens, data fetching, routing, error boundaries, code organization. Triggers: component architecture, state management, design system, design tokens, component library, React structure, folder structure, Zustand vs Redux, React Query, code splitting, error boundary, compound component.
SWEStash/swe-workflow-skills/plugins/designer/skills/ui-ux-design Skill
1★ repoDesign user experiences from an engineer's perspective — user flows, wireframes, interaction patterns, responsive strategy, navigation, loading/error/empty states. Triggers: design the UI, user flow, wireframe, how should this screen look, loading state, error state, empty state, responsive design, navigation, page layout, form design, mockup.
SWEStash/swe-workflow-skills/plugins/devops/skills/observability-design Skill
1★ repoDesign production observability — SLIs, SLOs, SLAs, error budgets, OpenTelemetry traces/metrics/logs, structured logging, alerting, dashboards. Triggers: SLO, SLI, SLA, error budget, observability, monitoring, OpenTelemetry, OTel, tracing, distributed tracing, structured logging, alerting, dashboard, metrics, correlation ID, alert fatigue.
SWEStash/swe-workflow-skills/plugins/frontend/skills/accessibility-design Skill
1★ repoDesign and implement accessible web/mobile apps to WCAG 2.1/2.2 — semantic HTML, ARIA patterns, keyboard navigation, focus management, color contrast, screen readers, accessible forms. Triggers: accessibility, a11y, WCAG, screen reader, keyboard navigation, ARIA, focus management, color contrast, alt text, semantic HTML, tab order, focus trap, skip link, announce. Build it in, don't bolt it on.
SWEStash/swe-workflow-skills/plugins/frontend/skills/browser-verification Skill
1★ repoVerify a web app change by driving the real UI in a browser — reproduce the user flow end to end, watch console errors and network failures, exercise loading/error/empty states, capture screenshots as evidence. Use before claiming a UI change works. Triggers: check it in the browser, verify the UI, click through the flow, console errors, test it like a user, smoke test the frontend. Designing persistent test suites → test-suite-design; the generic done-gate → verification-before-completion (this is its browser-specific practice).
SWEStash/swe-workflow-skills/plugins/frontend/skills/frontend-architecture Skill
1★ repoDesign frontend architecture — React component hierarchy, state management, design tokens, data fetching, routing, error boundaries, code organization. Triggers: component architecture, state management, design system, design tokens, component library, React structure, folder structure, Zustand vs Redux, React Query, code splitting, error boundary, compound component.
SWEStash/swe-workflow-skills/plugins/frontend/skills/test-suite-design Skill
1★ repoDesign comprehensive test suites for existing code — strategy across unit/integration/e2e, fixtures, factories, helpers. Triggers: add tests, write tests for, increase coverage, test this module, testing strategy, test plan, what tests do I need, test infrastructure, test helpers, this has no tests. Not for TDD — use tdd-workflow.
SWEStash/swe-workflow-skills/plugins/frontend/skills/ui-ux-design Skill
1★ repoDesign user experiences from an engineer's perspective — user flows, wireframes, interaction patterns, responsive strategy, navigation, loading/error/empty states. Triggers: design the UI, user flow, wireframe, how should this screen look, loading state, error state, empty state, responsive design, navigation, page layout, form design, mockup.
SWEStash/swe-workflow-skills/plugins/ml/skills/ml-pipeline-design Skill
1★ repoDesign reproducible ML training and data pipelines — ingestion, validation, feature engineering, training, evaluation, continuous training orchestration. Analytics/BI ELT and dbt warehouse pipelines → data-pipeline-design; refactoring general analysis/reporting notebooks (no model training) to production code → notebook-to-production.
SWEStash/swe-workflow-skills/plugins/ml/skills/observability-design Skill
1★ repoDesign production observability — SLIs, SLOs, SLAs, error budgets, OpenTelemetry traces/metrics/logs, structured logging, alerting, dashboards. Triggers: SLO, SLI, SLA, error budget, observability, monitoring, OpenTelemetry, OTel, tracing, distributed tracing, structured logging, alerting, dashboard, metrics, correlation ID, alert fatigue.
SWEStash/swe-workflow-skills/plugins/mobile/skills/accessibility-design Skill
1★ repoDesign and implement accessible web/mobile apps to WCAG 2.1/2.2 — semantic HTML, ARIA patterns, keyboard navigation, focus management, color contrast, screen readers, accessible forms. Triggers: accessibility, a11y, WCAG, screen reader, keyboard navigation, ARIA, focus management, color contrast, alt text, semantic HTML, tab order, focus trap, skip link, announce. Build it in, don't bolt it on.
SWEStash/swe-workflow-skills/plugins/mobile/skills/mobile-architecture Skill
1★ repoDesign mobile app architecture — native (Swift/Kotlin) vs cross-platform (React Native/Flutter) selection, navigation and deep linking, state management, offline-first design and data sync, local persistence, push notifications, platform constraints (background work, battery, permissions). Triggers: mobile app architecture, iOS app, Android app, React Native or Flutter, offline first, data sync, mobile state management, deep linking, push notifications, app structure. Web SPA component architecture → frontend-architecture.
SWEStash/swe-workflow-skills/plugins/mobile/skills/ui-ux-design Skill
1★ repoDesign user experiences from an engineer's perspective — user flows, wireframes, interaction patterns, responsive strategy, navigation, loading/error/empty states. Triggers: design the UI, user flow, wireframe, how should this screen look, loading state, error state, empty state, responsive design, navigation, page layout, form design, mockup.
SWEStash/swe-workflow-skills/plugins/qa/skills/browser-verification Skill
1★ repoVerify a web app change by driving the real UI in a browser — reproduce the user flow end to end, watch console errors and network failures, exercise loading/error/empty states, capture screenshots as evidence. Use before claiming a UI change works. Triggers: check it in the browser, verify the UI, click through the flow, console errors, test it like a user, smoke test the frontend. Designing persistent test suites → test-suite-design; the generic done-gate → verification-before-completion (this is its browser-specific practice).
SWEStash/swe-workflow-skills/plugins/qa/skills/test-suite-design Skill
1★ repoDesign comprehensive test suites for existing code — strategy across unit/integration/e2e, fixtures, factories, helpers. Triggers: add tests, write tests for, increase coverage, test this module, testing strategy, test plan, what tests do I need, test infrastructure, test helpers, this has no tests. Not for TDD — use tdd-workflow.
SWEStash/swe-workflow-skills/skills/accessibility-design Skill
1★ repoDesign and implement accessible web/mobile apps to WCAG 2.1/2.2 — semantic HTML, ARIA patterns, keyboard navigation, focus management, color contrast, screen readers, accessible forms. Triggers: accessibility, a11y, WCAG, screen reader, keyboard navigation, ARIA, focus management, color contrast, alt text, semantic HTML, tab order, focus trap, skip link, announce. Build it in, don't bolt it on.
SWEStash/swe-workflow-skills/skills/browser-verification Skill
1★ repoVerify a web app change by driving the real UI in a browser — reproduce the user flow end to end, watch console errors and network failures, exercise loading/error/empty states, capture screenshots as evidence. Use before claiming a UI change works. Triggers: check it in the browser, verify the UI, click through the flow, console errors, test it like a user, smoke test the frontend. Designing persistent test suites → test-suite-design; the generic done-gate → verification-before-completion (this is its browser-specific practice).
SWEStash/swe-workflow-skills/skills/data-pipeline-design Skill
1★ repoDesign batch and streaming data pipelines — ELT into a warehouse/lakehouse, dbt and analytics engineering (staging/intermediate/marts layers), orchestration with Airflow or Dagster, idempotent loads, incremental models, backfills, CDC ingestion. Triggers: data pipeline, ELT, ETL, dbt models, data warehouse, Snowflake, BigQuery, ingest into the warehouse, Airflow DAG, Dagster, Kafka streaming, backfill, incremental load, nightly job duplicates rows. ML training/feature pipelines → ml-pipeline-design; validating the data → data-quality.
SWEStash/swe-workflow-skills/skills/frontend-architecture Skill
1★ repoDesign frontend architecture — React component hierarchy, state management, design tokens, data fetching, routing, error boundaries, code organization. Triggers: component architecture, state management, design system, design tokens, component library, React structure, folder structure, Zustand vs Redux, React Query, code splitting, error boundary, compound component.
SWEStash/swe-workflow-skills/skills/ml-pipeline-design Skill
1★ repoDesign reproducible ML training and data pipelines — ingestion, validation, feature engineering, training, evaluation, continuous training orchestration. Analytics/BI ELT and dbt warehouse pipelines → data-pipeline-design; refactoring general analysis/reporting notebooks (no model training) to production code → notebook-to-production.
SWEStash/swe-workflow-skills/skills/mobile-architecture Skill
1★ repoDesign mobile app architecture — native (Swift/Kotlin) vs cross-platform (React Native/Flutter) selection, navigation and deep linking, state management, offline-first design and data sync, local persistence, push notifications, platform constraints (background work, battery, permissions). Triggers: mobile app architecture, iOS app, Android app, React Native or Flutter, offline first, data sync, mobile state management, deep linking, push notifications, app structure. Web SPA component architecture → frontend-architecture.
SWEStash/swe-workflow-skills/skills/observability-design Skill
1★ repoDesign production observability — SLIs, SLOs, SLAs, error budgets, OpenTelemetry traces/metrics/logs, structured logging, alerting, dashboards. Triggers: SLO, SLI, SLA, error budget, observability, monitoring, OpenTelemetry, OTel, tracing, distributed tracing, structured logging, alerting, dashboard, metrics, correlation ID, alert fatigue.
SWEStash/swe-workflow-skills/skills/test-suite-design Skill
1★ repoDesign comprehensive test suites for existing code — strategy across unit/integration/e2e, fixtures, factories, helpers. Triggers: add tests, write tests for, increase coverage, test this module, testing strategy, test plan, what tests do I need, test infrastructure, test helpers, this has no tests. Not for TDD — use tdd-workflow.
SWEStash/swe-workflow-skills/skills/ui-ux-design Skill
1★ repoDesign user experiences from an engineer's perspective — user flows, wireframes, interaction patterns, responsive strategy, navigation, loading/error/empty states. Triggers: design the UI, user flow, wireframe, how should this screen look, loading state, error state, empty state, responsive design, navigation, page layout, form design, mockup.
kjhk3082/master-assistant-skill/skills/ui-ux Skill
1★ repo[EN] You MUST use this when designing, building, or reviewing user interfaces. Enforces design consistency, accessibility, and modern aesthetics. [KO] 사용자 인터페이스를 설계, 구축 또는 검토할 때 반드시 사용해야 합니다. 디자인 일관성, 접근성 및 현대적인 미학을 강제합니다.
leoluyi/skills/skills/infographic-design Skill
1★ repoMy personal collection of portable SKILL.md agent skills and tooling for Claude Code, Cursor & Codex — currently focused on Traditional Chinese (Taiwan) writing, de-AI editing, and business docs.
UniverLab/skills/canopy-loop-design Skill
1★ repoUse this skill when the user wants to turn a recurring or multi-step process into a reusable Canopy loop, write specs for a backlog or pool, inspect or reshape an existing loop graph, or coordinate background agent/check/gate flows with approvals and retries. Prefer reusable graph patterns over one-off pipelines, and build against the MCP loop tools that actually exist in the environment.
lgtm-hq/ai-skills/skills/test-ui-qsf Skill
1★ repoQSF project conventions for the Playwright E2E suite. Use when working in the QSF playwright-tests directory (authFixtures, ___ping-* handles, data-test-label test IDs, .auth storage states) — not for generic Playwright advice.
lgtm-hq/ai-skills/skills/test-ui Skill
1★ repoPlaywright E2E testing best practices. Use when writing browser tests, visual regression, or accessibility tests in any project. Enforces user-facing locators, auto-waiting, web-first assertions, and Page Object Model.