Implement dependency injection in Angular v20+ using inject(), injection tokens, and provider configuration. Use for service architecture, providing dependencies at different levels, creating injectable tokens, and managing singleton vs scoped services. Triggers on service creation, configuring providers, using injection tokens, or understanding DI hierarchy.
# Protocol Writing — Reproducible Lab Protocols & SOPs
Capture-the-flag reverse engineering — find the flag efficiently
Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
Define version control strategies for design files, components, and libraries.
Establish a naming convention system for design elements, components, and tokens with clear rules and examples.
Structure a pattern library entry with problem context, solution pattern, usage examples, and related patterns.
Design a theming architecture that supports brand variants, dark mode, and high-contrast modes with token mapping.
Design loading, skeleton, and progressive content reveal patterns.
Create user flow diagrams showing paths, decisions, and branch logic.
Design effective dark mode interfaces with proper color adaptation, contrast, and elevation.
Define responsive layout grid systems with columns, gutters, margins, and breakpoint behavior.
Design adaptive layouts and interactions that work across all screen sizes and input methods.
Create a consistent spacing system based on a base unit with contextual application rules.
Establish clear visual hierarchy through size, weight, color, spacing, and positioning.
Define a set of actionable design principles that guide decision-making and resolve trade-offs.
Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).
Plan implementation, design an approach, or create an architecture plan for a Bitwarden iOS feature. Use when asked to "plan implementation", "design approach", "architecture plan", "how should I implement", "what files do I need", or to create a design doc before writing code.
Operational guide for enabling hierarchical context parallelism in Megatron-Bridge, including config knobs, code anchors, pitfalls, and verification. Use when the user asks about hierarchical_context_parallel_sizes, a2a+p2p, CP scaling beyond KV heads, or multi-level context parallelism.
MoE expert-parallel communication overlap in Megatron Bridge. Use when the user asks about overlap_moe_expert_parallel_comm, MoE dispatch overlap, flex dispatcher, DeepEP overlap, or expert wgrad scheduling.
