Jarvis: Skill for Claude Code

.claude/skills/senior-frontend/SKILL.md

senior-frontend is a skill for Claude Code from Szesnasty/Jarvis. It costs 53 tokens per session (777 once invoked), scanned A, original, Apache-2.0.

A guide for building and reviewing frontend applications—the part of software users see and interact with—using React, Next.js, TypeScript, and Tailwind CSS.

In plain words
What is it for?
Use it to develop React or Next.js interfaces, create reusable components, manage application data, improve loading and rendering performance, or review frontend code.
Why use it?
It provides practical rules for organizing components, managing state, choosing types, and improving performance without adding unnecessary complexity.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Szesnasty/Jarvis's own configuration. It tells Claude Code how to work on Jarvis itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Jarvis configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Szesnasty/Jarvis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Szesnasty/Jarvis/main/.claude/skills/senior-frontend/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Szesnasty/Jarvis

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 senior-frontend

README.md
[![agentmods](https://agentmods.dev/badge/skills/szesnasty/jarvis/senior-frontend/github.svg)](https://agentmods.dev/skills/szesnasty/jarvis/senior-frontend)
Your own site
<a href="https://agentmods.dev/skills/szesnasty/jarvis/senior-frontend"><img src="https://agentmods.dev/badge/skills/szesnasty/jarvis/senior-frontend/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 senior-frontend

Your own site · 80×15
<a href="https://agentmods.dev/skills/szesnasty/jarvis/senior-frontend"><img src="https://agentmods.dev/badge/skills/szesnasty/jarvis/senior-frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 777 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.00053 $0.00777
Opus 5 $0.00026 $0.00388
Sonnet 5 $0.00011 $0.00155
Haiku 4.5 $0.00005 $0.00078

Measured 11d ago against content hash 53addf01bda4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

senior-frontend 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 11d 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.

.claude/skills/senior-frontend/SKILL.md · 82 lines

How it starts

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

Frontend Development

Component Design

Structure

  • One component per file, named to match the export
  • Co-locate styles, tests, and types with the component
  • Extract shared components only when used in 3+ places
  • Keep components under 200 lines — split when they do too much

Props

  • Use TypeScript interfaces for all props — no any
  • Prefer specific types over broad ones: "sm" | "md" | "lg" not string
  • Destructure props in the function signature for readability
  • Default optional props at the destructuring site, not with defaultProps

State Management

  • Local state first (useState), lift only when needed
  • Use useReducer for complex state with multiple related fields
  • Context for truly global state (theme, auth, locale) — not for prop drilling avoidance
  • External state libraries (Zustand, Jotai) for server cache or cross-component state
  • Never put derived data in state — compute it

Performance

Rendering

  • Avoid unnecessary re-renders: React.memo only when measured, not preventively
  • Move expensive computations to useMemo — but measure first
  • Stabilize callback references with useCallback when passed to memoized children
  • Use key props correctly — stable IDs, not array indices for dynamic lists

Loading

  • Lazy-load routes and heavy components with React.lazy / next/dynamic
  • Optimize images: proper sizes, modern formats (WebP/AVIF), lazy loading
  • Minimize bundle size — check imports, avoid barrel file re-exports in libraries
  • Prefetch critical data, defer non-critical requests

Next.js Specific

  • Use Server Components by default — add "use client" only when needed
  • Fetch data in Server Components, not in client useEffect
  • Use loading.tsx and error.tsx for route-level loading/error states
  • Leverage ISR or static generation for content that doesn't change per-request

Styling

Tailwind CSS

  • Extract repeated patterns into component abstractions, not @apply classes
  • Use design tokens via tailwind.config — don't hardcode colors or spacing
  • Keep className strings readable — break to multiple lines if long
  • Use cn() or clsx() for conditional classes

Read the full file on GitHub · 82 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. 11d ago First seen · 82 lines · 53 tokens per session scan A 53addf01bda4

Subscribe to this mod's changes

senior-frontend is a skill published in the GitHub repository Szesnasty/Jarvis (10 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 777 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

open-design-homepage

A pixel-faithful, self-contained mirror of the live open-design.ai homepage — an interactive React Three Fiber / Next.js hero with a real-time 3D wordmark, sticker collage, variable fonts, and scroll-driven motion. First-party showcase of the visual ceiling for interactive web marketing surfaces.

nexu-io/open-design · 65 tokens

sn-motion-html

Build continuous-shot motion-driven HTML stories from a subject or narrative, including research, story structure, consistent AI stills, Seedance scene and connector clips, interface styling, media normalization, and browser QA. Use for immersive journeys, timelines, product stories, fictional worlds, or other…

OpenSenseNova/SenseNova-Skills · 84 tokens

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

ThinkInAIXYZ/deepchat · 64 tokens

web-design-engineer

Build or redesign polished browser-rendered visual artifacts with HTML/CSS/JavaScript/React: pages, dashboards, prototypes, slide decks, animations, UI mockups, and data visualizations. Use for visual front-end creation, design-system exploration, design critique, or explicit browser acceptance / QA of a web artifact.…

ConardLi/garden-skills · 96 tokens

byted-util-vite-react-tailwind

A setup guide for building frontend projects with Vite, React, Tailwind CSS, TypeScript, and Lucide icons.

bytedance/agentkit-samples · 64 tokens

panel-app-react-vite-creator

Create or update an engineering-style NextClaw Panel component with pnpm, Vite, React, TypeScript, and Tailwind CSS, then build it into a static .panel directory inside a schema v2 package or an explicitly loose workspace Panel. Use for modern, reusable, complex, Agent-powered, typed Panel interfaces.

Peiiii/nextclaw · 73 tokens