nccgs 1.0.0

package/.claude/nccgs/workflow-catalog.json

@@ -0,0 +1,317 @@
+{
+  "schemaVersion": 1,
+  "entrypoints": [
+    "work",
+    "design",
+    "audit",
+    "migrate-project",
+    "test",
+    "review",
+    "release",
+    "status"
+  ],
+  "workflows": [
+    {
+      "name": "work",
+      "type": "entrypoint",
+      "primaryRoles": [
+        "nccgs-production-coordinator",
+        "nccgs-programming-lead",
+        "nccgs-unity-implementer",
+        "nccgs-verification-engineer"
+      ],
+      "defaultClassification": "auto"
+    },
+    {
+      "name": "design",
+      "type": "entrypoint",
+      "primaryRoles": [
+        "nccgs-game-design-lead",
+        "nccgs-game-designer",
+        "nccgs-systems-designer"
+      ],
+      "defaultClassification": "auto"
+    },
+    {
+      "name": "audit",
+      "type": "entrypoint",
+      "primaryRoles": [
+        "nccgs-adversarial-reviewer",
+        "nccgs-technical-architect",
+        "nccgs-qa-lead"
+      ],
+      "defaultClassification": "auto"
+    },
+    {
+      "name": "migrate-project",
+      "type": "entrypoint",
+      "primaryRoles": [
+        "nccgs-producer",
+        "nccgs-technical-director",
+        "nccgs-technical-architect",
+        "nccgs-adversarial-reviewer"
+      ],
+      "defaultClassification": "auto"
+    },
+    {
+      "name": "test",
+      "type": "entrypoint",
+      "primaryRoles": [
+        "nccgs-qa-lead",
+        "nccgs-qa-engineer",
+        "nccgs-verification-engineer"
+      ],
+      "defaultClassification": "auto"
+    },
+    {
+      "name": "review",
+      "type": "entrypoint",
+      "primaryRoles": [
+        "nccgs-adversarial-reviewer"
+      ],
+      "defaultClassification": "auto"
+    },
+    {
+      "name": "release",
+      "type": "entrypoint",
+      "primaryRoles": [
+        "nccgs-release-lead",
+        "nccgs-release-engineer",
+        "nccgs-unity-build-specialist"
+      ],
+      "defaultClassification": "auto"
+    },
+    {
+      "name": "status",
+      "type": "entrypoint",
+      "primaryRoles": [
+        "nccgs-documentation-manager"
+      ],
+      "defaultClassification": "auto"
+    },
+    {
+      "name": "context-pack",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-documentation-manager"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "plan-feature",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-production-coordinator"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "story-readiness",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-programming-lead"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "architecture-decision",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-technical-architect"
+      ],
+      "defaultClassification": "CONTROLLED"
+    },
+    {
+      "name": "design-review",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-game-design-lead"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "code-review",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-programming-lead"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "evidence-review",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-verification-engineer"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "closure",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-documentation-manager"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "qa-plan",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-qa-lead"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "bug-triage",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-qa-lead"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "performance-audit",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-performance-analyst"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "security-audit",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-security-engineer"
+      ],
+      "defaultClassification": "CONTROLLED"
+    },
+    {
+      "name": "accessibility-review",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-accessibility-specialist"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "balance-review",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-economy-designer"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "prototype-feature",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-prototyper"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "playtest",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-qa-lead"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "localize-game",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-localization-lead"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "hotfix",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-release-lead"
+      ],
+      "defaultClassification": "CONTROLLED"
+    },
+    {
+      "name": "project-stage",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-production-coordinator"
+      ],
+      "defaultClassification": "FAST"
+    },
+    {
+      "name": "sprint-plan",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-production-coordinator"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "milestone-review",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-production-coordinator"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "asset-audit",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-unity-content-specialist"
+      ],
+      "defaultClassification": "STANDARD"
+    },
+    {
+      "name": "release-readiness",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-release-lead"
+      ],
+      "defaultClassification": "CONTROLLED"
+    },
+    {
+      "name": "dependency-review",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-technical-director"
+      ],
+      "defaultClassification": "CONTROLLED"
+    },
+    {
+      "name": "compatibility-review",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-technical-architect"
+      ],
+      "defaultClassification": "CONTROLLED"
+    },
+    {
+      "name": "incident-recovery",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-technical-director"
+      ],
+      "defaultClassification": "CONTROLLED"
+    },
+    {
+      "name": "retrospective",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-production-coordinator"
+      ],
+      "defaultClassification": "FAST"
+    },
+    {
+      "name": "ui-review",
+      "type": "module",
+      "primaryRoles": [
+        "nccgs-ux-designer"
+      ],
+      "defaultClassification": "STANDARD"
+    }
+  ]
+}

