[self-care:reactive-ui] Align reactive-ui skill with element registration and view metadata

Cerrado
  • ¿Algo no está bien?
#20,042 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
20/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, markdown
Área
documentation

Línea de trabajo

Read .github/skills/reactive-ui/SKILL.md and the spec in dashboard/site/src/specification.js (VIEW_KEYS, VIEW_ELEMENT_VALUES) and dashboard/site/src/components/ui-elements.js (LAZY_ELEMENT_RENDERERS). Update SKILL.md to describe element registration and lazy rendering as specified. Done when skill text matches the current implementation and docs/dashboard-language-specification.md.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

agentic-workflows self-care self-care:reactive-ui-expert

[!TIP]
Your pull request is ready to create! 🎉 ✅

Everything is OK—the changes have been pushed to a branch. Please review the protected files, then create the pull request when you are ready.

Create the pull request

The original pull request description is below.

This updates the reactive-ui skill so its guidance for named UI elements matches the current implementation. No production code, dashboard document, or test changes.

No eligible pure-declarative view-source migration exists. The remaining JavaScript-produced source is the synthetic simulation-days source. It is also consumed by the validator and by declarative.js, so migrating it would need production JavaScript changes.

Fixes
  • The skill said to "record a concise intent" on elements. VIEW_KEYS has no intent; it belongs to pages and row actions. The skill now says to register the element name in VIEW_ELEMENT_VALUES and to give the view subject, objective, and acceptance, with sources in data.sources.
  • The skill's lazy-registration note was vague. It now names the actual mechanism: a <name>-lazy entry in LAZY_ELEMENT_RENDERERS via lazyElementRenderer.
Evidence
  • dashboard/site/src/specification.js: VIEW_KEYS, VIEW_ELEMENT_VALUES
  • dashboard/site/src/components/ui-elements.js: LAZY_ELEMENT_RENDERERS, lazyElementRenderer
  • docs/dashboard-language-specification.md: DLS-VIEW-002 and DLS-VIEW-022
Validation

Documentation-only change to a skill file, so no test suites were run.

Control Plane

[!NOTE]
Protected files

This patch modifies protected files, which may affect project dependencies, CI/CD pipelines, or agent behaviour.

Protected files

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Generated by SelfCare / Reactive UI Expert · copilot · auto · ~59 AIC · ⌖ ~2 AIC · ⊞ 16K · ◷

  • expires on Nov 7, 2026, 7:37 PM UTC
Lenguaje dominante
JavaScript
Estrellas
14
Forks
5
Merge medio
4 h 16 min
PR fusionados (30 d)
688

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/gh-cao

Todos los issues de githubnext/gh-cao

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.