In the studioZen — a little more clarity for ambitious work
sico studio®
Open workspace

Zen / Shaping

/prototype

Explore three directions. Choose with confidence.

Next mode →Template and example
npx skills@latest add sico-vibes/zen-skills --skill zen zen-prototype

Public repository release pending. Install the router with this mode for shared references and the local record writer.

Make an unresolved choice visible. Establish the question, constraints and comparison criteria before building alternatives.

  1. Read the brief, references, existing system and relevant applied feedback. Identify what must be learned: an interaction, hierarchy, technical seam or visual direction. Do not invent unrelated features or fake production behavior.
  2. Default to three meaningfully distinct runnable variants under one ART collection unless instructed otherwise. Vary a real decision, not only an accent. Bound implementation so comparison stays cheap.
  3. Create ART with the question/criteria, then SRT children using its returned UUID as parentId. Preserve source, run/preview instructions, limitations, screenshots and provenance. For file-backed variants resolve paths against the recorded repository/source root and pin a file manifest, SHA-256 hashes and immutable snapshot before selection. For small self-contained HTML variants store the complete source in data.html with data.kind=inline-html; its selected record revision pins the content. Do not claim a mutable path alone is exact evidence. ART-0001-SRT-01 is a child, not an unrelated collection.
  4. Run and inspect every offered option. Generated HTML previews must be sandboxed without application credentials or trusted privileges. Label fixtures, simulations and unavailable integrations where they affect a decision.
  5. Compare against the agreed criteria using observations, not adjectives. Recommend a direction but leave selection explicit. Do not silently choose the latest-built variant or delete rejected options.
  6. Persist selection with artifact.select, current ART revision and exact SRT UUID. Read back selectedVariantId, selectedVariantRevision and selectedRef; supply the returned copyable sub-reference. The next task reads the collection's pinned revision, checks the source manifest and resolves the immutable snapshot. If the live source or SRT revision changed, surface drift and do not silently implement the changed file as the selected version.

Tool and local paths

See artifact payloads and the comparison template and tools.md. Without a website use MCP/companion directly; a file-only workspace uses standalone create/select. With no writer, retain runnable variant folders and a labelled draft index, without invented record refs.

Finish with runnable alternatives, a fair comparison and an explicit selection state. Promote selected behavior into a linked specification/task. A prototype is not a deployed feature, a complete backend or permission for Git delivery.

Skill settings

The owner's settings for this skill arrive in a "Skill settings" block. Honour them.

  • variants (two, three or four; default three): build exactly that many comparable versions for each design question. Label them, say what differs between them, and keep each one small enough to compare in one sitting.