jui-dombuilder

Build and update DOM with JUI's DomBuilder. Use this skill whenever rendering or re-rendering DOM in a JUI component, control or fragment: building element trees with Div/Span/H3/A/Button etc. under Wrap.$(el), extracting elements with .by()/.use(), wiring events with .onclick()/.on(), inserting child components, and — critically — updating part of the DOM at runtime. Triggers include: DomBuilder, Wrap, Wrap.buildInto, buildInto, rerender, re-render, refresh part of the DOM, update the DOM, ElementBuilder, INodeProvider, StateComponent, StateVariable, 'my onclick stopped firing after re-render', 'event handler not wired up', 'how do I redraw a section'.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable reference with executable examples and a useful decision table for the DOM-update problem space. The main gaps are minor: a few trimmable prose passages and no explicit verification step in the runtime-update workflow.

Suggestions

Tighten framing prose (e.g., 'the part that trips people up most', 'This is the cleaner semantic and the default choice') to lift conciseness toward a lean, every-token-earns-its-place standard.

Add an explicit verification checkpoint to the Workflow (e.g., 'After any rebuild, confirm onclick/on handlers still fire; if dead, you used Wrap.buildInto on interactive content — switch to the component's buildInto').

Consider moving the detailed per-method builder reference (Common builder methods, Text nodes, Events listings) into a bundled reference file so SKILL.md reads as a tighter overview pointing one level deep.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and code-heavy with no padding about concepts Claude already knows, but a few framing sentences ('the part that trips people up most', 'This is the cleaner semantic and the default choice') could be trimmed. Not a 5 because not every prose token strictly earns its place.	4 / 5
Actionability	Fully executable copy-paste Java examples covering building, extracting, events, inserting children, and all four update paths, plus a decision table and concrete method signatures — specific examples cover the common cases.	5 / 5
Workflow Clarity	A clear 4-step Workflow sequence and a decision table act as a checklist for choosing the right update path, with the 'trap' callout as a correctness checkpoint. Not a 5 because there is no explicit verify/feedback step (e.g., 'confirm events are still wired after a rebuild').	4 / 5
Progressive Disclosure	Well-organized into clear sections with well-signaled one-level-deep references (the Documentation links to external docs and pointers to the sibling jui-components skill). Not a 5 because the bulk reference material lives inline in SKILL.md rather than being split into bundled reference files.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: third-person, concrete, and comprehensive, with an explicit 'Use when...' trigger clause and a rich list of both technical and natural-language triggers. It clearly conveys capability and invocation conditions with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'building element trees with Div/Span/H3/A/Button', 'extracting elements with .by()/.use()', 'wiring events with .onclick()/.on()', 'inserting child components', 'updating part of the DOM at runtime' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' ('Build and update DOM with JUI's DomBuilder' plus enumerated actions) and 'when' ('Use this skill whenever rendering or re-rendering DOM in a JUI component, control or fragment' plus a concrete 'Triggers include' list).	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms (rerender / re-render) and real user phrasings ('my onclick stopped firing after re-render', 'event handler not wired up', 'how do I redraw a section') alongside the technical API names users would invoke.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (JUI's DomBuilder specifically) with distinctive triggers like 'Wrap.$(el)', 'Wrap.buildInto', 'INodeProvider', 'StateComponent' that would not fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: juiproject/jui-stack
Path: jui-skills/jui-dombuilder/SKILL.md
Commit: 3639345

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.