design

仓库创建 2026年7月25日最近提交 4 天前SkillHot 收录 3 天前

这个 Skill 做什么

把项目的 UI 体系做成一套可复用的规范（色板、间距、tokens、基础组件），再按每个功能画出对应的屏幕和流程。分两步走：先把全局 design system 定好，之后在要做某个 feature 时单独出该功能的 screens/flows。适合在 /start 后、与 /architect 和 /features 配合使用，保证界面一致且按功能逐步落地。

▸ 展开 SKILL.md 英文原文

Define the project's UI design system (principles, tokens, base components) and, per feature, the screens/flows for that feature specifically. Two modes — run without a feature named for the system, or naming a feature for its screens. Use after /start; the system pass works alongside /architect and /features, the per-feature pass happens as each feature is about to be built.

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/bjoxiah/buildloop/main/skills/design/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/bjoxiah/buildloop/main/skills/design/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Design: System once, screens per feature

Design work splits into two things that don't belong on the same
schedule: the design *system* (palette, type, spacing, principles) is a
global invariant decided once, the same way `/architect` decides the
stack once. The screens/flows for an individual feature are feature-shaped
and can't all be known upfront — they get worked out per feature, as it's
about to be built, the same way `/features` breaks the roadmap down one
feature at a time. This skill has two modes for that reason.

## Which mode

- **Mode 1 — System.** No feature named, or `docs/DESIGN.md` doesn't
  exist yet. Run this once, early (after `/start`, alongside `/architect`).
- **Mod

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有