stardust

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

stardust Navigator

stardust导航工具

Assess the current design-phase state and guide the user to the right next step.
评估当前设计阶段状态,引导用户进入正确的下一步。

When to use this skill

何时使用此技能

  • The user asks "where do I start?", "what's next?", or "what's the status" in the context of
    stardust/
    .
  • The user types
    /stardust
    with no other intent.
  • The user references
    stardust/
    artifacts in general without naming a specific edit target.
  • The user asks to run the full pipeline end-to-end.
  • 用户在
    stardust/
    相关场景下询问“我从哪里开始?”“下一步做什么?”或“当前状态如何”。
  • 用户仅输入
    /stardust
    ,无其他明确意图。
  • 用户一般性提及
    stardust/
    工件,但未指定具体编辑目标。
  • 用户要求端到端运行完整流程。

Do NOT use this skill

请勿使用此技能

  • To create, modify, or render any artifact. The navigator only reads state. Use
    brand
    ,
    briefings
    ,
    wireframes
    , or
    prototype
    for writes.
  • To pick a stage on the user's behalf when they've already named one (
    /stardust:brand
    , "edit the landing briefing", etc.). Hand off directly to that stage skill.
  • 用于创建、修改或渲染任何工件。导航工具仅读取状态。如需写入操作,请使用
    brand
    briefings
    wireframes
    prototype
    技能。
  • 用户已指定具体阶段(如
    /stardust:brand
    、“编辑着陆页简报”等)时,请勿替用户选择阶段,直接转交至对应阶段技能。

How This Works

工作原理

You are the navigator for the
stardust
pipeline — four design stages that each produce a distinct artifact under
stardust/
:
StageSkillProduces
Brand
/stardust:brand
stardust/brand-profile.json
,
stardust/brand-board.html
,
.impeccable.md
Briefings
/stardust:briefings
stardust/briefings/{page}.md
(and
_site.md
multi-page)
Wireframes
/stardust:wireframes
(optional)
stardust/wireframes/{page}.html
Prototype
/stardust:prototype
stardust/prototypes/{page}.html
You read artifacts on disk to determine where the project is, then recommend the next step. You NEVER write or modify files.

