菜单
Help a designer audit a live interface for drift, understand who they are designing for, turn feedback into design themes, and present work. Use to choose a first design workflow and complete one real result.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dendrite-systems/strawberry-official-skills --skill getting-started-with-design-work-in-strawberry命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Help a venture investor use Strawberry across market intelligence, deal sourcing, company research, pipeline review, meetings, diligence, investment memos, introductions, and portfolio monitoring. Use when someone wants a useful first investing workflow or a connected way to run venture work over time.
Turn accepted consulting or agency work into one reliable engagement brief covering scope, stakeholders, milestones, evidence standards, communication, systems, risks, and client-data restrictions. Use after a proposal, statement of work, or internal mandate has been accepted and delivery needs a clear starting point.
Turn an RFP, discovery conversation, or defined consulting opportunity into a clear client proposal covering the problem, outcomes, approach, scope, responsibilities, timeline, approved fees, assumptions, exclusions, and terms. Use when a consultant or client-services team wants a proposal or statement of work ready for review.
基于 SOC 职业分类
正在显示 SKILL.md
| name | getting-started-with-design-work-in-strawberry |
| description | Help a designer audit a live interface for drift, understand who they are designing for, turn feedback into design themes, and present work. Use to choose a first design workflow and complete one real result. |
Help the user finish one real piece of design work, then show them the workflow behind it.
The useful ground here is the built product rather than wherever the design is authored. Walking the live interface, gathering the evidence a decision needs, capturing what a review actually decided, and turning accepted work into something the people building it can follow.
The most useful thing here is that the companion can open the real interface and move through it.
Use strawberry/design/audit-a-design-system to walk agreed pages and record where the built
interface has drifted from the system, across the states and breakpoints that matter.
Use strawberry/product-engineering/audit-a-product-flow when the question is whether the flow
works rather than whether it looks consistent.
Use strawberry/product-engineering/synthesize-customer-feedback to turn approved feedback into
source-linked themes, so a design argument rests on what users said rather than on whoever spoke
last in the review.
Use strawberry/marketing/research-an-audience when the user needs a sourced picture of who they
are designing for.
Design decisions are usually made in a room and then lost. Use
strawberry/operations/prepare-for-meetings to walk into a review with what was decided last time,
what has changed since, and the open questions that need answers. Use
strawberry/operations/debrief-a-meeting afterwards to capture what was actually decided, what is
still open, and who owns the next move, so the same discussion does not run twice.
Use strawberry/product-engineering/write-a-product-spec when a design decision needs specifying
for the people building it, and strawberry/research-analysis/create-beautiful-slide-deck when the
work needs presenting to a room rather than reviewed in a file.
Preserve the accepted system, audit scope, states checked, and report format as a custom skill. Use
strawberry/operations/set-up-shared-team-workflow when the design team needs one shared method. A
Routine can re-walk agreed surfaces after each release and report only new drift, once scope and
review point are clear.