artifact-refiner

Coordinate iterative artifact refinement across specify, plan, execute, reflect, and persist phases.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/GQAdonis/turboquant-rs --skill artifact-refiner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: artifact-refiner
Source: https://github.com/GQAdonis/turboquant-rs/tree/main/.opencode/skills/artifact-refiner/skills/artifact-refiner
Command: npx skills add https://github.com/GQAdonis/turboquant-rs --skill artifact-refiner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Artifact creation often requires structured, iterative refinement across multiple artifact types (logos, UI components, specifications, images, or content) with strict constraints and traceable state.

Core Features & Use Cases

  • Deterministic PMPO-driven refinement across multiple artifact domains (logos, UI components, content, specs).
  • Persisted state and versioned decisions with a canonical runtime contract.
  • Domain adapters and schema-based validation to guide consistent refinements.

Quick Start

Refine a selected artifact by applying deterministic PMPO constraints and persist the artifact state after each iteration.

Frequently Asked Questions about artifact-refiner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure iterative design refinement with deterministic execution and persistent state?

Iterative design refinement uses PMPO orchestration to coordinate specify, plan, execute, reflect, and persist phases, applying deterministic execution and schema-based validation to persist artifact state to disk after each iteration.

What is deterministic artifact refinement and how does it handle UI components and logos?

Deterministic artifact refinement applies structured PMPO constraints across multiple artifact domains like UI components, logos, and content, using domain adapters and schema validation to guide consistent iterations without relying on conversational context.

Can I use schema-based validation for iterative content refinement across different artifact domains?

Yes, schema-based validation guides consistent refinements across different artifact domains by applying domain adapters that enforce explicit constraints and traceable state throughout the staged governance process.

What's the best way to persist artifact state to disk during iterative design workflows?

The best way to persist artifact state is using a canonical runtime contract that writes versioned decisions to disk during the persist phase, ensuring deterministic execution and traceable state across refinement iterations.

Do I need a canonical runtime contract to run PMPO orchestration for artifact refinement?

Yes, PMPO orchestration requires a canonical runtime contract that enforces disk-based state persistence, deterministic execution, and schema-based validation, explicitly rejecting reliance on conversational context for reliable refinement.

When should I not use deterministic PMPO orchestration for artifact refinement?

Deterministic PMPO orchestration is not suitable for workflows lacking explicit constraints or those relying on conversational context, as it demands strict schema validation, disk-persisted state, and staged governance across all refinement phases.