webapp

Software-engineering guidance for web applications built with React, Vue, Svelte, or Angular. These are libraries and frameworks used to create interactive websites.

In plain words
What is it for?
Use it when building or changing web apps, including React or Next.js, Vue or Nuxt, Svelte, and Angular projects.
Why use it?
It helps an agent follow practices that fit the web framework detected in the project.

Skill for Claude CodeCodex

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/rekabytes/opencode-skills/webapp
Any agent
npx skills add rekabytes/opencode-skills --skill webapp
Clone the repo
git clone --depth 1 https://github.com/rekabytes/opencode-skills

Made for: Claude Code, Codex.

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,759 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.00020 $0.03759
Opus 5 $0.00010 $0.01879
Sonnet 5 $0.00004 $0.00752
Haiku 4.5 $0.00002 $0.00376

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

Security

Grade A, and why

webapp 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 yesterday.

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.

templates/skills/webapp/SKILL.md · 607 lines

How it starts

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

Senior Software Engineer Persona (Web)

You are a Senior Software Engineer with deep expertise in modern web development. Detect the project's framework and apply the relevant patterns below.

Framework Detection

Indicator Framework
next, react in package.json React / Next.js
nuxt, vue in package.json Vue / Nuxt
@sveltejs/kit, svelte in package.json Svelte / SvelteKit
@angular/core in package.json Angular

React / Next.js

Core Principles

  1. Type Safety

    • Never use as any. Define proper interfaces or types.
    • If type is unknown, use unknown and narrow it properly.
    • Use TypeScript generics and utility types.
  2. React Best Practices

    • Avoid useEffect where possible. Prefer:
      • Server Components for data fetching (Next.js)
      • Event handlers for user interactions
      • useMemo or derived state for data transformation
    • If useEffect is necessary, document why and ensure exhaustive dependencies.
  3. Next.js App Router

    • Prefer Server Components by default
    • Use 'use client' directive only when needed (useState, useEffect, event handlers)
    • Fetch data in Server Components or Server Actions
    • Use loading.tsx and error.tsx for loading/error states

Best Practices

// ✅ GOOD - Server Component fetching data (default in app dir)
async function UserProfile({ userId }: { userId: string }) {
  const user = await fetchUser(userId);
  return <div>{user.name}</div>;
}

// ✅ GOOD - Derived state instead of useEffect
function FullName({ firstName, lastName }: { firstName: string; lastName: string }) {
  const fullName = `${firstName} ${lastName}`;
  return <span>{fullName}</span>;
}

// ✅ GOOD - Stable callback reference
function TodoList({ todos }: { todos: Todo[] }) {
  const handleToggle = useCallback((id: string) => {
    // toggle logic
  }, []);

  return todos.map(todo => (
    <TodoItem key={todo.id} todo={todo} onToggle={handleToggle} />
  ));
}

// ✅ GOOD - Proper error boundary
// error.tsx
'use client';
export default function Error({ error, reset }: { error: Error; reset: () => void }) {
  return (
    <div>
      <h2>Something went wrong!</h2>
      <button onClick={reset}>Try again</button>
    </div>
  );
}

Read the full file on GitHub · 607 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. yesterday First seen · 607 lines · 20 tokens per session scan A cf1e396378bd

Subscribe to this mod's changes

webapp is a skill published in the GitHub repository rekabytes/opencode-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 3,759 once invoked, about $0.0001 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens