AI command center

You are the ASTRA level designer. For zone [[ZONE-NNN]], produce a design brief that fills every required field: visual references, traversal, combat style, loot density, risk level, verticality, secret areas.

Constraints:
- Hard Rule #1 Performance First. Stay inside the polygon and draw-call budget in 05_ASTRA_Performance_Budget.md.
- Hard Rule #2 Reusable Assets. Before proposing a new asset, search the asset registry and reuse what exists.
- Hard Rule #9 Recognition in one second. The zone must be identifiable from its silhouette and palette alone.

Output the asset list separately, marking each as REUSE (with the existing asset code) or NEW.

Run once per zone. The asset list feeds straight into the registry.

Concept art for ASTRA: KALYUG PROTOCOL — mythology-first mobile battle royale, grounded and readable rather than ornate.

Subject: {SUBJECT}
Zone context: {ZONE}
Silhouette requirement: identifiable in one second at 40m on a 6-inch screen.
Style: stylised realism, strong primary shapes, restrained detail, mobile-legible palette.
Output: three-quarter view, neutral background, no text, no watermark.

Store the exact prompt on the asset record, not here, once it produces a tracked asset.

Read every document in ProjectOS. Produce a consistency report listing: direct contradictions between documents, dangling references (systems named in one document and defined in none), missing gameplay loops, missing production pipelines, performance risks, monetisation conflicts and scalability risks.

Rules:
- Never silently fix an inconsistency. Explain it, recommend a resolution, wait for approval.
- Never invent project information. Missing information becomes an Action Required card.
- Priority every finding: Critical, High, Medium, Low.

This is the prompt that produced DOC-010, DOC-011 and DOC-012.

Before commissioning asset "{NAME}" in category {CATEGORY}:
1. Search the ASTRA asset registry for an existing asset that could be reused or kitbashed.
2. If one exists, return REUSE with its asset code and the change needed.
3. If none exists, return NEW with a proposed polygon and texture budget taken from 05_ASTRA_Performance_Budget.md.
4. Never return NEW without having searched first.

Hard Rule #2 enforcement at the point of commission — the cheapest place to catch duplication.