RajwanYair

Explore RegiLattice codebase architecture, data flow, dependencies, and design decisions. Use when asked to explain how the system works, trace a feature end-to-end, understand module structure, or find where specific logic lives. Triggers on: 'how does', 'where is', 'explain', 'architecture', 'data flow', 'TweakEngine', 'RegistrySession'.

Bump the version, update the changelog, tag, and publish a GitHub release for RegiLattice. Use when preparing a new release, updating version numbers, creating a CHANGELOG entry, or pushing a version tag to trigger the CI release workflow. Triggers on: 'bump version', 'release', 'publish', 'version', 'tag', 'changelog', 'MINOR bump', 'PATCH bump'.

Write, run, or improve xUnit tests for RegiLattice. Use when adding tests for a new feature, increasing coverage, debugging failing tests, or following testing conventions. Triggers on: 'write tests', 'add tests', 'test coverage', 'xUnit', 'failing test', 'test pattern', 'TweakDef test', 'TweakEngine test'.

Profile and diagnose performance issues in RegiLattice: slow searches, UI lag, TweakEngine bottlenecks, WinForms rendering delays, BenchmarkDotNet micro-benchmarks. Use when asked to profile, measure, or improve performance. Triggers on: 'slow', 'performance', 'profile', 'benchmark', 'lag', 'freeze', 'latency', 'too slow', 'optimize speed', 'BenchmarkDotNet'.

Auto-draft CHANGELOG entries and release notes from git commits. Use when preparing a new release, summarising what changed since last tag, drafting the CHANGELOG section, or generating GitHub Release body text. Triggers on: 'draft changelog', 'release notes', 'what changed', 'CHANGELOG entry', 'generate release notes', 'summarise commits'.

Add registry tweaks to RegiLattice. Use when creating new TweakDef entries, adding to a category module, generating unique IDs, choosing RegOp factories, or registering a new category. Triggers on: 'add tweak', 'new tweak', 'registry tweak', 'create tweak', 'TweakDef'.

Check, update, or add version detection for external tools used by RegiLattice (PowerShell, Python, winget, scoop, chocolatey, git, node). Use when verifying tool availability, adding a new tool to ToolVersionChecker, or debugging version detection failures. Triggers on: 'tool version', 'ToolVersionChecker', 'winget version', 'check tools', 'update tools'.

Diagnose and fix build errors, test failures, compile warnings, or runtime exceptions in RegiLattice. Use when there are CS errors, test failures, duplicate tweak IDs, nullable warnings, or unexpected runtime behaviour. Triggers on: 'error', 'fails', 'broken', 'exception', 'CS8', 'MSB', 'duplicate', 'not found', 'fix'.

Add a new route card to the CrossTide app. Use when: adding a new view or page, creating a new CardModule, registering a new route, or wiring a card into the router, registry and test guards. Produces a complete card with registry entry, router route, view container, unit tests and E2E coverage.

Add a new technical indicator to the CrossTide domain layer. Use when: implementing a new calculator (RSI/MACD-style), adding a signal method to the consensus engine, or extending screener/backtest inputs. Covers purity constraints, the calculator + series export pair, consensus registration, property tests and generated docs.

Add a new Hono route to the CrossTide Cloudflare Worker. Use when: adding a new API endpoint, integrating a new market data provider, exposing a new server-side calculation, or adding a new WebSocket fan-out. Produces a complete, production-ready integration with KV cache, Valibot validation, rate limit, OpenAPI entry, and tests.

Debug broken API calls and fetch failures in CrossTide. Use when: a card shows an error state, data is not loading or stale, worker route returns 502, provider chain failing, or fetch never resolves. Covers worker tail logs, KV state inspection, fixture comparison, and common failure patterns.

Deploy CrossTide to Cloudflare Workers and Pages, provision KV/D1/R2 resources, verify production health, or troubleshoot deployment failures. Use when deploying, provisioning, rolling back, or checking production.

Create, apply, verify, or troubleshoot CrossTide Cloudflare D1 migrations. Use when changing database schema, applying migrations locally or remotely, checking migration status, or planning rollback migrations.

Create a versioned release of CrossTide. Use when: bumping the version number, publishing a new release, updating CHANGELOG, tagging a git commit, or preparing a GitHub release. Covers the full release checklist from version bump to git tag.

Add or update tests in the CrossTide test suite. Use when: adding a new domain function, new worker route, new card module, changing a type or constant, fixing broken test assertions, or when coverage drops below the threshold gate. Covers Vitest 4 + happy-dom, domain purity tests, worker mock tests, and card unit tests.

Audit and optimize the FamilyDashBoard workspace for production readiness, clean generated files, enforce $TEMP for intermediates, and validate VS Code integration quality. Use when: before a release, after adding new tooling, or when generated files accumulate.

Create a versioned release of the FamilyDashBoard. Use when: bumping the version number, publishing a new release, updating CHANGELOG, updating SVG documentation assets, tagging a git commit, or preparing a GitHub release. Covers the full release checklist from version bump to git tag.

Add or update tests in the FamilyDashBoard test suite. Use when: adding a new card or API (need new test coverage), changing a CSS/JS constant, adding a new HTML element, fixing broken test assertions, or running and triaging test failures. Covers Vitest 4 + happy-dom, per-file test suites in tests/unit/.

Add a new API data source to the FamilyDashBoard. Use when: integrating a new external data provider, adding a new dashboard card/widget with live data, wiring a new fetch with caching, proxy fallback, sync indicator, diagnostic logging, and refresh interval. Produces a complete, production-ready integration.

Debug broken API calls and fetch failures in FamilyDashBoard. Use when: a dashboard pane shows an error indicator, data is not loading or is stale, proxy fallback is failing, a stock or weather or news feed is broken, or diagLog shows repeated failures. Covers diagnostic overlay, proxy chain testing, cache state inspection, and common failure patterns.