frontend-engineer

Enforces build-test-verify workflow for web projects with browser-based visual verification.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill frontend-engineer-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-engineer
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/container/skills/frontend-engineer
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill frontend-engineer-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend work often gets declared finished without real verification, leading to broken layouts, console errors, and unresponsive pages reaching production. This Skill enforces a disciplined build-test-verify workflow so every web project is actually built, tested, and visually confirmed in a real browser before being called done. ## Core Features & Use Cases - Structured Build Workflow: Enforces a fixed sequence of understanding the codebase, writing TypeScript/React code following best practices, building with pnpm, and fixing all errors before deploying. - Mandatory Visual Verification: Uses agent-browser to screenshot pages at desktop and tablet widths, check console errors, and detect layout overflow before any deploy. - Production Verification with Vercel: Deploys via the Vercel CLI and re-verifies the live URL with screenshots after deployment. - Use Case: Ask the agent to build a landing page with Next.js and Tailwind; it will write the code, run the build, screenshot the result at multiple viewport sizes, fix any visual issues, and only then deploy to Vercel. ## Quick Start Build a responsive landing page with Next.js, verify it visually in a browser at desktop and tablet widths, then deploy it to Vercel.

Frequently Asked Questions about frontend-engineer

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

FAQPage Schema
How do I verify a website visually before deploying?

Start the dev server, then use agent-browser to open the local URL and capture screenshots at desktop (1280px) and tablet (768px) widths. Also check the console for errors and confirm there is no horizontal overflow before deploying.

How to deploy a Next.js app to Vercel from the command line?

Run vercel deploy --yes --prod with your token and the project directory after the build passes. Afterwards, open the live URL in a browser and screenshot it to confirm the production site matches local behavior.

What React practices reduce bundle size and improve performance?

Import directly from source files instead of barrel files, use optimizePackageImports for icon libraries, dynamically import non-critical components, and prefer Server Components with minimal use client boundaries. Use Promise.all for independent async work to avoid waterfalls.

Does this workflow work with plain HTML and CSS projects?

Yes, the same build-test-verify sequence applies to plain HTML/CSS pages, Vite SPAs, and full Next.js apps. The tooling choice is made per project, but visual verification in a real browser is mandatory in all cases.

Why does my build pass but the site still looks broken?

A passing build only checks compilation, not rendering. Layout overflow, missing images, and contrast issues only appear visually, which is why screenshots at multiple viewport sizes and console error checks are required before declaring work done.