frontend-engineer

Enforce build, test, and visual verification workflows for web applications.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill frontend-engineer-vincentchong123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-engineer
Source: https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy/tree/main/container/skills/frontend-engineer
Command: npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill frontend-engineer-vincentchong123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the common pitfalls of frontend development by enforcing a rigorous, disciplined workflow that ensures every web project is fully tested, responsive, and production-ready before deployment.

Core Features & Use Cases

  • Visual Verification: Mandates real-browser testing and screenshot proofing to ensure UI integrity.
  • Build Integrity: Enforces strict TypeScript, semantic HTML, and accessibility standards to prevent broken production builds.
  • Use Case: Use this skill when building a new landing page or feature to ensure it meets professional standards for responsiveness, accessibility, and performance without manual oversight.

Quick Start

Ask the frontend engineer to build the new dashboard component and verify it across desktop and tablet viewports.

Frequently Asked Questions about frontend-engineer

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

FAQPage Schema
How do I automate visual verification for React components during web development?

Automate visual verification by integrating real-browser testing and screenshot proofing into your web development workflow to ensure UI integrity. This process validates component architecture across desktop and tablet viewports without manual oversight.

How do I enforce TypeScript and semantic HTML standards to prevent broken production builds?

Enforce TypeScript and semantic HTML standards by applying strict build integrity checks before production deployment. This ensures high-quality, accessible, and error-free web interfaces while preventing broken builds from reaching deployment.

What is the best way to integrate automated browser testing into a frontend deployment workflow?

The best way to integrate automated browser testing is to establish a disciplined workflow connecting build, test, and visual verification phases. This operates across the full development lifecycle from initial component architecture to production deployment.

Do I need strict TypeScript compliance to use automated frontend build and verification workflows?

Yes, strict TypeScript compliance is required to execute automated frontend build and verification workflows. Adherence to TypeScript, semantic HTML, and responsive design principles ensures accessible and error-free web interfaces before deployment.

Can I verify responsive design across different viewports without manual UI testing?

Yes, you can verify responsive design automatically by mandating real-browser testing and screenshot proofing. This visual verification checks UI integrity across desktop and tablet viewports to meet professional accessibility and performance standards.

When should I use a strict frontend engineering discipline workflow for web applications?

Use a strict frontend engineering discipline workflow when building new landing pages or features to ensure they meet professional standards for responsiveness, accessibility, and performance. It eliminates common pitfalls by ensuring projects are fully tested and production-ready.