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

Open
  • Is something wrong?
#20,042 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, markdown
Domain
documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

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
Dominant language
JavaScript
Stars
14
Forks
5
Avg merge
3h 24m
Merged PRs (30d)
796

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-cao

All issues in githubnext/gh-cao

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.