@ericrisco/rsc 0.1.34 → 0.1.36

package/README.md

@@ -12,7 +12,7 @@
   ██    ██   ███████     ███████ 
 ```
 
-# `rsc` — 231 agent skills, one CLI, zero bloat
+# `rsc` — 242 agent skills, one CLI, zero bloat
 
 **A self-recommending skill catalog for 17 coding assistants** — Claude Code,
 Codex, GitHub Copilot, Cursor, Gemini, Windsurf, Cline, Antigravity, Zed and more.
@@ -243,7 +243,7 @@ just asks in plain language.
 
 ## The catalog
 
-232 skills, grouped by what you're trying to do. Click any skill to read its
+243 skills, grouped by what you're trying to do. Click any skill to read its
 `SKILL.md`. It fires on its own when a task matches.
 
 ### 🧭 Core & control plane
@@ -256,6 +256,26 @@ The front door and the workspace brain.
 > self-improving wiki. It governs software *or* a whole company. **orient** is the
 > always-on compass that keeps a non-technical human oriented after every step.
 
+> #### 📦 The `02-DOCS/` brain is now 100% Open Knowledge Format (OKF v0.1) conformant
+>
+> Google Cloud published the [**Open Knowledge Format**](https://github.com/GoogleCloudPlatform/knowledge-catalog/tree/main/okf)
+> — a vendor-neutral standard for portable, agent-readable knowledge — built on the
+> same Karpathy *LLM-wiki* pattern our `02-DOCS/` engine has used from day one. We
+> independently converged on the same design, so adopting the standard cost almost
+> nothing. As of now, **every `02-DOCS/wiki/` is a valid, portable OKF bundle**:
+>
+> - **Markdown + YAML frontmatter**, `type` on every concept doc, OKF-standard
+>   fields (`title`, `description`, `resource`, `tags`, `timestamp`).
+> - **Standard markdown links** (not wikilinks) form the knowledge graph — any OKF
+>   consumer reads it, *and* it stays a native Obsidian vault (graph, backlinks,
+>   Properties, Bases). Same files, no export step.
+> - **Reserved files** honored: `index.md` (no frontmatter) for navigation,
+>   `log.md` (newest-first, ISO 8601) for history.
+>
+> Tarball a `wiki/` and any OKF tool — including Google's own viewer — can read it.
+> And the brain now **keeps your repo clean**: a loose file it ingests (a PDF at the
+> root, anything in `inbox/`) is *moved* into `raw/`, never left as clutter.
+
 ### 📐 Spec-Driven Development
 Take a fuzzy intent to a shipped, verified change — phase by phase. `npx @ericrisco/rsc install --profile core`.
 
@@ -306,6 +326,12 @@ Each with a `02-DOCS` feedback loop that learns from your own results. `remotion
 
 [fastapi](skills/fastapi/) · [nextjs](skills/nextjs/) · [react](skills/react/) · [react-native](skills/react-native/) · [vue-nuxt](skills/vue-nuxt/) · [angular](skills/angular/) · [svelte](skills/svelte/) · [astro](skills/astro/) · [solid-js](skills/solid-js/) · [htmx](skills/htmx/) · [nodejs](skills/nodejs/) · [nestjs](skills/nestjs/) · [django](skills/django/) · [laravel](skills/laravel/) · [rails](skills/rails/) · [spring-boot](skills/spring-boot/) · [phoenix](skills/phoenix/) · [flutter](skills/flutter/) · [swift-ios](skills/swift-ios/) · [kotlin-android](skills/kotlin-android/) · [compose-multiplatform](skills/compose-multiplatform/) · [expo](skills/expo/) · [tauri](skills/tauri/) · [electron](skills/electron/) · [rust](skills/rust/) · [wordpress](skills/wordpress/) · [shopify](skills/shopify/) · [no-code-app](skills/no-code-app/) · [chrome-extension](skills/chrome-extension/) · [api-design](skills/api-design/)
 
+### 🎮 Game development
+
+Three engines + engine-agnostic disciplines. Every engine skill pins the current version and bans deprecated APIs, so the agent stops emitting stale Godot-3 / legacy-Unity code.
+
+[godot](skills/godot/) · [unity](skills/unity/) · [unreal](skills/unreal/) · [game-design](skills/game-design/) · [game-storytelling](skills/game-storytelling/) · [level-design](skills/level-design/) · [gamedev-shaders](skills/gamedev-shaders/) · [gamedev-multiplayer](skills/gamedev-multiplayer/) · [gamedev-physics](skills/gamedev-physics/) · [gamedev-pathing](skills/gamedev-pathing/) · [gamedev-shipping](skills/gamedev-shipping/)
+
 ### 🗄️ Databases & data layer
 
 [postgresdb](skills/postgresdb/) · [mysql](skills/mysql/) · [mongodb](skills/mongodb/) · [redis](skills/redis/) · [supabase](skills/supabase/) · [neon](skills/neon/) · [planetscale](skills/planetscale/) · [sqlite-turso](skills/sqlite-turso/) · [prisma-orm](skills/prisma-orm/) · [drizzle-orm](skills/drizzle-orm/) · [firebase](skills/firebase/) · [dynamodb](skills/dynamodb/) · [vector-db](skills/vector-db/) · [clickhouse-analytics](skills/clickhouse-analytics/) · [duckdb](skills/duckdb/) · [db-migrations](skills/db-migrations/) · [backups](skills/backups/)

