agentleFS
tiankonglantiankonglan/TomeWiki/.cursor/skills/tomtwiki-quick-start/SKILL.md

tomtwiki-quick-start

Skill7 starsChanged 3 months agoMITView on GitHub

Turns a fresh TomeWiki clone into a named unofficial fan wiki. Fills site identity, SEO, homepage copy, theme, and brand images from a short game brief. Use when the user names a game and wants this template customized, when Example Game placeholders remain, or when they say 建站, 快速接入, 改成自己的站, or bootstrap a guide site from this repo.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 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.

  • 2

    Very specific

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

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

    Keep this folder identical in three places: .claude/skills/tomtwiki-quick-start/ (Claude Code), .cursor/skills/tomtwiki-quick-start/ …

    line 13
  2. Distinctive:

    After the file edits:

    line 37
  3. Very specific:

    If the new logo does not appear, Next is serving a cached asset.

    line 42
  4. Distinctive:

    Call the generator that already lives in this repo.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
SKILL.md

TomeWiki Quick Start

Keep this folder identical in three places: .claude/skills/tomtwiki-quick-start/ (Claude Code), .cursor/skills/tomtwiki-quick-start/ (Cursor), and .agents/skills/tomtwiki-quick-start/ (Codex).

A new clone of TomeWiki still reads "Example Game". This skill swaps that identity using knobs the template already ships. It does not add routes, features, or a new content model.

Open a single file under references/ when you need it. Do not dump the whole folder into context.

Permitted edits

references/07-checklist.md is the full path list. Nothing else is in scope.

Leave these alone:

  • App Router and most UI (src/app/**, src/components/site/** except the two brand/font entry files)
  • template-contract.json
  • Auth, databases, billing, admin screens
  • Invented Steam IDs, patch numbers, loot tables, or publisher endorsement
  • src/app/favicon.ico (clashes with public/favicon.ico and 500s the icon)
  • Guide category folder names (must keep matching content/guides/<slug>/)
  • Stock public/logo.png, favicon.png, or og-image.png

Finish line

pnpm install once if node_modules is missing.

After the file edits:

  • pnpm validate:site
  • pnpm build

If the new logo does not appear, Next is serving a cached asset; delete .next and rebuild. pnpm quality:gate is optional and matches CI (format, lint, types, validate, build).

Repair failures only on permitted paths unless the user widens the job.

Brief

references/00-brief.md — game title and domain are enough to start. Ask at most once for holes, then leave searchable TODO: comments. Ignore Steam ID, analytics, and extra languages unless the user gave them.

Order of work

StepFile
Worker + envreferences/01-env-and-worker.md
Game / site identityreferences/02-identity.md
Title, description, keywordsreferences/03-seo.md
Homepage strings (same blocks)references/04-homepage.md
Accent color and visual presetreferences/05-theme.md
Logo, favicon, social previewreferences/06-brand-assets.md
Permitted paths and sign-offreferences/07-checklist.md

Brand images

Call the generator that already lives in this repo. Do not add a new image script.

node scripts/gen-brand-assets.mjs \
  --game "<gameFullName>" \
  --short "<gameShortName>" \
  --domain "<domain>" \
  --color "<#RRGGBB>" \
  --tagline "<short tagline>"

Pass --emblem path/to/emblem.png when the user has a square mark. sharp is already a dependency.

Hand off

Real guides belong in content/guides/; entity records in content/entities/. Extra locales follow docs/QUICKSTART.md section 7 (drop // scaffold-default:en-only). Domain bind, analytics, and pnpm cf:deploy / Vercel import stay with the user.

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.