laurigates-plugins

Basedpyright static type checker configuration, installation, and usage patterns. Use when implementing type checking, configuring LSP, comparing type checkers, or setting up strict type validation in Python projects. Triggered by: basedpyright, pyright, type checking, LSP, mypy alternative, static analysis.

Advanced pytest patterns including fixtures, markers, parametrization, and parallel execution. Use when implementing test infrastructure, organizing test suites, writing fixtures, or running tests with coverage. Covers pytest-cov, pytest-asyncio, pytest-xdist, pytest-mock.

Python code quality with ruff (linting & formatting) and mypy (type checking). Covers pyproject.toml configuration, pre-commit hooks, and type hints. Use when user mentions ruff, mypy, linting, formatting, type checking, code style, or Python code quality.

Core Python development concepts, idioms, best practices, and language features. Covers Python 3.10+ features, type hints, async/await, and Pythonic patterns. For running scripts, see uv-run. For project setup, see uv-project-management. Use when user mentions Python, type hints, async Python, decorators, context managers, or writing Pythonic code.

Build and publish Python packages with uv and modern build tools. Covers uv build, uv publish, pyproject.toml, versioning, entry points, and PyPI publishing. Use when user mentions building packages, publishing to PyPI, uv build, uv publish, package distribution, or Python wheel/sdist creation.

Python testing with pytest, coverage, fixtures, parametrization, and mocking. Covers test organization, conftest.py, markers, async testing, and TDD workflows. Use when user mentions pytest, unit tests, test coverage, fixtures, mocking, or writing Python tests.

Install and manage Python interpreter versions with uv. Covers uv python install, uv python list, uv python pin, version pinning with .python-version file. Use when user mentions installing Python versions, switching Python versions, .python-version, uv python, or managing CPython/PyPy interpreters.

Run Python scripts with uv including inline dependencies (PEP 723), temporary dependencies (--with), and ephemeral tool execution. Use when running scripts, needing one-off dependencies, or creating executable Python scripts. No venv activation required.

Install and manage global Python CLI tools with uv (pipx alternative). Covers uv tool install, uvx for ephemeral execution, tool isolation, and updates. Use when user mentions uv tool, uvx, installing CLI tools globally, pipx replacement, or running Python tools without installation.

Manage monorepo and multi-package Python projects with uv workspaces. Covers workspace configuration, member dependencies, shared lockfiles, and building. Use when user mentions uv workspaces, Python monorepo, multi-package projects, workspace members, or shared dependencies across packages.

Vulture and deadcode tools for detecting unused Python code (functions, classes, variables, imports). Use when cleaning up codebases, removing unused code, or enforcing code hygiene in CI. Triggered by: vulture, deadcode, dead code detection, unused code, code cleanup, remove unused.

Commit message conventions, staging practices, and commit best practices. Covers conventional commits, explicit staging workflow, logical change grouping, humble fact-based communication style, and automatic issue detection. Use when user mentions committing changes, writing commit messages, git add, git commit, staging files, or conventional commit format.

Pre-commit security validation and secret detection. Runs detect-secrets scan and audit workflow, validates secrets baseline, and integrates with pre-commit hooks to prevent credential leaks. Use when user mentions scanning for secrets, detect-secrets, secret detection, credential scanning, pre-commit security, or .secrets.baseline.

Configures release-please for monorepos and single-package repos. Handles manifest files, component tagging, changelog sections, and extra-files setup. Use when setting up automated releases, fixing release workflow issues, or configuring version bump automation.

Detects and prevents manual edits to release-please managed files (CHANGELOG.md, version fields in package.json, pyproject.toml, Cargo.toml). Provides conventional commit templates. Use when editing changelogs, version bumps, release files, or when user mentions "release", "changelog", "version bump", or "conventional commits".

Convert and manipulate images with ImageMagick. Covers format conversion, resizing, batch processing, quality adjustment, and image transformations. Use when user mentions image conversion, resizing images, ImageMagick, magick command, batch image processing, or thumbnail generation.

Initialize VectorCode with automatic configuration generation. Installs git hooks, generates vectorcode.include and vectorcode.exclude patterns based on project type. Use when user mentions "initialize VectorCode", "set up VectorCode", vectorcode.include, vectorcode.exclude, or VectorCode configuration.

