Borrowing it
Nothing to install: this file belongs to utensils/claudette. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/utensils/claudette/main/.github/instructions/frontend.instructions.mdgit clone --depth 1 https://github.com/utensils/claudetteWrote 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/instructions/utensils/claudette/frontend)<a href="https://agentmods.dev/instructions/utensils/claudette/frontend"><img src="https://agentmods.dev/badge/instructions/utensils/claudette/frontend/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/instructions/utensils/claudette/frontend"><img src="https://agentmods.dev/badge/instructions/utensils/claudette/frontend.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.00394 | $0.00394 |
| Opus 5.5 | $0.00158 | $0.00158 |
| Sonnet 5.5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
claudette frontend.instructions.md 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 1mo 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.
What it actually says
Frontend code is React, TypeScript strict mode, Zustand, CSS modules, Vite, Bun, and Vitest. Do not use any; read the actual type definitions before constructing fixtures or Tauri payloads.
State belongs in the existing Zustand slices under src/ui/src/stores/slices/. Add or update a domain slice instead of growing component-local state that must survive navigation, workspace switching, or event replay.
Keep large components from becoming god files. Before adding substantial logic to Sidebar.tsx, ChatPanel.tsx, ChatInputArea.tsx, TerminalPanel.tsx, settings sections, or large CSS modules, prefer a focused child component, hook, pure helper, or testable logic module in the same feature folder.
Preserve established workflows and UI affordances. Treat removed buttons, changed keyboard behavior, lost selection, broken scrolling, altered terminal sizing, dropped context-menu actions, changed tab/session ordering, and missing loading/error states as regressions unless explicitly requested.
Use existing service wrappers in src/ui/src/services/ for Tauri IPC. Keep command names and payload shapes aligned with Rust models and commands. Do not bypass typed wrappers for one-off invoke calls when a service module owns the domain.
All colors outside src/ui/src/styles/theme.css must use CSS custom properties, usually var(--token-name) or rgba(var(--token-rgb), alpha). Do not add raw hex/rgb/rgba literals to components or CSS modules.
Prefer logic tests for behavior-heavy UI. Put pure behavior in helpers when possible and cover it with Vitest. For TypeScript changes, run cd src/ui && bunx tsc -b; test passing alone is not enough.
Do not update bun.lock unless dependency changes are intentional. Use Bun commands, not npm or yarn.
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.
- 1mo ago First seen · 20 lines · 394 tokens per session scan A bc66396e1811
claudette frontend.instructions.md is an instructions file published in the GitHub repository utensils/claudette (83 stars, last pushed 1mo ago), licensed MIT. It adds 394 tokens to every session, about $0.0016 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.