Borrowing it
Nothing to install: this file belongs to Synerise/synerise-design. 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/Synerise/synerise-design/master/CLAUDE.mdgit clone --depth 1 https://github.com/Synerise/synerise-designWrote 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/synerise/synerise-design/claude-md)<a href="https://agentmods.dev/instructions/synerise/synerise-design/claude-md"><img src="https://agentmods.dev/badge/instructions/synerise/synerise-design/claude-md.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.1 | $0.01413 | $0.01413 |
| Opus 5 | $0.00707 | $0.00707 |
| Sonnet 5 | $0.00283 | $0.00283 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
synerise-design CLAUDE.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 today.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Synerise Design System
Project Overview
- Component library / design system — publishes
@synerise/ds-*packages to npm - React 18.3 + TypeScript 5.8, monorepo via pnpm workspaces + Lerna (
"npmClient": "pnpm") - styled-components for all styling; antd has been fully removed (see
docs/adr/0001-remove-antd-dependency.md) — never reintroduce it, eslint bans the import - Functional components with hooks for all new code
Code Quality
- ESLint + Prettier (120 char lines, single quotes, 2-space indent)
- Relative imports only — no path aliases
- Named exports preferred, PascalCase components, camelCase utilities
- TypeScript
strict: true, noany— useunknown+ type guards
Components
- styled-components with design system tokens — no hardcoded values
- Keep local state in
useState/useReducer - No Redux — this is a UI component library, not an app
Testing
- Vitest in every package (
vitest run), jsdom environment, React Testing Library - Co-located tests:
*.test.tsxnext to source - 80% minimum coverage on business logic and shared components
- Test config lives only in the
testblock of the rootvite.config.base.ts. Per-packagevitest.*.config.*files are rejected bypnpm check:no-package-test-configin CI — they replace the basetest/resolveblocks instead of merging, silently droppingsetupFilesand the source resolution - Specs resolve
@synerise/*imports from the sibling package'ssrc/, not its builtdist/, so a cross-package change is visible without rebuilding the dependency (dsTestSourceRedirectPlugin) - Prerequisite: the generated sources (
pnpm run generate— core theme variables, icon/flag/avatar SVGR output). The rootpostinstalldoes this; a fresh git worktree or--ignore-scriptsinstall does not, and the test run fails fast naming the command DS_TEST_FROM_SOURCE=0sends bare imports back todistfor one run; deep@synerise/ds-x/dist/...imports always resolve from source (theexportsmap cannot resolve them).DS_TEST_RESOLVE_DEBUG=1logs every redirect
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.
- today Changed · +13 tokens per session 3aedb00be08f
- 3d ago First seen · 57 lines · 1,400 tokens per session scan A 4c0917c572ea
synerise-design CLAUDE.md is an instructions file published in the GitHub repository Synerise/synerise-design (96 stars, last pushed yesterday), licensed MIT. It adds 1,413 tokens to every session, about $0.0071 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-09-04.
Other instructions, from other repositories
agent-compass backoffice.instructions.md
Use when modifying the React backoffice in apps/backoffice, including TanStack Router routes, React Query flows, MUI UI, and Vitest tests.
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.