Coordinate multi-agent workflows: sequential, parallel, and iterative patterns. Defines agent handoffs, dependencies, communication protocols, and integration. Use when designing multi-agent workflows, coordinating agent handoffs, planning agent dependencies, or building complex agent pipelines.

File-based context sharing for multi-agent workflows. Provides directory organization, agent output templates, progress tracking, and inter-agent context. Use when setting up multi-agent workflows, reading/writing agent context files, or maintaining workflow transparency with file-based coordination.

Standardized inline markers for inter-agent communication. Use when creating handoff annotations for other agents, scanning for pending work from upstream agents, or when the user mentions handoff markers, agent coordination, or cross-agent communication.

Write safe context expressions in Claude Code slash command files. Covers backtick expressions, find vs ls patterns, and commands that always exit 0. Use when creating slash commands, writing context sections with backtick expressions, or debugging command execution failures.

Default behavior pattern that automatically delegates implementation tasks to specialized sub-agents while keeping the main conversation focused on architecture, design, and strategy. Use when receiving ANY implementation request - the main Claude acts as architect/coordinator while sub-agents handle code, tests, debugging, and documentation.

Orchestrate complex multi-agent workflows for development, infrastructure, and research. Provides workflow templates, agent sequences, and integration patterns. Use when planning complex projects, coordinating multiple agents, designing API development workflows, or infrastructure setup workflows.

Update Bun lockfiles (bun.lockb) with proper dependency management. Covers bun update, bun install, lockfile regeneration, and security audits. Use when user mentions bun lockfile, bun update, bun.lockb, updating Bun dependencies, or resolving Bun lockfile conflicts.

Modern Node.js development with Bun, Vite, Vue 3, Pinia, and TypeScript. Covers JavaScript/TypeScript projects, high-performance tooling, and modern frameworks. Use when user mentions Node.js, Bun, Vite, Vue, Pinia, npm, pnpm, JavaScript runtime, or building frontend/backend JS applications.

ArgoCD CLI authentication with SSO. Provides argocd login command, gRPC-Web configuration, and post-login operations. Use when user mentions ArgoCD login, argocd authentication, SSO auth, or accessing ArgoCD applications and clusters.

Debug and troubleshoot Helm deployment failures, template errors, and configuration issues. Covers helm template, helm lint, dry-run, debugging YAML parse errors, value type errors, and resource conflicts. Use when user mentions Helm errors, debugging Helm, template rendering issues, or troubleshooting Helm deployments.

Manage Helm releases: install, upgrade, uninstall, list, and inspect releases. Covers helm install, helm upgrade, helm list, helm status, release history. Use when user mentions deploying Helm charts, upgrading releases, helm install, helm upgrade, or managing Kubernetes deployments with Helm.

Recover from failed Helm deployments, rollback releases, fix stuck states (pending-install, pending-upgrade). Covers helm rollback, release history, atomic deployments. Use when user mentions rollback, failed Helm upgrade, stuck release, or recovering from Helm deployment failures.

Debug Kubernetes pods, nodes, and workloads using kubectl debug. Covers ephemeral containers, pod copying, node debugging, debug profiles, and interactive troubleshooting sessions. Use when user mentions kubectl debug, debugging pods, ephemeral containers, node debugging, or interactive troubleshooting in Kubernetes clusters.

Kubernetes operations including deployment, management, troubleshooting, kubectl mastery, and cluster stability. Covers K8s workloads, networking, storage, and debugging pods. Use when user mentions Kubernetes, K8s, kubectl, pods, deployments, services, ingress, ConfigMaps, Secrets, or cluster operations.

Configure Claude Code security settings including permission wildcards, shell operator protections, and project-level access controls. Use when setting up project permissions, configuring allowed tools, or securing Claude Code workflows.

FVH (Forum Virium Helsinki) pre-commit hook standards and configuration. Use when configuring pre-commit hooks in FVH repositories, checking hook compliance, or when the user mentions FVH pre-commit, conventional commits, or hook configuration.

FVH (Forum Virium Helsinki) release-please standards and configuration. Use when configuring release-please workflows, checking release automation compliance, or when the user mentions FVH release-please, automated releases, or version management.

GO Feature Flag (GOFF) self-hosted feature flag solution with OpenFeature integration. Covers flag configuration, relay proxy, targeting rules, rollouts. Use when user mentions GO Feature Flag, GOFF, gofeatureflag, self-hosted feature flags, or flags.goff.yaml configuration.

