프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. Google로 로그인하면 리뷰를 쓸 수 있어요.프로토타입 · 30분마다 업데이트
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

Front-End-Checklist Skill

저장소 ↗

같은 프로젝트의 MCP 버전도 있습니다 →

제작자: thedaviddias★ 74,768 (whole repo)skill 392개

★ 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 디자인과 웹
Maker’s original description
🗂 The essential checklist for modern web development, for humans and AI agents
제작자용: README에 배지 달기

제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.

[![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)

함께 쓰기

같은 작업에서 AI를 서비스에 연결하는 MCP

Next AI Draw.io

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

제작자: DayuanJiang널리 사용됨↓ 2.2만/주★ 3.7만 저장소 전체의 별5일 전 업데이트

MCP · 서비스 연결내 컴퓨터에서 실행

Pascal 3D Editor

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

제작자: pascalorg널리 사용됨↓ 1천/주★ 2.6만 저장소 전체의 별어제 업데이트

MCP · 서비스 연결컴퓨터 또는 클라우드✓ 서비스 회사 · pascal.app

Semiotic

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

제작자: nteract널리 사용됨↓ 8.5천/주★ 2.7천오늘 업데이트

MCP · 서비스 연결컴퓨터 또는 클라우드

비슷한 Skill

같은 종류의 작업, Skill 목록과 같은 순서

비슷한 항목과 비교
이 항목
Front-End-Checklist
impeccablediagram-designfrontend-slidesguizang-ppt-skill
제작자thedaviddiaspbakauscathrynlaveryzarazhangruiop7418
Skill 수3921111
GitHub 별74,768112,54468,06932,51430,030
마지막 코드 변경2026년 10월 31일2026년 11월 18일2026년 11월 13일2026년 6월 24일2026년 10월 30일
라이선스MITApache-2.0MITMITAGPL-3.0

thedaviddias의 Skill(지시 묶음) 392개, AI가 읽고 그대로 일해요 · 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.

Skill과 MCP의 차이

MCP = 손

AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.

Skill = 안내서

작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.

겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.

쓸 수 있는 앱

제작자가 밝히지 않음 · SKILL.md 형식 Skill은 Claude Code, Codex, Cursor 같은 Agent Skills 지원 앱에서 써요

설치

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 ↑

토론

질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.

아직 글이 없어요. 처음으로 질문하거나 공유해 보세요.

이곳의 글은 사용자가 쓴 것으로, PopNx 팀의 글이 아니에요.

로그인하고 글쓰기

GitHub 정보

GitHub 스타
74,768
Stars are for the whole repo, not each skill
제작자
thedaviddias
라이선스
MIT
최근 코드 수정
2026년 10월 31일
repo 안 SKILL.md(번역본과 템플릿 포함)
30
토픽
ai-agent, ai-agents, checklist, css, front-end-developer-tool, front-end-development, frontend, guidelines, html, javascript, lists, reference