dotfiles

Apply Entity Framework Core patterns for tracking, migrations, retries, bulk operations, DbContext lifetime, query behavior, and database-backed tests. Use when implementing, reviewing, debugging, or optimizing EF Core data access and migration workflows.

Structure or modernize .NET solutions using .slnx, global.json, Directory.Build.props, Central Package Management, SourceLink, NuGet configuration, release metadata, and reproducible build conventions. Use for new solution setup, repository-wide build configuration, SDK pinning, or project-layout migrations.

Build or query a persistent knowledge graph for broad architecture, cross-file relationships, or mixed code-and-document corpora. Use when the user explicitly asks for Graphify or a knowledge graph, when graphify-out already exists and can answer an architecture question, or when persistent cross-session mapping materially helps. Do not trigger for routine code questions, focused audits, or small repository tasks.

Build or standardize Tailwind CSS v4 design systems with CSS-first tokens, variants, reusable components, responsive layouts, forms, theming, and accessibility. Use when creating a component library, defining design tokens, migrating design-system primitives, or removing inconsistent utility patterns.

Teach the user a new skill or concept, within this workspace.

Build .NET integration tests against disposable Docker dependencies with Testcontainers and xUnit. Use for databases, caches, brokers, migration tests, container lifecycle, isolation, wait strategies, CI execution, or replacing infrastructure mocks with real services.

Test Blazor Server or WebAssembly applications with Playwright, including navigation, authentication, stable selectors, forms, SignalR updates, error UI, screenshots, HTTPS, parallelism, and CI. Use when creating or repairing Blazor browser tests or end-to-end test infrastructure.

Implement or debug Three.js animation using AnimationClip, AnimationMixer, AnimationAction, GLTF clips, skeletal animation, morph targets, blending, procedural motion, and update-loop performance. Use when objects, characters, cameras, bones, or morph targets must animate or blend correctly.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Use for stronger secret leak prevention with Agent Guard and gitleaks: scan staged changes, working trees, or paths; install repo-local pre-commit hooks; mask command output; check PII; or compare/upgrade from lightweight secret scanning before commits, PRs, pushes, or agent runs.

Use when the user asks to fix a failing GitHub Actions CI run, repair a PR branch, inspect failed CI logs, or rerun a focused failure-fix loop from CI evidence.

Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when reviewing code changes or pull requests.

Design stable, compatible public APIs using extend-only design principles. Manage API compatibility, wire compatibility, and versioning for NuGet packages and distributed systems. Use when designing or reviewing public C# APIs, NuGet packages, or distributed system wire formats.

Write modern, high-performance C# code using records, pattern matching, value objects, async/await, Span and Memory types, and best-practice API design patterns. Emphasizes functional-style programming with C# 12+ features. Use when writing C# code to ensure modern best practices.

Choosing the right concurrency abstraction in .NET - from async/await for I/O to Channels for producer/consumer to Akka.NET for stateful entity management. Avoid locks and manual synchronization unless absolutely necessary. Use when implementing concurrent or asynchronous operations in .NET.

Design .NET types for performance. Seal classes, use readonly structs, prefer static pure functions, avoid premature enumeration, and choose the right collection types. Use when designing or reviewing .NET types, classes, structs, and collections for performance.

Database access patterns for performance. Separate read/write models, avoid N+1 queries, use AsNoTracking, apply row limits, and never do application-side joins. Works with EF Core and Dapper. Use when optimizing database queries or data access patterns.

Use when designing, reviewing, or changing remote calls, queues, webhooks, caches, brokers, streams, retries, timeouts, idempotency, backpressure, health checks, circuit breakers, or overload behavior.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Manage NuGet packages using Central Package Management (CPM) and dotnet CLI commands. Never edit XML directly - use dotnet add/remove/list commands. Use shared version variables for related packages. Use when adding, removing, or updating NuGet packages in .NET projects.

Choose the right serialization format for .NET applications. Prefer schema-based formats (Protobuf, MessagePack) over reflection-based (Newtonsoft.Json). Use System.Text.Json with AOT source generators for JSON scenarios. Use when implementing serialization or choosing a wire format in .NET.

Use Slopwatch to detect LLM reward hacking in .NET code changes. Run after every code modification to catch disabled tests, suppressed warnings, empty catch blocks, and other shortcuts that mask real problems.

Use when checking .env, .env.local, .env.production, or other environment files against .env.example without printing environment variable values.

Use when diagnosing flaky tests, nondeterministic failures, intermittent CI failures, race-prone test suites, or when the user asks to run a test command repeatedly.

Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.

Microsoft.Extensions.Options patterns including IValidateOptions, strongly-typed settings, validation on startup, and the Options pattern for clean configuration management. Use when configuring strongly-typed settings or implementing configuration validation in .NET.

Organize DI registrations using IServiceCollection extension methods. Group related services into composable Add* methods for clean Program.cs and reusable configuration in tests. Use when organizing dependency injection registrations in .NET applications.

Use for launch, migration, traffic shift, release readiness, go/no-go, production impact, customer-impacting changes, recovery, rollback, observability, SLO, ownership, or operational readiness reviews.

Use when cutting releases, tags, version bumps, build artifacts, packages, deployment artifacts, release candidates, artifact promotion, rollback targets, flaky builds, cache trust, or build reproducibility.

Use before commits, PRs, pushes, or when checking staged diffs/files for leaked API keys, tokens, private keys, JWTs, credentials, or high-entropy secrets with redacted output.

Use when delegating to subagents, receiving subagent results, coordinating multi-agent work, or asking for worker output that must be auditable, resumable, or easy to validate.

Use after tests with coverage, during PR review, or when comparing changed git diff lines against coverage.xml, lcov.info, or coverage.json to find untested changed lines.

Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code. Use OpenCover format with ReportGenerator for Risk Hotspots showing cyclomatic complexity and untested code paths. Use when analyzing code complexity and test coverage.

Create a PRD through user interview, codebase exploration, module design, success criteria, risk analysis, and testing strategy. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.