[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MC8GWD3781NFBSAA59V4PR":3,"skill-same:01M6MC8GWD3781NFBSAA59V4PR":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6MC8GWD3781NFBSAA59V4PR","game-geometry-representation-choice",null,"Choose the right geometric representation for game systems before implementing rendering, collision, procedural generation, editing, or conversion code. Use when deciding between meshes, SDFs, voxels, splines, parametric surfaces, fields, or hybrid geometry workflows for games.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgame-geometry-representation-choice\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"game geometry representation choice","game","choice","geometry","procedural-generation","when","procedural generation","hybrid","for","implementing","procedural","games","rendering","workflows","surfaces","conversion","editing","choose","dev","code","development","2026-11-10 10:12:30",false,"---\nname: game-geometry-representation-choice\ndescription: Choose the right geometric representation for game systems before implementing rendering, collision, procedural generation, editing, or conversion code. Use when deciding between meshes, SDFs, voxels, splines, parametric surfaces, fields, or hybrid geometry workflows for games.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Game Geometry Representation Choice\n  category: Game Development\n  tags: game-dev,game-geometry,geometry,representation,procedural-generation\n---\n\n# Game Geometry Representation Choice\n\nUse this skill before writing geometry-heavy game code. Pick the representation\nthat makes the important operation simple, robust, and fast enough, then plan\nconversion boundaries deliberately.\n\nPrimary source: Geometry for Programmers by Oleksandr Kaleniuk\n(https:\u002F\u002Fwww.manning.com\u002Fbooks\u002Fgeometry-for-programmers), transformed and\nparaphrased, especially chapters 2 and 10-12.\n\n## Core Workflow\n\n1. Name the operation first: render, collide, pick, offset, deform, Boolean,\n   smooth motion, destruct terrain, generate props, edit geometry, or convert.\n2. List the data the game already has and the data the game ultimately needs.\n   Include textures, normals, animation bindings, gameplay tags, and LODs.\n3. Pick the working representation where the core operation is cheapest and\n   least fragile. Do not default to meshes just because rendering ends there.\n4. Define conversion boundaries: input representation, working representation,\n   output representation, resolution, tolerated error, and attribute transfer.\n5. Add invariants and tests for the representation, not just the final visual.\n6. Revisit the choice when the operation mix changes. A good rendering\n   representation may be a poor editing or collision representation.\n\n## Representation Guide\n\n- Use triangle meshes for rendering, GPU pipelines, LODs, static level geometry,\n  and approximating smooth surfaces when attribute data matters.\n- Use SDFs or implicit fields for Boolean composition, offsets, hollowing,\n  organic procedural forms, cheap inside\u002Foutside tests, and robust repair steps.\n- Use voxels or image masks for destructible terrain, coarse occupancy,\n  erosion\u002Fdilation, denoising, flood fill, gap checks, and reliable Boolean-like\n  operations on a shared grid.\n- Use splines or Bezier curves for player paths, camera rails, projectile trails,\n  roads, rivers, UI curves, and animation controls where continuity matters.\n- Use parametric surfaces when procedural objects come from a small number of\n  parameters, such as surfaces of revolution, terrain patches, tubes, or rails.\n- Use vector fields or deformation fields for smooth warps, influence maps,\n  wind\u002Fcurrent effects, procedural variation, and nonrigid deformation.\n- Use hybrids when one representation owns interaction and another owns\n  rendering, such as voxel sculpting with mesh LOD output.\n\n## Decision Rules\n\n- If the operation is Boolean or offset-like, prefer SDFs or voxels over triangle\n  meshes unless exact mesh topology is required.\n- If the operation needs exact texture, normal, skinning, or authoring data,\n  preserve mesh attributes or plan how to regenerate them after conversion.\n- If the system needs smooth paths, start with curves and parameterization, not\n  with sampled points.\n- If the game needs thousands of repeated spatial tests, choose a representation\n  that supports indexing, locality, or precomputed coefficients.\n- If memory dominates, prefer boundary data such as meshes or splines over full\n  voxel volumes.\n- If robustness dominates, prefer grid, SDF, or redundant fallback workflows over\n  a single brittle mesh algorithm.\n\n## Output Checklist\n\nReturn a short representation brief:\n\n- Chosen working representation:\n- Existing input representation:\n- Required output representation:\n- Operations made simpler:\n- Operations made harder:\n- Conversion steps:\n- Error\u002Fresolution budget:\n- Attribute preservation plan:\n- Degenerate or failure cases:\n- Minimal tests or debug views:\n\n## Common Mistakes\n\n- Rendering from meshes, then forcing every gameplay operation to run on the\n  same mesh.\n- Applying offsets or Booleans to arbitrary triangle meshes before considering\n  SDF or voxel workflows.\n- Converting representations without a plan for normals, UVs, materials,\n  gameplay labels, collision layers, or LODs.\n- Treating a sign-only implicit function as a true distance field after operations\n  that destroyed distance meaning.\n- Choosing a high-resolution grid without proving the memory and streaming\n  model.\n- Optimizing the algorithm implementation before choosing the representation\n  that makes the algorithm unnecessary.\n","# Game Geometry Representation Choice\n\nUse this skill before writing geometry-heavy game code. Pick the representation\nthat makes the important operation simple, robust, and fast enough, then plan\nconversion boundaries deliberately.\n\nPrimary source: Geometry for Programmers by Oleksandr Kaleniuk\n(https:\u002F\u002Fwww.manning.com\u002Fbooks\u002Fgeometry-for-programmers), transformed and\nparaphrased, especially chapters 2 and 10-12.\n\n## Core Workflow\n\n1. Name the operation first: render, collide, pick, offset, deform, Boolean,\n   smooth motion, destruct terrain, generate props, edit geometry, or convert.\n2. List the data the game already has and the data the game ultimately needs.\n   Include textures, normals, animation bindings, gameplay tags, and LODs.\n3. Pick the working representation where the core operation is cheapest and\n   least fragile. Do not default to meshes just because rendering ends there.\n4. Define conversion boundaries: input representation, working representation,\n   output representation, resolution, tolerated error, and attribute transfer.\n5. Add invariants and tests for the representation, not just the final visual.\n6. Revisit the choice when the operation mix changes. A good rendering\n   representation may be a poor editing or collision representation.\n\n## Representation Guide\n\n- Use triangle meshes for rendering, GPU pipelines, LODs, static level geometry,\n  and approximating smooth surfaces when attribute data matters.\n- Use SDFs or implicit fields for Boolean composition, offsets, hollowing,\n  organic procedural forms, cheap inside\u002Foutside tests, and robust repair steps.\n- Use voxels or image masks for destructible terrain, coarse occupancy,\n  erosion\u002Fdilation, denoising, flood fill, gap checks, and reliable Boolean-like\n  operations on a shared grid.\n- Use splines or Bezier curves for player paths, camera rails, projectile trails,\n  roads, rivers, UI curves, and animation controls where continuity matters.\n- Use parametric surfaces when procedural objects come from a small number of\n  parameters, such as surfaces of revolution, terrain patches, tubes, or rails.\n- Use vector fields or deformation fields for smooth warps, influence maps,\n  wind\u002Fcurrent effects, procedural variation, and nonrigid deformation.\n- Use hybrids when one representation owns interaction and another owns\n  rendering, such as voxel sculpting with mesh LOD output.\n\n## Decision Rules\n\n- If the operation is Boolean or offset-like, prefer SDFs or voxels over triangle\n  meshes unless exact mesh topology is required.\n- If the operation needs exact texture, normal, skinning, or authoring data,\n  preserve mesh attributes or plan how to regenerate them after conversion.\n- If the system needs smooth paths, start with curves and parameterization, not\n  with sampled points.\n- If the game needs thousands of repeated spatial tests, choose a representation\n  that supports indexing, locality, or precomputed coefficients.\n- If memory dominates, prefer boundary data such as meshes or splines over full\n  voxel volumes.\n- If robustness dominates, prefer grid, SDF, or redundant fallback workflows over\n  a single brittle mesh algorithm.\n\n## Output Checklist\n\nReturn a short representation brief:\n\n- Chosen working representation:\n- Existing input representation:\n- Required output representation:\n- Operations made simpler:\n- Operations made harder:\n- Conversion steps:\n- Error\u002Fresolution budget:\n- Attribute preservation plan:\n- Degenerate or failure cases:\n- Minimal tests or debug views:\n\n## Common Mistakes\n\n- Rendering from meshes, then forcing every gameplay operation to run on the\n  same mesh.\n- Applying offsets or Booleans to arbitrary triangle meshes before considering\n  SDF or voxel workflows.\n- Converting representations without a plan for normals, UVs, materials,\n  gameplay labels, collision layers, or LODs.\n- Treating a sign-only implicit function as a true distance field after operations\n  that destroyed distance meaning.\n- Choosing a high-resolution grid without proving the memory and streaming\n  model.\n- Optimizing the algorithm implementation before choosing the representation\n  that makes the algorithm unnecessary.\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":55},{"tags":51,"version":52,"category":53,"displayName":54},"game-dev,game-geometry,geometry,representation,procedural-generation","0.1.0","Game Development","Game Geometry Representation Choice","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgame-geometry-representation-choice",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill game-geometry-representation-choice",{"tool":72,"command":73},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill game-geometry-representation-choice",{"tool":75,"command":76},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill game-geometry-representation-choice","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fgame-geometry-representation-choice\u002FSKILL.md",true,[],[81,90,98,106,114,122],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":89},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":89},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":89},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":89},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":89},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]