Skip to content
cccskills
FreePublished on GitHub

build-frontend

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (3)

  • SKILL.md1.5 KB
  • agents/openai.yaml217 B
  • references/verification.md1.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 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:

component test → feature test → type/lint → build → visual/interaction check

If a command cannot run, report the exact blocker and what remains unverified.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

See all skills by Phelan164

Report a problem with this skill