Research

Reference and maintain knowledge of the project's technical stack including frameworks, languages, databases, testing tools, and third-party services. Use this skill when making architectural decisions about which technologies to use. When adding new dependencies or integrating third-party services. When setting up development environments or deployment infrastructure. When choosing between different libraries or frameworks for a feature. When documenting the technology choices made in the project. When onboarding new team members to understand the tech stack. This skill helps ensure technology choices align with the established stack and provides a reference for all technical decisions.

Property-based testing with Hypothesis for discovering edge cases and validating invariants.Use when implementing comprehensive test coverage, testing complex logic with many inputs,or validating mathematical properties and invariants across input domains.Triggered by: hypothesis, property-based testing, @given, strategies, generative testing.

Comprehensive research, analysis, and content extraction system. Multi-source parallel research using available researcher agents. Deep content analysis with extended thinking. Intelligent retrieval for difficult sites. Fabric pattern selection for 242+ specialized prompts. USE WHEN user says 'do research', 'extract wisdom', 'analyze content', 'find information about', or requests web/content research.

PAI (Personal AI Infrastructure) - Your AI system core. AUTO-LOADS at session start. USE WHEN any session begins OR user asks about PAI identity, response format, stack preferences, security protocols, or delegation patterns.

Create unique visual designs by synthesizing from inspirations and preferences. Covers typography, color, layout, spacing, and animation philosophy.

Generates metadata for research documents and specifications including date/time, git commit, branch, and repository info. Use when creating research documents, handoffs, or any documentation that needs timestamp and git metadata.

HODD-RUST: Validation-first Rust development. Strictly validation-first before-and-after(-and-while) planning and execution. Merges Type-driven + Spec-first + Proof-driven + Design-by-contracts. Use for Rust projects requiring formal verification, safety proofs, comprehensive validation, or when working with unsafe code, concurrency, or FFI boundaries. This skill provides both reference documentation AND execution capabilities for the full PLAN -> CREATE -> VERIFY -> REMEDIATE workflow.

Skill for validating and repairing evidence references in the dismech knowledge base. Use this skill when working with evidence items in disorder YAML files, validating that snippet text matches PubMed abstracts, and repairing misquoted or fabricated evidence. Critical for ensuring scientific accuracy and preventing AI hallucinations.

This skill provides comprehensive security assessment and vulnerability management tools through x-cmd CLI, including network reconnaissance with Shodan, vulnerability scanning with OSV, and known exploited vulnerability tracking with KEV. This skill should be used when users need to perform security assessments, vulnerability research, network reconnaissance, or security monitoring from command line interfaces.

eXtreme Programming Test-Driven Development (XP-style TDD) Skill. This skill provides both reference documentation AND execution capabilities for the full PLAN -> RED -> GREEN -> REFACTOR workflow.

Automated validation orchestration across proof, spec, type, contract, and test artifacts with configurable precedence and gating. This skill provides both reference documentation AND execution capabilities for the full PLAN -> CREATE -> EXECUTE -> REPORT workflow.

Create isolated jj workspaces for testing changes, running experiments in parallel, and exploring alternative implementations. Use when testing breaking changes, comparing different approaches, or running long-running operations without blocking other work. (project)

This skill enables GitHub repository documentation exploration using DeepWiki API directly via curl. Use when researching repository structure, understanding library APIs, or asking questions about open-source projects. MCP server not required.

Integration guide for SawyerHood/dev-browser, a Claude Code plugin for browser automation. This skill enables agents to research, test web UIs, and interact with web applications using a headless browser.

Conduct comprehensive market research and competitive analysis to validate the problem and understand the market landscape. Use when user asks to conduct market research, validate market, analyze competitors, or start Stage 1 after init-ideas.

Generate color-coded electronics schematic diagrams from wiring documentation using AI image generation.Parses WIRING.md or similar documentation files, researches component pinouts via web search,and generates visual schematic images with hobby-friendly color coding using Nano Banana Pro.Use when the user wants to:- Generate a schematic from wiring documentation- Visualize circuit connections from a WIRING.md file- Create circuit diagrams for embedded projects- Generate hardware documentation imagesTriggers: "generate schematic", "create schematic", "schematic from wiring","visualize circuit", "circuit diagram", "wiring diagram image"

This skill provides guidance for using DeepWiki MCP to explore GitHub repository documentation. Use when researching repository structure, understanding library APIs, asking questions about open-source projects, or exploring documentation for any GitHub repository.

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

Gather information about users from materials, profile config, GitHub, and web search to inform portfolio content and design decisions.

Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.