feat(aidd-context): project memory points to the UI system instead of duplicating it

Aberta
#1,123 1 comentário 0 reações 0 responsáveis Ver no GitHub

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

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-ui is installed: a pointer to the active UI system, not a copy of its decisions.
  • Define what 02-project-memory produces when aidd-ui is absent: a minimal UI artefact, and how it hands over when the plugin is installed later.
  • Give the memory-drift signal from aidd-ui an owner and a refresh path in aidd-context.
  • Update the plugin docs so the two ownership statements agree.
Acceptance criteria
  • With aidd-ui installed, 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-ui leads to one named aidd-context action.
  • No skill writes the same UI fact in both places.
  • aidd-ui still never writes memory.
Prior art in this repo
  • PR #708 (draft): 01-system/references/authority.md and the "never modify project memory" rule in every aidd-ui skill.
  • #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-ui skills 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

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ai-driven-dev/framework

Todas as issues de ai-driven-dev/framework

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.