OpenFeature vendor-agnostic feature flag SDK with standardized API across languages. Covers SDK installation, flag evaluation, providers, and hooks. Use when implementing feature flags, A/B testing, canary releases, or when user mentions OpenFeature, feature toggles, or progressive rollouts.

Pre-commit hook standards and configuration. Use when configuring pre-commit hooks in repositories, checking hook compliance, or when the user mentions pre-commit, conventional commits, or hook configuration.

README.md templates and standards. Use when generating or improving README files, checking README compliance, or when the user mentions README best practices or documentation.

Release-please standards and configuration. Use when configuring release-please workflows, checking release automation compliance, or when the user mentions release-please, automated releases, or version management.

Property-based testing with Hypothesis for discovering edge cases and validating invariants. Use when testing code with many possible inputs, verifying mathematical properties, testing serialization round-trips, or finding edge cases that example-based tests miss.

Validate test effectiveness with mutation testing using Stryker (TypeScript/JavaScript) and mutmut (Python). Find weak tests that pass despite code mutations. Use when user mentions mutation testing, Stryker, mutmut, test effectiveness, finding weak tests, or improving test quality through mutation analysis.

Property-based testing with fast-check (TypeScript/JavaScript) and Hypothesis (Python). Generate test cases automatically, find edge cases, and test mathematical properties. Use when user mentions property-based testing, fast-check, Hypothesis, generating test data, QuickCheck-style testing, or finding edge cases automatically.

Automatic selection of appropriate test tiers based on change scope. Guides unit tests for small changes, full suite for larger changes. Use when running tests, discussing testing strategy, or after code modifications.

Generate project-specific rules and commands from PRDs for Blueprint Development methodology. Use when generating behavioral rules for architecture patterns, testing strategies, implementation guides, or quality standards from requirements documents.

Assess quality of PRPs and work-orders using systematic confidence scoring. Use when evaluating readiness for execution or subagent delegation.

Go-specific container optimization patterns including static binary compilation, scratch/distroless base images, CGO handling, and systematic optimization journey from 846MB to 2.5MB (99.7% reduction). Covers ldflags, trimpath, and build flag optimizations specific to Go applications. Use when working with Go containers, Dockerfiles for Go apps, or optimizing Go image sizes.

Node.js-specific container optimization patterns including Alpine variants, multi-stage builds, node_modules caching, production dependency separation, and optimization from ~900MB to ~50-100MB. Covers npm/yarn/pnpm patterns, BuildKit cache mounts, and non-root user configuration. Use when working with Node.js containers, Dockerfiles for Node apps, or optimizing Node image sizes.

Python-specific container optimization patterns including slim base images (NOT Alpine), virtual environment handling, multi-stage builds with pip/poetry/uv, and optimization from ~1GB to ~80-120MB. Covers musl libc issues, wheel building, and Python-specific dependency management patterns. Use when working with Python containers, Dockerfiles for Python apps, or optimizing Python image sizes.

OrbStack-optimized Skaffold workflows for local Kubernetes development without port-forward. Use when configuring Skaffold with OrbStack, accessing services via LoadBalancer or Ingress, or when the user mentions OrbStack, k8s.orb.local, service access, or eliminating port-forward.

Analyze codebases for anti-patterns, code smells, and quality issues using ast-grep structural pattern matching. Use when reviewing code quality, identifying technical debt, or performing comprehensive code analysis across JavaScript, TypeScript, Python, Vue, React, or other supported languages.

Infrastructure as Code with Terraform including HCL configuration, state management, modular design, and plan-apply workflows. Covers cloud and on-prem resource provisioning, remote backends, and Terraform modules. Use when user mentions Terraform, HCL, terraform plan, terraform apply, tfstate, infrastructure as code, or IaC provisioning.

List Terraform Cloud runs for a workspace with filtering by status, operation type, and date. Use when reviewing run history, finding failed runs, or auditing infrastructure changes. Requires TFE_TOKEN environment variable.

Download and analyze structured Terraform plan JSON output from Terraform Cloud. Use when analyzing resource changes, diffing infrastructure, or programmatically inspecting plan details. Requires TFE_TOKEN environment variable.

Retrieve plan and apply logs from Terraform Cloud runs. Use when examining TFC run output, debugging failed plans/applies, or reviewing infrastructure changes. Requires TFE_TOKEN environment variable.