package/manifest.json

@@ -1,7 +1,7 @@
 {
-  "version": "0.1.34",
+  "version": "0.1.36",
   "counts": {
-    "skills": 232
+    "skills": 243
   },
   "skills": [
     {
@@ -1737,6 +1737,156 @@
       ],
       "profiles": []
     },
+    {
+      "id": "game-design",
+      "description": "Use when designing or repairing the design of a game — inventing mechanics and systems, shaping the core loop, layering moment-to-moment / session / meta loops, planning progression, economy, currencies and sinks/faucets, tuning difficulty curves and balance, killing dominant strategies, adding 'juice'/game feel as design intent, prototyping and playtesting, or controlling scope, and especially when the ask is 'why isn't my game fun'. Triggers: 'design the core loop', 'my game isn't fun / doesn't hook', 'balance the economy', 'the difficulty curve feels off', 'players found a dominant strategy', 'how do I scope this', 'reward / progression loop', 'diseñar la mecánica', 'el juego no engancha', 'com equilibro l'economia'. NOT writing engine code, scripts or shaders (route to godot/unity/unreal), NOT narrative, dialogue or story beats (route to game-storytelling), NOT level layout or encounter placement (route to level-design).",
+      "tags": [
+        "game-design",
+        "mechanics",
+        "core-loop",
+        "balancing",
+        "progression",
+        "playtesting",
+        "scope",
+        "fun"
+      ],
+      "recommends": [
+        "level-design",
+        "game-storytelling",
+        "godot",
+        "unity",
+        "unreal"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
+    {
+      "id": "game-storytelling",
+      "description": "Use when designing a game's STORY as an interactive system: premise, theme and narrative pillars; branching narrative and meaningful choice; dialogue trees with state and flags; quests, objectives and fail states; worldbuilding; environmental and systemic storytelling; and keeping story in harmony with play (avoiding ludonarrative dissonance). Engine-agnostic — it designs the narrative graph, variables and beats, then hands the wiring to the engine skill. Triggers: 'write my game's story/premise', 'branching narrative', 'dialogue system/tree', 'quest structure', 'worldbuilding', 'meaningful choices', 'illusion of choice', 'Ink/Yarn Spinner/Twine/articy narrative', 'story keeps fighting the gameplay'. NOT core mechanics, systems or balance (that's game-design); NOT spatial/level layout or encounter placement (that's level-design); NOT the actual dialogue-node code, save format or plugin wiring inside an engine (that's godot/unity/unreal).",
+      "tags": [
+        "game",
+        "narrative",
+        "story",
+        "dialogue",
+        "quest",
+        "branching",
+        "worldbuilding"
+      ],
+      "recommends": [
+        "game-design",
+        "level-design"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
+    {
+      "id": "gamedev-multiplayer",
+      "description": "Use when adding multiplayer, netcode, or replication to a game — syncing players/state across a network, online co-op or PvP, client-server vs peer-to-peer, server-authoritative design, client-side prediction + server reconciliation, snapshot interpolation, lag compensation, tick/netrate, and per-engine wiring: Godot 4.x MultiplayerSpawner/MultiplayerSynchronizer/@rpc/ENetMultiplayerPeer/set_multiplayer_authority, Unity Netcode for GameObjects (NetworkObject/NetworkBehaviour/NetworkVariable/[Rpc]/ServerRpc/ClientRpc), Unreal Actor replication (Replicated/ReplicatedUsing, Server/Client/NetMulticast RPCs, relevancy). Triggers: 'how do I sync players', 'client and server desync', 'players rubber-band or teleport', 'who has authority', 'laggy movement', 'cheater set their own health'. NOT single-player gameplay, AI, or input (route to engine skill godot/unity/unreal), and NOT matchmaking, dedicated-server hosting, or backend infra (route to deployment).",
+      "tags": [
+        "multiplayer",
+        "netcode",
+        "replication",
+        "networking",
+        "prediction",
+        "authority"
+      ],
+      "recommends": [
+        "godot",
+        "unity",
+        "unreal",
+        "gamedev-physics"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
+    {
+      "id": "gamedev-pathing",
+      "description": "Use when implementing AI navigation or pathfinding in a game - moving enemies/NPCs/units toward goals, \\\"how do enemies navigate the level\\\", A*/Dijkstra/JPS/HPA* search, choosing grid vs waypoint-graph vs navmesh, baking a navmesh and tuning agent radius/height, off-mesh/nav links, dynamic obstacles and re-baking, steering (seek/flee/arrive/pursue/wander/path-following/flocking), local avoidance (RVO/ORCA, crowds), and flow fields for many agents to one goal. Per-engine: Godot 4.x (NavigationServer2D/3D, NavigationRegion, NavigationAgent, get_next_path_position), Unity (NavMeshAgent + NavMeshObstacle + AI Navigation baking), Unreal (RecastNavMesh + AIController + Behavior Trees/EQS). Triggers: \\\"my enemies get stuck\\\", \\\"units clump together\\\", \\\"navmesh not updating\\\", \\\"agentes se atascan\\\". NOT physics/rigidbody collision response or character-controller tuning (gamedev-physics), and NOT high-level enemy AI behaviour design like aggro/states/difficulty (game-design).",
+      "tags": [
+        "pathfinding",
+        "navmesh",
+        "navigation",
+        "steering",
+        "a-star"
+      ],
+      "recommends": [
+        "godot",
+        "unity",
+        "unreal",
+        "gamedev-physics"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
+    {
+      "id": "gamedev-physics",
+      "description": "Use when working with a game engine's physics — rigid bodies, colliders, collision layers/masks, character controllers, joints, forces vs impulses, raycasts/shapecasts, or when physics is unstable. Triggers: \\\"my character falls through the floor\\\", \\\"bullet tunnels through walls at high speed\\\", \\\"rigidbody jitters / vibrates / explodes\\\", \\\"objects that should collide pass through each other\\\", \\\"which collision layer and mask do I set\\\", \\\"kinematic vs dynamic body\\\", \\\"move_and_slide / CharacterBody\\\", \\\"AddForce vs impulse vs setting velocity\\\", \\\"physics in FixedUpdate or _physics_process\\\", \\\"slope and step detection\\\", \\\"trigger / Area overlap not firing\\\", Godot RigidBody/StaticBody/CharacterBody/Area, Unity Rigidbody/Collider/CharacterController, Unreal Chaos/collision presets. NOT rendering, materials, or visual jitter from shaders (use gamedev-shaders); NOT AI navigation, pathfinding, or navmesh (use gamedev-pathing).",
+      "tags": [
+        "physics",
+        "collision",
+        "rigidbody",
+        "character-controller",
+        "colliders"
+      ],
+      "recommends": [
+        "godot",
+        "unity",
+        "unreal",
+        "gamedev-pathing"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
+    {
+      "id": "gamedev-shaders",
+      "description": "Use when writing shaders, materials, VFX, or post-processing for a game engine, or asking \\\"how do I make this effect\\\" — covers the vertex→fragment pipeline, UVs / normals / coordinate spaces, and per-engine authoring in Godot 4.x (shader_type spatial/canvas_item/particles, source_color, hint_screen_texture, ShaderMaterial), Unity 6 (Shader Graph vs HLSL, URP/HDRP, ShaderLab), and Unreal 5.x (Material graph, material domains, Custom HLSL node). Includes recipes for dissolve, rim/outline, toon/cel, water/flow, force field, hologram; full-screen post-process; and shader performance (overdraw, texture-sample cost, branching, mobile). Triggers: \\\"write a dissolve shader\\\", \\\"rim light\\\", \\\"toon shading\\\", \\\"screen-space effect\\\", \\\"my shader is slow on mobile\\\", \\\"cómo hago un shader de agua\\\". NOT gameplay or engine-API code (→ godot / unity / unreal) and NOT physics simulation, collision, or rigid bodies (→ gamedev-physics).",
+      "tags": [
+        "shaders",
+        "vfx",
+        "materials",
+        "post-processing",
+        "shadergraph"
+      ],
+      "recommends": [
+        "godot",
+        "unity",
+        "unreal",
+        "gamedev-shipping"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
+    {
+      "id": "gamedev-shipping",
+      "description": "Use when exporting, building, packaging, or publishing a game — per engine (Godot export templates, Unity Build Profiles, Unreal Shipping vs Development) and per platform: desktop (Windows/macOS/Linux; macOS codesign + notarytool notarization), web (the COOP same-origin + COEP require-corp headers threaded SharedArrayBuffer WebAssembly builds need, and that Godot's C#/.NET edition can't export to web), mobile (Android JDK 17 build template, AAB vs APK, release keystore; iOS provisioning). Also store prep (icons/splash, metadata, age ratings, AAB for Play, Mac App Store, Steamworks/SteamPipe, itch.io butler), headless-export CI/CD, build/version numbers, and ship-time size/startup optimization. Triggers: 'export my game', 'build for Steam', 'ship to web/mobile', 'publish to the Play Store', 'notarize my Mac build', 'itch.io upload', 'SharedArrayBuffer is not defined'. NOT for writing gameplay/runtime code (that's the engine skill — godot/unity/unreal) or hosting a normal web app/API/container (→ deployment).",
+      "tags": [
+        "export",
+        "build",
+        "release",
+        "packaging",
+        "store",
+        "steam",
+        "itch",
+        "notarization",
+        "webassembly",
+        "aab"
+      ],
+      "recommends": [
+        "godot",
+        "unity",
+        "unreal",
+        "deployment"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
     {
       "id": "gcp-essentials",
       "description": "Use when running a small product on the core of Google Cloud with the gcloud CLI: creating a project, deploying a container to Cloud Run, standing up a Cloud Storage bucket, a managed Cloud SQL Postgres/MySQL, and wiring them together with least-privilege IAM. Triggers: 'deploy to Cloud Run', 'gcloud run deploy', 'set up a GCP project', 'crear bucket en GCP', 'desplegar a Cloud Run', 'service account sin claves JSON', 'why is my Cloud Run running as the default service account', 'connect Cloud Run to Cloud SQL', 'turn off the bucket public access'. NOT AWS (that is aws-essentials).",
@@ -1845,6 +1995,29 @@
       ],
       "profiles": []
     },
+    {
+      "id": "godot",
+      "description": "Use when writing, reviewing, or debugging Godot 4.x games in GDScript (typed) or C# — nodes/scenes/custom Resources, autoload singletons and an EventBus, signals via Callable, @onready/@export/@tool, static typing, CharacterBody2D/3D + velocity + move_and_slide(), _process vs _physics_process, .tscn/.tres text formats, and headless GUT/gdUnit4 tests. Enforces Godot 4 APIs and rejects Godot 3 leftovers: yield→await, onready→@onready, .instance()→.instantiate(), KinematicBody→CharacterBody, Spatial→Node3D, string connect(\\\"sig\\\",obj,\\\"m\\\")→Callable. Triggers: 'write a Godot player controller', 'my move_and_slide does nothing', 'port this Godot 3 script to 4', 'connect a signal in Godot', 'GDScript won't type-check', 'CharacterBody2D won't move', 'add an autoload', 'escribe un script de Godot', 'por qué no se mueve mi personaje'. NOT Unity MonoBehaviour or Unreal (route to unity/unreal); NOT pure C++/CMake tooling unrelated to GDExtension (that is cpp); NOT shader code in .gdshader (that is gamedev-shaders).",
+      "tags": [
+        "godot",
+        "gdscript",
+        "game-dev",
+        "csharp",
+        "godot4"
+      ],
+      "recommends": [
+        "gamedev-shaders",
+        "gamedev-multiplayer",
+        "gamedev-physics",
+        "gamedev-pathing",
+        "gamedev-shipping",
+        "game-design",
+        "cpp"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
     {
       "id": "google-workspace",
       "description": "Use when building server-side automation that reads or writes Gmail, Drive, Calendar, or Sheets against a real Google Workspace account via the official client libraries and a GCP service account — picking the auth mode, scoping OAuth scopes, building the authed client, and debugging 403/429/unauthorized_client errors. Triggers: 'send mail from a service account in a cron', 'unauthorized_client when impersonating a user', 'which Drive scope to upload to a shared drive', 'set up domain-wide delegation client ID', 'getting 403 insufficient permissions from the Sheets API', 'automatizar Gmail con cuenta de servicio sin login del usuario', 'enviar correos desde un script sense login d'usuari'. NOT generic SMTP/marketing/deliverability email (that is email-connector).",
@@ -2289,6 +2462,26 @@
       ],
       "profiles": []
     },
+    {
+      "id": "level-design",
+      "description": "Use when designing a game level, map, arena, or encounter — laying out a blockout/greybox, fixing pacing that drags or spikes, guiding players without hand-holding, placing secrets and rewards, or diagnosing a level that plays as boring, confusing, or where players get lost or stuck. Engine-agnostic craft: the blockout->greybox->playtest->art pipeline, sightlines and landmarks, tension/release rhythm, the introduce->develop->twist->combine encounter progression, readability via light/color/composition, and traversal heatmaps. Triggers: 'design this level', 'my level is boring/confusing', 'players keep getting lost', 'how do I pace this', 'blockout', 'greybox', 'encounter design', 'where do I put the secret'. NOT systemic mechanics or economy tuning (that's game-design), NOT narrative or story beats (that's game-storytelling), and NOT engine-specific level tooling — nav meshes, occlusion, tilemap editors, lightmap baking (that's the godot/unity/unreal skill).",
+      "tags": [
+        "level-design",
+        "blockout",
+        "pacing",
+        "encounter",
+        "playtest"
+      ],
+      "recommends": [
+        "game-design",
+        "godot",
+        "unity",
+        "unreal"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
     {
       "id": "linkedin-api",
       "description": "Use when wiring an app to LinkedIn's organic Posts / Community Management API — completing 3-legged OAuth, publishing text/article/document posts to a member profile or company page, or pulling impressions/engagement/follower stats and logging them as a durable feedback record. Triggers: 'connect our app to the LinkedIn Posts API', 'publish to our company page programmatically', 'pull last month's impressions for our org posts', 'my /v2/ugcPosts call returns 403', 'unauthorized scope w_organization_social at consent', 'log post performance into the wiki', 'publica a la pàgina de LinkedIn per API', 'conectar la API de LinkedIn y traer las impresiones'. NOT writing the post copy (that is linkedin-content), planning cadence (that is linkedin-strategy), or DM sequences (that is linkedin-outreach).",
@@ -4474,6 +4667,52 @@
       ],
       "profiles": []
     },
+    {
+      "id": "unity",
+      "description": "Use when writing, reviewing, or structuring Unity game code in C# for current Unity 6 LTS (6000.x) — GameObjects and Transform hierarchy, MonoBehaviour lifecycle, prefabs and prefab variants, ScriptableObjects for data, scenes and additive loading, the new Input System, coroutines vs async/await/Awaitable, Addressables, and build/player settings for 2D and 3D. Triggers: 'my Unity script', 'Awake vs Start', 'why is my physics jittery', MonoBehaviour .cs files, 'set up the new Input System', 'ScriptableObject config', 'load a scene additively', 'Instantiate a prefab', 'convert Input.GetAxis to the new system', 'build for Android/WebGL', 'por qué no se llama mi Start', 'com carrego una escena en additiu'. NOT Godot/GDScript (that is godot); NOT Unreal/Blueprint/C++ engine work (that is unreal); NOT the netcode wire protocol itself (that is gamedev-multiplayer).",
+      "tags": [
+        "unity",
+        "csharp",
+        "game-dev",
+        "monobehaviour",
+        "input-system"
+      ],
+      "recommends": [
+        "gamedev-multiplayer",
+        "gamedev-physics",
+        "gamedev-shaders",
+        "gamedev-pathing",
+        "gamedev-shipping",
+        "godot",
+        "unreal"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
+    {
+      "id": "unreal",
+      "description": "Use when building, scripting, or debugging a game in Unreal Engine 5 (UE5) with Blueprint and/or C++ — gameplay framework (Actor/Pawn/Character/GameMode/PlayerController), Actor lifecycle and tick, UPROPERTY/UFUNCTION/UCLASS reflection and garbage collection, Enhanced Input, dynamic multicast delegates, UMG widgets, Paper2D sprites/flipbooks, and Blueprint↔C++ parity (exposing C++ to Blueprint, calling Blueprint from C++). Triggers: \\\"UE5\\\", \\\"Unreal\\\", \\\"Blueprint\\\", \\\"make a Character in C++\\\", \\\"expose this to Blueprint\\\", \\\"BlueprintCallable\\\", \\\"why is my UObject garbage collected\\\", \\\"Enhanced Input mapping context\\\", \\\"UMG widget\\\", \\\"Paper2D flipbook\\\", \\\".uproject\\\", \\\"GameMode vs GameState\\\". NOT for Godot (→ godot), NOT for Unity/C#/MonoBehaviour (→ unity), NOT for language-only C++ memory/RAII questions with no Unreal types (→ cpp).",
+      "tags": [
+        "unreal",
+        "ue5",
+        "blueprint",
+        "unreal-engine",
+        "gamedev"
+      ],
+      "recommends": [
+        "cpp",
+        "gamedev-shipping",
+        "gamedev-multiplayer",
+        "game-design",
+        "gamedev-physics",
+        "godot",
+        "unity"
+      ],
+      "profiles": [
+        "full"
+      ]
+    },
     {
       "id": "vector-db",
       "description": "Use when operating a vector store as a data layer — choosing or migrating between Pinecone, Qdrant, Weaviate, or pgvector; designing a collection/index (distance metric, dimensions, HNSW m/ef_construction, named vectors); filtering on metadata/payload; running hybrid dense+sparse search; or picking quantization to cut RAM and cost. Symptoms: search returns garbage, filters get silently ignored, recall is low, queries are slow, the bill is too high, a filtered query returns fewer than k rows. Triggers: 'set up a vector database', 'my similarity search ignores the metadata filter', 'ef_search vs recall', 'move off Pinecone to pgvector to cut cost', 'hybrid search with RRF', 'why does my filtered query return fewer than k results', 'crear una colección en Qdrant con cuantización binaria', 'la cerca vectorial retorna resultats dolents'. NOT how to produce, chunk, or judge embeddings (that is embeddings-search).",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ericrisco/rsc",
-  "version": "0.1.34",
+  "version": "0.1.36",
   "description": "Eric Risco's agent-skills catalog as a granular, self-recommending CLI installer.",
   "type": "module",
   "bin": {

package/scripts/lib/domains.js

@@ -17,6 +17,7 @@ export const DOMAINS = [
   { title: 'AI — run it on', ids: ['replicate', 'runpod', 'modal', 'huggingface', 'ollama', 'together-fireworks', 'fal'] },
   { title: 'Languages', ids: ['typescript', 'python', 'java', 'csharp-dotnet', 'php', 'ruby', 'cpp', 'elixir', 'bash-scripting', 'sql', 'go'] },
   { title: 'Frameworks & app stacks', ids: ['fastapi', 'nextjs', 'react', 'react-native', 'vue-nuxt', 'angular', 'svelte', 'astro', 'solid-js', 'htmx', 'nodejs', 'nestjs', 'django', 'laravel', 'rails', 'spring-boot', 'phoenix', 'flutter', 'swift-ios', 'kotlin-android', 'compose-multiplatform', 'expo', 'tauri', 'electron', 'rust', 'wordpress', 'shopify', 'no-code-app', 'chrome-extension', 'api-design'] },
+  { title: 'Game development', ids: ['godot', 'unity', 'unreal', 'game-design', 'game-storytelling', 'level-design', 'gamedev-shaders', 'gamedev-multiplayer', 'gamedev-physics', 'gamedev-pathing', 'gamedev-shipping'] },
   { title: 'Databases & data layer', ids: ['postgresdb', 'mysql', 'mongodb', 'redis', 'supabase', 'neon', 'planetscale', 'sqlite-turso', 'prisma-orm', 'drizzle-orm', 'firebase', 'dynamodb', 'vector-db', 'clickhouse-analytics', 'duckdb', 'db-migrations', 'backups'] },
   { title: 'Ship & operate — platforms', ids: ['vercel', 'netlify', 'cloudflare', 'railway', 'render', 'fly-io', 'coolify', 'hetzner', 'digitalocean', 'aws-essentials', 'gcp-essentials'] },
   { title: 'Ship & operate — devops', ids: ['docker', 'github-actions', 'git-workflow', 'domains-dns', 'monitoring', 'email-deliverability', 'scaling', 'deployment'] },

package/scripts/lib/recommend.js

@@ -16,6 +16,10 @@ const OUTCOMES = {
   'building-agents': 'Your own AI agent',
   'secure-coding': 'Make it secure',
   deployment: 'Put it online',
+  godot: 'Your game (Godot)',
+  unity: 'Your game (Unity)',
+  unreal: 'Your game (Unreal)',
+  'game-design': "Design a game that's fun",
 };
 
 export function hasOutcome(id) {

package/skills/agent-eval/SKILL.md

@@ -199,7 +199,7 @@ Pick by where the eval runs and what it must do. Versions as of 2026-06 — re-v
 
 ## Project grounding
 
-If the workspace has a `02-DOCS/` harness, record the eval policy in `02-DOCS/wiki/stack/evals.md`: dataset location, scorer mix, gate baseline file, judge model, and the failure modes covered. Index it in `02-DOCS/wiki/index.md` (the Knowledge map; root `CLAUDE.md` keeps only a short pointer). This is **recorded, not gated** — skip silently if there is no harness.
+If the workspace has a `02-DOCS/` harness, record the eval policy in `02-DOCS/wiki/stack/evals.md`: dataset location, scorer mix, gate baseline file, judge model, and the failure modes covered. Write it as an OKF v0.1 wiki article per the harness [`wiki-article-template.md`](../harness/references/wiki-article-template.md): open with YAML frontmatter carrying a non-empty `type:` (use `type: stack`), `timestamp` in ISO 8601, and standard markdown links — never wikilinks. Index it in `02-DOCS/wiki/index.md` (the Knowledge map; root `CLAUDE.md` keeps only a short pointer). This is **recorded, not gated** — skip silently if there is no harness.
 
 ## verify.sh
 

package/skills/analyze/SKILL.md

@@ -112,7 +112,7 @@ Produce a single consistency report:
 3. **Findings table** — `# | Severity | Type | Artifact A (loc) | Artifact B (loc) | Conflict | Resolve in (phase)`.
 4. **Recommended routing** — group fixes by the phase that owns them (`clarify` for spec ambiguity, `plan` for missing architecture, `tasks` for a missing done-check, `constitution` if a principle itself is wrong).
 
-Write the report to `02-DOCS/wiki/sdd/analysis/<slug>.md` (create the dir if absent) and index it in `02-DOCS/wiki/index.md` (the Knowledge map; root `CLAUDE.md` keeps only a short pointer) under the `sdd/` topic, so the next phase and the harness can find it. The report is the artifact analyze owns — it is the *only* thing analyze writes. Per-run point-in-time; overwrite on re-run, the wiki keeps history.
+Write the report to `02-DOCS/wiki/sdd/analysis/<slug>.md` (create the dir if absent) and index it in `02-DOCS/wiki/index.md` (the Knowledge map; root `CLAUDE.md` keeps only a short pointer) under the `sdd/` topic, so the next phase and the harness can find it. It is an OKF v0.1 wiki article: open it with YAML frontmatter carrying a non-empty `type:` (use `type: analysis`), a `timestamp` in ISO 8601, and standard markdown links — never wikilinks. The report is the artifact analyze owns — it is the *only* thing analyze writes. Per-run point-in-time; overwrite on re-run, the wiki keeps history.
 
 Adapt the rendered verbosity to the dial (L0 = table only; L3 = full walk-through). Do not log a decision to `decisions.md` — analyze decides nothing; the phase that resolves the finding logs its own decision.
 

package/skills/brand-voice/SKILL.md

@@ -150,7 +150,7 @@ Tone by context: onboarding=warm; error=plain+reassuring, no humor;
   success=light warmth, no hype; billing=precise+calm; legal=formal+exact.
 ```
 
-**Persist it.** Write the compiled guide under `02-DOCS/wiki/brand/voice-guide.md` and the voice-DNA block beside it, per the `harness` Karpathy-wiki convention (compiled brand articles under `02-DOCS/wiki/brand/`, raw user inputs under `02-DOCS/raw/brand/`). This is the exact study `marketing`, `landing-copy`, and `content-engine` read to ground their copy. A guide in a slide deck is invisible to them.
+**Persist it.** Write the compiled guide under `02-DOCS/wiki/brand/voice-guide.md` and the voice-DNA block beside it, per the `harness` Karpathy-wiki convention (compiled brand articles under `02-DOCS/wiki/brand/`, raw user inputs under `02-DOCS/raw/brand/`). The persisted file is an OKF v0.1 wiki article: open it with YAML frontmatter carrying a non-empty `type:` (use `type: brand-voice`) — see the frontmatter block in [`references/voice-guide-template.md`](references/voice-guide-template.md). This is the exact study `marketing`, `landing-copy`, and `content-engine` read to ground their copy. A guide in a slide deck is invisible to them.
 
 ## Auditing for drift
 

package/skills/brand-voice/references/voice-guide-template.md

@@ -2,6 +2,20 @@
 
 Fill every slot. Delete the instruction lines in italics before you ship. The finished file lives at `02-DOCS/wiki/brand/voice-guide.md`. A fully worked mini-example follows the blank template — copy its shape, not its content.
 
+The persisted guide is an OKF v0.1 wiki article: it MUST open with YAML frontmatter carrying a non-empty `type`. Copy the block below verbatim to the top of `02-DOCS/wiki/brand/voice-guide.md`, fill the values, and set `timestamp` to the ISO 8601 datetime of the edit:
+
+```yaml
+---
+type: brand-voice
+title: <brand> — Voice & Tone Guide
+description: How the <brand> brand sounds — traits, rules, dimensions, word bank, and AI voice-DNA.
+tags: [brand-voice, tone-of-voice, voice-guide]
+timestamp: YYYY-MM-DDTHH:MM:SSZ
+topic: brand
+status: stable
+---
+```
+
 ---
 
 ## Blank template

package/skills/building-agents/SKILL.md

@@ -454,9 +454,9 @@ agent inherits the conventions instead of re-deriving them.
 
 1. **Find the article** `02-DOCS/wiki/stack/agents.md`, indexed in `02-DOCS/wiki/index.md` (the Knowledge map index; root `CLAUDE.md` points to it).
 2. **If missing or stale**, create/update it with the project's real choices — the provider(s) and model routing, where the provider adapter lives, tool/RAG conventions, the eval gates, and the observability backend —
-   then index it in `02-DOCS/wiki/index.md` (the Knowledge map; root `CLAUDE.md` keeps only a short pointer to it).
+   then index it in `02-DOCS/wiki/index.md` (the Knowledge map; root `CLAUDE.md` keeps only a short pointer to it). Write it as an OKF v0.1 wiki article per the harness [`wiki-article-template.md`](../harness/references/wiki-article-template.md): open with YAML frontmatter carrying a non-empty `type:` (use `type: stack`), and use standard markdown links — never wikilinks.
 3. **Read it first on every use** and stay consistent; when a convention changes, update the
-   article (bump its `Updated` date) in the same change.
+   article (bump its `timestamp`) in the same change.
 
 No `02-DOCS/` layer? Skip silently (optionally suggest `harness`). Unlike the
 brand study, technical conventions are *recorded, not gated* — never block the task on this.

package/skills/competitor-watch/SKILL.md

@@ -122,10 +122,15 @@ Good: 2026-05-20 · pricing · Acme · acme.com/pricing
 ## The tracker artifacts
 
 Three structured files. Required fields named here; full schema + a filled end-to-end example
-competitor live in `references/tracker-schema.md`.
-
-- **Competitor profile** (one per rival): `name`, `positioning_line`, `segment`, pricing tiers
-  (each with `amount`, `currency`, `source_url`, `date`), feature-matrix rows, watched URLs.
+competitor live in `references/tracker-schema.md`. The profile is a `.md` page under the
+`02-DOCS/wiki/` OKF v0.1 bundle, so its YAML frontmatter carries a non-empty `type: competitor`
+(plus the OKF-recommended `title`/`description`/`tags`/`timestamp`) alongside the domain keys;
+its body uses standard markdown links, never wikilinks. The two CSVs are data files, not OKF
+documents.
+
+- **Competitor profile** (one per rival): OKF frontmatter (`type: competitor`, …) + the domain
+  keys `name`, `positioning_line`, `segment`, pricing tiers (each with `amount`, `currency`,
+  `source_url`, `date`), feature-matrix rows, watched URLs.
 - **Feature matrix** (CSV): rows = features, columns = competitors, each cell sourced + dated.
 - **Change log** (CSV, append-only): `date,competitor,axis,url,old_value,new_value,materiality,action`.
 

package/skills/competitor-watch/references/tracker-schema.md

@@ -5,12 +5,28 @@ captures (the diffed HTML/JSON snapshots) go under `02-DOCS/raw/competitors/<riv
 rule that overrides everything: **a price or feature cell without a `source_url` + `date` is
 not knowledge — leave it blank and say so.**
 
+`02-DOCS/wiki/` is an OKF v0.1 bundle, so the one `.md` file here (the competitor profile)
+carries YAML frontmatter with a non-empty `type:`; the two CSVs are data files, not OKF
+documents. Any cross-references in the profile body use **standard markdown links** (e.g.
+`[Beta](./beta.md)`), never wikilinks. See `../../harness/references/wiki-protocol.md`
+"## Conventions".
+
 ## 1. Competitor profile (one file per rival)
 
 Markdown front-matter + body. One per rival, named `02-DOCS/wiki/competitors/<rival>.md`.
+The frontmatter is OKF v0.1 conformant: `type:` is the only required field (non-empty);
+`title`/`description`/`tags`/`timestamp` are the recommended standard surface. All the
+domain keys below (`name`, `positioning_source.date`, every `pricing_tiers[].date`, …) are
+kept verbatim — OKF allows any extra key and `verify.sh` reads them, so adding the OKF
+fields is purely additive.
 
 ```yaml
 ---
+type: competitor
+title: Acme
+description: "Tracker of record for Acme — positioning, pricing tiers, and watched surfaces."
+tags: [competitor, pricing-watch, feature-watch]
+timestamp: 2026-05-28T00:00:00Z
 name: Acme
 positioning_line: "The all-in-one workspace for remote-first teams"
 positioning_source: { url: "https://acme.com", date: "2026-05-28" }
@@ -28,6 +44,9 @@ pricing_tiers:
 
 ## Notes
 Repositioned from "project tool" to "workspace" in Q2 2026 — see change log 2026-05-12.
+
+## Related
+- [Beta](./beta.md) — closest competing positioning; cross-watch their pricing moves.
 ```
 
 Every `pricing_tiers` row and any feature claim must carry `source_url` + `date`. If you only

package/skills/constitution/references/constitution-template.md

@@ -5,6 +5,16 @@ Render this into `02-DOCS/wiki/sdd/constitution.md`. Keep it to 1-2 screens. Eve
 ---
 
 ```markdown
+---
+type: constitution
+title: <Project> — Constitution
+description: The non-negotiable principles every rsc-sdd phase obeys.
+tags: [sdd, constitution]
+timestamp: YYYY-MM-DDTHH:MM:SSZ
+topic: sdd
+version: v1.0.0
+---
+
 # <Project> — Constitution
 
 > Version: v1.0.0 · Ratified: YYYY-MM-DD · Last amended: YYYY-MM-DD

package/skills/content-engine/SKILL.md

@@ -79,7 +79,7 @@ date,pillar,cluster,format,owner,stage,brief_link,atomization,mix
 
 ## The brief
 
-A slot **cannot leave the `idea` stage without a brief.** One canonical brief format means consistent output regardless of who writes it. Required fields (inline minimum):
+A slot **cannot leave the `idea` stage without a brief.** One canonical brief format means consistent output regardless of who writes it. The brief is a `.md` page in the `02-DOCS/wiki/` OKF v0.1 bundle: its YAML frontmatter carries a non-empty `type: content-brief` (plus the OKF-recommended `title`/`description`/`tags`/`timestamp`) alongside the domain fields below, and any body cross-references use standard markdown links, never wikilinks. Required fields (inline minimum):
 
 - **objective** — the one outcome this piece drives.
 - **persona** — which of the 2–4 you target.

package/skills/content-engine/references/brief-and-pipeline.md

@@ -8,6 +8,13 @@ template, the stage gates, and the CSV column docs you fill in.
 Every slot carries one brief in the same shape. A slot cannot leave the `idea` stage
 without it. Store briefs under `02-DOCS/wiki/content/briefs/<slug>.md`.
 
+These briefs live in the `02-DOCS/wiki/` OKF v0.1 bundle, so each brief `.md` carries YAML
+frontmatter with a non-empty `type: content-brief` (the OKF-recommended `title`/`description`/
+`tags`/`timestamp` are added where meaningful). The domain brief fields below are kept as-is —
+OKF allows any extra key. Cross-references in the body use **standard markdown links**, never
+wikilinks (e.g. `[brand voice](../brand-voice.md)`). See
+`../../harness/references/wiki-protocol.md` "## Conventions".
+
 | Field | Required | What goes here |
 |---|---|---|
 | `objective` | yes | the one outcome (e.g. "drive activation-checklist signups") |
@@ -25,6 +32,13 @@ without it. Store briefs under `02-DOCS/wiki/content/briefs/<slug>.md`.
 
 ```markdown
 ---
+# OKF v0.1 standard surface — `type` is the only REQUIRED field (non-empty).
+type: content-brief
+title: "Onboarding activation guide — brief"
+description: "Brief of record for the flagship activation-checklist guide."
+tags: [content-brief, onboarding, flagship]
+timestamp: 2026-07-01T00:00:00Z
+# Domain brief fields (OKF allows any extra key; the pipeline + verify read these).
 slug: onboarding-activation-guide
 objective: drive activation-checklist signups from new-trial users
 persona: hands-on-ops-lead
@@ -36,7 +50,7 @@ owner: ana
 target_keyword: "saas user activation checklist"
 success_metric: 100 checklist downloads in 30 days
 atomization_intent: 10 derivatives — 3 LinkedIn, 1 X thread, 2 shorts, 1 newsletter, 3 carousels
-voice_ref: 02-DOCS/wiki/brand-voice.md
+voice_ref: ../brand-voice.md
 ---
 ```
 

package/skills/course-builder/references/grounding-and-scoping.md

@@ -46,6 +46,29 @@ Reuse the learner profile if it exists rather than re-interviewing. When you wri
 matrix, persist them there so `course-storytelling` can pick up the same grounding for the hand-off.
 Note in the file that the profile is shared, so neither skill clobbers the other's section.
 
+Each persisted `02-DOCS/wiki/teaching/*.md` file is an OKF v0.1 wiki article: open it with YAML
+frontmatter carrying a non-empty `type:` (`type: course-outline`), then the H1 and body. Use standard
+markdown links between articles (`[Outcomes](./<course>-outcomes.md)`), never wikilinks. Mirror the
+harness `wiki-article-template.md` shape:
+
+```markdown
+---
+type: course-outline
+title: <Course> — Outcomes
+description: The measurable, ABCD-complete learning outcomes for <course>.
+tags: [course, learning-outcomes]
+timestamp: YYYY-MM-DDTHH:MM:SSZ
+topic: teaching
+status: stable
+---
+
+# <Course> — Outcomes
+
+> Sources: {user interview, YYYY-MM-DD}
+
+...
+```
+
 ## Right-sizing scope by format
 
 The single most common failure is too many outcomes for the time. Honest ceilings: