← Explore all agents

CREATIVE TOOLING / Agency Agents community

Technical art pipeline planner

A cross-engine technical-art profile linking asset handoff to measured rendering budgets.

“Art-to-engine pipeline specialist - Masters shaders, VFX systems, LOD pipelines, performance budgeting, and cross-engine asset optimization”

01 / THE REASONING

Why this made the selection.

  • It puts asset budgets before content production and requires in-engine review under target lighting.
  • It separates shader complexity, texture conventions and asset handoff checks so visual approvals depend on the shipped renderer.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • game-development/technical-artist.md (pinned complete source retained)
  • LICENSE
  • Repository README and current official host configuration documentation

Our findings

  • It puts asset budgets before content production and requires in-engine review under target lighting.
  • It separates shader complexity, texture conventions and asset handoff checks so visual approvals depend on the shipped renderer.

Not established by this review

  • Source review only: no agent was installed or invoked. Task correctness, effective host restrictions and integration behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. Read the pinned source and its licence, then configure an explicitly bounded host context.
  2. Check the original display-style name and optional color/emoji/vibe metadata against the installed host requirements before loading a working copy. Current Claude Code documentation says unknown frontmatter fields are ignored; it does not establish a need to rewrite these names. Keep the archived/downloaded original unchanged.
  3. Choose the actual engine/render pipeline, preserve source assets and test proposed changes using its profiler and import settings.
  4. Supply asset categories, renderer, target hardware and current bottleneck captures.

Before you start

  • Engine project and source assets
  • Representative target-device captures

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/game-development/technical-artist.md

    Supports: Workflow, inputs, outputs and stated boundaries

  2. Applicable licence ↗Checked

    https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE

    Supports: Redistribution and attribution

  3. https://code.claude.com/docs/en/sub-agents.md

    Supports: Host loading and effective permission boundaries

Evidence & Ask