MicrosoftKnown publishermicrosoft/microsoft-ui-reactor/plugins/reactor/skills/reactor-recipes/SKILL.mdreactor-recipes
Skill839 starsChanged 7 days agoMITView on GitHub
Paste-ready single-file Reactor recipes indexed by intent — list with add/delete/toggle, sidebar navigation between pages, form with validation + submit gating, async fetch with loading/error/data states, themed Win11 card surface. Use a recipe instead of synthesizing from prose: copy, adjust, ship.
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-dslSkill
- reactor-formsSkill
- reactor-getting-startedSkill
- reactor-inputSkill
- reactor-navigationSkill
- reactor-windowingSkill
- reactor-wrappingSkill
- reactor-appSkill
- ChartingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 39
If you need analyzer coverage (REACTOR_DSL_001 and friends), promote the recipe to a .csproj — single-file .cs builds don't load analyzers.
≈ “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
How to use this skill
Each recipe is a complete, compilable single-file program. Copy the file's body directly into your project; don't synthesize the pattern from scratch. The recipes use real Reactor APIs only — no pseudocode.
The full recipe content is in references/<name>.cs. Read just the recipe(s) that match your intent.
Intent → recipe map
| Intent | Recipe | APIs used |
| Add / remove / toggle items in a list | references/list-add-delete.cs | UseReducer, WithKey, Command |
| Animate list insert / move / remove | references/animated-list.md | Animations.Animate, AnimationKind, IReactorKeyed, UseReducedMotion |
| Sidebar navigation between pages | references/sidebar-nav.cs | UseNavigation, NavigationView, NavigationHost, WithNavigation |
| Form with validation + submit gating | references/form-with-validation.cs | UseValidationContext, FormField, Validate.*, ShowWhen |
| Fetch data with loading / error / data states | references/async-fetch-list.cs | UseResource, AsyncValue<T>.Match |
| Themed Win11 card surface | references/themed-card.cs | Theme.* tokens, Border, FlexColumn, .Padding, .CornerRadius, .WithBorder |
| Absolute positioning with Canvas | references/canvas-positioning.cs | Canvas, .Canvas(left, top), .CenterAt, shapes |
See references/index.md for the full index.
Recipe contract
A good recipe:
- Compiles standalone (
dotnet runworks against the file). - Targets one intent — no kitchen-sink demos.
- Stays under ~120 lines including imports and
ReactorApp.Runshell. - Uses real Reactor APIs only.
- Comments only the non-obvious.
Adapting a recipe
The recipes use #:package Microsoft.UI.Reactor@0.0.0-local (selfhost default). Replace the version with whatever you depend on outside the source clone.
If you need analyzer coverage (REACTOR_DSL_001 and friends), promote the recipe to a .csproj — single-file .cs builds don't load analyzers. See reactor-getting-started for the .csproj template.
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.