EHotwagner

Consumer-facing guide to hosting an interactive FS.Skia.UI app — the keyboard/pointer input surface, the preview-vs-tree render distinction, and the windowed-fullscreen blur caveat.

Build Skia-rendered FS.Skia.UI Controls, rich text, chart controls, graph controls, DataGrid, custom wrappers, and generated product examples.

Generated product guidance for Skia-rendered FS.Skia.UI Controls, rich text, chart controls, graph controls, DataGrid, and custom wrappers.

Wire a generated FS.Skia.UI product to the desktop viewer host.

Understand and work with the internal keyed VDOM diff over the lowered Control<'msg> IR (feature 067) — its key-first-then-positional matching, the NodePatch/ChildOp operation set, the totality/determinism/identity-at-rest/round-trip invariants, and the module's disposition (internal, property-tested, wired onto the live render path via RetainedRender in feature 091 and current through feature 103 — layout/bounds cache, injected-delta animation clock, visual-state cross-fade). Use when reading the diff invariants, extending the property tests, or working on the wired retained render path.

Maintainer-facing guide to the FS.Skia.UI.Controls.Elmish interactive-host seam — how runInteractiveApp drives the retained render structure each frame (RetainedRender.step over the keyed diff), advances per-identity animation clocks from an injected Tick delta, stamps runtime visual state pre-reconcile, routes keys focus-first through routeFocusedKey, and resolves pointer hits to a stable identity via retainedHitTest. Use when reading or extending the live controls host loop, the per-frame retained-state/clock/visual-state wiring, or the key/pointer routing seam.

Generated product guidance for Skia-rendered FS.Skia.UI Controls, rich text, chart controls, graph controls, DataGrid, and custom wrappers.

Deterministic render-only evidence mode, visual-proof honesty, and benign/blocking host-warning classification.

Load FSBar assemblies into the FSI MCP server, including the libglfw/libSkiaSharp dlopen preload dance required before any #r. Use when the user wants to poke at FSBar.Viz / FSBar.Client / FSBar.Hub interactively via FSI.

Launch the FSBar Hub GUI (FSBar.Hub.App) with the required display env vars, and document the FSBAR_HUB_* env-var matrix for CI smoke tests, initial tab, auto-launch, screenshotting, and bundled-proxy overrides.

