warp

Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.

Rules for modifying ASP.NET Core configuration files (appsettings*.json) in the Warp project. Use when: adding, removing, or changing any configuration key in appsettings files; creating new Options classes that bind to configuration; the user mentions 'appsettings', 'configuration', 'options', 'config value', 'environment config', 'feature flag', or 'FeatureManagement'; adding a new service that reads IConfiguration or IOptions<T>. Also use when you need to decide which appsettings file a value belongs in. Prevents unnecessary duplication of config entries across environment files.

Workflow for adding, modifying, or removing log events, domain errors, and log messages in the Warp project. Use when: adding new log events to log-events.json; creating or updating domain errors; adding structured logging to a service; the user mentions 'log event', 'log message', 'domain error', 'LogEvents', 'DomainErrors', 'LogMessages', 'code generator', 'CodeGen', or 'log-events.json'. Also use when diagnosing FormatException errors in logging or build failures related to generated files.

Systematic methodology for running, diagnosing, and fixing Playwright E2E test failures in this project. Use this when running E2E tests, investigating flaky or failing E2E tests, verifying infrastructure readiness, or debugging issues where UI elements behave unexpectedly (buttons stay disabled, pages redirect to error, config values are wrong). Also use this when the user mentions "e2e", "playwright", "end-to-end", or asks to verify that the app works.