Solo Design

Solo Design

This Skill uses a decision -> load -> preflight -> dispatch -> validate -> readiness routing chain. SKILL.md only classifies the request, writes the resolved lane into working notes / summary when a project exists, and loads exactly one intent-workflows/<selected>/INTENT_WORKFLOW.md.

Do not scan all workflow folders. After a lane is selected, read only that lane's INTENT_WORKFLOW.md and the files declared in its Context Requirements. Before any dispatch, the selected lane's declared context files must be recorded with body-read evidence in runtime-orchestration-summary.json.project.contextRequirementsLoaded[].

Top-Level Skill Handoffs

Evaluate these handoffs in order before Route Priority and before reading any intent workflow.

Immediately invoke the Skill tool with name: "solo-image-edit" and stop applying this Skill when either condition matches:

1. Current-turn context contains an image-region annotation whose parsed payload type is design-image-annotation. Match this semantically across available envelopes such as a web-element record or a selected_browser_item; do not require one exact wrapper or field layout.
2. The user explicitly asks to edit, retouch, remove, replace, recolor, restyle, extend, or otherwise change pixels in an existing bitmap image, and an original image is available as a local file or current-turn attachment.

The structured design-image-annotation marker is authoritative even when the visible user text is only a short instruction such as "按评论改一下" or only names the selected image-region. Do not route ordinary HTML/DOM/CSS/page-component edits merely because the page contains images. Do not route text-to-image creation without an original bitmap; keep those requests in the graphic lanes below.

After the image-edit handoff does not match, immediately invoke the Skill tool with name: "solo-graphic-generation" and stop applying this Skill when the generated bitmap itself is the deliverable: poster, banner, KV/key visual, cover, invitation, social card, illustration, portrait, product image, transparent-background asset, cutout, or an image batch without editable HTML requirements.

The graphic-generation handoff also applies when the user asks to generate and append a new image asset to an existing canvas. solo-graphic-generation owns the required pre-generation size confirmation, image generation, canvas registration, and image-only validation. Keep text-critical static layouts in this Skill when exact readable/editable copy, DOM typography, tables, schedules, prices, legal copy, PPT, one-pager, or manual/document structure is required.

Global Invariants

• Output is canvas-first: every produced page or kept image asset must be represented in the .design file.
• .design validity is blocking: valid JSON, non-empty data, existing devMetadata.htmlSrc / imageSrc, unique node ids, and registered image assets.
• Explicit user instructions win for design direction and optional process choices, but cannot override canvas validity, rendering correctness, safety, or required validation gates.
• Existing page/project changes create a new comparison page by default. In-place edit is allowed only when the user explicitly asks to overwrite, replace, or modify in place.
• New dispatches must never target shared-runtime/blocked-legacy-entrypoints/blocked-legacy-page-template.md.
• shared-runtime/agent-dispatch-runtime/shared-page-rendering-kernel.md is a Declared Load only; it is not an Always Load file.
• visual-experience/ and delivery-quality/ are loaded only when the selected INTENT_WORKFLOW.md declares them.
• Flow-control rules are model-agnostic. Do not add model-specific branches, model names, or per-model instructions to this Skill.
• Production visual stability is a generation-time gate for layout-risk pages. Page Sub-Agents must build layout-critical structure with responsive-safe static CSS in the page, not rely only on Tailwind browser runtime compilation, late validation, or repair passes. If first-screen frame, density, overflow, or overlap checks cannot pass during generation, return qualityGate: "failed|blocked" instead of producing a low-fidelity page for later repair.

Route Priority

After no top-level handoff matches, evaluate from P1 to P9 and stop at the first match.

Conflict rule: earlier priorities win. Example: explicit restore wins over active Library; existing project mutation wins over new-project creation unless the user explicitly asks for a separate new project.

Dispatch Discipline

• Main Agent owns routing, .design writes, image-node registration, interaction registration, and validation.
• Before any dispatch, Main Agent must record a Step 0 lane gate in runtime-orchestration-summary.json.project: resolvedLane, selectedIntentWorkflowRead: true, contextRequirementsLoaded[], contextReadScope, validationRunDiscipline, and lowValueCallWatchdog. Each contextRequirementsLoaded[] row must include { path, readStatus: "loaded", bodyRead: true }. If this evidence cannot be written, do not dispatch.
• Page Sub-Agents consume only the selected lane page runtime guide, the selected lane dispatch contract, and the packet fields provided by Main Agent.
• Page Sub-Agents do not write .design, run project validators, start preview servers, create helper scripts, or generate images.
• Page Sub-Agent packets must include allowedWritePaths[]; completions must report changedFiles[]. The Main Agent owns .design, runtime-orchestration-summary.json, validation reports, readiness evidence, and final delivery text.
• Cross-lane collaboration uses runtime-orchestration-summary.json, dispatchPreflightManifest[], and sourceProjectLaneHeritage; do not make one intent workflow read another intent workflow's runbook.
• supplementaryReads[] entries must be explicit { path, reason, ownerLane }. Free lane may keep implementationEscalationReason only as a compatibility alias.
• Restore dispatches must lock project.sourceAuthorityLock before page generation. Screenshot/user-provided imagery is visual authority when present; URL/browser evidence may supplement content but must not override the locked visual authority.
• Static graphic / layout-heavy page dispatches must write project.visualQualityCheckpoints[] before generation. These checkpoints lock visual anchor, information hierarchy, composition structure, and implementation strategy without adding open-ended exploration.
• Layout-risk page dispatches must include a compact production stability target: target device/frame, viewport mode, first-screen content regions, responsive breakpoints, and high-risk compression/overlap risks. Page Sub-Agents must report staticRenderingEvidence and viewportIntegrityEvidence; missing evidence blocks that layout-risk dispatch before project validation.
• Long reasoning without tool calls, artifact diffs, or structured decisions must follow project.lowValueCallWatchdog.noProgressNextAction and move to readiness or a minimal blocked summary; do not continue thinking loops.

Allowed Scripts

Only Skill-provided deterministic scripts below are allowed during execution or maintenance:

Out-Of-Scope Routing

• Pixel-level edits of an existing bitmap, including structured Design image comments, go to solo-image-edit.
• Bitmap-first poster/banner/KV/cover/card/illustration/image-batch generation goes to solo-graphic-generation.
• Professional reusable Design Library / Design System / token architecture creation goes to design-library-creator.
• Legacy runtime templates are blocked. If any dispatch packet or task query names blocked-legacy-page-template.md, stop and re-route to the lane-owned page runtime guide.
• create-design-system style requests inside page creation are treated as page styling requirements only; they must not self-create a reusable Design Library.

Completion Gate

Before final delivery, run the validation required by the selected INTENT_WORKFLOW.md. For restore_1to1 workflows, skip validate-design-workspace.mjs entirely and proceed directly to validate-finish-readiness.mjs <designProjectPath> --check=all --final-response-file=<draft.md>; ensure the draft is link-free and path-free. For other HTML/page workflows, after validate-design-workspace.mjs --report-json=<designProjectPath>/validation-report.json succeeds, run validate-finish-readiness.mjs <designProjectPath> --check=all as the Design artifact readiness gate. Do not claim completion while validation has blocking errors, artifact readiness fails, validation report integrity fails, or restore final-response text policy fails.

If validate-design-workspace.mjs reports only repair-ledger metadata warnings, do not rerun full validation or inspect validator source. Repair-ledger metadata is diagnostic; continue only when validation-report.json success=true and validate-finish-readiness.mjs <designProjectPath> --check=all passes. If validation-report.json.terminalState is present, stop and report the blocking summary instead of starting another repair loop.