CSS documentation — MCP mirror

Agent skills

Synthetic long-form coverage for Agent skills overview.

Purpose

This page uses Agent skills overview as a realistic documentation scenario. It is synthetic test material designed to exercise long-form rendering, navigation, search, and publication without reproducing a reference project's prose.

The structure keeps assumptions, choices, implementation notes, and verification evidence close together. It intentionally combines prose, tables, code, callouts, lists, and internal links on one page.

Publication test

This callout must survive authoring validation and hosted publication as a supported Markdown directive.

Decision matrix

ConcernBaselineStress caseEvidence
StructureOne focused sectionNested navigation and long pagesPublic route resolves
ContentParagraphsTables, code, callouts, and tasksExpected elements render
DeliverySaved CurrentAsynchronous hosted buildLive status and HTTP 200

Example

.example-20 {
  display: grid;
  gap: clamp(0.5rem, 1vw, 1rem);
  color: oklch(42% 0.08 250);
}

Verification checklist

  • The page has one renderer-owned title.

  • Body headings begin at level two.

  • Code fences declare a language.

  • Confirm the hosted page after asynchronous promotion.

Detailed scenario 1

Scenario 1 for Agent skills overview separates inputs, expected behavior, and observable failure evidence. Reviewers compare the saved source with the hosted result and check navigation, search, code rendering, and responsive layout for omissions.

Boundary coverage includes near-empty values, long identifiers, repeated operations, and reordered nodes. The result is checked through both visible behavior and delivery state rather than appearance alone.

Detailed scenario 2

Scenario 2 for Agent skills overview separates inputs, expected behavior, and observable failure evidence. Reviewers compare the saved source with the hosted result and check navigation, search, code rendering, and responsive layout for omissions.

Boundary coverage includes near-empty values, long identifiers, repeated operations, and reordered nodes. The result is checked through both visible behavior and delivery state rather than appearance alone.

Detailed scenario 3

Scenario 3 for Agent skills overview separates inputs, expected behavior, and observable failure evidence. Reviewers compare the saved source with the hosted result and check navigation, search, code rendering, and responsive layout for omissions.

Boundary coverage includes near-empty values, long identifiers, repeated operations, and reordered nodes. The result is checked through both visible behavior and delivery state rather than appearance alone.

Trusted component check

Review checkpoint

This paired registry component must remain static and publishable.

Open the section landing page.