spike(aidd-ui): link the UI system to code and to external design tools
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Funcionalidade
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Stack de tecnologia
- typescript
- Domínio
- developer-experience
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- TypeScript
- Estrelas
- 481
- Forks
- 45
- Merge médio
- 1d 13h
- PRs com merge (30d)
- 91
Preparar o ambiente
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de ai-driven-dev/framework
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 86/100
ai-driven-dev/framework#1311 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 79/100
ai-driven-dev/framework#1244 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
ai-driven-dev/framework#1197 ·
Mantenedores costumam responder em até 1 dia
-
refactor(aidd-context): apply the new skill template to learnTalvez já em andamento @blafourcade assumiu há 3 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
ai-driven-dev/framework#1186 · 1 responsável ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
ai-driven-dev/framework#1163 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
Todas as issues de ai-driven-dev/framework
Issues semelhantes
-
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 87/100
Mantenedores costumam responder em até 1 dia
-
🛠️ dette technique
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 61/100
betagouv/mon-entreprise#4752 · 1 comentário ·
Mantenedores costumam responder em até 5 dias
-
type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
franciscoBSalgueiro/en-croissant#1111 ·
Mantenedores costumam responder em até 2 dias
-
area/providers type/feature version/v2
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
anomalyco/opencode#64845 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia