frontend-foundations

Establish frontend quality foundations for new React, Vue, or Svelte projects.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Ferreira-Jefferson/j-skills --skill frontend-foundations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-foundations
Source: https://github.com/Ferreira-Jefferson/j-skills/tree/main/frontend-foundations
Command: npx skills add https://github.com/Ferreira-Jefferson/j-skills --skill frontend-foundations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Estabelece fundações de qualidade para projetos frontend desde o começo. Princípios, estrutura de diretórios, regras de estilo, estratégia de testes, templates acionáveis e anti-padrões a evitar. Invocar ao iniciar novo projeto frontend, ao auditar um existente, ao pedir "boas práticas React/Vue/Svelte", "como organizar frontend", "estabelecer arquitetura frontend", "setup de projeto", ou antes de escrever a primeira task de UI de uma feature.

Core Features & Use Cases

  • Fornece um guia operacional para iniciar projetos com disciplina, auditar codebases existentes e orientar governance de frontend.
  • Inclui templates prontos, princípios estruturais, tokens de design e padrões de testes para manter qualidade e consistência em equipes.
  • Disponibiliza um protocolo de auditoria e templates para evoluir código sem alterar a stack.

Quick Start

Invocar frontend-foundations no início de um projeto para aplicar fundamentos de qualidade e templates prontos.

Frequently Asked Questions about frontend-foundations

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

FAQPage Schema
How do I establish frontend architecture and quality foundations for a new React or Vue project?

To establish frontend architecture foundations for a new React or Vue project, apply a documented directory structure, design tokens, and testing strategy templates. This enforces structural principles, style rules, and anti-pattern avoidance from the start.

What is the best way to audit an existing frontend codebase for best practices?

Auditing an existing frontend codebase for best practices involves running a repeatable audit workflow to evaluate directory structure, design tokens, and testing patterns. This protocol identifies architecture gaps and provides actionable templates to evolve code without altering the stack.

How do I set up design tokens and a testing strategy when starting a new Svelte project?

Setting up design tokens and a testing strategy for a new Svelte project requires applying predefined structural templates and quality rules. This ensures consistent UI architecture, repeatable testing patterns, and documented style governance from the first feature task.

Can I enforce frontend directory structure and anti-pattern rules in an existing codebase?

You can enforce frontend directory structure and anti-pattern rules in an existing codebase by executing an audit workflow. It evaluates current architecture against structural principles and provides actionable templates to align the codebase without changing its underlying stack.

When do I need to establish frontend quality foundations before writing UI features?

You need to establish frontend quality foundations before writing the first UI feature task to ensure structural discipline. Applying design tokens, testing strategies, and documented directory structures early prevents architectural drift and maintains codebase consistency.