spike(aidd-ui): link the UI system to code and to external design tools
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with PR #708, especially 01-system actions 02-map and 08-reconcile, references/authority.md, and aidd-dev:01-plan; also review closed issue #222. Run the proposed approaches against at least one real project and gather evidence for each scope question. Done means a written decision for every question, example mappings for a component and token, scoped follow-up issues, and explicit handling of projects without external design tools or existing code.
由索引模型根据 Issue 内容生成。
描述
Problem
aidd-ui keeps its UI system as agnostic Markdown contracts. Two links are missing, and PR #708 lists them as limitations ("No Figma integration"; the Dev wireframe fallback stays until UI capability can be assumed).
- Design to code. Nothing says which implementation file realises which contract entry.
01-systemrecords canonical source paths per surface, but there is no index a skill can follow from a component or token in the contract to the code that implements it, nor back. Without it, drift between design and code is found by reading, not by checking. - Design tools. Teams already hold their design elsewhere (Claude Design, Figma, Impeccable's own documents) or only in code (legacy projects with no design system). The plugin treats external documents as supporting evidence only (
authority.md), which is sound, but gives no way to bring them in, nor to know that the external source moved since the contract was last aligned.
The constraint: a participant reported that Claude Design talks to Claude Code through an MCP and that this link does not extend to other coding agents (to be verified by the spike). A plugin that depends on it would break AIDD's host-agnostic position.
This came out of a community lab on the plugin: the design-to-code mapping and the external-tool interface were the two points the presenter had no answer to.
Scope
A spike, not an implementation. Answer, with evidence from at least one real project:
- What minimal mapping from a contract entry to its implementation survives any stack? Compare one file per component against a single index file, and what each means for per-component versioning.
- Which part belongs to
aidd-uiand which toaidd-dev(the implementation side owns the code; the contract is agnostic). - What strict input contract does
01-systemneed so that any source (existing code, an external design export, nothing) produces the same contract shape? - How does a contract record where an entry came from and at which version of that source, so a later session can tell it is stale?
- At planning time, when the external source changed, how does the user choose between syncing first and planning against the current contract?
01-system/actions/08-reconcile.mdalready classifies the differences; the question is the trigger and the choice. - Which of the host-agnostic options cost least to keep working across Claude Code, Codex and the other supported hosts.
Acceptance criteria
- A written decision for each scope question, each one backed by a run on a real project, not by reasoning alone.
- A recommended minimal mapping format, with one example for a component and one for a token.
- A list of follow-up implementation issues, each scoped to one skill, with the ones that are not worth doing named as such.
- The decision states what happens for a project with no external design tool, and for one with no existing code.
- No dependency on a single host's native design-to-code link.
Prior art in this repo
- PR #708 (draft):
01-systemactions02-mapand08-reconcile,references/authority.md, "Known limitations". aidd-dev:01-planin PR #708: revalidates UI-system revisions before implementation and stops on drift.- #222 (closed): "ui: design to code" placeholder, never scoped.
Out of scope
- Importing from a specific design tool or shipping its connector: the spike decides whether one is worth building.
- Versioning the whole system per component: noted by the spike, decided only if the mapping format needs it.
- A gate on changes to widely reused surfaces: a separate increment once the mapping gives a reuse count.
- 主要语言
- TypeScript
- 星标
- 481
- 派生
- 45
- 平均合并
- 1 天 13 小时
- 30 天内合并 PR
- 91
环境准备
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ai-driven-dev/framework 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 86/100
ai-driven-dev/framework#1311 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 79/100
ai-driven-dev/framework#1244 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
ai-driven-dev/framework#1197 ·
维护者通常 1 天内回复
-
refactor(aidd-context): apply the new skill template to learn可能已有人在做 @blafourcade 于 3 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
ai-driven-dev/framework#1186 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
ai-driven-dev/framework#1163 · 1 条评论 ·
维护者通常 1 天内回复
查看 ai-driven-dev/framework 的全部 Issue
相似的 Issue
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keys可能已有人在做 @pcbeingused333 今天认领。 未关闭Bug db: d1-sqlite Payload OSS
难度 2/5 1-3 小时 新手友好度 76/100
payloadcms/payload#19766 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
device-management-toolkit/sample-web-ui#3711 ·
维护者通常 1 天内回复
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
难度 2/5 1-3 小时 新手友好度 72/100
elastic/kibana#306401 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
agentes-chat/agentes-chat#927 ·
维护者通常 1 天内回复
-
Closing a pinned tab jumps to the Tabs section instead of the next open pinned tab可能已有人在做 @seenimohamed 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
ardia-browser/ardia#2769 ·
维护者通常 1 天内回复