Menu
Assess ZeroLight-Framework architecture for scalable emergent gameplay simulation. Use when the user asks how ready the engine is for emergent gameplay, architecture assessment, extensibility review, or runs /architecture-assessment.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
ZeroLight-Framework (Zig 0.16, SDL3, SDL_GPU) specialist routing: design, implement, debug, PR/diff review, and multi-phase review passes. Use when the user asks for zig-design-specialist, zig-specialist, zig-debug-specialist, or zig-review-specialist; when zig build, zig test, or shader compile fails; when reviewing a PR or branch diff; when planning ECS, DataSystem, SimulationPipeline, pathfinding, collision, AI, or threading changes; or when assessing emergent-gameplay architecture readiness. Slash: /zig-workflows.
Multi-agent Zig review of the pathfinder module for coherency, cohesion, and standards adherence. Use when the user asks for pathfinder review, pathfinding module review, /pathfinder-review, or a module-wide pass on src/game/systems/pathfinding/.
Multi-agent Zig best-practices review of large hot subsystems: review, adversarial verify, then synthesize durable lint/agent/doc guidance. Use when the user asks for best-practices review, Zig idioms pass, durable lint guidance, or /zig-best-practices-review.
Deep behavioral correctness review (pass 3): concurrency, algorithms, SIMD parity, pipeline determinism, resource lifetime, outliers, and test-coverage gaps. Use when the user asks for deep correctness, concurrency review, determinism audit, race hunting, or /zig-deep-correctness-review. Goes beyond idiom/surface reviews.
ZeroLight-Framework (Zig 0.16, SDL3, SDL_GPU) specialist workflows: design plans, implementation, debug/triage, PR/diff review, pathfinder module review, architecture assessment. Use when the user asks for zig-design-specialist, zig-specialist, zig-debug-specialist, or zig-review-specialist; when zig build, zig test, or shader compile fails; when reviewing a PR or branch diff; when planning ECS, DataSystem, SimulationPipeline, pathfinding, collision, AI, or threading changes; or when assessing emergent-gameplay architecture readiness.
| name | architecture-assessment |
| description | Assess ZeroLight-Framework architecture for scalable emergent gameplay simulation. Use when the user asks how ready the engine is for emergent gameplay, architecture assessment, extensibility review, or runs /architecture-assessment. |
Multi-phase read-only assessment. Parent spawns all subagents (depth limit 1).
Prefer zig-design-specialist for analysis units; synthesis may be parent or one
final design specialist.
Spawn four zig-design-specialist agents (capability_mode: read-only,
background: true):
| Label | Read | Focus |
|---|---|---|
docs:arch+sim | docs/architecture.md, docs/simulation-tiers-and-pipeline.md | Layout, ownership, frame flow, pipeline/tiers, threading, adding systems |
docs:state+standards | docs/state-stack-and-input.md, docs/coding-standards.md | State/input contracts, DOD/SoA/SIMD/alloc rules |
docs:roadmap | docs/framework-implementation-slices.md (+ archive if needed) | Settled vs frontier slices, planned emergent capabilities, gaps |
docs:render+assets | docs/rendering-assets-shaders.md, docs/atlas-asset-workflow.md | Sim/render boundary, stable IDs, scale with entity variety |
Each unit returns: area, summary, strengths, weaknesses, gaps, key_facts.
Spawn five zig-design-specialist agents after listing live paths under
src/game/ (files may have moved — resolve via list/grep first):
| Label | Areas | Focus |
|---|---|---|
code:data+pipeline | data_system*, simulation_pipeline.zig, simulation scope | SoA, processor order, extensibility, data deps |
code:systems | systems/ movement, ai, collision, steering, … | Access patterns, shared-state safety, SIMD, slotting new systems |
code:engine+threads | src/app/engine.zig, thread_system.zig, time_loop.zig | Fixed-step drive, pool, parallel phases, limits |
code:world+pathfinding | world_system.zig, systems/pathfinding/ | World model, dynamic nav, spatial queries |
code:controllers | render_prep.zig, dig/audio controllers | Controllers, deferred structural changes, sim/render split |
Each unit returns: module, summary, data_layout, concurrency_model, extensibility_notes, bottlenecks, emergent_readiness, key_facts.
One synthesis pass (parent or zig-design-specialist) over all findings.
Produce a Markdown report:
