跳到正文
cccskills
免费在 GitHub 公开

doctype

Inspect raw HTML responses for a correct HTML5 doctype at the start of the document. Identify missing or outdated declarations and preceding content, then guide fixes that enable standards-mode rendering in browsers.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Use when applies to all HTML documents. Always check the very first line of the raw HTML source (view-source: or DevTools > Network > Response). In SSR frameworks, check the root HTML template (e.g., _document.tsx in Next.js, index.html in Vite/Vue, application.html.erb in Rails). The doctype is not a tag — it is a declaration and does not need a closing tag.

查看安装方法

适用场景

  • Checking the doctype in raw HTML responses
  • Replacing old HTML4 or XHTML declarations
  • Removing extra content before the doctype
  • Verifying HTML output from a framework

包含的文件(2)

  • SKILL.md3.3 KB
  • references/rule.md3.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Use the HTML5 doctype

Without the HTML5 doctype, browsers fall back to Quirks Mode, which emulates the rendering behavior of pre-standards browsers from the late 1990s. In Quirks Mode, the CSS box model changes (padding adds to element width), vertical centering breaks, and many modern HTML5 APIs may behave unexpectedly. This causes cross-browser rendering inconsistencies that are difficult to debug and may produce inaccessible layouts.

Quick Reference

  • Every HTML document must begin with <!DOCTYPE html> as its very first line
  • Without a doctype, browsers enter Quirks Mode — a legacy compatibility mode with inconsistent CSS and JavaScript behavior
  • The HTML5 doctype is case-insensitive but <!DOCTYPE html> (uppercase DOCTYPE) is the conventional form
  • No other content, not even whitespace or BOM characters, should appear before the doctype
  • Frameworks like Next.js, Nuxt, and Remix automatically include the doctype — verify in rendered HTML, not source templates

Check

Check the very first line of the HTML document source (not the DOM — the raw HTTP response). The document must begin with <!DOCTYPE html> (case-insensitive). Flag if: (1) the doctype is missing entirely; (2) an old HTML4 or XHTML doctype is used (contains PUBLIC and a DTD URL); (3) the doctype is not the absolute first content (whitespace or BOM before it triggers some browsers to enter Quirks Mode); (4) the doctype has incorrect syntax.

Fix

Add <!DOCTYPE html> as the absolute first line of the HTML document, before the <html> tag. Remove any old HTML4 or XHTML doctypes. Ensure no whitespace, comments, or BOM markers precede the doctype. For framework projects: verify in the root HTML template file, and confirm in the rendered HTML by viewing page source in the browser.

Explain

The DOCTYPE declaration tells the browser which version of HTML the document uses. <!DOCTYPE html> activates Standards Mode (also called Full Standards Mode) in all modern browsers, ensuring consistent rendering behavior. Without it, browsers enter Quirks Mode to emulate old IE behavior — a compatibility mode that changes the box model, float clearing, table rendering, and other CSS behaviors. The HTML5 doctype was intentionally made simple (just <!DOCTYPE html>) to replace the verbose HTML4/XHTML doctypes that required a full DTD URL.

Code Review

Review templates, server-rendered HTML, and shared components that output markup related to Use the HTML5 doctype. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/html/doctype

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

404-page

免费

Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.

中文简介正在准备中。当前显示英语简介。

  • Creating a helpful custom 404 page
  • Adding search and navigation for broken links
  • Checking missing pages that return HTTP 200
thedaviddias/Front-End-Checklist7.5万2026年10月6日 更新

Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.

中文简介正在准备中。当前显示英语简介。

  • Reviewing a website’s About page
  • Creating a page about the organization and its mission
  • Checking how operator information appears in rendered output
thedaviddias/Front-End-Checklist7.5万2026年10月6日 更新

Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.

中文简介正在准备中。当前显示英语简介。

  • Review accessibility coverage for shared components
  • Add accessibility checks to page flow tests
  • Run accessibility tests in CI
thedaviddias/Front-End-Checklist7.5万2026年10月6日 更新

Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.

中文简介正在准备中。当前显示英语简介。

  • Reviewing accessibility across the sign-in process
  • Checking verification code paste and autofill
  • Inspecting password reset and account recovery
thedaviddias/Front-End-Checklist7.5万2026年10月6日 更新

Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.

中文简介正在准备中。当前显示英语简介。

  • Reviewing form error announcements
  • Checking success message display duration
  • Auditing live update notifications
thedaviddias/Front-End-Checklist7.5万2026年10月6日 更新

Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.

中文简介正在准备中。当前显示英语简介。

  • Reviewing tables for screen reader accessibility
  • Checking header relationships in tables with merged cells
  • Reviewing table patterns in a design system
thedaviddias/Front-End-Checklist7.5万2026年10月6日 更新

查看 thedaviddias 的全部技能

报告此技能的问题