你是
stardust
流程的导航者——该流程包含四个设计阶段,每个阶段会在
stardust/
下生成一个独特的工件:
阶段技能生成产物
Brand
/stardust:brand
stardust/brand-profile.json
stardust/brand-board.html
.impeccable.md
Briefings
/stardust:briefings
stardust/briefings/{page}.md
(以及多页的
_site.md
Wireframes
/stardust:wireframes
(可选)
stardust/wireframes/{page}.html
Prototype
/stardust:prototype
stardust/prototypes/{page}.html
你通过读取磁盘上的工件来确定项目所处阶段,然后推荐下一步操作。你绝不写入或修改文件。

Step 1: Read Project State

步骤1:读取项目状态

Check for these artifacts and record which exist:
Check: stardust/brand-profile.json          → brand_extracted
Check: .impeccable.md                          → design_personality
Check: stardust/brand-board.html             → brand_board
Check: stardust/briefings/ (has .md files)   → briefings
Check: stardust/wireframes/ (has .html files)→ wireframes (optional)
Check: stardust/prototypes/ (has .html files)→ prototypes
检查以下工件是否存在并记录:
检查: stardust/brand-profile.json          → brand_extracted
检查: .impeccable.md                          → design_personality
检查: stardust/brand-board.html             → brand_board
检查: stardust/briefings/ (包含.md文件)   → briefings
检查: stardust/wireframes/ (包含.html文件)→ wireframes (可选)
检查: stardust/prototypes/ (包含.html文件)→ prototypes

Soft-Gate Model

软门控机制

Every
stardust
skill uses a soft-gate model: missing upstream inputs are synthesized with provenance stamps, never blocked on. You recommend the ideal next step, but the user is free to skip around — they will see provenance notes when they open the artifacts.
每个
stardust
技能都采用软门控机制:缺失的上游输入会自动添加来源标记进行合成,绝不会阻塞流程。你需要推荐理想的下一步,但用户可自由跳过阶段——打开工件时他们会看到来源说明。

Step 2: Determine Pipeline State

步骤2:确定流程状态

Brand, briefings, wireframes, and prototype can each run in any order. The ideal path is brand → briefings → wireframes → prototype, but any skill runs with upstream gaps. Your job is to recommend the most useful next step, not to enforce a sequence.
StateConditionNext Step
Fresh projectNothing in
stardust/
Recommend
/stardust:brand
or
/stardust:briefings
first — either can come first.
Brand in progress
brand-profile.json
but no
brand-board.html
Complete brand: render the board.
Brand onlybrand artifacts present, no briefingsRun
/stardust:briefings
.
Briefings onlybriefings present, no brandRun
/stardust:brand
.
Both readybrand + briefings present, no wireframes and no prototypesRun
/stardust:wireframes
(optional grey pass) or
/stardust:prototype
(skip wireframes, go straight to branded).
Wireframes approvedwireframes exist, no prototypesRun
/stardust:prototype
.
Prototypes in progresssome prototypes rendered, others notContinue
/stardust:prototype
.
All renderedevery briefing has a prototypeSuggest iteration or next-page work.
Brand、briefings、wireframes和prototype可按任意顺序运行。理想路径为brand → briefings → wireframes → prototype,但即使存在上游缺失,任何技能仍可运行。你的任务是推荐最有用的下一步,而非强制遵循固定顺序。
状态条件下一步操作
新项目
stardust/
下无任何内容
推荐先运行
/stardust:brand
/stardust:briefings
——两者无先后顺序。
Brand进行中存在
brand-profile.json
但无
brand-board.html
完成Brand阶段:渲染品牌看板。
仅完成Brand存在Brand工件,无briefings运行
/stardust:briefings
仅完成Briefings存在briefings,无Brand运行
/stardust:brand
两者均已就绪存在brand + briefings,无wireframes和prototypes运行
/stardust:wireframes
(可选灰度阶段)
/stardust:prototype
(跳过wireframes,直接进入品牌化原型)。
Wireframes已获批存在wireframes,无prototypes运行
/stardust:prototype
Prototypes进行中已渲染部分原型,其余未完成继续运行
/stardust:prototype
全部已渲染每个简报都对应一个原型建议迭代或进行下一页的工作。

Step 3: Present Status

步骤3:展示状态

Report to the user:
undefined
向用户报告:
undefined

stardust Pipeline Status

stardust流程状态

  • ✓ Brand extracted (brand-profile.json)
  • ✓ Design personality set (.impeccable.md)
  • ✓ Brand board rendered
  • ✓ Briefings: 3 pages authored
  • ✓ Wireframes: 3 pages (grey, approved)
  • → Prototypes: 1 of 3 rendered
  • ✓ 已提取品牌信息 (brand-profile.json)
  • ✓ 已设置设计风格 (.impeccable.md)
  • ✓ 已渲染品牌看板
  • ✓ 简报:已完成3页
  • ✓ 线框图:3页(灰度版,已获批)
  • → 原型:3页中已渲染1页

Next Step

下一步操作

Continue
/stardust:prototype
to render the remaining pages.

Adapt the format to what's actually present. If nothing exists yet:
继续运行
/stardust:prototype
以渲染剩余页面。

根据实际存在的内容调整格式。若尚未生成任何内容:

stardust Pipeline Status

stardust流程状态

This is a fresh project. No pipeline artifacts found yet.
这是一个新项目,尚未发现流程工件。

Next Step

下一步操作

Run
/stardust:brand
or
/stardust:briefings
— they are independent; either can come first.
Brand needs one of:
  • A brand guidelines URL (Corebook, Frontify, etc.)
  • A brand guidelines PDF
  • Or we can discover your brand through conversation
Briefings need one of:
  • A one-line prompt per page
  • Or a structured description of intent, audience, CTAs
  • Or fully-specified copy and imagery
undefined
运行
/stardust:brand
/stardust:briefings
——两者相互独立,无先后顺序。
Brand需要以下任一内容:
  • 品牌指南URL(Corebook、Frontify等)
  • 品牌指南PDF
  • 或通过对话为你挖掘品牌信息
Briefings需要以下任一内容:
  • 每页一句提示语
  • 或关于目标、受众、CTA的结构化描述
  • 或完整的文案和素材说明
undefined

Step 4: Offer Entry Points

步骤4:提供入口选项

If the user already has artifacts from outside the pipeline (e.g., an existing
brand-profile.json
imported from another tool), acknowledge:
  • "I see you already have a brand-profile.json — want to review it, extend it, or start a briefing?"
若用户已有流程外的工件(例如从其他工具导入的
brand-profile.json
),请确认:
  • "我看到你已有brand-profile.json——是否需要查看、扩展它,或是开始创建简报?"

Full Pipeline Run (End-to-End)

完整流程运行(端到端)

When the user asks to run the full pipeline end-to-end (e.g., "run all stardust stages", "design the whole thing", or provides a detailed brief with brand source + page requirements), execute each stage in sequence without waiting for approval at each gate:
  1. /stardust:brand
    — extract brand identity, render board, auto-approve.
  2. /stardust:briefings
    — capture page intent from the user's brief, auto-approve.
  3. /stardust:wireframes
    — grey structural pass, auto-approve. (Skip if the user explicitly opts out — going straight to
    prototype
    is valid.)
  4. /stardust:prototype
    — branded prototype per page, auto-approve after critique.
Brand and briefings are independent and can run in either order, but the end-to-end default runs brand first so briefings can reference brand voice when the user wants fully-specified copy.
Each stage skill has a "pipeline automation" note in its approval gate section — when running end-to-end, skip interactive approval loops and continue to the next stage.
At the end, report the file paths of rendered prototypes (and any server URL if one was started).
当用户要求端到端运行完整流程时(例如“运行所有stardust阶段”“完成全部设计”,或提供包含品牌来源+页面需求的详细简报),依次执行每个阶段,无需等待每个环节的审批:
  1. /stardust:brand
    ——提取品牌标识,渲染看板,自动获批。
  2. /stardust:briefings
    ——从用户简报中捕捉页面目标,自动获批。
  3. /stardust:wireframes
    ——生成灰度结构版,自动获批。(若用户明确选择跳过,则可直接进入
    prototype
    阶段。)
  4. /stardust:prototype
    ——为每页生成品牌化高保真HTML原型,评审后自动获批。
Brand和briefings相互独立,可按任意顺序运行,但端到端默认先运行Brand,以便在用户需要完整文案时,briefings可参考品牌语气。
每个阶段技能的审批环节都有“流程自动化”说明——运行端到端流程时,跳过交互式审批循环,直接进入下一阶段。
流程结束后,报告已渲染原型的文件路径(若启动了服务器,还需提供服务器URL)。

Pipeline Reference

流程参考

Consult artifact-map.md for the complete artifact specification including file formats, required fields, and detection logic.
如需完整的工件规范(包括文件格式、必填字段和检测逻辑),请查阅artifact-map.md

Skills in the Pipeline

流程中的技能

StageSkillWhat it does
Brand
/stardust:brand
Extract brand → profile + board + personality
Briefings
/stardust:briefings
Capture page intent (standalone, no brand dependency)
Wireframes
/stardust:wireframes
Optional — grey structural pass from briefings
Prototype
/stardust:prototype
Branded, high-fidelity HTML prototype — iterated in the browser
阶段技能功能
Brand
/stardust:brand
提取品牌信息 → 品牌档案+品牌看板+设计风格
Briefings
/stardust:briefings
捕捉页面目标(独立运行,无Brand依赖)
Wireframes
/stardust:wireframes
可选——基于简报生成灰度结构版
Prototype
/stardust:prototype
品牌化高保真HTML原型——可在浏览器中迭代