workshop: Instructions file for Claude Code

CLAUDE.md

workshop CLAUDE.md is an instructions file for Claude Code from RewritingTheCode/workshop. It costs 842 tokens per session, scanned A, original, MIT.

Project rules for building a single-page personal portfolio website. They define a five-stage workflow: clarify the context, record a specification decision, build, validate, and deploy.

In plain words
What is it for?
Use them when changing portfolio content, page sections, metadata, code, tests, or deployment. They also explain where profile data and architecture decisions belong.
Why use it?
They keep the portfolio’s content in one structured source and require every change to be checked at a narrow mobile width before deployment.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is RewritingTheCode/workshop's own configuration. It tells Claude Code how to work on workshop 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 workshop configures →

Reuse

Borrowing it

Nothing to install: this file belongs to RewritingTheCode/workshop. 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/RewritingTheCode/workshop/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/RewritingTheCode/workshop

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 workshop CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/rewritingthecode/workshop/claude-md"><img src="https://agentmods.dev/badge/instructions/rewritingthecode/workshop/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 842 This file is loaded in full into every session.
When invoked 842 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.00842 $0.00842
Opus 5.5 $0.00337 $0.00337
Sonnet 5.5 $0.00168 $0.00168
Haiku 4.5 $0.00084 $0.00084

Measured 2mo ago against content hash 84b4230b7905, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

workshop 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 2mo 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 · 75 lines

How it starts

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

Portfolio Starter - Project Rules

A single-page personal portfolio. Built live during RTC's "How RTC Builds Real Software with AI" workshop, and yours to keep extending afterward.

The loop

Every change follows the same five steps. No exceptions, including for small changes.

  1. Context - ask what this is and who it is for, before proposing anything
  2. Spec - write the decision down as an ADR in docs/adr/, before writing code
  3. Build - implement the ADR. The ADR is the instruction.
  4. Validate - npm run check. Look at it at 320px wide.
  5. Ship - npm run deploy. It is not done until it is on the internet.

Content

All personal content lives in src/content/profile.ts and must satisfy src/content/schema.ts. Never add a second source of truth for content. Never hardcode a name, a job title, or a date into a component.

That includes index.html. Its <title> and meta description are filled in from profile.ts at build time by the plugin in vite.config.ts - see src/content/metadata.ts. Leave the __PAGE_TITLE__ and __PAGE_DESCRIPTION__ tokens alone.

Page section order is content too: profile.sections is the order of the page and of the anchor nav. Adding a section means adding its id to SECTION_IDS in the schema and an entry in src/components/sections.tsx - never a hand-placed component in Page.tsx. See docs/adr/ADR-006-section-order.md.

Never invent content. If information is not in the source the user gave you, leave the field out. This is a public portfolio - a fabricated job or project is a serious problem, not a formatting detail.

Code

  • React 19 + TypeScript + Tailwind v4 + Vite. Match the existing patterns in src/components/.
  • Mobile first. Start at the phone layout with no prefix, add width at sm: and md:.
  • It must work at 320px. No fixed widths in the page shell.
  • Real semantics: one <h1>, headings that do not skip levels, <nav> for the nav, <button> for buttons. Never a <div> with an onClick.
  • Visible focus states on everything interactive.
  • Keep files under 200 lines. Split a component before it gets long.

Read the full file on GitHub · 75 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. 2mo ago First seen · 75 lines · 842 tokens per session scan A 84b4230b7905

Subscribe to this mod's changes

workshop CLAUDE.md is an instructions file published in the GitHub repository RewritingTheCode/workshop (12 stars, last pushed today), licensed MIT. It adds 842 tokens to every session, about $0.0034 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-31.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens