Job System

Use when the user asks about a game engine job system, work stealing, task scheduler, fibers, parallel for, job graph dependencies or engine threading. Produces job system design that fits the frame budget. Not for backend service concurrency (use backend-concurrency-mechanics) or GPU async compute (use render-graph).

45 stars 6 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill job-system
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/game/game-engine/job-system ~/.claude/skills/job-system

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Parallel Job Systems — Deep Engineering Guide

## Purpose
Modern CPUs give you 8–32 cores; a single-threaded `Update()` leaves them idle. The job system is the backbone that spreads simulation, animation, physics, and render-command generation across cores — transparently, deterministically, and within the frame budget.

## Agent Protocol

### Trigger
"job system", "work stealing", "task scheduler", "fibers", "parallel for", "job graph", "engine threading".

### Input Context
- Language/runtime and core counts on targets
- Workloads to parallelise and their dependencies
- Determinism requirements

### Output Artifact
Scheduler design and C++ code. No file unless requested.

### Response Format
```
Scheduler: {work-stealing | fixed queues | fibers}
Graph: {jobs and edges}
Code: {snippet}
Verify: {profiler lanes, contention}
```

## 1. Why a Job System

### 1.1 The Multicore Reality

| Workload | Threads that help | Where it breaks |
|----------|-------------------|-----------------|
| Graphics (GPU) | Async compute helps | Raster work is GPU-bound |
| Simulation (physics, AI) | Many cores | Contention on shared state |
| Animation skel + pool | Many cores | Ordering (blend tree) |
| Render command gen | Medium parallel | Sorting at end |

Raw multicore won't help if every thread fights over one lock. Job systems give *structured* parallel workers: fixed worker threads, work queues, and dependencies.

### 1.2 One Worker per Core — No Oversubscription
Read the full skill on GitHub

Details

Skill name
job-system
Path
skills/game/game-engine/job-system/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Job System skill do?

Use when the user asks about a game engine job system, work stealing, task scheduler, fibers, parallel for, job graph dependencies or engine threading. Produces job system design that fits the frame budget. Not for backend service concurrency (use backend-concurrency-mechanics) or GPU async compute (use render-graph).

How do I install the Job System skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill job-system. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Job System popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Lang Assembly

45

j4flmao/agent-skills

Use when the user asks about assembly, x86-64 or AArch64 code, calling conventions, System V or Windows x64 ABI, reading disassembly, objdump, Compiler Explorer, inline asm or stack frames. Produces annotated assembly and small hand-written routines. Not for microarchitecture tuning (use cpu-architecture) or compiler implementation (use compiler-design).

Software Development

Golang Patterns

45

j4flmao/agent-skills

Use when the user asks about goroutines, channels, Go context cancellation, worker pools, errgroup, sync.Mutex, Go error wrapping, net/http middleware or go test -race. Produces idiomatic Go concurrency and error-handling code. Not for package layout (use golang-architecture).

Software Development

Level Streaming

45

j4flmao/agent-skills

Use when the user asks about level streaming, open world streaming, World Partition, streaming cells, async loading, loading hitches or pop-in. Produces cell layout, residency rules and hitch-free load scheduling. Not for asset cooking and packaging (use asset-pipeline) or server zone sharding (use scaling-architecture).

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.