interpreting-html

$npx mdskill add github/replica/interpreting-html

When the site is rendered to HTML, you can identify several aspects of the app code via HTML properties:

SKILL.md

.github/skills/interpreting-htmlView on GitHub ↗
---
name: interpreting-html
description: 'Map rendered/pasted HTML class names back to source code (CSS Modules, Fluent UI, Griffel). USE WHEN: inspecting Playwright DOM output, debugging styles in the browser, or reverse-engineering pasted HTML.'
---

# How to Interpret Pasted HTML Code

When the site is rendered to HTML, you can identify several aspects of the app code via HTML properties:

- Class names with the pattern `_camelCase_123ab_45` correspond to class names applied from CSS Modules.
  - For example, `class="_headerWrapper_16arl_15"` in HTML comes from `className={styles.headerWrapper}` in React.
- Class names prefixed with `fui-` are derived from Fluent UI components.
  - These are Fluent component root elements. For example, `fui-Button` is a `<Button/>`.
  - These are Fluent component sub-elements if they contain the `__` delimiter (BEM style). For example, `fui-Button__icon` comes from `<Button icon={<SomeIcon20Regular/>}/>`.
- Class names that follow the pattern `f123abc` are Griffel-generated atomic classes. Reset classes use an `r…` hash, and sequence classes start with `___`. These are auto-generated and are not authored source identifiers. For example: `class="f11589ue f1q5o8ev f1pdflbu fkfq4zb"`. Do not search these hashes to locate authored styles.
- `data-*` attributes may be authored in React, generated by a framework, or derived from dynamic state. Verify their origin before using them to locate source; do not assume their values are static.
- `aria-label` attributes and text content often appear as literal strings in this prototype, so searching them can help locate the corresponding JSX. For example, `Create agent` appears directly in the agents route. Values may also come from props, data, or localization, so a rendered string does not always have an exact literal match in source.

## Interpreting React Grab Context

The prototype's customized React Grab context is not raw DOM output. It decodes CSS Module class names to their local names and omits Fluent/Griffel classes. A cleaned class such as `brandLink` can therefore correspond to a hashed CSS Module class in the browser.

The `in Component (path:line:column)` entries describe component usage or rendering ancestry, not necessarily component definitions. Components that render passed-in children may appear in the ancestry even when another component created that JSX. Use the reported location to inspect the relevant call site or component body before deciding which source to edit.

More from github/replica

SkillDescription
accessibility-auditAudits actual components and routes against applicable WCAG 2.2 A/AA criteria using consumer-owned design-system evidence and repository tools. Use when asked for an accessibility audit, a11y check, keyboard or focus review, contrast check, or screen-reader verification.
add-seed-dataCreates or updates believable deterministic raw fixture scenarios without breaking an existing prototype. Use when asked to add or change fixtures, seed data, sample data, scenarios, or cross-record relationships. Not for UI redesign, live-data infrastructure, or unrelated commands.
agent-browserUse for explicit agent-browser CLI checks or a named browser capability neither the Copilot canvas nor configured Playwright MCP can supply. Ordinary rendered checks and browser selection belong to browser-canvas-validation.
browser-canvas-validationUse the Copilot browser canvas first for rendered route checks, interaction tests, screenshots and visual, responsive or accessibility evidence. Use configured isolated Playwright MCP only when the canvas is unavailable for a required check.
component-design-system-reviewReviews existing UI components for design-system consistency, states, responsiveness and accessibility using consumer-owned context. Use when asked to review component quality, check design-system adherence or audit component consistency.
context-templatesShared context template library for setup-skills. Read when discovering context documents or their ownership. This library supplies research inputs, not active product context or a separate authoring workflow.
coreai-ds-fluentui-reactFind and apply CoreAI design-system documentation. Use when choosing or reviewing @coreai-ds/react-components components, props, tokens, themes, templates, or UI patterns.
create-prototypeBuilds new UI prototypes and makes targeted changes to existing prototypes using consumer-owned context. Use when asked to build a prototype, mock up a UI, or add, change, refine or recreate part of an existing prototype. Do not use for unrelated tasks, routine commands, Git lifecycle actions, acknowledgements or infrastructure work.
css-stylingCSS Modules conventions, design tokens, container queries, and CSS-vs-component boundaries. USE WHEN: editing any `*.css` / `*.module.css` file in this repo, or writing styles for a new component.
developer-handoffWrites a lightweight Markdown concept handoff from existing decisions and evidence. Use when explicitly asked for a developer handoff, to transfer a prototype or concept to another team, or to prepare a brief for implementation. Not for ordinary prototype completion, building, reviewing or publishing.