frontend-checklist

Enforce Vue, JS, and TS frontend code quality with checklists for reviews.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill frontend-checklist-bingeli1379
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-checklist
Source: https://github.com/bingeli1379/eli-claude-marketplace/tree/main/plugins/eureka-sdd/skills/frontend-checklist
Command: npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill frontend-checklist-bingeli1379

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a formal, repeatable set of frontend coding principles to enforce consistent patterns across Vue/JS/TS projects, reducing bugs and code smells.

Core Features & Use Cases

  • Enforces reactivity rules (e.g. correct use of refs and reactive values) and proper Vue component structure.
  • Guides proper Composition API usage, SFC layout, and naming conventions for maintainable code.
  • Assists code reviews and onboarding by codifying best practices into a reusable standard.

Quick Start

Review each frontend change against the checklist before merging a Vue/JS/TS task.

Frequently Asked Questions about frontend-checklist

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

FAQPage Schema
How do I enforce Vue and TypeScript frontend code quality during code reviews?

To enforce frontend code quality during code reviews, apply a formal checklist validating Vue SFC structure, Composition API usage, TypeScript typing, and reactivity rules. This ensures consistent patterns across feature development and component refactoring.

What are the best practices for Vue Composition API reactivity and SFC structure?

Best practices for Vue Composition API reactivity and SFC structure mandate correct use of refs and reactive values, proper SFC layout, and consistent naming conventions. Codifying these principles reduces bugs and code smells across Vue projects.

Can I use this frontend checklist for both JavaScript and TypeScript projects?

Yes, this frontend checklist supports both JavaScript and TypeScript projects. It enforces coding principles and best practices across Vue, JS, and TS environments to maintain consistent code quality during feature development and component refactoring.

Does this frontend checklist require any specific dependencies or environment setup?

No specific dependencies or environment setup are required. The checklist applies as a formal, repeatable standard during Vue, JS, and TS feature development, component refactoring, and code reviews to validate adherence to frontend best practices.

Why should I use a formal checklist for frontend code consistency instead of ad-hoc reviews?

A formal frontend checklist provides a repeatable set of coding principles to enforce consistent patterns, unlike ad-hoc reviews. It codifies best practices for reactivity and SFC structure into a reusable standard, reducing bugs and code smells during onboarding.

What limitations exist when applying a strict checklist to Vue component refactoring?

The checklist focuses strictly on codifying Vue, JS, and TS best practices for reactivity, Composition API, and SFC structure. It does not handle backend logic or non-Vue frameworks, serving only as a post-implementation validation standard for frontend changes.