frontend-engineer Skill
Pro frontend engineering discipline. Enforces build-test-verify workflow for every web project. Never declare done until the site is built, tested, responsive, accessible, and visually verified in a real browser. Use alongside vercel-cli for production-quality deployments. Published by microsoft in amplifier-app-nanoclaw.
What is frontend-engineer Skill?
Pro frontend engineering discipline. Enforces build-test-verify workflow for every web project. Never declare done until the site is built, tested, responsive, accessible, and visually verified in a real browser. Use alongside vercel-cli for production-quality deployments. Published by microsoft in amplifier-app-nanoclaw. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Testing
- Design and media
- Writing
- Research
Technical details
- Install or run with Copy skill directory
When to use frontend-engineer Skill
- Use it for browser automation.
- Use it for testing.
- Use it for design and media.
- Use it for writing.
- Use it for research.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-nanoclaw
- Skill file: container/skills/frontend-engineer/SKILL.md
What it does
Pro frontend engineering discipline. Enforces build-test-verify workflow for every web project. Never declare done until the site is built, tested, responsive, accessible, and visually verified in a real browser. Use alongside vercel-cli for production-quality deployments.
Skill instructions
Frontend Engineer You are a senior frontend engineer. You build production-quality websites and web applications. You do not cut corners. You do not declare work done until everything is tested and working. Core Rule Never say "done" until you have visually verified the result in a real browser. Screenshots are your proof. If you can't take a screenshot, you're not done. Build Workflow Every frontend task follows this sequence. Do not skip steps. 1. Understand Before Coding - For existing projects: read package.json, check existing patterns, components, and design tokens before changing anything - For new projects: pick the right tool (Next.js for full apps, Vite for SPAs, plain HTML/CSS for simple pages) - Search the codebase before creating any new component. If an existing component does 80% of what you need, extend it with props. If two components share the same pattern, extract a shared component. 2. Write Quality Code TypeScript: - Use TypeScript for all code - Avoid any — prefer
Explore related resources
Frequently asked questions
What is frontend-engineer?
frontend-engineer is a open-source AI agent skill with Copy skill directory. Pro frontend engineering discipline. Enforces build-test-verify workflow for every web project.
Who is frontend-engineer best for?
frontend-engineer is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows, design and media workflows.
How do I install frontend-engineer?
Install or run frontend-engineer using Copy skill directory. Check frontend-engineer for the latest setup command.
Is frontend-engineer actively maintained?
frontend-engineer may need a closer maintenance check before production use.
Auto-fetched from GitHub.
