rask

Build and drive the `rask` CLI (src/Rask.Cli) — the framework's scaffolding front door (rask new / generate / db / dev / deploy / info). Use to run, build, smoke-test, or exercise the CLI, or to confirm a change to `rask new` or `rask generate` actually scaffolds a real project on disk (not just that a unit test passes). Driven by a committed bash smoke script.

Build, launch, and drive the Rask WASM showcase (samples/Rask.Example.Wasm, served by Rask.Example.Wasm.Host) — the same components running client-side on WebAssembly. Use to run/start/launch the WASM app, take a screenshot, or confirm a change works in the real browser-WASM runtime (not just tests). Drives it headlessly with a committed C# Playwright driver — pure .NET, no Node.

Build, launch, and drive the Rask Server showcase app (samples/Rask.Example.Server) — the server-rendered, live-over-WebSocket demo of the framework. Use to run/start/launch the app, take a screenshot, or confirm a UI change works in the real running app (not just tests). Drives it headlessly with a committed C# Playwright driver — pure .NET, no Node.

Cut a Rask release. Use when publishing a new version to NuGet/GitHub. Promotes the CHANGELOG [Unreleased] section to a dated version, then tags vX.Y.Z so MinVer derives the version and release.yml runs the unit gate + sharded E2E + packs and pushes the NuGet packages and GitHub release.

The Rask "definition of done" gate. Use before committing or opening a PR for any change in the Rask repo — it formats with dotnet format (.editorconfig), enforces a warnings-as-errors analyzer-clean build, requires unit tests for new features and E2E tests for example-app changes, runs benchmarks for framework/render-hotpath changes, updates the CHANGELOG, reviews for security/perf/memory, then opens a PR with no AI attribution.

Run Rask render/runtime benchmarks before and after a framework change and report the Allocated delta. Use whenever you modify render hot-path or live-runtime code in src/Rask.Core or src/Rask.Server (HtmlSerializer, Element/Component render, Live/* diff codec, WS/WASM dispatch, payload build). Required evidence for any hotpath PR.

Add a Roslyn CodeFixProvider (IDE lightbulb quick-fix) for an existing RASK0xx diagnostic. Use when a diagnostic has a single obvious mechanical fix. Implements the provider in src/Rask.Generators.CodeFixes, adds an apply-and-compare test in tests/Rask.Generators.Tests, notes the quick-fix in docs/diagnostics.md.

Add a new RASK0xx compile-time diagnostic to the Rask Roslyn generators/analyzers. Use when introducing a new warning or error in src/Rask.Generators. Defines the DiagnosticDescriptor, wires DiagnosticHelp.Link, documents it in docs/diagnostics.md (TOC row + section), and adds a generator test.

Scaffold a new HTML tag component in Rask.Core. Use whenever adding support for an HTML element (e.g. <dialog>, <details>, <progress>, <video>) to the Rask framework. Creates src/Rask.Core/Components/{Tag}.cs and the matching tests/Rask.Core.Tests/Components/{Tag}Tests.cs asserting exact attribute order; the factory is generated automatically.

Check for outdated NuGet dependencies in the Rask repo and propose safe bumps. Use periodically or before a release. Reads central package management (Directory.Packages.props), reports outdated/vulnerable/deprecated packages, and updates versions behind the rask-ship gate.

Open a GitHub PR for the current Rask branch following project conventions. Use when ready to submit a change. Branches off main if needed, writes a structured PR body (summary, testing, benchmarks, changelog), and omits all AI attribution footers.

Review a Rask diff or PR for security, performance, memory usage, and .NET/C# best practices before merge. Use whenever reviewing changes in the Rask repo, or as the review step of rask-ship. Runs the built-in /code-review and /security-review, then adds Rask framework-aware checks.