feat(aidd-context): project memory points to the UI system instead of duplicating it
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- developer-experience
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- TypeScript
- Stelle
- 481
- Fork
- 45
- Merge medio
- 1g 13h
- PR unite (30g)
- 91
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ai-driven-dev/framework
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
ai-driven-dev/framework#1311 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
ai-driven-dev/framework#1244 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
ai-driven-dev/framework#1197 ·
I maintainer di solito rispondono entro 1 giorno
-
refactor(aidd-context): apply the new skill template to learnForse già presa @blafourcade l’ha presa 3 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
ai-driven-dev/framework#1186 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
ai-driven-dev/framework#1163 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di ai-driven-dev/framework
Issue simili
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
elastic/kibana#306401 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
agentes-chat/agentes-chat#927 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Webapp workspace fails to render in Safari — "Can't find variable: requestIdleCallback"Apertacomp/desktop P2 type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
NousResearch/hermes-agent#157702 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
e2e-failure ready-to-code
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
redhat-developer/rhdh-plugin-export-overlays#4794 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno