frontend-development_skill

This skill helps you choose and implement frontend patterns across React, Vue, Svelte, and Angular for faster, scalable UIs.
  • Python

12

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill samhvw8/dotfiles --skill frontend-development

  • SKILL.md30.6 KB

Overview

This skill provides practical guidance and actionable patterns for building modern frontend applications across React, Vue 3, Svelte 5, and Angular. It focuses on component and feature structure, TypeScript standards, routing, data fetching, state management, and performance optimization. Use it to create, refactor, or optimize components, pages, and full features with framework-specific best practices.

How this skill works

The skill inspects common frontend tasks and prescribes concrete patterns: component checklists, feature folder layouts, import aliases, and data-fetching strategies (for example useSuspenseQuery or SvelteKit load). It recommends framework idioms—hooks for React, Composition API/Pinia for Vue, runes and SvelteKit for Svelte, and signals/standalone components for Angular—and gives performance and TypeScript rules that apply across frameworks. Actionable steps include lazy loading, Suspense boundaries, API service layers, and cache invalidation patterns.

When to use it

  • Creating new components or pages in React, Vue, Svelte, or Angular
  • Building a new feature with a clear folder and API service structure
  • Implementing or improving state management (Pinia, Zustand, stores, signals)
  • Setting up routing and lazy-loaded routes (TanStack Router, Vue Router, SvelteKit, Angular Router)
  • Implementing data fetching and caching (TanStack Query, composables, load functions)
  • Optimizing performance, bundle size, and CLS prevention

Best practices

  • Use TypeScript strict mode, explicit return types, and avoid any for safety
  • Lazy load heavy components and lazy-load routes; wrap in Suspense or equivalent to avoid layout shifts
  • Organize features with api/, components/, hooks/, helpers/, types/ subfolders and export a public index
  • Prefer framework idioms: hooks/composables/runes/signals and framework-native routing patterns
  • Keep components small and focused; use memoization (useMemo/useCallback/derived values) for expensive work
  • Choose styles by size: inline/sx for <100 lines, separate style files for larger components

Example use cases

  • Create a lazily loaded React feature using useSuspenseQuery, SuspenseLoader, and a feature-level API client
  • Migrate a Vue component to Composition API with Pinia state and a composable for data fetching
  • Build a small SvelteKit page using runes for reactivity and a load function for server-side data
  • Implement an Angular standalone component with signals, OnPush change detection, and a service-based API layer
  • Refactor a large component into smaller presentational units and a feature folder with types, hooks, and helpers

FAQ

Choose based on team skill, project size, and performance needs: large enterprise → React or Angular, progressive/medium apps → Vue or React, small/performance-critical apps → Svelte.

How do I avoid layout shifts while loading data?

Never return early with loading spinners; use Suspense boundaries or equivalent loading wrappers to preserve layout and prevent CLS.

What is the recommended data fetching pattern for React?

Prefer useSuspenseQuery with Suspense boundaries and a cache-first approach; centralize API calls in a feature-level api service.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
frontend-development skill by samhvw8/dotfiles | VeilStrat