frontend-dev-guidelines

frontend-dev-guidelines is a skill for Claude Code, Codex from diet103/claude-code-infrastructure-showcase. It costs 76 tokens per session (2,788 once invoked), scanned A, original, MIT.

A set of coding guidelines for building React and TypeScript front ends, including component structure, data loading, routing, styling, and performance. It is written for React 18 with MUI v7 and TanStack tools.

In plain words
What is it for?
Use it when creating components, pages, or features; fetching data; setting up routes; styling with MUI; improving performance; or applying TypeScript practices.
Why use it?
It gives developers consistent decisions for organizing and implementing front-end code, reducing guesswork and common performance or maintenance problems.

Skill for Claude CodeCodex

About the project

Claude Code Infrastructure Showcase is a reference library of configuration patterns for Claude Code, including skills, hooks, agents, and commands that shape how the coding agent works. It helps developers organize and automate Claude Code in their own projects, especially larger TypeScript codebases. The catalogue entries are examples of infrastructure that users can copy into their projects.

diet103/claude-code-infrastructure-showcase · 10,014 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/diet103/claude-code-infrastructure-showcase/frontend-dev-guidelines
Any agent
npx skills add diet103/claude-code-infrastructure-showcase --skill frontend-dev-guidelines
Clone the repo
git clone --depth 1 https://github.com/diet103/claude-code-infrastructure-showcase

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for frontend-dev-guidelines

README.md
[![agentmods](https://agentmods.dev/badge/skills/diet103/claude-code-infrastructure-showcase/frontend-dev-guidelines.svg)](https://agentmods.dev/skills/diet103/claude-code-infrastructure-showcase/frontend-dev-guidelines)
Your own site
<a href="https://agentmods.dev/skills/diet103/claude-code-infrastructure-showcase/frontend-dev-guidelines"><img src="https://agentmods.dev/badge/skills/diet103/claude-code-infrastructure-showcase/frontend-dev-guidelines.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,788 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00076 $0.02788
Opus 5 $0.00038 $0.01394
Sonnet 5 $0.00015 $0.00558
Haiku 4.5 $0.00008 $0.00279

Measured 5d ago against content hash c5e42323a0bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

frontend-dev-guidelines scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

5 near-identical copies found in the catalogue:

.agents/skills/frontend-dev-guidelines/SKILL.md · 401 lines

How it starts

The opening of the file, as written. The whole thing — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Frontend Development Guidelines

Purpose

Comprehensive guide for modern React development, emphasizing Suspense-based data fetching, lazy loading, proper file organization, and performance optimization.

Written for React 18 + TypeScript + MUI v7 + TanStack Router/Query. Different stack? Adapt the principles - see CLAUDE_INTEGRATION_GUIDE.md in the repo root.

When to Use This Skill

  • Creating new components or pages
  • Building new features
  • Fetching data with TanStack Query
  • Setting up routing with TanStack Router
  • Styling components with MUI v7
  • Performance optimization
  • Organizing frontend code
  • TypeScript best practices

Quick Start

New Component Checklist

Creating a component? Follow this checklist:

  • Use React.FC<Props> pattern with TypeScript
  • Lazy load if heavy component: React.lazy(() => import())
  • Wrap in <SuspenseLoader> for loading states
  • Use useSuspenseQuery for data fetching
  • Import aliases: @/, ~types, ~components, ~features
  • Styles: Inline if <100 lines, separate file if >100 lines
  • Use useCallback for event handlers passed to children
  • Default export at bottom
  • No early returns with loading spinners
  • Use useMuiSnackbar for user notifications

New Feature Checklist

Creating a feature? Set up this structure:

  • Create features/{feature-name}/ directory
  • Create subdirectories: api/, components/, hooks/, helpers/, types/
  • Create API service file: api/{feature}Api.ts
  • Set up TypeScript types in types/
  • Create route in routes/{feature-name}/index.tsx
  • Lazy load feature components
  • Use Suspense boundaries
  • Export public API from feature index.ts

Import Aliases Quick Reference

Alias Resolves To Example
@/ src/ import { apiClient } from '@/lib/apiClient'
~types src/types import type { User } from '~types/user'
~components src/components import { SuspenseLoader } from '~components/SuspenseLoader'
~features src/features import { authApi } from '~features/auth'

Read the full file on GitHub · 401 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 401 lines · 76 tokens per session scan A c5e42323a0bf

Subscribe to this mod's changes

frontend-dev-guidelines is a skill published in the GitHub repository diet103/claude-code-infrastructure-showcase (10,014 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 2,788 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

frontend-conventions

Coding conventions, architecture patterns, and testing rules for the SkillHub React frontend. Ensures agents follow Feature-Sliced Design and use the generated OpenAPI types.

iflytek/skillhub · 36 tokens

fast-typescript-check

Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…

internet-development/www-sacred · 84 tokens

xstate-store

XState Store (@xstate/store v4) event-driven state for TypeScript apps. Use when creating a store with createStore or createStoreLogic, writing transitions and enqueue effects, declaring Standard Schema contracts, wiring selectors or atoms, adding the persist, undo-redo, reset, or validateSchemas extensions, binding a…

compozy/compozy · 123 tokens

typescript-react

Apply, review, and explain React conventions from the TypeScript Style Guide. Use automatically for TypeScript and TSX tasks involving prop-derived state, prop typing, component responsibilities, data flow, compound components, or client and server state.

mkosir/typescript-style-guide · 50 tokens

electron-dev

Electron desktop apps with React, TypeScript, and Vite. Use for IPC, window/tray, PTY terminals, WebRTC, and packaging.

jamditis/claude-skills-journalism · 34 tokens

frontend-module-standards

Enforce this repository's React and TypeScript frontend module architecture standards. Use whenever creating, modifying, refactoring, or reviewing frontend code under src/, including feature modules, components, hooks, contexts, shared UI, API access, state, utilities, and frontend tests. Do not apply these rules to…

siteboon/claudecodeui · 82 tokens