What is react-components?

A set of rules for building React components in a desktop application. React is a tool for creating interfaces from reusable pieces called components.

Adding pages and overlay panels, wiring hash-based navigation, managing shared state with Zustand, enforcing the onboarding gate, and connecting renderer code to AI services.

It keeps component locations, routing, state management, lazy loading, and access to application settings consistent across the codebase.

react-components — Cursor rule by zeyadelosherey

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 rules/zeyadelosherey/tapwisper-desktop/react-components

Clone the repo

git clone --depth 1 https://github.com/zeyadelosherey/tapwisper-desktop

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 541 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00541
Opus 5	$0.00000	$0.00270
Sonnet 5	$0.00000	$0.00108
Haiku 4.5	$0.00000	$0.00054

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

Security

Grade A, and why

react-components 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 3d 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/react-components.mdc · 59 lines

How it starts

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

React Renderer Patterns

Component Structure

Overlay components (recording pill, pinned panel, command popup, AI panel) are loaded with React.lazy()
Pages (onboarding, home, settings, triggers, notes, snippets, actions-config) live in src/renderer/pages/
Shared overlay UI lives in src/renderer/components/
Routing is hash-based: the renderer reads window.location.hash to decide which component to render
The main window has an onboarding gate: if onboardingCompleted is false in the config store, main-window.tsx renders the <Onboarding> component instead of the normal sidebar + page layout

State Management

Use Zustand for global state (src/renderer/store/)
Current stores: stats.ts (usage statistics), activity.ts (activity tracking)
Keep state minimal -- derive computed values instead of storing them
Access config via window.tapwisper.store.* (IPC to electron-store in main process)

Path Alias

@/ maps to src/renderer/ (configured in electron.vite.config.ts)
Example: import { processText } from '@/services/ai-router'

AI Services

All AI provider clients live in src/renderer/services/
The router (ai-router.ts) dispatches to the correct provider based on user config
Each provider exports a single async function: processWithGemini(), transcribeWithWhisper(), etc.
Provider types are defined in src/renderer/constants/providers.ts

Animations

Use Framer Motion for all animations
Import from framer-motion (e.g. motion, AnimatePresence)

Icons

Use Lucide React for UI icons (lucide-react)
Brand/provider icons use simple-icons or static assets in src/renderer/assets/
Icon mapping utility: src/renderer/components/icon-map.tsx

Hooks

use-audio.ts -- audio recording state and controls
use-ai-action.ts -- AI text processing actions
use-shortcuts.ts -- keyboard shortcut handlers in renderer

Styling

Tailwind CSS utility classes for all styling
Theme colors use CSS variables from src/renderer/styles/globals.css
RTL support is built in for Arabic locale
Dark/light/system theme switching

Read the full file on GitHub · 59 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.

3d ago First seen · 59 lines · 0 tokens per session scan A 83ded4ce031a

Subscribe to this mod's changes

react-components is a cursor rule published in the GitHub repository zeyadelosherey/tapwisper-desktop (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 541 tokens. 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.

Frontend React

react-components

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

React Renderer Patterns

Component Structure

State Management

Path Alias

AI Services

Animations

Icons

Hooks

Styling

What this file has done since we first saw it

Other cursor rules, from other repositories

react-vite-web

frontend-patterns

new-component

frontend-architecture

performance-optimization-rule

nextjs