Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Inicia sesión con Google para escribir reseñas.Prototipo · se actualiza cada 30 min
PopNx MCPServidores MCP para quienes usan IA · en palabras sencillas

Front-End-Checklist Skill

Repositorio ↗

También disponible como servidor MCP →

de thedaviddias★ 74.768 (whole repo)392 skills

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 392 skills

  • Connects Instruction files the AI reads
  • Account or key Not confirmed (README mentions a key or .env file)
  • Category Diseño y web
Maker’s original description
🗂 The essential checklist for modern web development, for humans and AI agents
Para autores: añade una insignia a tu README

Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/thedaviddias-front-end-checklist.svg)](https://mcp.popnx.com/en/skills/thedaviddias-front-end-checklist)

Úsalo junto con

Servidores MCP que conectan la IA a servicios para el mismo trabajo

Next AI Draw.io

draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand

de DayuanJiangMuy usado↓ 21,7 mil/sem★ 37,1 mil Estrellas de todo el repositorioActualizado hace 5 días

MCP · Conecta un servicioSe ejecuta en tu computadora

Pascal 3D Editor

Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.

de pascalorgMuy usado↓ 1 mil/sem★ 25,6 mil Estrellas de todo el repositorioActualizado ayer

MCP · Conecta un servicioComputadora o nube✓ del servicio · pascal.app

Semiotic

Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.

de nteractMuy usado↓ 8,5 mil/sem★ 2,7 milActualizado hoy

MCP · Conecta un servicioComputadora o nube

Skills parecidas

Mismo tipo de trabajo, ordenadas como la lista de Skills

Comparado con otros parecidos
Este
Front-End-Checklist
impeccablediagram-designfrontend-slidesguizang-ppt-skill
Autorthedaviddiaspbakauscathrynlaveryzarazhangruiop7418
Skills3921111
Estrellas de GitHub74.768112.54468.06932.51430.030
Último cambio de código31 oct 202618 nov 202613 nov 202624 jun 202630 oct 2026
LicenciaMITApache-2.0MITMITAGPL-3.0

392 skills (conjuntos de instrucciones) de thedaviddias que la IA lee y sigue · no es un MCP server

Pick the skill to install

Install only the ones you use. Open a skill to see how to install it

This set has 392 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below

Showing 30 of 392 See all on GitHub

  • 404-page

    Use when reviewing templates, rendered HTML, or shared components related to Create a custom 404 error page. Validate the final browser-facing markup, not just the source framework abstraction.

  • about-page

    Use when auditing metadata, crawlability, structured data, or indexability related to Create a dedicated About page. Verify the rendered HTML and HTTP response rather than relying only on source files.

  • accessibility-testing

    Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.

  • accessible-authentication

    Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.

  • accessible-notifications

    Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction.

  • accessible-tables

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic table markup for screen readers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • accessible-tooltips

    Use when reviewing templates, rendered HTML, or shared components related to Create accessible tooltips. Validate the final browser-facing markup, not just the source framework abstraction.

  • accesskeys

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure accesskey values are unique. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • accordion-accessibility

    Use when reviewing templates, rendered HTML, or shared components related to Make accordions keyboard navigable. Validate the final browser-facing markup, not just the source framework abstraction.

  • affiliate-disclosure

    Use when auditing metadata, crawlability, structured data, or indexability related to Provide clear affiliate disclosures. Verify the rendered HTML and HTTP response rather than relying only on source files.

  • ai-content

    Use when auditing metadata, crawlability, structured data, or indexability related to Audit and refine AI-generated content. Verify the rendered HTML and HTTP response rather than relying only on source files.

  • all-noindex-pages

    Use when auditing metadata, crawlability, structured data, or indexability related to Audit all noindex pages. Verify the rendered HTML and HTTP response rather than relying only on source files.

  • alt-text

    Use when reviewing image assets, markup, and CDN or build transforms related to Provide meaningful alt text for images. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.

  • anchor-smooth-scroll

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide instant anchor scroll option. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • anchor-text

    Use when auditing metadata, crawlability, structured data, or indexability related to Use descriptive anchor text. Verify the rendered HTML and HTTP response rather than relying only on source files.

  • animated-content

    Use when auditing slow page loads, heavy assets, or rendering delays related to Convert animated GIFs to video. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

  • animation-performance

    Use when reviewing stylesheets, component styles, and responsive behavior related to Use transform and opacity for animations. Check the rendered layout across breakpoints and interaction states before proposing a fix.

  • aria-allowed-attr

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use only allowed ARIA attributes for each role. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • aria-command-name

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for ARIA command elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • aria-deprecated-role

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid using deprecated ARIA roles. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • aria-dialog-name

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure dialogs have an accessible name. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • aria-hidden-body

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Do not use aria-hidden on the document body. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • aria-hidden-focus

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Remove focusable elements from aria-hidden containers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • aria-input-field-name

    Use when applies to all ` ` (except type=hidden), ` `, ` `, and custom form widgets using role=textbox, role=combobox, role=spinbutton, role=searchbox, or role=listbox.

  • aria-labels

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for all interactive elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • aria-live-regions

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Announce dynamic content with ARIA live regions. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • aria-meter-name

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for meter elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • cli

    Review frontend code and live pages against the Front-End Checklist (380+ rules for accessibility, performance, SEO, security, HTML, CSS, JavaScript, images, i18n, privacy, testing) using the `frontendchecklist` CLI. Use when writing, reviewing, or shipping HTML/CSS/JS/JSX/TSX/Vue/Svelte/Astro code…

  • frontend-checklist-global

    Use when auditing or improving any frontend codebase against the full Front-End Checklist rule corpus through one entry point.

  • h1

    Use when auditing a page's heading structure, generating H1 text for landing pages or blog posts, or reviewing a CMS template that may produce empty or missing H1 elements.

En qué se diferencia un Skill de MCP

MCP = las manos

Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.

Skill = el manual

Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.

A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.

Funciona con

El autor no lo indica · los skills con SKILL.md funcionan en apps compatibles con Agent Skills, como Claude Code, Codex y Cursor

Instalar

Pick a skill first

This repo has 392 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP

Let the AI install it
Upload to claude.ai

Go to the skill list ↑

Conversación

Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.

Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.

Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.

Inicia sesión para publicar

Desde GitHub

Estrellas en GitHub
74.768
Stars are for the whole repo, not each skill
Autor
thedaviddias
Licencia
MIT
Último cambio de código
31 oct 2026
Archivos SKILL.md del repo (con traducciones y plantillas)
30
Temas
ai-agent, ai-agents, checklist, css, front-end-developer-tool, front-end-development, frontend, guidelines, html, javascript, lists, reference