Borrowing it
Nothing to install: this file belongs to skovtun/coherent-design-method. 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/skovtun/coherent-design-method/main/CLAUDE.mdgit clone --depth 1 https://github.com/skovtun/coherent-design-methodWrote 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/skovtun/coherent-design-method/claude-md)<a href="https://agentmods.dev/instructions/skovtun/coherent-design-method/claude-md"><img src="https://agentmods.dev/badge/instructions/skovtun/coherent-design-method/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.03590 | $0.03590 |
| Opus 5 | $0.01795 | $0.01795 |
| Sonnet 5 | $0.00718 | $0.00718 |
| Haiku 4.5 | $0.00359 | $0.00359 |
Grade A, and why
coherent-design-method 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 7d 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coherent Design Method
Coherent solves a specific problem: AI-generated UIs all look the same. Every tool produces Inter font, purple gradients, identical card grids. Coherent's job is to make that impossible — by encoding design decisions as a tiered constraint system that runs before the AI writes a single line of code.
Current version: 0.26.0
Packages: @getcoherent/core + @getcoherent/cli (published together, same version)
Tests: 2587 passing
⚡ Start-of-session reading (REQUIRED before any work)
Coherent maintains a platform-level LLM wiki with decisions, patterns, and ideas that persist across sessions. Read these before touching code:
docs/wiki/PATTERNS_JOURNAL.md— append-only log of every AI-output bug we've seen, its root cause, and what we shipped in response. If you're debugging something that feels familiar, it probably IS.docs/wiki/RULES_MAP.md— every rule indesign-constraints.tswith origin bug, validator, golden pattern. Check this before adding or modifying a rule.docs/wiki/MODEL_PROFILE.md— empirical notes on Claude Sonnet 4's systematic behaviors. Saves time on "why does AI keep doing X?" questions.docs/wiki/IDEAS_BACKLOG.md— open proposals, deferred work, rejected ideas with reasons. Check before proposing a new feature — it might already be scoped.docs/wiki/ADR/— architectural decision records for significant shifts (e.g., "why golden patterns over word-based rules").
These files capture why things are the way they are. CLAUDE.md and CHANGELOG.md answer "what is" and "what changed"; the wiki answers "why". Update them when you:
- Add a new rule (row in RULES_MAP.md + JOURNAL entry if bug-driven).
- Observe a new AI-output failure pattern (JOURNAL entry).
- Make a breaking or philosophically-significant change (new ADR).
- Propose or defer an idea (IDEAS_BACKLOG.md).
Not in the wiki, on purpose:
docs/FAQ.md— user-facing answers. Not retrieval-indexed (would pollute generation context).docs/runbooks/— operational how-tos (cut a release, validate retrieval, debug indexing). Not retrieval-indexed. Seedocs/runbooks/README.mdfor the layering rule.
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.
- 7d ago First seen · 364 lines · 3,590 tokens per session scan A 736cb7d406ef
coherent-design-method CLAUDE.md is an instructions file published in the GitHub repository skovtun/coherent-design-method (21 stars, last pushed 1mo ago), licensed MIT. It adds 3,590 tokens to every session, about $0.0180 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-30.
Other instructions, from other repositories
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).
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.
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 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.