Results for “methodology”

Domain-Driven Design methodology using bounded contexts, ubiquitous language, and strategic/tactical patterns

Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

QA a completed analysis for methodology, accuracy, and bias before it is shared, shipped, or acted on.

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

Use this skill when the user asks about FMCSA Compliance Safety Accountability (CSA) program scoring — the seven BASIC categories, BASIC Severity Indicator (BSI), peer percentiles, intervention thresholds, how violations age out, SMS Methodology, ISS (Inspection Selection System), what "alert" status means, Safety Measurement System mechanics, or DataQ disputes. Cite SMS Methodology v3.20.

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.

Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.

Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.

Capture friction as methodology notes. Three modes — explicit description, contextual (review recent corrections), session mining (scan transcripts for patterns). Triggers on "/remember", "/remember [description]".

Reduces cognitive complexity of a specified method by extracting logic into focused helper methods, improving readability and maintainability.

A* pathfinding skill for heuristics and optimization.

Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure.

Strategic patterns for solving intractable problems through cascading approximation, self-improvement, and heterogeneous evaluation from DeepMind's AlphaGo system

Publication Specialist - Writing, Review, Pre-registration & Quality Assurance Light VS applied: Avoids template-based writing + audience-specific message design Absorbed G3 (Peer Review Strategist), G4 (Pre-registration Composer), F1-F3 (Quality functions) capabilities Use when: writing abstracts, creating summaries, peer review response, pre-registration, reporting checklists, reproducibility Triggers: abstract, plain language, press release, summary, communication, peer review, revision, pre-registration, OSF, PRISMA, CONSORT, reproducibility

Conduct failure mode and effects analyses. TRIGGERS - Use when user needs help with fmea-guide related tasks.

Challenge system assumptions against accumulated evidence. Triages observations and tensions, detects patterns, generates proposals. The scientific method applied to knowledge systems. Triggers on "/rethink", "review observations", "challenge assumptions", "what have I learned".

Gemini: A Family of Highly Capable Multimodal Models

Correspondence Reply Modal

Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure.

Refactor given method `${input:methodName}` to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting helper methods.

Use for identifying and resolving performance bottlenecks.

Conduct failure mode and effects analyses. TRIGGERS - Use when user needs help with fmea-guide related tasks.

Guides users through the specification-driven development workflow, from requirements gathering through specification, test derivation, implementation, and validation.

Refactors Java methods by extracting code blocks into separate, well-named methods to improve readability and maintainability.