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

Ouverte
#1,123 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
TypeScript
Étoiles
481
Forks
45
Merge moyen
1 j 13 h
PR mergées (30 j)
91

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ai-driven-dev/framework

Toutes les issues de ai-driven-dev/framework

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.