What is claude-code-workflow CLAUDE.md?

Project instructions for an AI frontend automation knowledge base built around a UmiJS, React, and TypeScript application. They define the project structure and coding rules.

Use them when adding or changing frontend features, routes, API code, styles, or documentation in this project.

They help an agent make changes consistently, especially the rule that values such as text, colors, endpoints, and spacing must come from shared configuration rather than being written directly in components.

How Caspian-Sun/claude-code-workflow configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Caspian-Sun/claude-code-workflow. 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/Caspian-Sun/claude-code-workflow/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/Caspian-Sun/claude-code-workflow

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/caspian-sun/claude-code-workflow/claude-md/github.svg)](https://agentmods.dev/instructions/caspian-sun/claude-code-workflow/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/caspian-sun/claude-code-workflow/claude-md"><img src="https://agentmods.dev/badge/instructions/caspian-sun/claude-code-workflow/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/caspian-sun/claude-code-workflow/claude-md"><img src="https://agentmods.dev/badge/instructions/caspian-sun/claude-code-workflow/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,385 This file is loaded in full into every session.

When invoked 1,385 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.

Model	Per session	Once invoked
Fable 5.1	$0.01385	$0.01385
Opus 5.5	$0.00554	$0.00554
Sonnet 5.5	$0.00277	$0.00277
Haiku 4.5	$0.00138	$0.00138

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

Security

Grade A, and why

claude-code-workflow 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 · 120 lines

How it starts

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

Project Configuration — AI Frontend Automation Knowledge Base

Onboarding for Claude Code. Detailed rules are split under .claude/rules/ and loaded on demand. When a specific scenario comes up, read the relevant rule file first, then execute.

Project Structure

This project has two layers:

Layer	Directory	Responsibility
Root	`.claude/` / `docs/` / `CLAUDE.md`	AI automation framework (commands / rules / PRDs / tasks)
workspace/	`workspace/src/` / `workspace/config/` / ...	The actual frontend project (UmiJS)

Commands like pnpm dev / pnpm gen:api at the root automatically proxy into workspace/, so you never have to cd manually.

P0 No Hardcoding (Highest Priority)

Every variable value is introduced via config / constants / Design Tokens / i18n — never hardcoded. Config itself must not duplicate; reuse hierarchically. Covers: copy i18n, colors and styles, API endpoints, business enums, sizes and spacing, magic numbers.

Detailed rules and examples → .claude/rules/no-hardcode.md

Tech Stack (Summary)

UmiJS 4 + React 18 + TypeScript 5 + Ant Design 5 (@umijs/max)

Routing: Umi convention-based routing | Requests: @umijs/plugin-request | State: useModel + Zustand
Build: Umi + Vite mode | Lint: @umijs/lint | Package manager: pnpm
Do not install dependencies that Umi already bundles (axios / react-router-dom / webpack, etc.)

Full tech stack and project structure → .claude/rules/tech-stack.md

Coding Style (Summary)

Comments explain "why," not restate code; file-header JSDoc is mandatory; commented-out code is deleted outright
Components PascalCase / hooks use prefix / constants UPPER_SNAKE_CASE / types without I prefix
Function components + exported Props interface + logic extracted to hooks + components only render
Requests use umi-request; interceptors live in app.ts; no axios
State: useModel first → Zustand as fallback → server data never goes in the store
Routing: convention-based first; permissions via @umijs/plugin-access + wrappers
Git: type(scope): description; branches feature/ fix/ refactor/

Read the full file on GitHub · 120 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.

2mo ago First seen · 120 lines · 1,385 tokens per session scan A 67fc95004142

Subscribe to this mod's changes

claude-code-workflow CLAUDE.md is an instructions file published in the GitHub repository Caspian-Sun/claude-code-workflow (10 stars, last pushed 1mo ago), licensed MIT. It adds 1,385 tokens to every session, about $0.0055 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.

Claude Code agent-sdk ai-agent ai-workflow forward-deployed-engineering methodology

vibe-coding-prompt-template backend.instructions.md

Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.

KhazP/vibe-coding-prompt-template · 139 tokens

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

claude-code-workflow: Instructions file for Claude Code