القائمة
Start/restart the alaria-map-site Next.js dev server (web) in background. Use when starting the dev server, checking status, debugging server issues, or needing to know where logs live.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Author a complete Alaria bestiary creature — canon-integrated lore + at least one outward codex edge + a validated 5e statblock — at Monster-Manual quality, without the convergence/monotony that destroys a bestiary at scale. Carries the anti-slop bar (the one diagnostic: does it hand a GM a live lever this session?) and the anti-convergence rules that are the value-add over plain lore-writing: the death-residue section is OPTIONAL not mandatory, the cinderbound/galebound bound-family litany is banned, resolution beats rotate, CR/role spread is a hard batch gate, naming heads diversify, and a batch passes a read-five-in-a-row gate before it ships. Use when writing any new `content/codex/entities/creature-*.md`, when running or reviewing a batch, or whenever you need the bestiary quality contract in one place. This skill is the front door; the detailed contract is `context/method-taxonomy.md`.
Enrich an Alaria codex page with specific, reciprocally-linked lore using the page-topic checklist. Walk a page's topics (famous individuals, factions, conflicts/wars, legendary items, locations, historical events, peoples), add named specific detail for the relevant ones, then make every reference two-way — create/update the referenced entity to point back in prose AND wire a codex edge. Use when fleshing out, deepening, or connecting any entity in content/codex/entities/, when building out a domain (e.g. undead), or when the goal is "make the world feel alive / add connective glue."
Context for the /pin admin workflow — what location pinning is for, how the data flows, and what invariants must not break. Use when working in src/app/pin/, src/app/api/pin/, src/app/api/manual-pin/, scripts/extract-locations.ts, scripts/finalize-locations.ts, data/work-queue.json, data/pinned.json, data/manual-pins.json, or when planning changes that touch lore data, the work queue, pinned coordinates, or free-form manual pins.
| name | headless |
| description | Start/restart the alaria-map-site Next.js dev server (web) in background. Use when starting the dev server, checking status, debugging server issues, or needing to know where logs live. |
| allowed-tools | Bash, Read, Grep, Glob |
Start and manage the alaria-map-site Next.js dev server as a supervised background process. Logs are isolated per grove instance at /tmp/grove/<path-slug>/ — run the script once to see the exact path.
.claude/scripts/headless.sh # start all (just web)
.claude/scripts/headless.sh web # start the web server
.claude/scripts/headless.sh restart web # restart it
.claude/scripts/headless.sh stop all # stop everything
| Service | Port Source | Directory | Start Command | Log |
|---|---|---|---|---|
| web | ./.env PORT (default 3000) | . | PORT=$PORT pnpm dev (Next.js 16, App Router) | <LOG_DIR>/web-dev.log |
The web service serves / (map viewer), /codex (lore browser), and /pin (admin pinning UI). Tiles are fetched from Cloudflare R2 at runtime — no local tile generation needed before pnpm dev.
echo "/tmp/grove/$(pwd | sed 's|^/||; s|/|-|g')"
tail -100 /tmp/grove/$(pwd | sed 's|^/||; s|/|-|g')/web-dev.log
lsof -i :<port> -sTCP:LISTEN to find it. The supervisor only starts services whose port is free OR already owned by this repo path.https://pub-2f7d72a936214040b067e1f9ffc82e63.r2.dev/tiles/config.json at runtime. If R2 is down or the bucket is empty, the map won't render. Check the browser console; this is not a dev-server problem./pin writes vanish in production: the /api/pin route uses fs.writeFileSync to data/*.json. Works locally; fails on Vercel/serverless. This is by design (pinning is local-only).WATCHDOG: port X unresponsive for 30s, the Next.js process was alive but not listening. This usually means a compile error inside next dev that didn't crash the process. Check the log above the WATCHDOG line for the actual error..next/: if dev server starts but pages 500 with weird hydration errors after a Next.js version bump, rm -rf .next and restart.Check logs first, not dashboards. Check listening sockets with lsof -i :<port> -sTCP:LISTEN.
all (or no args) — start every service<alias> — start only that service (currently only web)stop <alias|all> — stop without restartingrestart <alias|all> — stop then start