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.
npx agentmods add rules/zeyadelosherey/tapwisper-desktop/coding-standardsgit 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/coding-standards)<a href="https://agentmods.dev/rules/zeyadelosherey/tapwisper-desktop/coding-standards"><img src="https://agentmods.dev/badge/rules/zeyadelosherey/tapwisper-desktop/coding-standards.svg" alt="Measured on agentmods" 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 | $0.01114 | $0.01114 |
| Opus 5 | $0.00557 | $0.00557 |
| Sonnet 5 | $0.00223 | $0.00223 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
coding-standards 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 5d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards
File Naming
- kebab-case for all files:
my-component.tsx,use-audio.ts,ai-router.ts - PascalCase for React component exports:
export function MyComponent() - camelCase for hooks, utilities, and variables:
useAudio,formatDuration
TypeScript
- Never use
any-- use proper type definitions - Use
interfacefor object shapes,typefor unions and intersections - Define shared types in
src/renderer/models/orsrc/renderer/types/ - Prefix unused function parameters with
_(e.g._event)
React
- Functional components only -- no class components
- Extract reusable logic into custom hooks in
src/renderer/hooks/ - Keep components focused; split large ones into smaller pieces
- Use
React.lazy()for overlay components loaded on demand
Styling
- Use Tailwind CSS utility classes -- no custom CSS unless necessary
- Theme-aware colors via CSS variables (defined in
src/renderer/styles/globals.css) - Custom theme values go in
tailwind.config.js
Internationalization
- All user-facing strings must use
useTranslation()from react-i18next - Add translations to every locale file in
src/renderer/i18n/(en, ar, de, es, fr, it)
Formatting (Prettier)
These rules are enforced by Prettier -- do not deviate:
- No semicolons
- Single quotes
- No trailing commas
- 100 character line width
- 2-space indentation
- LF line endings
- Always use parentheses around arrow function parameters
Linting (ESLint)
@typescript-eslint/no-explicit-any: warn@typescript-eslint/no-unused-vars: warn (ignored if prefixed with_)no-console: warn -- avoidconsole.login production code (stripped in prod builds)
Git Branching Strategy (Git Flow)
Primary Branches
| Branch | Purpose | Merges Into |
|---|---|---|
main |
Production-ready releases. Always stable and tagged. | -- |
develop |
Integration branch for features. All new work starts here. | main (via release/*) |
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.
- 5d ago First seen · 116 lines · 1,114 tokens per session scan A 0458693741e5
coding-standards is a cursor rule published in the GitHub repository zeyadelosherey/tapwisper-desktop (5 stars, last pushed 4mo ago), licensed MIT. It adds 1,114 tokens to every session, about $0.0056 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.
Other cursor rules, from other repositories
nextjs-typescript-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript and Tailwind CSS integration.
nextjs-tailwind-typescript-apps-cursorrules-prompt
Cursor rules for Next.js development with Tailwind CSS and TypeScript integration.
qwik-tailwind-cursorrules-prompt-file
Cursor rules for Qwik development with Tailwind CSS integration.
no-magic-numbers
Prefer named constants over unexplained numeric literals in TypeScript. Apply when editing .ts/.tsx behavior code.
ts-coding-rules
The current codebase enforces strict type safety, accessibility standards, and consistent code quality for JavaScript/TypeScript projects using Biome's lightning-fast formatter and linter.
svelte-typescript
Svelte 5 and TypeScript patterns for Keymoji components and stores.