package/.claude/rules/nccgs-canonical-docs.md

@@ -0,0 +1,19 @@
+---
+paths:
+  - ".nccgs/**"
+  - "design/**"
+  - "docs/**"
+---
+
+# NCCGS canonical documentation rules
+
+- Preserve recorded PO decisions and distinguish approved canon from drafts,
+  inference, implementation status, and evidence.
+- Use stable IDs only for meaningful contracts, invariants, acceptance criteria,
+  and cross-system dependencies.
+- Synchronize implementation status and technical evidence after verified work.
+- Never rewrite game design silently to match implementation drift.
+- Prefer one feature contract and one closure record over duplicated story, QA,
+  review, and completion reports.
+- Link to existing canonical sections instead of copying whole documents into each
+  feature record.

package/.claude/rules/nccgs-editor-tools.md

@@ -0,0 +1,12 @@
+---
+paths:
+  - "Assets/**/Editor/**/*.cs"
+  - "Packages/**/Editor/**/*.cs"
+---
+
+# NCCGS editor tooling rules
+
+- Make bulk operations scoped, previewable, deterministic, and recoverable.
+- Use Undo, dirty/serialization handling, and asset database operations correctly.
+- Never normalize protected import settings or user-owned content implicitly.
+- Separate editor-only code through established assembly boundaries.

package/.claude/rules/nccgs-localization.md

@@ -0,0 +1,12 @@
+---
+paths:
+  - "Assets/**/*Localization*"
+  - "Assets/**/*Locale*"
+---
+
+# NCCGS localization rules
+
+- Preserve stable string IDs, placeholder/plural semantics, context, and deterministic
+  extraction/import.
+- Verify font coverage, fallback, layout expansion, input, and locale-specific assets.
+- Do not invent supported locales, translations, or linguistic approval.

package/.claude/rules/nccgs-networking.md

@@ -0,0 +1,13 @@
+---
+paths:
+  - "Assets/**/*Network*.cs"
+  - "Assets/**/*Multiplayer*.cs"
+---
+
+# NCCGS networking rules
+
+- Treat authority, protocol, message version, persistence, and service changes as
+  CONTROLLED unless project policy explicitly narrows the risk.
+- Validate untrusted input and failure paths; make latency, reconnect, and rollback
+  assumptions testable.
+- Preserve compatibility unless an approved migration says otherwise.

package/.claude/rules/nccgs-performance.md

@@ -0,0 +1,14 @@
+---
+paths:
+  - "Assets/**/*.cs"
+  - "Assets/**/*.shader"
+  - "Assets/**/*.hlsl"
+---
+
+# NCCGS performance rules
+
+- Use project budgets and reproducible target-platform scenarios.
+- Measure before broad optimization; compare identical before/after conditions.
+- Treat demonstrated hot-path allocation, loading, frame pacing, GPU, and memory
+  failures as evidence, not generic style rules.
+- Preserve correctness, determinism, and visual/product targets while optimizing.

package/.claude/rules/nccgs-rendering.md

@@ -0,0 +1,16 @@
+---
+paths:
+  - "Assets/**/*.shader"
+  - "Assets/**/*.hlsl"
+  - "Assets/**/*Shader*"
+  - "Assets/**/*VFX*"
+---
+
+# NCCGS rendering rules
+
+- Respect the configured render pipeline, target platforms, visual direction, and
+  measured GPU budgets.
+- Record visual changes as reproducible scenarios and leave subjective acceptance to
+  the Product Owner.
+- Render-pipeline, package, and broad project-setting changes are CONTROLLED.
+- Use official Unity rendering skills for API and Editor operation mechanics.

package/.claude/rules/nccgs-security.md

@@ -0,0 +1,13 @@
+---
+paths:
+  - "Assets/**/*.cs"
+  - "Packages/**/*.json"
+---
+
+# NCCGS security rules
+
+- Never embed secrets, credentials, signing material, or privileged endpoints.
+- Treat client state and network/service input as untrusted at declared boundaries.
+- Dependency, analytics, commerce, account, privacy, and external-service changes
+  require explicit authority and targeted security evidence.
+- Do not expose sensitive values in logs or evidence records.

package/.claude/rules/nccgs-tests.md

