feat(aidd-context): project memory points to the UI system instead of duplicating it
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- developer-experience
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 481
- Forks
- 45
- Merge medio
- 1 d 13 h
- PR fusionados (30 d)
- 91
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ai-driven-dev/framework
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
ai-driven-dev/framework#1311 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
ai-driven-dev/framework#1244 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ai-driven-dev/framework#1197 ·
Los mantenedores suelen responder en 1 día
-
refactor(aidd-context): apply the new skill template to learnPosiblemente ocupada @blafourcade la tomó hace 3 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ai-driven-dev/framework#1186 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
ai-driven-dev/framework#1163 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de ai-driven-dev/framework
Issues similares
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPosiblemente ocupada @pcbeingused333 la tomó hoy. AbiertoBug db: d1-sqlite Payload OSS
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
payloadcms/payload#19766 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
device-management-toolkit/sample-web-ui#3711 ·
Los mantenedores suelen responder en 1 día
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elastic/kibana#306401 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
agentes-chat/agentes-chat#927 ·
Los mantenedores suelen responder en 1 día
-
Closing a pinned tab jumps to the Tabs section instead of the next open pinned tabPosiblemente ocupada @seenimohamed la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ardia-browser/ardia#2769 ·
Los mantenedores suelen responder en 1 día