web-expert

web-expert is a cursor rule for Cursor from iHildy/jules-task-queue. It costs 719 tokens per session, scanned A, original, MIT.

A set of project coding rules for TypeScript and React web applications, including how to build components, style pages, validate APIs, and run commands.

In plain words
What is it for?
It is for developing Next.js and React interfaces, TypeScript APIs, database-backed features, styling, animations, and unit tests.
Why use it?
It gives agents consistent technical and naming rules, reducing mismatched code and avoidable type or formatting errors.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It is for developing Next.js and React interfaces, TypeScript APIs, database-backed features, styling, animations, and unit tests.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ihildy/jules-task-queue/web-expert
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.

Clone the repo
git clone --depth 1 https://github.com/iHildy/jules-task-queue

Made for: Cursor.

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 web-expert

README.md
[![agentmods](https://agentmods.dev/badge/rules/ihildy/jules-task-queue/web-expert/github.svg)](https://agentmods.dev/rules/ihildy/jules-task-queue/web-expert)
Your own site
<a href="https://agentmods.dev/rules/ihildy/jules-task-queue/web-expert"><img src="https://agentmods.dev/badge/rules/ihildy/jules-task-queue/web-expert/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 web-expert

Your own site · 80×15
<a href="https://agentmods.dev/rules/ihildy/jules-task-queue/web-expert"><img src="https://agentmods.dev/badge/rules/ihildy/jules-task-queue/web-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 719 This file is loaded in full into every session.
When invoked 719 The same file — it is already loaded in full.
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.00719 $0.00719
Opus 5.5 $0.00288 $0.00288
Sonnet 5.5 $0.00144 $0.00144
Haiku 4.5 $0.00072 $0.00072

Measured 13d ago against content hash 84a69fc21b3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

web-expert 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 13d 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.

.cursor/rules/web-expert.mdc · 78 lines

How it starts

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

This rule provides standards for frontend components, ensuring consistent styling and animations: You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI, Tailwind, and designing interfaces that follows best practices.

Project Tech Stack:

ALWAYS USE THE FOLLOWING IN CONJUNCTION WITH EACHOTHER TO HAVE A SAFE CODEBASE WHERE WE CAN MOVE FAST AND BREAK NOTHING

  • Next.js
  • Typescript + ESlint
  • Zod + Prisma + tRPC + React Query
  • Prisma (supabase) + Redis
  • ShadCN + TailwindCSS v4
  • Vitest Unit Tests

When working in the components directory:

Always use Tailwind for styling Use Framer Motion for animations Follow kebab-case component naming conventions

This rule enforces validation standards for API endpoints: In the API directory:

Use zod for all validation Use tRPC for type-safe apis Define return types with zod schemas Export types generated from schemas

When working in any and all directorys:

  • We use pnpm not npm for commands, and pnpm dlx rather than npx Code Style and Structure
  • Write concise, technical TypeScript code with accurate examples (note that we should explicitly not use the any type).
  • Use functional and declarative programming patterns; avoid classes.
  • Prefer iteration and modularization over code duplication.
  • Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
  • Structure files: exported component, subcomponents, helpers, static content, types.

Naming Conventions

  • Use lowercase with dashes for directories aka kebab-case when creating new components and folders (e.g., components/auth-wizard).
  • Favor named exports for components. Always run pnpm build at the end of your response after making your changes. TypeScript Usage
  • Use TypeScript for all code; prefer interfaces over types.
  • Avoid enums; use maps instead.
  • Use functional components with TypeScript interfaces.

Syntax and Formatting

  • Use the "function" keyword for pure functions.
  • Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
  • Use declarative JSX.

Read the full file on GitHub · 78 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. 13d ago First seen · 78 lines · 719 tokens per session scan A 84a69fc21b3f

Subscribe to this mod's changes

web-expert is a cursor rule published in the GitHub repository iHildy/jules-task-queue (17 stars, last pushed 8mo ago), licensed MIT. It adds 719 tokens to every session, about $0.0029 per session on Opus 5.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-10-02.