t1k:designer:wiki:core
| Field | Value |
|---|---|
| Module | wiki |
| Version | 0.15.1 |
| Effort | medium |
| Tools | — |
Keywords: ai-context, battle pass, clan war, daily missions, dept-add, dept-remove, dungeons, game wiki, game-wiki, init wiki, limited-time events, meta events, meta-add, meta-remove, per-game wiki, pvp arena, scaffold wiki, update wiki, validate wiki, wiki create, wiki staleness, wiki workflow
How to invoke
Section titled “How to invoke”/t1k:designer:wiki:core<create|update|validate|dept-add|dept-remove|meta-add|meta-remove|ai-context-rebuild> [--dry-run]Game Wiki Workflow
Section titled “Game Wiki Workflow”Implements the Game Project Wikis workflow: scaffold, sync, and validate per-game-project GitHub Wikis serving both humans (designers, artists, audio, QA, PMs, marketing, tech artists, backend, liveops) and AI (Knowledge Retrieval MCP, in-repo Claude Code).
SSOT for design: Adoption Spec (1247 lines: JSON Schema Draft 2020-12, parser pseudocode, CI gate workflow, escape-hatch authorization). DO NOT duplicate that content here. Read it before any non-trivial mutation. See
references/adoption-spec-link.mdfor the section index.
When This Skill Triggers
Section titled “When This Skill Triggers”- “init wiki for
<game>”, “scaffold a new game wiki”, “create the wiki for our Cocos playable” →create - “update the wiki”, “sync wiki to code”, “wiki is stale” →
update - “validate the wiki”, “check wiki frontmatter”, “lint wiki”, “wiki anchor check” →
validate - “add a department to the wiki”, “remove a department” →
dept-add/dept-remove - “add a meta system to the wiki”, “scaffold daily-missions / battle-pass / dungeons / pvp-arena / clan-war / limited-time-events page”, “we need an events section” →
meta-add/meta-remove - “rebuild AI-Context.md”, “regenerate the AI-Context aggregate” →
ai-context-rebuild
Decision Tree
Section titled “Decision Tree”| Intent | Sub-op |
|---|---|
| Brand-new game has no wiki yet | create (a.k.a. init) |
| Wiki exists; code/CSV changed; wiki text outdated | update (resolves <!-- ai-owned --> only; preserves <!-- human-owned -->) |
| Confirm wiki structure (frontmatter, schema, links, freshness) | validate |
| New department joining the team mid-project | dept-add <dept-id> |
| Department disbanded or out-sourced | dept-remove <dept-id> |
| New meta-system / event archetype scaffolds a wiki page (battle-pass, daily-missions, dungeons, pvp-arena, clan-war, limited-time-events, gacha-mini-game, world-boss-or-raid, achievements-and-login) | meta-add <slug> |
| Meta-system retired / merged into another | meta-remove <slug> |
| AI-Context.md drifted from individual pages | ai-context-rebuild |
| Test what would happen without writing | append --dry-run to any of the above |
Sub-Op Workflows
Section titled “Sub-Op Workflows”| Sub-op | Summary |
|---|---|
create (init) | AskUserQuestion (tier, engine version, art-style, genre, departments staffed, meta-systems staffed) → scaffold AI-Context.md + tier page set (Tier A 16 pages / Tier B 28+N pages) → append genre-overlay pages → art-touching dept pages get a Reskin Self-Service section; Engineering-bucket pages get the 9 required sections → stage wiki PR. Before tagging the next release, run references/create-smoke-test.md against both tiers. |
update | Art-style pre-flight guard (declare if legacy wiki) → read canonical_files[] mtimes → stale pages resolve <!-- ai-owned --> regions from source-of-truth, preserving <!-- human-owned --> verbatim → stage wiki PR with per-page diff. |
validate | JSON Schema + frontmatter check → Meta & Events bucket consistency → art-style consistency → link integrity → staleness → severity per Adoption-Spec §4.5 (warn-only during rollout). |
dept-add / dept-remove | Scaffold/archive dept page, update sidebar, regenerate AI-Context, stage PR with audit trail. Art-style guard BLOCKS incompatible additions (e.g. art-3d against 2D-only) without an explicit re-declaration. |
meta-add / meta-remove | Validate slug against the canonical taxonomy → scaffold/remove the matching archetype page → update team.metaSystems[] + sidebar bucket → audit-trail PR citing the design decision. BLOCKED on Tier-A wikis (no meta loops). Page structure is owned here; design content for LTE archetypes lives in t1k-designer-base-events. |
ai-context-rebuild | Aggregate frontmatter + canonical YAML/JSON blocks from individual pages into AI-Context.md. Idempotent. |
Full step-by-step procedures — AskUserQuestion field lists, per-tier/per-genre template file mapping, art-style gate detail per sub-op, cross-skill linkage — are in references/sub-op-workflows.md.
Dept-Page Reskin Self-Service Convention (MANDATORY for art-touching pages)
Section titled “Dept-Page Reskin Self-Service Convention (MANDATORY for art-touching pages)”Every dept page that owns art assets — Art-2D, Art-3D, VFX, Audio, Animation — MUST include a ## Reskin Self-Service — Project + Prefab Structure section so the artist team can replace, reskin, or swap assets without engineering help.
Required subsections:
- Folder Map for Drop-In Replacement — flat table:
Asset family | Drop new file at <Assets/ path> | Linked prefab/material/SO - Prefab Hierarchy Reference — for each reskinnable prefab, show the GameObject tree + which Renderer/Image/SpriteRenderer slot reads which asset. Use ASCII tree format with
[reskinnable]markers on the artist-editable slots. - DOTS Subscene Warning (VFX only) —
[!WARNING]callout naming which effects are engineering-only (subscene-baked) vs which are artist-self-serve (Mono pool). - Reskin Workflow — numbered 5-step recipe: export → drop → wait for AssetImportProcessor → confirm in Inspector → Play-mode verify. “No engineering escalation required” sentence MANDATORY in the workflow steps.
- Atlas + Addressables Linkage — table showing which asset-family packs into which atlas / which Addressables group (so artist knows download-size impact).
- Realm-Tint / Rarity-Tint Self-Service — when applicable, show how SO-driven tints work (artist edits SO field, not texture).
- Material + Shader Linkage — table showing material families + which shader each uses + which is realm-tinted.
Template reference: see references/dept-page-reskin-template.md for a copy-paste skeleton with all 7 subsections pre-structured.
Engineering-Page Required Sections (MANDATORY for ⚙️ Engineering bucket)
Section titled “Engineering-Page Required Sections (MANDATORY for ⚙️ Engineering bucket)”Per the 5-round review pattern (StickManForge 2026-05-27, 89 findings), every page in the ⚙️ Engineering sidebar bucket MUST include:
| Section | Source finding | Purpose |
|---|---|---|
| Source: attribution line | F4.9 | Marks SSOT status or upstream pointer |
| Decision Register | F5.1 | Decision | Status | Owner | Decided-by | Reversal cost |
| Asset Production Phases (or domain equivalent) | F1.1 | Numbered phase model with inputs/outputs/owner |
| Risk Register | F1.7 + F5.2 | ID | Risk | Likelihood | Impact | Mitigation | Owner | SLA |
| Performance Budgets | F2.7 | Aggregate caps (size, draw calls, memory) |
| Ship Gates / Acceptance Criteria | F1.2 + F5.3 | Entry-gates + exit-gates checklists |
| Action Items | F5.5 | ID | Item | Section ref | Owner | By-date | Status |
| Implementation Notes + Milestone gates | F1.14 | Per-release deliverables with dates |
| Tooling table with Owner column + TODO markers | F1.3 + F5.4 | Mark scripts not yet in source repo as 🚧 TODO |
These are kit-wide for game-dev engineering reference pages. The /t1k:designer:wiki:core create flow should scaffold these sections automatically for engineering-bucket page types.
Cross-References
Section titled “Cross-References”- Wiki section hub (8 pages, 6,318 lines): https://github.com/The1Studio/AIPoweredGameDevelopmentSystem/wiki/Game-Project-Wikis
- Adoption Spec (implementation contract): https://github.com/The1Studio/AIPoweredGameDevelopmentSystem/wiki/Game-Project-Wikis-Adoption-Spec
- Sister skill:
game-design-document(per-page authoring within a wiki)
Reference Files
Section titled “Reference Files”| File | Coverage |
|---|---|
references/adoption-spec-link.md | Pointer + section index for the live Adoption-Spec (avoid duplicating 1247 lines locally) |
references/anchor-format.md | GitHub Wiki anchor algorithm (emoji stripping, multi-space → multi-hyphen) — load before authoring any cross-page link |
references/frontmatter-and-markers.md | Frontmatter spec + <!-- ai-owned --> / <!-- human-owned --> marker contract enforced by update |
references/ai-context-schema.md | AI-Context.md aggregate schema + Tier A and Tier B filled examples |
references/sidebar-convention.md | _Sidebar.md canonical template + Tier A / Tier B filter rules |
references/tier-a-page-templates.md | Ready-to-paste templates for Tier A non-dept pages (Home, Game-Pitch, Design-Pillars, Mechanic, Variants, Tech-Stack, Scene-Map, Asset-Inventory, Network-Spec) |
references/tier-a-department-templates.md | Ready-to-paste Tier A dept onboarding pages (Game-Design, Engineering, Art-2D, Audio, Marketing-UA) |
references/tier-b-page-templates.md | Ready-to-paste templates for Tier B non-dept pages (16 pages incl. Systems/ |
references/tier-b-department-templates.md | Ready-to-paste Tier B dept onboarding pages (10 of 12 — Tech-Artist and Backend-Services templates pending) |
references/genre-rpg-page-templates.md | Genre overlay — RPG (Idle/Hack-Slash/JRPG): 8 pages (Realm-Progression, Combat-Design, Equipment, Forge [opt], Heroes-Pets-Mounts, Hero-Skills, Dungeons-PvP, Loot-Tables) |
references/genre-puzzle-page-templates.md | Genre overlay — Puzzle (match-3, polyomino, sokoban, sudoku, hidden-object): 6 pages (Mechanic-Catalog, Difficulty-Curve, Level-Database, Power-up-Economy, Daily-Challenge, FTUE) |
references/genre-casual-page-templates.md | Genre overlay — Casual / Hyper-casual (single-loop, ad-monetized): 6 pages (Mechanic-Spec, Difficulty-Pacing, Cosmetic-Economy, Ad-Placement, Retention-Hook, Run-Length-Session) |
references/genre-roguelike-page-templates.md | Genre overlay — Roguelike / Roguelite (action, deckbuilder, survivor-like, bag-builder): 7 pages (Run-Structure, Meta-Progression, Item-Catalog, Synergy-Combos, Boss-Encounter, ProcGen-Rules, Death-Restart-UX) |
references/update-and-sync-workflow.md | /update-wiki slash command behaviour, CI staleness gate workflow, escape mechanisms |
references/dept-page-reskin-template.md | Copy-paste skeleton for ## Reskin Self-Service section on art-touching dept pages (Art-2D, Art-3D, VFX, Audio, Animation) — 7 mandatory subsections with placeholder text + pre-merge checklist |
references/meta-events-page-templates.md | Canonical slug taxonomy + per-archetype page templates (venue / progression / event / social) for the 🌀 Meta & Events sidebar bucket. Used by create + meta-add to scaffold Daily-Missions, Dungeons, PvP-Arena, Clan-War, Battle-Pass, Limited-Time-Events, and other meta-loop pages. Tier-B only. |
references/create-smoke-test.md | End-to-end smoke test checklist for the create sub-op (Tier A + Tier B) — setup, expected page roster, pass criteria, failure protocol. Run before tagging the next minor release. |
references/sub-op-workflows.md | Full step-by-step procedures for all 8 sub-ops — AskUserQuestion field lists, per-tier/per-genre template file mapping, art-style gate detail per sub-op, cross-skill linkage |
references/gotchas-history.md | Incident narratives behind the Gotchas section (StickManForge art-style + Build & Ops mis-categorization postmortems, DOTS-AI 260520 §D5 Index.md-threshold audit) |
Art-Style Gate — 2D / 3D / Hybrid (MANDATORY pre-flight)
Section titled “Art-Style Gate — 2D / 3D / Hybrid (MANDATORY pre-flight)”Every wiki MUST declare team.artStyle ∈ {2D-only, 3D-only, hybrid-2D-3D} in AI-Context.md. The declaration gates:
| Surface | 2D-only | 3D-only | hybrid-2D-3D |
|---|---|---|---|
| Departments bucket scaffolding | Art-2D + Animation + VFX + Audio | Art-3D + Animation + VFX + Audio (+ Art-2D as UI-only) | Both Art-2D and Art-3D |
Mesh prefixes (SM_, SK_) | Removed from naming-prefix-conventions emitted into the wiki | Included | Included |
| Addressables group families | art_2d_characters, art_2d_environment, art_2d_ui, art_2d_items | art_3d_characters, art_3d_environment (+ art_2d_ui for HUD) | Both group families |
| Import-preset templates | Sprite + Spine + sprite-frame .anim only — no FBX import-preset table | FBX + LOD + skinned-mesh import-preset table | Both |
| Performance-budget table | Sprite atlas page, single sprite max, Spine bone count | 3D character / prop / environment poly count | Both |
| URP render-pipeline preset | 2D Renderer feature enabled by default | 3D Forward+ default | 3D Forward+ + 2D Sprite renderer feature |
| Anvil / forge tactile object spec (RPG-genre overlay) | Multi-layer 2D parallax stack (base + anvil mid-layer + hammer-strike highlight + ambient sparks) | 3D mesh on a sub-camera RT | Author’s choice — must be declared per object |
Validation: the validate sub-op cross-checks the declared style against every page’s content. A 2D-only wiki with a stray SM_* reference, .fbx mention, or Art-3D link emits an ERROR. A wiki without team.artStyle declared is treated as legacy → first update / validate run AskUserQuestions and writes the answer.
Re-declaration policy: changing team.artStyle after init is permitted (e.g., a 2D-only game adds a 3D anvil mid-development → re-declare as hybrid-2D-3D) but MUST go through dept-add art-3d so the audit trail captures it; the dept-add op then re-scaffolds the wiki sections that the gate previously suppressed.
Gotchas
Section titled “Gotchas”- Status: templates ported, sub-op scripts still pending.
createcan produce a complete wiki by copying templates and filling<placeholders>.update,validate,dept-add,dept-remove, andai-context-rebuildhave documented contracts but no implementation scripts yet — do NOT promise users those sub-ops are operational. - Anchor format is NOT GitHub-Markdown-standard. GitHub Wiki strips emojis, but multiple consecutive hyphens are NOT collapsed. Single space →
-,→(space-arrow-space) →--. Always readreferences/anchor-format.mdbefore authoring or validating any cross-page link. - Ownership markers are load-bearing.
<!-- ai-owned -->regions are mutable byupdate;<!-- human-owned -->regions are NEVER touched. Skipping the marker = AI overwrites human prose. Both markers are required on every page region. - canonical_files[] paths are repo-relative to the GAME repo, not the wiki repo. They point at the source of truth (game code/CSV), not at wiki pages. The CI staleness gate crosses the repo boundary using the deploy-key auth model (Adoption-Spec § “Open Questions for /t1k:plan” — Q2 deploy key vs GitHub App resolution).
- Do NOT regenerate
team.departments[]from sidebar or page list. SSOT isAI-Context.mdonly. Reverse derivation breaks the audit trail and conflicts withdept-add/dept-removeprovenance tracking. - Art-style is gating, not informational.
team.artStyleis a hard gate, not a hint —createfilters the Departments bucket roster by it,updaterejects incompatible ai-owned inserts,validateerrors on drift. A legacy wiki withoutteam.artStyleMUST be migrated on first run; do NOT silently default tohybrid-2D-3D“to be safe” — that’s exactly the failure mode that let 3D content leak into a 2D-only game (incident + full detail:references/gotchas-history.md). - Build & Ops ≠ design meta. The
📦 Build & Opssidebar bucket is for Build-Release + Telemetry + LiveOps + Open-Issues — CI/CD, ops dashboards, engineering issue log. Currency/IAP/Battle-Pass/Social/Clan/Daily-Missions/Dungeons/PvP belong in🌀 Meta & Events, not here. Validator emits ERROR if anyteam.metaSystems[].pagelives under📦 Build & Ops(incident this gate was added for:references/gotchas-history.md). - One archetype per page in Meta & Events. Bundling multiple event archetypes (e.g., a single “Events” page listing Double-Drop / Forge-Rush / Anniversary / etc. as
###subsections) is forbidden by the validator. Each archetype gets its own page so the LiveOps team can author them independently andmeta-add/meta-removeoperates at the right granularity.validateflags ≥2 inline###event archetypes on the same page as a WARNING. - A wiki section with more than 5 subpages needs an
Index.md. Without one, subpage discovery falls back to sidebar scanning and contributors duplicate pages instead of finding siblings. Index carries per page: title, one-line summary, last-verified date.validateshould flag any section past the threshold with noIndex.md(source + detail:references/gotchas-history.md). - 5 R5 open questions block full operational readiness: (1) where
/update-wikiexecutes, (2) deploy key vs GitHub App, (3) LFS for binary attachments, (4) validator severity during rollout, (5) canonical_files-deleted behavior. Surface these to the user when first activating the skill against a new project.