coding-frontend

Build and refactor React and Next.js user interfaces with test-backed verification.

10|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcocello/dot-codex --skill coding-frontend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-frontend
Source: https://github.com/marcocello/dot-codex/tree/main/skills/coding-frontend
Command: npx skills add https://github.com/marcocello/dot-codex --skill coding-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps build, bootstrap, and refactor repository-local React and Next.js interfaces without drifting from the existing design system or frontend conventions. It is meant for user-facing work where the UI, interaction flow, and implementation structure all need to stay consistent.

Core Features & Use Cases

  • Frontend construction: Create or extend React and Next.js app structure for greenfield or existing projects.
  • UI refactors: Rework interface components while preserving repository patterns, layout conventions, and shared utilities.
  • User-facing features: Implement interactive screens, navigation, and stateful UI behavior with test-backed verification.
  • Platform-aware routing: Prefer the repository's established frontend approach, or Sites only when explicitly requested or already established.

Quick Start

Use the coding-frontend skill to implement this repository's React or Next.js feature while preserving existing conventions and verifying the user-facing behavior with appropriate tests.

Frequently Asked Questions about coding-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build React and Next.js user interfaces while preserving existing frontend conventions?

To build React and Next.js user interfaces while preserving existing conventions, scaffold or extend repository-local components by adhering to the established repository structure, design-system consistency, and observable test-backed verification of UI behavior.

How do I refactor React components without breaking the repository's design system?

Refactoring React components without breaking the design system requires reworking interface components while preserving repository patterns, layout conventions, and shared utilities to maintain strict design-system consistency across the frontend.

Does this frontend development approach support greenfield app scaffolding and existing projects?

Yes, this frontend development approach supports both greenfield app scaffolding and existing projects by constructing and extending React and Next.js app structures tailored to the repository's established conventions.

How do I implement interactive Next.js screens with test-backed UI behavior verification?

Implementing interactive Next.js screens with test-backed UI behavior verification involves building stateful user-facing features, navigation, and browser-facing interactions while validating the observable behavior through established testing practices.

Can I use this for platform-aware routing in Next.js beyond the repository's established approach?

Yes, for platform-aware routing in Next.js, it prefers the repository's established frontend approach by default, but it can utilize alternative routing platforms like Sites when explicitly requested or already established in the project.

What is the best way to ensure UI consistency when adding user-facing features to a React repository?

The best way to ensure UI consistency when adding user-facing features to a React repository is to enforce adherence to repository structure and design-system consistency while verifying observable UI behavior with tests.