agentleFS
elevaiteworkselevaiteworks/website-template/CLAUDE.md

website-template

CLAUDE.md1 starsChanged 6 months agoMITView on GitHub

You're helping the user customize a Next.js website built from a starter template. This file tells you where things live and how to make changes that don't break the patterns. Pre-built workflows that ship with this repo. Invoke them by describing what you want — you don't need to type a slash command. Recommended MCP install (one-time, for the user): chrome-devtools-mcp enables the visual iteration loop in match-reference. Without it, the skill falls back to a manual mode where the…

The file

We split this CLAUDE.md into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Recommended first-touch routing: if the user is fresh (no content/_brief.md yet), default to suggesting onboard-site before any …

    line 23
  2. Very specific:

    New section on an existing page: create a new component in components/sections/, add its data to the relevant content/*.md frontmatter, and …

    line 29
  3. Very specific:

    New page: create app/[name]/page.tsx, mirror the pattern from app/about/page.tsx, add content/[name].md, and add a link to it in …

    line 30
  4. Very specific:

    Don't add MEMORY.md or persistent memory files — this is a shared template, not a personal workspace.

    line 43
  5. Distinctive:

    Don't add analytics, SEO meta, or contact-form backends unless the user asks.

    line 44
  6. Distinctive:

    Don't refactor the structure to be "more elegant." The flat, obvious layout is the point.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

You're helping the user customize a Next.js website built from a starter template. This file tells you where things live and how to make changes that don't break the patterns.

How this site is organized

  • brand.config.ts — the single source of truth for site name, colors, fonts, and social links. When the user wants a global visual change, edit this first.
  • content/home.md and content/about.md — all page copy. Frontmatter (between the --- lines) controls structured sections; the body of about.md is long-form prose rendered as markdown.
  • app/ — page files. Each page imports section components and passes them data from the markdown files.
  • components/sections/ — individual page sections (Hero, Features, CTA, etc.). One section per file. Components read props, never read files directly.
  • public/ — images, favicon, logo. Reference as /filename.jpg from markdown or components.
  • .claude/skills/ — pre-built workflows you can invoke by description. See "Skills" below.

Skills

Pre-built workflows that ship with this repo. Invoke them by describing what you want — you don't need to type a slash command.

  • onboard-site — the first skill a new user should run. Five-question pre-flight that captures site type, target visitor, tone, primary CTA, and 3 reference sites. Writes answers to content/_brief.md so every later edit refers back to a written declaration of intent. Invoke when the user opens the template fresh, asks "what should I do first", or hasn't yet written a brief. See .claude/skills/onboard-site/SKILL.md.
  • match-reference — match the visual feel of a reference site. User drops a screenshot into references/, you screenshot the live dev server via chrome-devtools-mcp, compare, edit brand.config.ts, iterate. See .claude/skills/match-reference/SKILL.md for the full loop.

Recommended MCP install (one-time, for the user): chrome-devtools-mcp enables the visual iteration loop in match-reference. Without it, the skill falls back to a manual mode where the user describes what's off. Encourage the user to install it for the auto loop.

Recommended first-touch routing: if the user is fresh (no content/_brief.md yet), default to suggesting onboard-site before any customization work. If a brief exists, route based on what they ask for (visual change → match-reference, copy edit → direct edit of content/*.md, new section → see "Editing rules" below).

Editing rules

  • Copy changes: edit markdown files in content/, never hardcode strings in components.
  • Color or font changes: edit brand.config.ts. Tailwind reads from it via tailwind.config.ts.
  • New section on an existing page: create a new component in components/sections/, add its data to the relevant content/*.md frontmatter, and render it in the page file.
  • New page: create app/[name]/page.tsx, mirror the pattern from app/about/page.tsx, add content/[name].md, and add a link to it in components/Nav.tsx.
  • Don't add CMSes, databases, or auth. This is a static marketing site. If the user asks for dynamic features, suggest deploying to Vercel and using their tooling.

Workflow: "match this reference"

The full workflow lives in .claude/skills/match-reference/SKILL.md. Invoke it when the user drops a screenshot into references/ and asks to "match this reference," "make it feel like X," or similar.

Always insist on a screenshot, not just a URL. A CSS scrape tells you what colors exist on a site; only the screenshot tells you how those colors are used. A pink hex value might be a 4px badge or a full-page background — same hex, totally different vibe. Ask the user to drop a PNG into references/ if they only gave you a link.

The skill handles the rest: vision-read the reference, screenshot the live dev server via chrome-devtools-mcp, articulate diffs in plain language, edit brand.config.ts first, iterate. Falls back to a user-described-diffs mode if chrome-devtools-mcp isn't installed.

What not to do

  • Don't add MEMORY.md or persistent memory files — this is a shared template, not a personal workspace.
  • Don't add analytics, SEO meta, or contact-form backends unless the user asks. Point them at Vercel's docs instead.
  • Don't refactor the structure to be "more elegant." The flat, obvious layout is the point.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.