frontend-engineer

Enforce a build-test-verify lifecycle for Next.js, Vite, or HTML/CSS projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CjLogic/nanocrew --skill frontend-engineer-cjlogic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-engineer
Source: https://github.com/CjLogic/nanocrew/tree/main/container/skills/frontend-engineer
Command: npx skills add https://github.com/CjLogic/nanocrew --skill frontend-engineer-cjlogic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure frontend projects are built, tested, accessible, and visually verified in a real browser before declaring work done, preventing silent quality gaps.

Core Features & Use Cases

  • Enforces a strict build-test-verify workflow for every web project to ensure reliability.
  • Guides developers through code quality, accessibility, responsiveness, and performance checks.
  • Use Case: a team shipping a Next.js app can rely on this workflow to guarantee browser-visible quality before deployment.

Quick Start

Follow this workflow on a frontend project to enforce build-test-verify and ensure production-ready, visually verified results.

Frequently Asked Questions about frontend-engineer

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

FAQPage Schema
How do I enforce a build-test-verify workflow for my Next.js project?

A build-test-verify workflow prevents silent quality gaps by requiring Next.js projects to pass code structure checks, automated testing, accessibility validation, and real browser visual verification before declaring work done.

What is a deterministic build workflow in frontend engineering?

A deterministic build workflow in frontend engineering enforces strict standards for code structure and testing strategy, ensuring consistent builds and preventing silent quality gaps before deployment.

Does this build-test-verify workflow support plain HTML and Vite projects?

Yes, the build-test-verify workflow supports plain HTML/CSS and Vite projects alongside Next.js, guiding implementation, testing, accessibility, and performance checks for each framework.

How do I check accessibility and responsive design before deploying a web app?

To check accessibility and responsive design before deploying, follow a strict workflow that guides developers through specific testing strategies and performance checks to ensure browser-visible quality.

Why do I need visual verification in a real browser for frontend projects?

Visual verification in a real browser is needed to prevent silent quality gaps, ensuring your frontend project is accessible, responsive, and visually correct before declaring work done.

What is the best way to prevent silent quality gaps in frontend deployments?

The best way to prevent silent quality gaps is enforcing a strict build-test-verify lifecycle that applies standards for code structure, testing, accessibility, responsive design, and deterministic builds.