Artifact Refiner — Claude Plugin Adapter
This is the Claude plugin entry point. It delegates to the canonical PMPO skill definition.
When To Use This Skill
Use when the user asks for structured, iterative refinement of:
- Logos and brand artifacts
- React/HTML UI components
- A2UI specifications
- Image assets
- Content artifacts (Markdown, HTML)
Source Of Truth
Load these files in order when this skill activates:
- Root
SKILL.md— Canonical PMPO behavior, inputs/outputs, execution model prompts/meta-controller.md— Orchestration entry point- Phase controllers in
prompts/—specify.md,plan.md,execute.md,reflect.md,persist.md - Domain adapters in
references/domain/— Domain-specific refinement knowledge - Schemas in
references/schemas/—artifact-manifest.schema.json,constraints.schema.json
Non-Negotiable Runtime Contract
- Persist state to disk:
artifact_manifest.json,constraints.json,refinement_log.md,decisions.md,dist/ - Use deterministic execution for measurable requirements (code interpreter or e2b sandbox)
- Validate outputs against schema contracts before termination
- Never rely on conversational context for state
Under KBD (VLBV)
When a KBD phase invokes this skill, it is the static quality-assurance pass
over the whole value phase: one cumulative pass at B4 step 5
(kbd-process-orchestrator/references/boundaries.md), after the boundary packet has
run and recorded boundary-results.json, and before
scripts/kbd-phase-close-eval.mjs. It never runs per task or per change (B1/B2
invoke nothing), and it never triggers a build, test or compiler check —
generated code executes only inside the boundary packet. Deterministic execution
above applies to the artifacts this skill itself measures, not to the project's
generated code. Constraint-driven refinement of repaired artifacts runs only inside
an owner-authorized B5 repair. State: .refiner/artifacts/<phase-id>/.