agentsclimarketplace

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

  • Content design

    planifest/planifest-framework/planifest-framework/external-skills/content-design Skill

    0★ repo

    Rewrite and improve an LLM prompt using proven prompt engineering techniques — covering clarity, persona, delimiters, chain-of-thought, examples, and output format specification.

  • Csharp style guide

    planifest/planifest-framework/planifest-framework/external-skills/csharp-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for C#/.NET codebases. Trigger when `.cs`, `.csproj`, `.sln`, `.props`, `.targets`, or `.razor` artifacts are created, modified, or reviewed and C#-specific quality rules (naming, nullability, async patterns, API design consistency) must be enforced. Do not use for Java/Kotlin or JavaScript/TypeScript style concerns unless C# artifacts are also changed. In multi-language pull requests, run together with other applicable `*-style-guide` skills.

  • Db transaction design

    planifest/planifest-framework/planifest-framework/external-skills/db-transaction-design Skill

    0★ repo

    Transaction design workflow for boundary definition, isolation-level choice, and contention control under real workload behavior. Use when correctness depends on concurrent read/write semantics; do not use for schema-only tasks that do not affect transaction behavior.

  • Design consultation

    planifest/planifest-framework/planifest-framework/external-skills/design-consultation Skill

    0★ repo

    Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. For existing sites, use /plan-design-review to infer the system instead. Use when asked to "design system", "brand guidelines", or "create DESIGN.md". Proactively suggest when starting a new project's UI with no existing design system or DESIGN.md. (gstack)

  • Design principles

    planifest/planifest-framework/planifest-framework/external-skills/design-principles Skill

    0★ repo

    Define and align product design principles that teams can apply consistently across UX decisions. Use when product or UX direction is ambiguous and teams need explicit decision guardrails before detailed screens or components are produced; do not use for backend data-model or deployment pipeline decisions.

  • Design qa implementation parity

    planifest/planifest-framework/planifest-framework/external-skills/design-qa-implementation-parity Skill

    0★ repo

    Verify implementation parity against approved design specs with severity-based decisions and fix guidance. Use when implemented UI must be compared against approved specs before release or sign-off; do not use for backend data-model or deployment pipeline decisions.

  • Design review

    planifest/planifest-framework/planifest-framework/external-skills/design-review Skill

    0★ repo

    Run structured design reviews that produce actionable findings and clear approval decisions. Use when a design artifact needs formal review for usability, accessibility, consistency, and implementation readiness before handoff or approval; do not use for backend data-model or deployment pipeline decisions.

  • Design shotgun

    planifest/planifest-framework/planifest-framework/external-skills/design-shotgun Skill

    0★ repo

    Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. Standalone design exploration you can run anytime. Use when: "explore designs", "show me options", "design variants", "visual brainstorm", or "I don't like how this looks". Proactively suggest when the user describes a UI feature but hasn't seen what it could look like. (gstack)

  • Design system foundations

    planifest/planifest-framework/planifest-framework/external-skills/design-system-foundations Skill

    0★ repo

    Define scalable design-system foundations with clear ownership and adoption boundaries. Use when multiple teams need shared component standards, foundational patterns, and ownership rules to deliver consistent UI across products; do not use for backend data-model or deployment pipeline decisions.

  • Design tokens

    planifest/planifest-framework/planifest-framework/external-skills/design-tokens Skill

    0★ repo

    Design token architecture workflow for semantic, scalable, implementation-ready token systems. Use when multiple screens or products need consistent color/type/spacing/motion decisions and token definitions before component implementation; do not use for backend data-model or deployment pipeline decisions.

  • Domain driven design

    planifest/planifest-framework/planifest-framework/external-skills/domain-driven-design Skill

    0★ repo

    Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", or "strategic design". Also trigger when splitting a monolith into services, defining microservice boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.

  • Fixing accessibility

    planifest/planifest-framework/planifest-framework/external-skills/fixing-accessibility Skill

    0★ repo

    Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.

    The same file is in 5 other repositories

  • Frontend design

    planifest/planifest-framework/planifest-framework/external-skills/frontend-design Skill

    0★ repo

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

    The same file is in 39 other repositories

  • Frontend ui engineering

    planifest/planifest-framework/planifest-framework/external-skills/frontend-ui-engineering Skill

    0★ repo

    Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

    The same file is in 6 other repositories

  • Github actions workflow design

    planifest/planifest-framework/planifest-framework/external-skills/github-actions-workflow-design Skill

    0★ repo

    Design and maintain GitHub Actions workflows with explicit trigger scope, security boundaries, and reliable job orchestration. Use when GitHub automation (build/test/release jobs, triggers, permissions, caching, concurrency, environments) must be created or revised; do not use for non-GitHub runtime architecture or data-layer design.

  • Go style guide

    planifest/planifest-framework/planifest-framework/external-skills/go-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for Go codebases. Trigger when `.go`, `go.mod`, `go.sum`, or `go.work` files are created, changed, or reviewed and Go-specific quality rules (error handling, concurrency patterns, interface design, package boundaries) must be enforced. Do not use for generic shell scripts, SQL-only changes, or non-Go runtime style concerns unless Go artifacts are also changed. In multi-language pull requests, run together with other applicable `*-style-guide` skills.

  • Interaction design

    planifest/planifest-framework/planifest-framework/external-skills/interaction-design Skill

    0★ repo

    Interaction design workflow for user flows, state transitions, and feedback behavior across key tasks. Use when user journeys require explicit interaction rules (state changes, validation feedback, error recovery, empty/loading behavior) before UI implementation; do not use for backend data-model or deployment pipeline decisions.

  • Java style guide

    planifest/planifest-framework/planifest-framework/external-skills/java-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for Java codebases with strong typing, explicit failure handling, and maintainable architecture boundaries. Use when `.java`, `pom.xml`, `build.gradle`, or `build.gradle.kts` artifacts are created, changed, or reviewed and Java-specific quality rules must be enforced. Do not use for Kotlin-only, Android-Gradle-only, or non-JVM language style concerns unless Java artifacts are also changed.

  • Javascript style guide

    planifest/planifest-framework/planifest-framework/external-skills/javascript-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for JavaScript codebases with explicit runtime contracts, safe async behavior, and maintainable module boundaries. Use when `.js`, `.jsx`, `.mjs`, or `.cjs` artifacts are created, changed, or reviewed and JS-specific quality rules must be enforced. Do not use for `.ts`, `.tsx`, `.d.ts`, or `tsconfig*.json`-owned code. For shared JS/TS config files, run together with `typescript-style-guide` when both JS and TS artifacts change in the same pull request.

  • Kubernetes workload design

    planifest/planifest-framework/planifest-framework/external-skills/kubernetes-workload-design Skill

    0★ repo

    Kubernetes workload design workflow for resource sizing, autoscaling behavior, and safe rollout strategy. Use when workload specs need concrete sizing and resilience decisions to meet reliability/performance targets; do not use for API contract design or requirement prioritization.

  • Lean ux

    planifest/planifest-framework/planifest-framework/external-skills/lean-ux Skill

    0★ repo

    Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "UX experiment", "collaborative design", "outcome over output", "design studio method", "assumption mapping", or "lightweight research". Also trigger when reducing design documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.

  • Mlops pipeline design

    planifest/planifest-framework/planifest-framework/external-skills/mlops-pipeline-design Skill

    0★ repo

    MLOps pipeline design workflow for orchestrating training, validation, packaging, and promotion with explicit gates. Use when ML lifecycle stages must be automated end-to-end with traceable promotion criteria; do not use for model-architecture research decisions.

  • Powershell style guide

    planifest/planifest-framework/planifest-framework/external-skills/powershell-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.

  • Privacy by design

    planifest/planifest-framework/planifest-framework/external-skills/privacy-by-design Skill

    0★ repo

    Privacy-by-design workflow for embedding data minimization, lawful basis, retention, and user-rights readiness into product decisions. Use when a feature touches personal data and privacy controls must be defined before implementation; do not use for narrow infrastructure tuning that does not affect personal-data handling.

  • Python style guide

    planifest/planifest-framework/planifest-framework/external-skills/python-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for Python codebases with strong typing, explicit error handling, and maintainable module boundaries. Use when Python artifacts are created, changed, or reviewed and Python-specific quality rules must be enforced.

  • React component design

    planifest/planifest-framework/planifest-framework/external-skills/react-component-design Skill

    0★ repo

    React component design workflow for state ownership, composition boundaries, and predictable rendering behavior. Use when React component behavior or structure must be implemented or revised; do not use for repository-wide architecture governance or release policy decisions.

  • React nextjs development

    planifest/planifest-framework/planifest-framework/external-skills/react-nextjs-development Skill

    0★ repo

    React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.

    The same file is in 5 other repositories

  • Refactoring ui

    planifest/planifest-framework/planifest-framework/external-skills/refactoring-ui Skill

    0★ repo

    Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off", "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent design tokens, creating dark mode themes, improving data visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.

  • Responsive layout design

    planifest/planifest-framework/planifest-framework/external-skills/responsive-layout-design Skill

    0★ repo

    Responsive layout design workflow for defining adaptive structure and component behavior across viewport ranges. Use when UI layouts must remain usable and readable across device contexts; do not use for backend data modeling or deployment pipeline decisions.

  • Rust style guide

    planifest/planifest-framework/planifest-framework/external-skills/rust-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for Rust codebases. Trigger when `.rs`, `Cargo.toml`, or `Cargo.lock` files are created, changed, or reviewed and Rust-specific quality rules (ownership/borrowing clarity, error handling, trait/API design, crate boundaries) must be enforced. Do not use for C/C++ toolchain conventions, shell-only changes, or non-Rust runtime style concerns unless Rust artifacts are also changed. In multi-language pull requests, run together with other applicable `*-style-guide` skills.

  • Sh style guide

    planifest/planifest-framework/planifest-framework/external-skills/sh-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for POSIX `sh` scripting. Trigger when `.sh` files, files with `#!/usr/bin/env sh` or `#!/bin/sh`, or CI workflow blocks with `shell: sh` are created, modified, or reviewed and portability/safety controls for POSIX shell must be enforced. Do not use for Bash-specific, Zsh-specific, or PowerShell-specific style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.

  • Software design philosophy

    planifest/planifest-framework/planifest-framework/external-skills/software-design-philosophy Skill

    0★ repo

    Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", or "pass-through method". Also trigger when reviewing interface designs for simplicity, evaluating whether an abstraction is pulling its weight, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For boundaries, see clean-architecture.

  • Sql style guide

    planifest/planifest-framework/planifest-framework/external-skills/sql-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for SQL schema, migration, and query artifacts. Trigger when `.sql` schema/query/migration artifacts are created, changed, or reviewed and SQL-specific quality rules (naming, migration safety, query clarity, and performance intent) must be enforced. Do not use for ORM-only code changes with no SQL artifacts, or for non-SQL data modeling documents. Use together with language-specific style guides only when both SQL and application code are modified.

  • Terraform style guide

    planifest/planifest-framework/planifest-framework/external-skills/terraform-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for Terraform infrastructure-as-code. Trigger when `.tf` or `.tfvars` source/modules/workflow configuration is created, changed, or reviewed and IaC-specific quality rules (module boundaries, variable typing, state safety, plan/apply discipline) must be enforced. Do not use for CloudFormation, Pulumi, or application-runtime coding conventions unless Terraform artifacts are also changed. Combine with language-specific guides only when application code and IaC both change.

  • Theme factory

    planifest/planifest-framework/planifest-framework/external-skills/theme-factory Skill

    0★ repo

    Toolkit 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

  • Typescript style guide

    planifest/planifest-framework/planifest-framework/external-skills/typescript-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for TypeScript codebases. Trigger when `.ts`, `.tsx`, `.d.ts`, or `tsconfig*.json` files are created, changed, or reviewed and TS-specific quality rules (type safety, narrowing, async/error handling, module boundaries) must be enforced. Do not use for JavaScript-only modules that are outside TypeScript type-check scope. In mixed JS/TS repositories, this skill owns `tsconfig`-scoped modules. For shared JS/TS configuration files (for example `package.json`, shared lint/test config), run together with `javascript-style-guide` when both JS and TS artifacts change in the same pull request.

  • Ux research synthesis

    planifest/planifest-framework/planifest-framework/external-skills/ux-research-synthesis Skill

    0★ repo

    UX research synthesis workflow for turning mixed evidence into prioritized design actions. Use when multiple qualitative and quantitative inputs must be consolidated into clear design implications; do not use for backend architecture or deployment planning.

  • Web design engineer

    planifest/planifest-framework/planifest-framework/external-skills/web-design-engineer Skill

    0★ repo

    Build high-quality visual Web artifacts using HTML/CSS/JavaScript/React — web pages, landing pages, dashboards, interactive prototypes, HTML slide decks, animated demos, UI mockups, data visualizations, and more. Use this skill whenever the user's request involves a visual, interactive, or front-end deliverable, including: - Creating web pages, landing pages, dashboards, marketing pages - Building interactive prototypes or UI mockups (with device frames) - Building HTML slide decks / presentations - Creating CSS/JS animations or timeline-driven animated demos - Turning design mockups, screenshots, or PRDs into interactive implementations - Data visualization (Chart.js / D3, etc.) - Design system / UI Kit exploration Even if the user doesn't explicitly say "HTML" or "web page," this skill applies whenever the intent is to produce something visual, interactive, or presentational. Not applicable: pure back-end logic, CLI tools, data-processing scripts, non-visual code tasks, command-line debugging.

    The same file is in 1 other repository

  • Webapp testing

    planifest/planifest-framework/planifest-framework/external-skills/webapp-testing Skill

    0★ repo

    Toolkit 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

  • Zsh style guide

    planifest/planifest-framework/planifest-framework/external-skills/zsh-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for Zsh scripting. Trigger when `.zsh`, `.zshrc`, `.zprofile`, `.zshenv`, `.zlogin`, `.zlogout` files, files with `#!/usr/bin/env zsh` or `#!/bin/zsh`, or CI workflow blocks with `shell: zsh` are created, modified, or reviewed and Zsh-specific quality controls must be enforced. Do not use for POSIX `sh`, Bash-specific, or PowerShell-specific style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.

  • Planifest design critic

    planifest/planifest-framework/planifest-framework/skills/planifest-design-critic Skill

    0★ repo

    Fresh-context REJECT-default critique of P1 spec and P2 ADR artifacts before the human sees them. Spawned by the orchestrator as a subagent; report-only until promoted.

  • A11y audit

    badass-courses/a11y-agent/.claude/skills/a11y-audit Skill

    no license0★ repo

    Structured accessibility assessment following a structured testing order. Asks targeted questions, walks through keyboard → tools → contrast → zoom → screen readers, produces prioritized report with WCAG references. Use when asked to "check accessibility", "audit a11y", "test accessibility", or before shipping UI.

  • A11y component

    badass-courses/a11y-agent/.claude/skills/a11y-component Skill

    no license0★ repo

    Scaffold accessible interactive components with correct ARIA, keyboard handling, and focus management. Supports modal, menu, tabs, accordion (v1), plus date picker, combobox, slideshow (v2). Use when building these from scratch.

  • A11y fix

    badass-courses/a11y-agent/.claude/skills/a11y-fix Skill

    no license0★ repo

    Fix accessibility issues in current code. Works through findings from a11y-audit, a11y-scan, or a11y-review. Makes changes, explains rationale, notes what to test manually. Use when asked to "fix accessibility", "make this accessible", or after any a11y assessment.

  • A11y review

    badass-courses/a11y-agent/.claude/skills/a11y-review Skill

    no license0★ repo

    Lightweight code review pass for accessibility. Checks markup, event handlers, ARIA, test coverage in changed files. Use for PR reviews, pre-merge checks, or when asked to "review for accessibility". For comprehensive assessment, use a11y-audit instead.

  • A11y scan

    badass-courses/a11y-agent/.claude/skills/a11y-scan Skill

    no license0★ repo

    Run automated accessibility scan using axe-core via Playwright. Captures WCAG violations, tracks progress over time. Use when asked to "scan for accessibility", "run axe", or "check a11y automatically".

  • A11y test

    badass-courses/a11y-agent/.claude/skills/a11y-test Skill

    no license0★ repo

    TDD workflow for accessibility. Write tests that fail when a11y breaks, at unit, integration, and E2E levels. Use when asked to "write accessibility tests", "add a11y tests", or "test this component for accessibility".

  • A11y advocate

    badass-courses/a11y-agent/source/skills/a11y-advocate Skill

    no license0★ repo

    Build accessibility culture and communicate with stakeholders. Generate statements, prioritize issues, write tickets, create team checklists, produce risk assessments. Use when asked to "prioritize a11y", "accessibility statement", "convince PM about a11y", or "create testing process".

  • A11y agent

    badass-courses/a11y-agent/source/skills/a11y-agent Skill

    no license0★ repo

    Accessibility expertise for building inclusive web interfaces. Covers semantic HTML, ARIA, keyboard interaction, screen reader support, color contrast, focus management, responsive zoom, motion safety, automated testing, and organizational culture. Use when building or reviewing any web UI to ensure it works for everyone.

  • A11y audit

    badass-courses/a11y-agent/source/skills/a11y-audit Skill

    no license0★ repo

    Structured accessibility assessment following a structured testing order. Asks targeted questions, walks through keyboard → tools → contrast → zoom → screen readers, produces prioritized report with WCAG references. Use when asked to "check accessibility", "audit a11y", "test accessibility", or before shipping UI.

  • A11y component

    badass-courses/a11y-agent/source/skills/a11y-component Skill

    no license0★ repo

    Scaffold accessible interactive components with correct ARIA, keyboard handling, and focus management. Supports modal, menu, tabs, accordion (v1), plus date picker, combobox, slideshow (v2). Use when building these from scratch.

  • A11y fix

    badass-courses/a11y-agent/source/skills/a11y-fix Skill

    no license0★ repo

    Fix accessibility issues in current code. Works through findings from a11y-audit, a11y-scan, or a11y-review. Makes changes, explains rationale, notes what to test manually. Use when asked to "fix accessibility", "make this accessible", or after any a11y assessment.

  • A11y review

    badass-courses/a11y-agent/source/skills/a11y-review Skill

    no license0★ repo

    Lightweight code review pass for accessibility. Checks markup, event handlers, ARIA, test coverage in changed files. Use for PR reviews, pre-merge checks, or when asked to "review for accessibility". For comprehensive assessment, use a11y-audit instead.

  • A11y scan

    badass-courses/a11y-agent/source/skills/a11y-scan Skill

    no license0★ repo

    Run automated accessibility scan using axe-core via Playwright. Captures WCAG violations, tracks progress over time. Use when asked to "scan for accessibility", "run axe", or "check a11y automatically".

  • A11y test

    badass-courses/a11y-agent/source/skills/a11y-test Skill

    no license0★ repo

    TDD workflow for accessibility. Write tests that fail when a11y breaks, at unit, integration, and E2E levels. Use when asked to "write accessibility tests", "add a11y tests", or "test this component for accessibility".

  • Figma create design system rules

    michelve/hugin-v0/skills/figma-create-design-system-rules Skill

    0★ repo

    Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.

  • Figma generate design

    michelve/hugin-v0/skills/figma-generate-design Skill

    0★ repo

    Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code'. This is the preferred workflow skill whenever the user wants to build or update a full page, screen, or view in Figma from code or a description. Discovers design system components, variables, and styles via search_design_system, imports them, and assembles screens incrementally section-by-section using design system tokens instead of hardcoded values.

  • Figma generate library

    michelve/hugin-v0/skills/figma-generate-library Skill

    0★ repo

    Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.

  • Figma implement design

    michelve/hugin-v0/skills/figma-implement-design Skill

    0★ repo

    Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.

  • Playwright skill

    michelve/hugin-v0/skills/playwright-skill Skill

    0★ repo

    Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.