design-refs

design-refs

This is a Codex-native Skill projection generated from the portable capability contract. It is adapter-owned output, not a legacy compatibility Skill copy.

Source

• Portable source: capabilities/design-refs.md
• Runtime check: adapters/codex/bin/preflight.sh capability-info design-refs
• Bootstrap: adapters/codex/AGENTS.md

Use

1. Read capabilities/design-refs.md for the runtime-neutral contract.
2. Run adapters/codex/bin/preflight.sh capability-info design-refs.
3. Obey the reported status:
   • instruction-only: use this Skill as Codex guidance plus explicit preflight guards.
   • tool-contract: report the named tool_contract, run any tool_contract_check, and obey runtime_surface / fallback before claiming full support.
   • unsupported: stop or use the reported fallback.

Shape

• Identifier: design-refs
• Invocation class: parent-invoked
• Supported modes: none
• Argument shape: <design task> [--design <path>] [--refs <image paths>] [--no-web]
• Portable meaning: Collect external and user-provided visual references and create a brief.

Portable Contract

• Invocation semantics: Reference collection and briefing: gather user-provided images, external web references through the material role's web-image-search mode, and existing design-system assets. Write a brief that informs subsequent phases. Adapters may expose this capability through native commands, skill files, prompt instructions, or explicit wrappers. The adapter must report unsupported runtime mechanics instead of silently treating another runtime's native file format as portable.

Projected Portable Details

Artifact Ownership

Artifact root: core/CONVENTIONS.md §5.1; output placement: §5.

Artifact Producer Lifecycle

design-refs is a standard+ stage worker: it never issues its own campaign or cycle. It receives the owner's open cycle through AGENT_ARTIFACT_CAMPAIGN_ID/AGENT_ARTIFACT_CYCLE_ID/AGENT_ARTIFACT_PRODUCER_ID/ AGENT_ARTIFACT_CYCLE_DIR/AGENT_ARTIFACT_OUTPUT_DIR (dispatch env pass-through), may call utilities/artifact_producer.py begin --node <node id> on the same route to resume that cycle, and writes only inside <cycle_dir>/artifacts/<bucket>/... within its node write_scope. artifact_producer.py owns the open cycle and its output paths; finalize and admit-shared belong to the owner, never to a stage worker. See producer_lifecycle in capabilities/topologies.json.

Role Requirements

Use portable role names from roles/README.md and core/CONVENTIONS.md. Concrete model names, subagent frontmatter, and runtime-specific tool lists belong in adapter files.

Guard Requirements

Adapters must preserve the portable invariants relevant to this capability:

• resolve artifact root through utilities/artifact-root.sh or equivalent logic;
• use DB memory paths, not runtime-native memory files.

Portable procedure and reference documents are owned under capabilities/design-refs/references/ when present. Claude, Codex, and OpenCode Skill bodies are generated projections of this capability and use the same logical procedure read-set.

Shared Procedure References

Read the complete portable procedure files listed here when they apply; this logical read-set is shared across Claude, Codex, and OpenCode.

• capabilities/design-refs/references/procedure.md

Workflow Evidence

• Before capability grounding/spec-changing work: adapters/codex/bin/preflight.sh route design-refs [cwd] [session-id]
• For workflow state: adapters/codex/bin/preflight.sh status [cwd] [session-id] and adapters/codex/bin/preflight.sh prompt-signal [cwd] [session-id]

Do not use legacy compatibility Skill files or non-native adapter Skill files as Codex-native source. Those files are compatibility/reference surfaces only.