with one click
simm
simm contains 6 collected skills from SirTidez, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Route broad work in the SIMM Tauri/React/Rust repo to the right focused SIMM skill and validation path. Use for ambiguous or cross-cutting SIMM tasks involving frontend/backend contracts, runtime-aware mod library behavior, Nexus/FOMOD debugging, releases/updater workflows, desktop UI changes, or when Codex needs a repo-specific starting checklist before editing.
Design, implement, or review SIMM desktop UI changes using the app's native utility direction, existing React/Tauri boundaries, overlay architecture, CSS system, and real Tauri smoke-test concerns. Use for app shell, overlays, mod library UI, environment UI, logs/configuration/accounts/settings screens, responsive desktop layout, or UI ship-readiness work.
Maintain SIMM frontend/backend IPC contracts across Tauri commands, Rust DTOs, TypeScript types, ApiService wrappers, event helpers, and tests. Use when adding, renaming, deleting, or debugging invoke commands, Tauri events, shared request/response types, or frontend/backend contract drift.
Diagnose and fix SIMM NexusMods integrations, nxm deeplink handling, OAuth/API key behavior, manual download completion, FOMOD parsing, runtime-selection prompts, and callback replay loops. Use when reports mention Nexus, Vortex handoff, simm OAuth callbacks, ModuleConfig.xml, FOMOD archives, repeated prompts, invalid_grant, or manual download failures.
Prepare, debug, and review SIMM changelog, versioning, release notes, GitHub Actions release workflows, Tauri updater manifests, Windows NSIS installer artifacts, and CI failures. Use for release or beta release tasks, updater JSON, signed installer artifacts, workflow PowerShell JSON mutation, changelog backfill, contributor credit normalization, or version alignment.
Preserve SIMM runtime-aware mod library behavior for mods, plugins, UserLibs, shared storage, metadata synchronization, symlink installs, runtime prompts, compatibility badges, and mod update state. Use for changes under library management, environment installs, runtime detection, source metadata, or update summaries.