[self-care:reactive-ui] Sync reactive-ui skill with element registry and reactive runtime

Open Beginner friendly
  • Is something wrong?
#19,923 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Edit .github/skills/reactive-ui/SKILL.md to separate EMPTY_AWARE_ELEMENTS from UNAVAILABLE_AWARE_ELEMENTS, document ASYNC_SOURCE_ELEMENTS, PAGE_BOUND_ELEMENTS, the -lazy key, and the untracked primitive. Read dashboard/site/src/components/ui-elements.js, presenter.js, and reactive.js to confirm behavior. Done when the skill file matches the source; no tests to run.

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.

The reactive-ui skill now matches how ui-elements.js, the presenter and reactive.js behave. No eligible pure-declarative view-source migration was found, so this is the single fallback task (skill drift).

Changes (.github/skills/reactive-ui/SKILL.md only)

  • Separated EMPTY_AWARE_ELEMENTS from UNAVAILABLE_AWARE_ELEMENTS. The old text treated them as one. The presenter checks them independently (presenter.js ~2695-2708).
  • Documented ASYNC_SOURCE_ELEMENTS and PAGE_BOUND_ELEMENTS. These set source lifetime and sourcesSubscribed.
  • Documented the <name>-lazy key in LAZY_ELEMENT_RENDERERS. renderUiElement wraps these in an abort-scoped root.
  • Added the exported untracked primitive from reactive.js, which was missing.

Source evidence

  • dashboard/site/src/components/ui-elements.js
  • dashboard/site/src/presenter.js
  • dashboard/site/src/reactive.js

Validation: documentation-only change, so no tests 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 · ⌖ ~1 AIC · ⊞ 16K · ◷

  • expires on Nov 5, 2026, 11:40 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.