feat(aidd-context): project memory points to the UI system instead of duplicating it
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
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- typescript
- Domínio
- developer-experience
Direção de pesquisa
Start with 01-system/references/authority.md and the 02-project-memory skills and templates, then compare their ownership rules with the aidd-ui skills and the Project Memory model in #801. Define the refresh and handover behavior for both plugin states, and name the aidd-context action that handles stale-memory reports. Done means the acceptance criteria are met and the plugin docs agree; coordinate with the open #801 and draft PR #708.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Problem
PR #708 makes aidd-ui read project memory and never write it, with code winning over memory when they differ (01-system/references/authority.md). The other half is on the aidd-context side and is not specified: what the memory holds about UI once the plugin is installed.
Today a project's UI knowledge can live in two places: the memory that 02-project-memory builds, and the UI system and feature contracts that aidd-ui maintains. When both describe the same design, they diverge and the model reads the stale one. The plugin reports memory drift "for a separate Context-owned refresh", but no skill owns that refresh yet.
Raised in a community lab on the plugin: if the UI plugin is installed, memory should point to it instead of duplicating it; if it is not, memory should still create a minimal UI artefact rather than leave a gap.
Scope
- Define what project memory holds about UI when
aidd-uiis installed: a pointer to the active UI system, not a copy of its decisions. - Define what
02-project-memoryproduces whenaidd-uiis absent: a minimal UI artefact, and how it hands over when the plugin is installed later. - Give the memory-drift signal from
aidd-uian owner and a refresh path inaidd-context. - Update the plugin docs so the two ownership statements agree.
Acceptance criteria
- With
aidd-uiinstalled, a memory refresh writes a pointer to the active UI system and no copy of its decisions. - Without
aidd-ui, a memory refresh writes a minimal UI artefact, and installing the plugin later replaces it by a pointer without losing information. - A stale-memory report from
aidd-uileads to one namedaidd-contextaction. - No skill writes the same UI fact in both places.
-
aidd-uistill never writes memory.
Prior art in this repo
- PR #708 (draft):
01-system/references/authority.mdand the "never modify project memory" rule in everyaidd-uiskill. - #801 (open): documents the Project Memory model and lifecycle; this issue must stay consistent with it.
- #732 (merged): reshaped the memory bank to its own templates.
Out of scope
- Writing memory from
aidd-ui: it stays read-only by design. - Renaming the
aidd-uiskills or artefact files (design,adapt, the system file name): a review change on PR #708.
- 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
-
type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
db-ux-design-system/core-web#8856 ·
Mantenedores costumam responder em até 1 dia
-
'!' breaking change is lost when the commit also has an empty BREAKING CHANGE footerTalvez já em andamento @wittdennis assumiu hoje. Abertapriority: p3 type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
googleapis/release-please#2971 ·
Mantenedores costumam responder em até 1 dia
-
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