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.
git clone --depth 1 https://github.com/zeyadelosherey/tapwisper-desktopWrote 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.
[](https://agentmods.dev/rules/zeyadelosherey/tapwisper-desktop/react-components)<a href="https://agentmods.dev/rules/zeyadelosherey/tapwisper-desktop/react-components"><img src="https://agentmods.dev/badge/rules/zeyadelosherey/tapwisper-desktop/react-components/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.
<a href="https://agentmods.dev/rules/zeyadelosherey/tapwisper-desktop/react-components"><img src="https://agentmods.dev/badge/rules/zeyadelosherey/tapwisper-desktop/react-components.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00000 | $0.00541 |
| Opus 5.5 | $0.00000 | $0.00216 |
| Sonnet 5.5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 2mo 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.
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.hashto decide which component to render - The main window has an onboarding gate: if
onboardingCompletedisfalsein the config store,main-window.tsxrenders 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 tosrc/renderer/(configured inelectron.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 controlsuse-ai-action.ts-- AI text processing actionsuse-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
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.
- 2mo ago First seen · 59 lines · 0 tokens per session scan A 83ded4ce031a
react-components is a cursor rule published in the GitHub repository zeyadelosherey/tapwisper-desktop (6 stars, last pushed 4d 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.
Other cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
tanstack-react-router_routing
TanStack Router: Routing.
new-component
Workflow for creating new React components.