@@ -0,0 +1,18 @@
+---
+paths:
+  - "Assets/**/Tests/**/*.cs"
+  - "Tests/**/*.cs"
+---
+
+# NCCGS test rules
+
+- Map tests to behavior or requirement IDs, not implementation trivia.
+- Bug fixes require a regression test when the failure can be reproduced
+  deterministically.
+- Keep EditMode tests independent of scene/runtime state unless integration is the
+  purpose; use PlayMode or runtime verification for behavior that requires Unity.
+- Cover the normal path and material edge cases. Do not inflate coverage with
+  assertions that do not prove the acceptance criterion.
+- A green test run is objective evidence, not subjective gameplay validation.
+- Follow project test conventions before choosing new folders, assemblies, helpers,
+  or frameworks.

package/.claude/rules/nccgs-ui.md

@@ -0,0 +1,14 @@
+---
+paths:
+  - "Assets/**/*UI*.cs"
+  - "Assets/**/*.uxml"
+  - "Assets/**/*.uss"
+---
+
+# NCCGS Unity UI rules
+
+- UI presents and requests state; authoritative gameplay state remains outside views.
+- Follow approved UX, input, localization, and accessibility contracts.
+- Verify navigation/focus, errors, scaling, layout expansion, binding lifecycle, and
+  platform input rather than checking appearance only.
+- Use official Unity UI skills for operation and API mechanics.

package/.claude/rules/nccgs-unity-assets.md

@@ -0,0 +1,21 @@
+---
+paths:
+  - "Assets/**/*.unity"
+  - "Assets/**/*.prefab"
+  - "Assets/**/*.asset"
+  - "Assets/**/*.meta"
+  - "ProjectSettings/**"
+---
+
+# NCCGS Unity asset and settings rules
+
+- Read the ownership section of `.nccgs/project.yaml` before modifying assets or
+  settings.
+- If a connected Editor can perform the operation, use the appropriate official
+  Unity Skill and Unity CLI/Pipeline; do not hand-edit serialized YAML.
+- Inspect before modifying and make the smallest targeted change. Preserve existing
+  hierarchy, GUIDs, serialized references, import settings, and handcrafted values
+  unless the request requires changing them.
+- Package, service, platform, render-pipeline, input-system, and compatibility
+  changes require the authority specified in project policy.
+- Verify persistent Editor changes after saving and reimporting where applicable.

package/.claude/rules/nccgs-unity-code.md

@@ -0,0 +1,22 @@
+---
+paths:
+  - "Assets/**/*.cs"
+  - "Packages/**/*.cs"
+---
+
+# NCCGS Unity code rules
+
+- Follow `.nccgs/project.yaml`, governing decisions, and established project
+  patterns before generic recommendations.
+- Preserve approved behavior and serialized compatibility unless the task explicitly
+  authorizes a change.
+- Do not introduce packages, services, architecture patterns, or global managers
+  merely because they are common Unity practices.
+- Separate testable domain logic from presentation when it materially improves
+  verification; do not force an abstraction for trivial code.
+- Avoid allocations in demonstrated hot paths, but profile before broad performance
+  rewrites.
+- Treat warnings, nullable assumptions, Unity object lifetime, domain reload, and
+  serialization behavior as part of correctness.
+- Use the relevant official Unity Skill for Unity-specific mechanics rather than
+  relying on copied NCCGS guidance.

package/.claude/skills/accessibility-review/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: accessibility-review
+description: Reviews a Unity feature, screen, control scheme, content, or build for scoped accessibility barriers and testable accommodations.
+allowed-tools: Read, Glob, Grep, Task, WebSearch, WebFetch
+---
+
+# Accessibility Review
+
+Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
+
+Remain read-only unless explicitly asked to implement. Read project accessibility targets, UX/design, platforms, inputs, content, and implementation. Review applicable vision, hearing, motor, cognitive, motion, timing, language, and difficulty-support barriers. Report severity, affected task/player, evidence, requirement, feasible remediation, and validation scenario. Do not claim compliance or lived-experience validation.
+
+Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.
+

package/.claude/skills/architecture-decision/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: architecture-decision
+description: Analyzes and records a focused Unity architecture decision when system boundaries, compatibility, dependencies, persistence, networking, or migration risk require durable rationale.
+allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, WebSearch, WebFetch
+---
+
+# Architecture Decision
+
+Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
+
+Read policy, context packet, affected contracts, code, tests, and existing decisions. Define forces and invariants; present materially distinct options with consequences; recommend one; obtain Product Owner authority for dependencies, compatibility, services, or irreversible migration. Record the accepted decision using the project template, including status, scope, alternatives, consequences, implementation constraints, verification, rollback, and superseded decisions. Do not create an ADR for a private local implementation choice.
+
+Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.
+