Quick status check for Terraform Cloud runs showing status, resource changes, timestamps, and available actions. Use when monitoring run progress or checking if a run can be applied/canceled. Requires TFE_TOKEN environment variable.

Convenience wrapper for listing Terraform Cloud runs in Forum Virium Helsinki workspaces (github, sentry, gcp, onelogin, twingate). Requires TFE_TOKEN. Use when user mentions TFC runs, Terraform Cloud workspace, listing TFC runs, infrastructure run history, or checking Terraform Cloud status.

Code coverage for Rust using LLVM instrumentation with support for multiple output formats and CI integration. Use when measuring test coverage, generating coverage reports, enforcing coverage thresholds, or integrating with codecov/coveralls. Trigger terms: coverage, llvm-cov, code coverage, test coverage, coverage report, codecov, coveralls, branch coverage.

Detect unused dependencies in Rust projects for cleaner Cargo.toml files and faster builds. Use when auditing dependencies, optimizing build times, cleaning up Cargo.toml, or detecting bloat. Trigger terms: unused dependencies, cargo-machete, dependency audit, dependency cleanup, bloat detection, cargo-udeps.

Next-generation test runner for Rust with parallel execution, advanced filtering, and CI integration. Use when running tests, configuring test execution, setting up CI pipelines, or optimizing test performance. Trigger terms: nextest, test runner, parallel tests, test filtering, test performance, flaky tests, CI testing.

Modern Rust development with cargo, rustc, clippy, rustfmt, async programming, and memory-safe systems programming. Covers ownership patterns, fearless concurrency, and the modern Rust ecosystem including Tokio, Serde, and popular crates. Use when user mentions Rust, cargo, rustc, clippy, rustfmt, ownership, borrowing, lifetimes, async Rust, or Rust crates.

Store episodes in Graphiti Memory: agent executions, error resolutions, workflow completions, technical decisions. Provides JSON schemas and storage patterns. Use when user mentions storing in Graphiti, add_memory, episode storage, building knowledge base, or documenting agent work.

Learn from historical data and build institutional knowledge with Graphiti Memory. Integrates episode storage and retrieval into learning patterns across sessions. Use when user mentions learning workflows, building knowledge over time, analyzing past work patterns, or improving from historical data.

Search and retrieve information from Graphiti Memory graph database. Covers search_memory_facts, search_memory_nodes, query construction, and group filtering. Use when user mentions Graphiti search, memory retrieval, finding past work, searching knowledge graph, or querying episodic memory.

Modern Neovim configuration expertise including Lua scripting, plugin management with lazy.nvim, LSP setup with Mason, AI integration with CodeCompanion, and workflow optimization. Covers keymaps, autocommands, and treesitter configuration. Use when user mentions Neovim, nvim, lazy.nvim, Mason, init.lua, Lua config, nvim plugins, or Neovim customization.

Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.

Analyze Claude Code changelog for changes that impact plugin development. Use when checking for new features, breaking changes, or opportunities to improve plugins based on Claude Code updates.

Systematic project orientation for unfamiliar codebases. Automatically activates when Claude detects uncertainty about project state, structure, or tooling. Analyzes git state (branch, changes, commits), project type (language, framework, structure), and development tooling (build, test, lint, CI/CD). Provides structured summary with risk flags and recommendations. Use when entering new projects or when working on shaky assumptions.

WCAG 2.1/2.2 compliance implementation, ARIA patterns, keyboard navigation, focus management, and accessibility testing. Use when implementing accessible components, fixing accessibility issues, or when the user mentions WCAG, ARIA, screen readers, or keyboard navigation.

CSS custom property architecture, theme systems, design token organization, and component library integration. Use when implementing design systems, theme switching, dark mode, or when the user mentions tokens, CSS variables, theming, or design system setup.

HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Covers REST APIs, GraphQL, request/response validation, authentication, and error handling. Use when user mentions API testing, Supertest, httpx, REST testing, endpoint testing, HTTP response validation, or testing API routes.

Access Claude Blog for latest Claude Code improvements, usage patterns, and best practices. Use when researching Claude Code features, CLAUDE.md optimization, or staying current with Claude capabilities. Checks recent articles for relevant updates and patterns.

Claude Code hooks configuration and development. Covers hook lifecycle events, configuration patterns, input/output schemas, and common automation use cases. Use when user mentions hooks, automation, PreToolUse, PostToolUse, SessionStart, SubagentStart, or needs to enforce consistent behavior in Claude Code workflows.