WireStudio: Instructions file for Claude Code

CLAUDE.md

WireStudio CLAUDE.md is an instructions file for Claude Code from moellere/WireStudio. It costs 514 tokens per session, scanned A, original, MIT.

A set of instructions for editing the WireStudio code repository, covering its writing style, coding rules, architecture, and library files.

In plain words
What is it for?
Use it when writing, reviewing, or refactoring WireStudio code and its generated files.
Why use it?
It gives the coding agent the project’s working conventions so changes fit the repository and avoid unwanted patterns.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is moellere/WireStudio's own configuration. It tells Claude Code how to work on WireStudio itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything WireStudio configures →

Reuse

Borrowing it

Nothing to install: this file belongs to moellere/WireStudio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/moellere/WireStudio/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/moellere/WireStudio

Made for: Claude Code.

Wrote 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.

agentmods badge for WireStudio CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/moellere/wirestudio/claude-md/github.svg)](https://agentmods.dev/instructions/moellere/wirestudio/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/moellere/wirestudio/claude-md"><img src="https://agentmods.dev/badge/instructions/moellere/wirestudio/claude-md/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.

agentmods 80×15 button for WireStudio CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/moellere/wirestudio/claude-md"><img src="https://agentmods.dev/badge/instructions/moellere/wirestudio/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 514 This file is loaded in full into every session.
When invoked 514 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00514 $0.00514
Opus 5.5 $0.00206 $0.00206
Sonnet 5.5 $0.00103 $0.00103
Haiku 4.5 $0.00051 $0.00051

Measured 15d ago against content hash 8f661f960e8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

WireStudio 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 15d 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.

CLAUDE.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — working conventions

Notes for Claude (and humans) when editing this repo.

Voice

  • Concise. No marketing language, no emojis in code, comments, commits, PRs.
  • Prefer plain prose over headers in short replies.
  • State decisions and tradeoffs directly. Don't hedge.

Code

  • Default to no comments. Add one only when the why is non-obvious (hidden constraint, workaround, surprising invariant).
  • No "added for X" / "used by Y" comments. That belongs in commit messages.
  • No backwards-compat shims, dead-code stubs, or unused-arg renames. Delete it.
  • No premature abstraction. Three similar lines beat a wrong helper.
  • Validate at boundaries (file load, CLI input, future API). Trust internal callers.

Architecture

  • design.json is the single source of truth. Generators are pure functions of design.json + library files. No artifact → document round-trips.
  • Conversation history (when the agent lands in 0.2) lives in sessions/<id>.jsonl, never in design.json.
  • Permissive mode: electrical/CSP violations surface in warnings[], do not block generation. (Strict mode is a later toggle.)
  • Secrets never go in design.json. Reference fleet-for-esphome's secrets.yaml via !secret name.

Library files

  • library/components/<id>.yaml carries electrical metadata that ESPHome doesn't (pins, passives, current draw, pull-up requirements) plus a Jinja2 ESPHome YAML template.
  • library/boards/<id>.yaml carries board pinout, rails, and the PlatformIO board key.

Tests

  • Generator output is pinned to goldens in tests/golden/.
  • When a golden changes intentionally, regenerate via the CLI and commit the new file in the same diff as the code change.

TODOs

Use # TODO(0.x): to mark deferred work tied to an item in docs/roadmap.md. Plain # TODO: is fine for unscoped notes.

What not to do

  • No new top-level documentation files unless explicitly asked.
  • No splitting wirestudio/ into more packages until 0.2 needs them.
  • No vendoring upstream ESPHome source. Schema-derived data only.

Read the full file on GitHub · 49 lines

Changes

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.

  1. 15d ago Changed · +3 tokens per session 8f661f960e8e
  2. 2mo ago First seen · 49 lines · 511 tokens per session scan A 1a7ac4d3c02a

Subscribe to this mod's changes

WireStudio CLAUDE.md is an instructions file published in the GitHub repository moellere/WireStudio (27 stars, last pushed 6d ago), licensed MIT. It adds 514 tokens to every session, about $0.0021 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.

Related

WireStudio CLAUDE.md compared with instructions from other repositories

WireStudio CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
WireStudio CLAUDE.mdmoellere/WireStudioInstructions file276d agoMITA514Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode