anderssv

Reviews access control, authentication, and authorization patterns. Use when reviewing security boundaries, permission models, role-based access, or authentication flows.

Queries Azure Application Insights for logs, errors, and telemetry data. Use when investigating production issues, querying traces, or analyzing application telemetry.

Designs software features collaboratively through visual scenarios and iterative refinement. Use when designing features, tools, UIs, workflows, or any system before implementation.

Reviews Kotlin code for idiomatic style and best practices. Use when reviewing Kotlin code quality, style, or converting Java-style Kotlin to idiomatic Kotlin.

Manual dependency injection using SystemContext (production) and TestContext (test doubles) patterns for Kotlin. Use when structuring service dependencies, wiring application components, or creating test contexts without DI frameworks.

Automate browser interactions, test web pages and work with Playwright tests. Use when writing end-to-end tests, browser automation, or web scraping.

Creates structured presentation briefs and outlines. Use when preparing talks, presentations, or slide decks about technical topics.

Designs systems using Event Modeling.

Parse, don't validate - using sealed classes for type-safe validation and state representation. Model valid/invalid states explicitly, validate at boundaries, operate on valid types internally. Use when implementing validation with sealed classes, modeling valid/invalid states, or applying parse-don't-validate patterns in Kotlin. The pattern is transferrable to other languages, though the mechanism will differ.

Enforces idiomatic Kotlin over Java-style patterns when writing or reviewing Kotlin code. Use when generating, reviewing, or refactoring Kotlin. Covers scope functions, collections, data/sealed/value classes, extensions, coroutines, and DSL builders.

Manual dependency injection using SystemContext (production) and TestContext (test doubles) patterns for Kotlin. Use when structuring service dependencies, wiring application components, or creating test contexts without DI frameworks.

Kotlin Test-Driven Development with fakes, object mothers, and Testing Through The Domain. Uses TestContext for dependency injection, extension functions for test data, and fakes instead of mocks. Use when writing Kotlin tests or setting up test infrastructure.

Enforces idiomatic Kotlin over Java-style patterns when writing or reviewing Kotlin code. Use when generating, reviewing, or refactoring Kotlin. Covers scope functions, collections, data/sealed/value classes, extensions, coroutines, and DSL builders.

Parse, don't validate - using sealed classes for type-safe validation and state representation. Model valid/invalid states explicitly, validate at boundaries, operate on valid types internally. Use when implementing validation with sealed classes, modeling valid/invalid states, or applying parse-don't-validate patterns in Kotlin. The pattern is transferrable to other languages, though the mechanism will differ.

Manual dependency injection using SystemContext (production) and TestContext (test doubles) patterns for Kotlin. Use when structuring service dependencies, wiring application components, or creating test contexts without DI frameworks.

Kotlin Test-Driven Development with fakes, object mothers, and Testing Through The Domain. Uses TestContext for dependency injection, extension functions for test data, and fakes instead of mocks. Use when writing Kotlin tests or setting up test infrastructure.

Anchors development in a Vault of structured research across all project pillars (users, market, competitors, tech, legal, ops, risks) before any PRD or code. Every learning updates the Vault first, then the plan, then code. Use when planning and building a new product, feature, or complex system.

Vault-structured research methodology: identifies all relevant pillars, researches each in parallel, writes each pillar to disk, then synthesizes into a final summary document. Use when researching a topic, technology, market, or system before making decisions.