Regenerate committed per-map analysis cache (chokepoints + MapGrid blobs) under bots/trainer/map-cache/*.json. Use after bumping MapCacheFile codeVersion or adding a SupportedMap.

Regenerate FSBar.Proto F# code from proto/highbar/*.proto and proto/hub/scripting.proto via buf generate. Use when a .proto file changed and the committed src/FSBar.Proto/Generated/*.gen.fs files need refreshing.

Regenerate src/FSBar.Viz/UnitLabels.generated.fs — the byte-stable 2- or 3-char label table for every BarData unit. Use after nupkg/BarData.*.nupkg changes or when a new unit appears.

Update a locally-developed NuGet dependency (SkiaViewer, BarData) into FSBarV1 via the upstream pack-dev.sh timestamp-versioned prerelease workflow. Use when user edits a sibling repo and needs the change picked up in FSBarV1.

Start a headless BAR engine REPL in FSI with live SkiaViewer visualization. Restarts FSI, loads Repl.fsx, and opens the module.

Start a graphical (windowed) BAR engine REPL in FSI. Restarts FSI, loads ReplGraphical.fsx, and opens the module.

Create or update project governing principles and development guidelines.

Merge-gate audit: synthetic propagation + diff-scan. Hard-blocks on either.

Validate and render the task DAG; compute synthetic propagation.

Execute all tasks from the task breakdown to build the feature.

Break down implementation plans into actionable task lists.

Create or update project governing principles and development guidelines.

Merge-gate audit: synthetic propagation + diff-scan. Hard-blocks on either.

Validate and render the task DAG; compute synthetic propagation.

Execute all tasks from the task breakdown to build the feature.

Break down implementation plans into actionable task lists.

Use when the user asks to "write a proto file", "create protobuf definitions", "generate F# from proto", "set up proto compilation", "define gRPC service contract", "convert proto to F#", or needs to work with .proto files and generate F# code from them.

Use when the user asks to "set up gRPC", "add gRPC to my F# project", "initialize gRPC", "configure gRPC tooling", "install gRPC packages", "create a gRPC project", or needs to bootstrap gRPC infrastructure in an F# solution.

Use when the user asks to "implement a gRPC server", "create gRPC service implementation", "host a gRPC service", "write gRPC server in F#", "add gRPC endpoint", "configure gRPC server", or needs to implement and host gRPC services in an F# ASP.NET Core application.

Use when the user asks to "call a gRPC service", "create gRPC client", "consume gRPC service from F#", "connect to gRPC server", "write gRPC client code", "gRPC client streaming", or needs to consume gRPC services from F# client code.

Use when the user asks to "create gRPC without proto files", "code-first gRPC", "define gRPC service in F#", "use protobuf-net with F#", "gRPC with F# records", "gRPC without .proto", or wants to define gRPC contracts using native F# types instead of .proto files.

This skill should be used when the user asks to "add doc comments", "improve XML docs", "document the API", "add XML documentation", "write doc comments for F#", "document public API", "add summary comments", or needs to write or improve `///` XML documentation comments in F# source files. This skill edits .fs source files, not docs/ content files.

This skill should be used when the user asks to "build docs", "build documentation", "run fsdocs", "preview docs", "watch docs", "fsdocs build errors", "fix doc build", or needs to build, preview, or troubleshoot an FSharp.Formatting documentation site. Covers build commands, watch mode, common errors, and build flags.

This skill should be used when the user asks to "write documentation examples", "create literate scripts", "add fsx docs", "write a tutorial", "create a how-to guide", "add example scripts to docs", "write literate F# documentation", or needs to create `.fsx` literate scripts in the `docs/` directory that teach library usage through executable, narrative-driven examples.

This skill should be used when the user asks to "set up fsdocs", "initialize documentation", "scaffold docs folder", "configure FSharp.Formatting", "add documentation to my F# project", "create docs site", or needs to set up a documentation pipeline for an F# project from scratch. Covers tool installation, directory structure, MSBuild configuration, and initial content creation.

This skill should be used when the user asks to "write architecture docs", "document design decisions", "create an ADR", "write technical documentation", "explain the architecture", "document internals", "add a migration guide", or needs to create Markdown documentation in `docs/` that explains architecture, design decisions, and system internals for an FSharp.Formatting site.

Create or update project governing principles and development guidelines.

Execute all tasks from the task breakdown to build the feature.

Break down implementation plans into actionable task lists.

Squash-merge all feature branches into the default branch (main or master), delete them, and push. Use when the user says "land this", "ship the feature", "merge the feature branches", "squash-merge and push", or anything that means consolidating feature work onto the trunk. After a successful merge, every packable project MUST be packed with a bumped version number.

Iteratively diagnose, fix, and re-test until the build and tests are green, with hard safety rails. Use when the user says "make it pass", "fix the build", "get tests green", "debug until it works", "iterate on the failures", or any request for an autonomous fix-until-green loop. Writes an iteration log to readiness/debug-loop.log.md.

Use when the user wants a feature branch squash-merged into its base branch and pushed to the remote GitHub repository. This skill performs a non-interactive GitHub CLI workflow: verify repo state, verify or push the feature branch, locate or create the pull request if needed, squash merge it with an explicit subject/body, and confirm the remote base branch now contains the merged work.

Use when a feature idea, spec, or implementation plan needs an adversarial review before or during delivery. This skill researches the feature as if trying to break the proposal, then reports holes, blockers, hidden dependencies, unrealistic assumptions, missing environments, missing contracts, required mockups, required synthetic data, and missing validation evidence. Use it to produce a structured go/no-go gap report for a feature that must actually work, not just look plausible on paper.

Finish a Speckit feature branch by squash-merging it into its target branch, committing all remaining work, pushing to the GitHub remote, and deleting the feature branch locally and remotely. Use when Codex needs to land a completed Speckit branch with non-interactive git commands and clean up the branch afterward.

Use this skill when working on F# applications built with Avalonia.FuncUI and Avalonia, especially when editing `.fs`, `.fsproj`, or Avalonia-related UI code, creating code-first views and components, wiring state or Elmish update loops, translating Avalonia layout or styling guidance into FuncUI DSL, or checking package/version compatibility between FuncUI and Avalonia docs.

Use when the user asks to "create a physics simulation", "throw a ball", "build a scene", "use PhysicsSandbox", "script physics in F#", "connect to physics server", "create bodies/spheres/boxes", "apply forces/impulses", "set up constraints", "run a physics experiment", or needs to work with PhysicsSandbox via the PClientV2 F# scripting library. Also use when the user is working in a .fsx file that references PClientV2 or PhysicsClient, or when using the FSI MCP server to interact with a physics simulation.