build-frontend skillA
build-frontend is agent-read markdown (skill) from phelan164/codex-howto: Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Build Frontend ## Domain contract - Preserve the project’s framework, styling system, and component conventions. - Do not invent API response fields or silently change backend contracts. - Do not replace an established design system with custom one-off styling. - Define loading, empty, error, success, and disabled states that the changed flow can reach. - Keep semantic HTML, keyboard navigation, focus behavior, labels, and contrast in scope. - Avoid speculative shared abstractions for a single component. - Treat screenshots and mockups as visual references, not proof of interaction behavior. - Do not claim visual verification unless the UI was rendered or inspected. ## Execute and verify Read [references/verification.md](references/verification.md) for UI, accessibility, responsive, and browser verification. Load it when the task changes rendered behavior or interaction. Reuse existing components and tokens, implement the smallest coherent change, and prove behavior at the lowest useful layer. Prefer: ```text component test → feature test → type/lint → build → visual/interaction check ``` If a command cannot run, report the exact blocker and what remains unverified.
Read the whole file at its exact version.
How to install
mdr add phelan164/codex-howto/build-frontend@git:20260731.42e092cmdr add phelan164/codex-howto/build-frontend@sha256:8c34e89a05f58bbcPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_7awcw6ziqjw4mer7)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260731.42e092c latest | 2026-07-31 | 42e092c | 1,567 B | A | view · diff |
| git:20260724.a8a7148 | 2026-07-24 | a8a7148 | 2,469 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1567 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
phelan164/codex-howto · 9 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7awcw6ziqjw4mer7 GET https://markdownregistry.com/api/v1/resolve?ref=phelan164/codex-howto/build-frontend GET https://markdownregistry.com/api/v1/blob/8c34e89a05f58bbc6dc8beb646673bddd6c43afa00e1756fdcf434ed98b2bc21
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.