Explains hybrid search in Qdrant. Use when someone asks 'how do I setup hybrid search?', 'how to combine keyword and semantic search?', 'sparse plus dense vectors?', 'missing…
Use when Go concurrency with goroutines, channels, and sync patterns. Use when writing concurrent Go code.
Expert skill for designing and implementing high-quality compiler error messages
Expert skill for implementing language-level concurrency support including threads, channels, and synchronization
Use when modifying existing files, refactoring, improving code quality, or touching legacy code by applying the Boy Scout Rule to leave code better than you found it.
Build input systems with action mapping, buffering, dead zones, and rebinding that feel responsive and fair.
Test collaborative features against concurrency, reconnection, and ordering rather than only the single-user path.
Version and share seed datasets so they stay small, realistic, and reproducible across a team. Use when tests or local environments depend on fixture data that is drifting,…
Decide when repeated code should be unified and when a duplicate is the cheaper choice. Use when tempted to extract a shared helper or facing copy-pasted code.
Virtualize long lists so only visible rows mount, with correct handling of dynamic heights and scroll anchoring.
Keep TODO comments actionable by requiring an owner, a ticket, and an expiry, or deleting them. Use when writing, reviewing, or sweeping in-code TODO, FIXME, and HACK markers.
End a project deliberately, with handover, documentation, and a decision about what happens to what was built. Use when a project reaches its goal or is being stopped.
Convene agents to model pricing options, argue them from customer, competitor, and margin angles, and hand a human a decision pack.
Share one physical GPU across several small workloads using MIG, MPS, or time slicing, and pick the mode whose isolation matches the risk.
Move user-facing text out of code into catalogs with stable keys and context, so translation becomes possible without touching logic.
Build immutable, provenance-tracked artifacts promoted unchanged through environments. Use when designing a build pipeline or fixing "works in staging, breaks in prod" from…
Run continuous compliance with agents that map controls to evidence, collect it on a schedule, and flag drift before an audit finds it.
Write first CUDA kernels that map work onto the grid, coalesce global memory, and keep enough warps resident to hide latency.
Write alt text that conveys an image's purpose, marks decorative images empty, and handles functional and complex images. Use when adding images to content or auditing alt text.
Run release agents that draft the changelog, scan risk, verify the candidate, and gate publish behind a go/no-go check.
Read coverage as a map of untested risk that steers the next test, rather than enforcing a percentage target.
Write role cards that pin each agent to one charter with declared inputs, outputs, refusal rules, and non-overlapping scope.
Load web fonts without layout shift by subsetting the file, setting font-display, preloading first-paint weights, and matching fallback metrics.
Write a north-star architecture document that sequences migrations and guides decisions without pretending to be a roadmap.
Identify what could derail a project, decide responses in advance, and track them rather than reacting when they happen. Use at project start and at every major checkpoint.
Use cryptography by calling vetted libraries with authenticated defaults and storing keys in a KMS, never by designing a scheme.
Let teams provision what they need within guardrails, without waiting for an infrastructure team to act. Use when provisioning requests queue and infrastructure work is reactive.
Use Tailwind-style utilities with discipline, extracting components at the right threshold and keeping class lists readable.
Produce a recurring newsletter with a sustainable format, a clear reason to open, and rendering that survives email clients. Use when publishing regularly to a subscribed audience.
Design React component props and boundaries so components compose cleanly and stay reusable. Use when creating a component, reviewing a bloated props list, or deciding controlled…
Reject excess work deliberately under overload so the system serves some requests well instead of failing all of them.
Use formatting rules to surface exceptions and patterns automatically, without turning the sheet into a colour chart. Use when readers need to spot outliers or status at a glance.
Break a project into milestones that each prove something, so progress is verifiable rather than asserted.
Return structured problem+json errors with stable codes, retryability signals, and correlation ids. Use when standardizing API error shapes or making failures debuggable across…
Operate as a product manager who picks the right problem, writes the spec, makes the tradeoff calls, and owns the launch outcome.
Speed up a CPU-bound hot path by fixing its algorithm and memory access first, then applying micro-optimization only where the profiler still points.
Reshape rows into columns and back, and know when the reshape belongs in SQL rather than in the reporting layer.
Design the empty, loading, error, and edge states that most designs skip but users constantly hit. Use when designing any screen that can be empty, loading, or fail, which is…
Patterns and strategies for cache invalidation - one of the two hardest problems in computer science.
Staff a pipeline with agents that research accounts, qualify leads against explicit criteria, draft outreach for human sending, and keep the CRM honest.
Move a file from the user's device to durable storage and a processed state, with validation, progress, and recovery at every stage.
Keep the public API small by defaulting to private visibility and retiring symbols through deprecation before deletion.
Lower the cost of a first contribution with a working setup, a clear scope, and a fast review so people come back.
Score incoming vulnerability reports the same way every time, tie each score to a fix deadline, and run disclosure on a predictable clock.
Decide what deserves a notification, on which channel, and at what urgency, before building any of it.
Run a lab of researcher agents that search in parallel, verify sources independently, and synthesize a cited answer.
Reason correctly about probability, base rates, conditional probability, and expected value, avoiding the common intuition traps.
Remove features with usage evidence, migration paths, and staged communication that preserves trust. Use when retiring product surface or making the case that something should die.
Halve the search space repeatedly across code, data, time, and configuration until a single change isolates the failure.
Precompute expensive read queries into materialized views and pick a refresh strategy that fits a stated staleness budget.
Write bash that fails loudly, quotes correctly, cleans up after itself, and passes shellcheck. Use when writing shell scripts that automation or other people will depend on.
Write Makefiles with honest dependencies, phony discipline, and self-documenting help, and know when make is the wrong tool.
Manage long agent sessions with checkpoints, context resets, and clear task boundaries so quality does not decay. Use when working with an agent over an extended piece of work.
Split data before looking at it, respect time and groups, and quarantine the test set so scores mean something.
Build save systems with versioned formats, corruption resistance, and autosave that never loses real progress.
Operate as a solutions architect who turns a customer's constraints into a defensible reference design and a path to production.
Learn something substantial without a course, by defining the goal, finding the right resources, and building feedback into the process.
Ask a model to reason before answering when the task needs intermediate steps, and know when it costs more than it gives.
Use .NET's built-in DI with correct lifetimes, the options pattern, and constructor injection free of service-locator drift.
Write ISRs that stay minimal, share data through volatile-correct handoffs, and defer real work safely.