coder

Implement frontend features with unit tests and linting before handoff.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Athos1972/pundo_frontend --skill coder-athos1972
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coder
Source: https://github.com/Athos1972/pundo_frontend/tree/main/.claude/skills/coder
Command: npx skills add https://github.com/Athos1972/pundo_frontend --skill coder-athos1972

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides and enforces a disciplined frontend development workflow by ensuring feature implementations in pundo_frontend are paired with thorough unit tests, linting, and a structured handoff to end-to-end testers.

Core Features & Use Cases

  • Unit-test driven development: implement TypeScript/React/Next.js changes with accompanying Vitest tests.
  • Quality gate enforcement: TS error checks and ESLint checks run before handoff to QA.
  • Structured handoff: clear handoff to the /e2e-tester with a defined, repeatable process for end-to-end validation.

Quick Start

Describe the feature you want implemented and I will scaffold the code changes and tests.

Frequently Asked Questions about coder

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

FAQPage Schema
How do I implement React and Next.js features with automatic Vitest unit tests?

To implement React and Next.js features with Vitest unit tests, describe the desired feature and the skill scaffolds the TypeScript code changes alongside the required test coverage. It enforces TypeScript correctness and ESLint compliance before completing the feature implementation.

Can I use this for TypeScript refactoring and bug fixes?

Yes, you can use this for TypeScript refactoring and bug fixes. It applies a structured workflow to code changes, component enhancements, and refactoring tasks by generating the modified code and pairing it with Vitest unit tests to verify the fixes.

What is the best way to enforce quality gates before end-to-end validation?

The best way to enforce quality gates before end-to-end validation is to run TypeScript error checks and ESLint compliance checks automatically. This skill enforces these gates after unit testing and provides a deterministic handoff to the end-to-end tester.

Does this workflow support automated handoff to an e2e-tester?

Yes, this workflow supports an automated handoff to an e2e-tester. After successful unit test verification, TypeScript correctness checks, and ESLint compliance, it executes a structured and deterministic handoff process for end-to-end validation.

How do I scaffold frontend code changes with linting and type checks?

To scaffold frontend code changes with linting and type checks, provide a description of the required feature or fix. The skill generates the implementation and automatically runs ESLint and TypeScript checks to ensure code quality before handoff.

What are the limitations of using a unit-test driven development workflow?

A limitation of this unit-test driven development workflow is its specific focus on the frontend stack, applying exclusively to TypeScript, React, Next.js, and Vitest environments. It handles unit testing and handoffs but does not execute the end-to-end validation itself.