reactor-dsl
Skill839 starsChanged 6 days agoMITView on GitHub
Pointer to the full Reactor API signatures index (`references/reactor.api.txt`). The 90% of DSL content — hooks, components, common factories, modifiers, theme tokens, gotchas, React-to-Reactor mapping — already lives in `reactor-getting-started`. Load this skill only when you need to verify a less-common signature against the alphabetized full index.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- analyzer-dymSkill
- coverage-upliftSkill
- perf-compareSkill
- pr-lifecycleSkill
- pr-reviewSkill
- reactor-advancedSkill
- reactor-asyncSkill
- reactor-build-and-checkSkill
- reactor-chartsSkill
- reactor-commandingSkill
- reactor-designSkill
- reactor-devtoolsSkill
- reactor-dockingSkill
- reactor-formsSkill
- reactor-getting-startedSkill
- reactor-inputSkill
- reactor-navigationSkill
- reactor-recipesSkill
- reactor-windowingSkill
- reactor-wrappingSkill
- reactor-appSkill
- ChartingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Read the file once, scan for what you need, then keep working from memory.
- Very specific: line 46
If you only need to confirm whether a single name exists, use a grep for the symbol against the file rather than viewing it whole.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What this skill carries
The full alphabetized signatures index lives at:
references/reactor.api.txt (~70K tokens, ~6.3K lines)It covers every public factory, modifier, hook, theme token and enum, plus a
## Public types section carrying the constructors, properties, methods and
events of every other public type — including public static classes, so
process-wide entry points such as ControlRegistry.Register and
ReactorApp.Run are listed there too.
It is large: grep it for the symbol you need rather than reading it end to end.
It is the source of truth for the public API surface, regenerated from Reactor.dll by mur --regen-api.
In addition, the skill carries focused topical references for surfaces big enough to need their own page:
| Topic | File | When to load |
| Keyed list reconciliation | references/keyed-lists.md | Choosing between IReactorKeyed, an explicit keySelector, and the three .WithKey(...) overloads; debugging a list that re-mounts on insert; understanding the bulk-replace bailout or the duplicate-key diagnostic. (Spec 042.) |
| Element refs and reference props | references/element-refs.md | Wiring UseElementRef<T>(), .Ref(...), .Target(...), accessibility relationships, XYFocus*, or custom descriptor .Reference / .ReferenceList entries. (Spec 057.) |
When to load this skill
You probably don't need to. The reactor-getting-started skill carries the hooks table, the most-used factory signatures, the React-to-Reactor mapping, modifiers, theme tokens, and the critical gotchas — that's the 90% case.
Load this skill only when:
- You've checked
reactor-getting-startedand the factory/modifier you need isn't listed. - You see a
REACTOR_*analyzer ID and want to confirm the exact API surface in question. - You're using a less-common control (DataGrid column overrides, AnnotatedScrollBar, AcrylicBrush parameters, etc.).
How to use the api index
Read the file once, scan for what you need, then keep working from memory. Do not re-page through it — the file is large and re-reading injects ~12K tokens per call. Per-pattern lookups are far cheaper than full re-reads.
If you only need to confirm whether a single name exists, use a grep for the symbol against the file rather than viewing it whole.
Fluent naming convention (callbacks)
Callback properties are named OnX on the record (e.g. OnClick, OnChanged,
OnSelectedTagChanged). The matching fluent extension drops the leading On
and is named after the event:
// Record property is OnClick — the fluent is .Click(...)
Button("Save").Click(() => Save());
// Record property is OnSelectedTagChanged — the fluent is .SelectedTagChanged(...)
NavigationView(...).SelectedTagChanged(tag => Navigate(tag));This is intentional — C# doesn't allow an extension method to share a name
with an instance property, so the On prefix lives on the property and the
event-style name lives on the fluent. The two surfaces are equivalent;
prefer the fluent for new code. Passing null to any OnX fluent clears
the handler.
Common naming gotchas
FlexElementrecord properties (set viawith { ... }):Direction,JustifyContent,AlignItems,AlignContent,Wrap,ColumnGap,RowGap⚠️ It'sJustifyContent— NOTJustify. Example:FlexRow(a, b, c) with { JustifyContent = FlexJustify.SpaceBetween, ColumnGap = 8 }
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