package/.claude/skills/asset-audit/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: asset-audit
+description: Audits Unity source assets, import settings, naming, references, size/budget, duplication, ownership, and content-pipeline integrity without mass-editing them.
+allowed-tools: Read, Glob, Grep, Bash, Task
+---
+
+# Asset Audit
+
+Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
+
+Remain read-only. Read asset policy, protected/user-owned settings, budgets, source/import paths, and generated-path rules. Use official Unity Skills for asset and serialized-reference inspection. Report missing/broken references, import drift, budget violations, duplicates, naming issues that affect tooling, and unsafe ownership. Separate source asset problems from generated/import artifacts; do not normalize hand-tuned settings automatically.
+
+Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.
+

package/.claude/skills/audit/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: audit
+description: Performs a read-only audit of an NCCGS Unity project, workflow, codebase, design, architecture, ownership, security, performance, evidence, or migration state. Use for diagnosis and gap analysis without implementing changes.
+allowed-tools: Read, Glob, Grep, Bash, Task, WebSearch, WebFetch
+---
+
+# Audit
+
+Remain read-only. Define scope, authority, expected standards, and evidence before inspecting. Read policy and only the canonical sources and artifacts relevant to the requested audit.
+
+Select applicable dimensions from [audit dimensions](references/dimensions.md). Route independent lenses to specialists when their conclusions can be compared without overlapping writes. For broad or CONTROLLED audits, use the adversarial reviewer to challenge assumptions and evidence.
+
+Every finding must identify severity, exact evidence, violated contract or concrete failure mode, impact, confidence, and smallest remediation direction. Separate confirmed defects, risks, missing evidence, and optional improvements. Do not convert style preference into a finding.
+
+Report strengths worth preserving, prioritized findings, systemic causes, decision blockers, and an ordered remediation plan. Do not edit files or silently transition into implementation.
+

package/.claude/skills/audit/references/dimensions.md

@@ -0,0 +1,46 @@
+# Audit dimensions
+
+Select only dimensions relevant to the request.
+
+## Project and governance
+
+- NCCGS installation integrity and project-policy completeness
+- canonical-source map and authority conflicts
+- protected/user-owned content boundaries
+- compact state accuracy and stale open decisions
+- closure mode, canonical record, linked artifacts, waivers, and legacy safeguards
+
+## Design and traceability
+
+- implementability and internal consistency
+- requirement IDs for meaningful contracts
+- objective acceptance versus subjective gates
+- code/design drift and downstream change impact
+
+## Architecture and code
+
+- module/data-flow boundaries and dependency direction
+- serialization, save, network, and package/service contracts
+- project conventions versus accidental legacy patterns
+- correctness, lifecycle, error handling, performance evidence, and testability
+
+## Verification
+
+- requirement-to-evidence coverage
+- EditMode, PlayMode, runtime, build, and regression adequacy
+- claims based only on file existence or inspection
+- subjective gates incorrectly marked technical PASS
+
+## Unity integration
+
+- Unity version and project configuration
+- official Unity Skills presence and integrity
+- Unity CLI/Pipeline availability and connected Editor behavior
+- hand-edited serialized assets where live tooling should be used
+- package/service changes lacking authority
+
+## Release and operations
+
+- reproducible targets and version identity
+- release-blocking tests, migrations, known issues, and rollback readiness
+- secrets, signing, external publishing, and approval boundaries

package/.claude/skills/balance-review/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: balance-review
+description: Analyzes mechanics, economy, combat, progression, rewards, and tuning data for outliers, degenerate strategies, fairness risks, and sensitivity without changing approved balance.
+allowed-tools: Read, Glob, Grep, Bash, Task
+---
+
+# Balance Review
+
+Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
+
+Read canonical formulas, tuning values, goals, telemetry/playtest evidence, and interacting systems. Recalculate assumptions, inspect boundaries and long-run behavior, compare player strategies, and identify dominant or dead choices. Separate mathematical defects from subjective target choices. Return evidence, sensitivity, options, recommendation, and PO gates; do not write new balance values unless implementation is explicitly requested.
+
+Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.
+

package/.claude/skills/bug-triage/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: bug-triage
+description: Reproduces, classifies, prioritizes, and routes Unity defects using player impact, data risk, scope, evidence, ownership, and regression exposure.
+allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task
+---
+
+# Bug Triage
+
+Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
+
+Read the report, logs, affected requirements, recent changes, and project severity policy. Reproduce through the strongest safe path; distinguish product defect, test defect, environment issue, data corruption, and unknown. Record severity, frequency, scope, evidence, suspected ownership without claiming unproven cause, containment, regression needs, and next role. Escalate data-loss, security, save, network, or release-critical defects to CONTROLLED.
+
+Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.
+