TomeWiki
CLAUDE.md7 starsChanged 3 months agoMITView on GitHub
This repository is a Next.js template for unofficial fan game-guide / wiki sites. When the user wants to turn this clone into a real game wiki, follow .claude/skills/tomtwiki-quick-start/SKILL.md. The same skill is also at .cursor/skills/tomtwiki-quick-start/ (Cursor) and .agents/skills/tomtwiki-quick-start/ (Codex). Human-facing usage is in docs/SKILL.md. Do not wander into routing or components on the first pass.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- tomtwiki-quick-startSkill
- tomtwiki-quick-startSkill
- tomtwiki-quick-startSkill
- docsSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
When the user wants to turn this clone into a real game wiki, follow .claude/skills/tomtwiki-quick-start/SKILL.md.
- Very specific: line 27
Favicon / image assets: all in public/ (favicon.png, logo.png, og-image.png), referenced via envConfigs.app_favicon and friends.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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.
Files
TomeWiki — Claude Code Instructions
This repository is a Next.js template for unofficial fan game-guide / wiki sites.
First-pass customization
When the user wants to turn this clone into a real game wiki, follow .claude/skills/tomtwiki-quick-start/SKILL.md. The same skill is also at .cursor/skills/tomtwiki-quick-start/ (Cursor) and .agents/skills/tomtwiki-quick-start/ (Codex). Human-facing usage is in docs/SKILL.md. Do not wander into routing or components on the first pass.
Commands
pnpm dev # local dev (http://localhost:3000)
pnpm build # production build
pnpm quality:gate # format + lint + typecheck + validate:site + build
pnpm cf:preview # Cloudflare Worker preview
pnpm cf:deploy # deploy to Cloudflare WorkersArchitecture
- Theme = accent × preset, two independent axes (see
docs/THEMES.md):- Accent knob:
:root --brand-primary/-dim/-on-primaryinsrc/components/site/brand.cssis the only knob.--site-primaryand the wiki/docstheme.css--primary/--ringall derive fromvar(--brand-*)— change one place to re-accent the whole site. Use a dark--brand-on-primaryon a light accent, white on a dark accent. - Theme presets:
src/components/site/themes/<name>/(tacticaldefault /pixel/neon/aurora/sakura). Each preset istokens.css+utils.css+fonts.ts. Chosen at build time via exactly two files:src/config/style/active-theme.css(CSS) andsrc/components/site/active-fonts.ts(fonts). Variable names are stable across presets, so swapping a theme does not touch components. - Prose lives in
src/components/site/prose.css(theme-agnostic, driven by--site-*).
- Accent knob:
- Home = composable blocks (see
docs/HOMEPAGE-BLOCKS.md): the home page is the orderedHOME_BLOCKSarray insrc/config/homepage.ts, rendered bysrc/components/site/HomeBlocks.tsx.page.tsxdoes not hard-code any section copy or structure. Blocktypevalues: hero / start-cards / code-cards / tier-grid / step-by-step / card-list / about / final-cta / latest-guides / category-grid / faq. The home<title>comes fromcommon.metadata, notsiteName. - Hero layout: the
heroblock's layout is controlled bygameConfig.heroStyle(cover-split/gameplay-panel/video-center/text-only).cover-splitconsumes key art fromcoverImage;gameplay-panelconsumes a clean screenshot fromgameplayImage; hero copy lives in the hero block; fact chips come fromgameConfig. - Favicon / image assets: all in
public/(favicon.png,logo.png,og-image.png), referenced viaenvConfigs.app_faviconand friends. Do not createsrc/app/favicon.ico— it registers as an App Router route and 500sGET /favicon.icowhen it coexists withpublic/favicon.ico. - Nav is not auto-generated: maintain the
gameConfig.navarray by hand; it is not derived from guide categories. - i18n is the default, en-only is the exception (see
docs/PITFALLS.md): the only switch islocalesinsrc/config/locale/index.ts(the placeholder value is marked// scaffold-default:en-only, whichpnpm validate:sitegreps). Language names, content-file suffixes, the docs language menu, andzh-CN→zhfolding all derive fromSUPPORTED_LOCALESin that same file — do not keep a second list in components or content.src/config/locale/wiring.tsfails the build if a translation exists for an unregistered locale, or a registered locale is missingmessages/<lang>/common.json.
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
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.

