frontend-fundamentals

frontend-fundamentals is a skill for Claude Code from kouroshez/coding-os. It costs 68 tokens per session (2,890 once invoked), scanned A, original, Apache-2.0.

A guide to common patterns for building frontend interfaces in frameworks such as React, Vue, Svelte, and Solid. It covers loading, error, and empty states, accessibility, performance, search visibility, hydration, and state management.

In plain words
What is it for?
Use it when writing or changing UI components, data-fetching screens, client/server code, navigation, accessibility behavior, performance work, SEO basics, or application state.
Why use it?
It helps prevent screens that go blank during a request, hide errors, mishandle empty data, or behave differently between server and browser. It also provides baseline practices for usable and maintainable interfaces.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when writing or changing UI components, data-fetching screens, client/server code, navigation, accessibility behavior, performance work, SEO basics, or application state.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kouroshez/coding-os/frontend-fundamentals
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.

Any agent
npx skills add kouroshez/coding-os --skill frontend-fundamentals
Clone the repo
git clone --depth 1 https://github.com/kouroshez/coding-os

Made for: Claude Code.

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-fundamentals

README.md
[![agentmods](https://agentmods.dev/badge/skills/kouroshez/coding-os/frontend-fundamentals/github.svg)](https://agentmods.dev/skills/kouroshez/coding-os/frontend-fundamentals)
Your own site
<a href="https://agentmods.dev/skills/kouroshez/coding-os/frontend-fundamentals"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/frontend-fundamentals/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for frontend-fundamentals

Your own site · 80×15
<a href="https://agentmods.dev/skills/kouroshez/coding-os/frontend-fundamentals"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/frontend-fundamentals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,890 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00068 $0.02890
Opus 5 $0.00034 $0.01445
Sonnet 5 $0.00014 $0.00578
Haiku 4.5 $0.00007 $0.00289

Measured 8d ago against content hash 5438516ff5d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

frontend-fundamentals 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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/check_frontend.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

src/core/skills/frontend-fundamentals/SKILL.md · 214 lines

How it starts

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

Frontend Fundamentals — Stack-Agnostic UI Patterns

Universal guidance for every component-based UI framework: React, React Native, Vue, Svelte, Solid. Framework-specific layering (Next.js App Router, React Native navigation, Vue composition API) lives in the stack-specific skill that depends_on: [frontend-fundamentals].

Loaded automatically when enforce-skill.sh routes a file under frontend/ that matches a stack skill.

0. Every async UI is three-state

Every screen or section that fetches data MUST explicitly handle three states. Missing any of them is a bug:

State Required UI
Loading skeleton or spinner; indication of progress
Error actionable message + retry affordance; never a blank screen
Empty explains why it's empty + suggests next action; never an ambiguous zero rows

A fourth state — stale/refreshing while data exists — is a common polish item. Render the previous data with a subtle loading indicator; don't blank the UI.

Anti-pattern: {data && <List data={data} />}. This silently hides error AND empty AND loading behind a single falsy check.

1. Server components vs. client components (React 19+ / Next 15+)

Default everything to server components. Convert to client only when one of these is present:

  • Interactive state (useState, useReducer, form state).
  • Event handlers (onClick, onChange, onSubmit).
  • Browser-only APIs (window, localStorage, navigator, document, IntersectionObserver).
  • Hooks that require a client (useEffect, useLayoutEffect, most third-party hooks).

Server components don't ship JS to the browser and can fetch directly. This is the single biggest first-load perf win in modern React. A component that's "use client" without a reason is accidental bundle bloat.

2. Hydration safety

Anything whose output differs between the first server render and the first client render causes a hydration mismatch. Common culprits:

  • new Date(), Math.random() at top level of a client component.
  • window.matchMedia(...) defaulting to different value.
  • Reading localStorage synchronously during render.

Read the full file on GitHub · 214 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 214 lines · 68 tokens per session scan A 5438516ff5d1

Subscribe to this mod's changes

frontend-fundamentals is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 2,890 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

graph-mutation-plan

Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.

potpie-ai/potpie · 51 tokens

potpie-cli

Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.

potpie-ai/potpie · 50 tokens

potpie-infra-architecture

Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.

potpie-ai/potpie · 43 tokens

screenshot-studio

Regenerate the Pisper product screenshots under docs/shots/ against the current UI. Starts an isolated dev instance, seeds fictional demo data through the real runtime APIs, captures every referenced page at the exact 2558x1380 asset size, and replaces the files. Use only when the user asks to refresh product…

ling-kong-ran/pisper · 80 tokens

css-debug

Use this skill to diagnose CSS and frontend layout issues such as positioning, overflow clipping, Tailwind class conflicts, z-index stacking, and React rendering visibility problems.

majiayu000/spellbook · 35 tokens

ring:validating-ux-completeness

Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer…

LerianStudio/ring · 113 tokens