detail-flow

Installation
SKILL.md

DetailFlow

Overview

Use this skill to turn a product or feature idea into a useful, polished detail page. Prioritize clear product communication, real user workflows, implementation quality, responsive behavior, and visual assets that reveal the product rather than decorative filler. Keep planning reusable across product categories and frontend stacks. The Agent owns planning and review; the user selects Starcanvas MCP or a compatible image API.

For image detail-page work, focus on content clarity and the visual design of the page set. Marketing-performance research, conversion measurement, and sales-effect validation are outside the default workflow.

Backend selection before installation

For image production or installation, read backend selection before any Starcanvas setup. Ask once for Starcanvas or API, reusing explicit choices. Planning-only work needs no backend. An installation-only request may install shared files and defer selection; it must not start Starcanvas by default.

API users provide their own base URL, private Key and exact model. Match supported protocols and perform read-only checks as described in API execution; stop with the actual reason on mismatch. No provider presets, automatic model substitution or on-the-fly adapters. Never offer chat as a Key input option. API mode skips Starcanvas setup/doctor/compiler/node readback and canvas-specific accounting; those instructions below apply only to Starcanvas. Shared direct-v4 product brief, reference roles, planning checks, editable review, approval and visual review apply to both routes. Keep the current no-currency delivery policy for both routes.

Ratio quick reference: 9:16 is the default only. PT2.5-stable options verified on Starcanvas 1.8.9 are 1:1, 2:3, 3:2, 3:4, 4:3, 4:5, 5:4, 9:16, 16:9, 21:9. Use the user's confirmed ratio directly. Reuse this list rather than repeatedly discovering it during generation or repair; refresh only for a model/version change, a specific parameter error, or an uncached request. See model settings. Changing ratio does not itself request a different backend or HTML screenshot production.

For Starcanvas execution, read Unified executor and use the bundled compiler/executor. New tasks use workflow=detail-flow-direct-v4: approved plan -> complete final-page batch -> visual review. No master or preview is required by default.

For a new product, follow the current-product and reviewed-reference contract. Start a fresh product brief; fill page subject/display choices and ordered reference roles within the existing plan, resolve concrete planning warnings, then compile. This adds no user approval gate. Historical v2/v3 packages remain inspectable and recoverable.

Installs
51
GitHub Stars
297
First Seen
Jun 15, 2026