experimental-research-metacognition
Do experiment-driven research (hypotheses → minimal repros → evidence) and continuously improve research skills + tooling. Use when behavior is uncertain, contested, or performance-sensitive.
Найдите подходящую возможность для вашего агента.
Do experiment-driven research (hypotheses → minimal repros → evidence) and continuously improve research skills + tooling. Use when behavior is uncertain, contested, or performance-sensitive.
Validates NWB files using NWB Inspector and provides intelligent correction recommendations
Probe and test SDR hardware capabilities (RTL-SDR, SDRplay, HackRF, etc.). Use when verifying device detection, discovering supported sample rates and gains, testing antenna ports, or troubleshooting SDR hardware issues.
Adjust SDR radio settings (frequency, gain, squelch, bandwidth, filters, AGC) in WaveCap-SDR. Use when changing tuning parameters, optimizing reception, or configuring channels.
Perform observational constraint (Emergent Constraint, EC) analysis for climate research. Use historical observations to constrain future climate projections from CMIP6 multi-model ensembles, reducing prediction uncertainty. Includes inter-model regression analysis, EC relationship establishment, physical mechanism diagnostics (residual analysis, teleconnection pathways, Walker circulation, lead-lag correlation, SVD), uncertainty quantification (variance reduction, confidence intervals), and reliability assessment (binning analysis, random EC comparison). Use when conducting observational constraint analysis, CMIP multi-model evaluation, reducing prediction uncertainty, validating inter-model relationships, or climate teleconnection research. Applicable to any climate variable pairs (e.g., SST-TAS, precipitation-circulation).
Deep analysis workflows for World Weaver memory systems, code, and architecture
Six-phase protocol for adapting methods across research domains
Conduct thorough, constructive code reviews that improve code quality and team knowledge. Focuses on what matters - architecture, logic, security, maintainability - while avoiding bikeshedding.
Standardized output format for code reviews with severity labels, file:line references, and fix code snippets. Use when generating review reports that need consistent, actionable feedback structure.
Validate code and configurations against the allowed technology stack per constitution. Use when writing platform code, selecting libraries, or checking framework compliance.
Code quality review skill focusing on readability, maintainability, and consistency (non-architectural). Checks for naming conventions, code duplication, type consistency, unused code, and other clean code issues.
Code review and quality assurance specialist for ensuring code quality, security, and maintainability
Validate wavecapsdr.yaml configuration files for syntax errors, schema violations, and logical inconsistencies. Use when editing config, troubleshooting startup failures, or verifying recipe/preset definitions before deployment.
Comprehensive code review before committing changes. Verifies alignment with specifications, ensures consistency, runs tests with 50%+ coverage requirement, and evaluates architecture and maintainability. Use when the user asks to "review my code", "review before commit", "check my changes", or before committing to ensure code quality.
Provides comprehensive TypeScript development expertise and coding standards. Ensures type safety through strict type checking, implements clean code patterns, and maintains consistent architectural decisions. Specializes in advanced type system features including generics, conditional types, mapped types, and template literal types. Use when: working with TypeScript files (.ts/.tsx), defining type definitions and interfaces, implementing generic programming patterns, designing type-safe APIs, handling complex type transformations, integrating TypeScript with React/Vue/Angular frameworks, configuring strict mode settings, resolving type errors, or optimizing type performance in large codebases.
Reviews code for architecture, performance, API design, and maintainability. AUTOMATICALLY INVOKE when user mentions "review", "PR", "pull request", "code review", "backend review", or "analyze code". Verifies against latest Microsoft C# and .NET standards.
Code review guidelines for commits and file changes. Covers four categories: Quality (security, correctness, maintainability), Regression (breaking changes, API compatibility), Documentation (code docs, changelogs), and Performance (optimization, efficiency).
Clean Code principles adapted for C#/.NET including naming, variables, functions, SOLID, error handling, and async patterns. Use when: (1) reviewing C# code, (2) refactoring for clarity, (3) writing new code, (4) code review feedback.
Thorough code review for Rust/WebAssembly projects. Identifies bugs, security issues, performance problems, and maintainability concerns. Provides actionable feedback with specific suggestions.
Check and enforce project policies from CLAUDE.md and POLICIES.md. Use when validating implementations against project standards, checking code style requirements, or ensuring compliance with development guidelines.