discovery-questions
Skill1 starsChanged 2 months agoMITView on GitHub
在新的或信息不足的页面、原型、演示文稿、品牌和其他设计任务开始前,集中确认受众、目标、保真度、品牌或设计系统、探索数量和重点轴。用户需求存在会显著改变设计方向的空白时使用;小改动、精确复刻或上下文已经充分时不要触发。
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Hyde-and-Larkin/product-marketing-toolkittheir own version, first seen Nov 1, 2026
- Onevium/skillsword for word, first seen Sep 4, 2026
Other versions2 projects use a version of this.
Word for word · 1
- Onevium/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 1
- Hyde-and-Larkin/product-marketing-toolkit★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- narrative-video-directorSkill
- portrait-shoot-directorSkill
- accessibility-auditSkill
- ai-slop-checkSkill
- component-extractSkill
- design-system-extractSkill
- frontend-aesthetic-directionSkill
- generate-variationsSkill
- hierarchy-rhythm-reviewSkill
- interaction-states-passSkill
- make-a-deckSkill
- make-a-prototypeSkill
- make-tweakableSkill
- polish-passSkill
- wireframeSkill
- code-quality-reviewSkill
The file
Files
设计启动问题
在高保真工作前一次性补齐真正影响方向的信息。问题的价值来自答案会改变设计,而不是因为提问显得谨慎。
1. 先读取已有材料
完整查看用户已提供的代码、截图、品牌规范、设计系统、UI Kit、需求和参考链接。能从材料确认的内容不要重复询问。
2. 判断是否需要提问
以下信息缺失且会改变结果时才问:
- 目标用户、业务目标或主要行动。
- 输出媒介、范围、保真度或目标设备。
- 必须遵循的品牌、设计系统、现有产品或参考。
- 需要多少方向,以及主要探索视觉、布局、交互、流程还是文案。
- 创新程度、明确禁区和必须保留内容。
- 最终哪些变量需要允许用户现场调整。
若只是标签、默认值或两个等价实现,直接做出合理决定并在交付时说明。精确复刻、小修复和上下文充分的后续任务应跳过提问。
3. 组成一次性问题集
根据歧义程度提出通常 3–6 个、最多约 10 个问题。优先级从高到低排列,避免为了凑数提问。
按任务补充:
- 演示文稿:受众知识水平、时长或页数、语气、来源材料、是否需要讲者备注。
- 落地页:主要行动、核心人群、喜欢与拒绝的参考、移动端或桌面端优先。
- 原型:完整流程、屏幕列表、保真度、设备框架、目标状态和示例数据。
- 品牌方向:三个形容词、行业语境、参考设计中具体喜欢的部分和禁用风格。
4. 提问并停下
一次性给出编号问题;运行环境提供结构化提问工具时可以使用。选择题应提供“帮我决定”和开放填写入口,但不要硬塞不适用的选项。
发出问题后结束当前轮次,等待用户回答。不要提前猜答案继续制作。
5. 收到答案后执行
简要复述最影响方向的选择,指出明显矛盾,再进入合适的制作流程。后续遇到小决定时自主判断;只有新信息会实质改变方向时才再次提问。
示例
输入:“给我们的新 API 产品做一个落地页。”
**输出:**一次性询问现有品牌或网站、主要行动、核心人群、需要探索的方向数量与轴、目标设备和禁用风格,然后停止并等待答案。
来源与许可
本 Skill 基于 Trystan Sarrade 的 claude-design-system-prompt 进行中文化与 Claude Skill 规范适配。上游与本改编均按 MIT License 发布,详见 LICENSE.txt。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

