Tools

Master microbiome data operations across Supabase, Neo4j, Upstash Vector, and Redis. Generates comprehensive BrilliantBiome reports with BrilliantScore calculations, species analysis, AMR assessments, and population insights. Use when querying microbiome data, generating reports, analyzing taxonomic relationships, or performing similarity searches across the two-lane architecture (clinical + research).

A short checklist for kicking off work effectively: plan, branch, track with bd, and set up validation.

Kyverno pod security policies enforcing Pod Security Standards, privilege restrictions, and security profiles for Kubernetes workloads.

Setup an autonomous software development cycle, inspired by Anthropic's "Effective harnesses for long-running agents" blog (https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents). Adapted to fit our tech-stack (TypeScript, NextJS, InstantDB, Trigger.dev, tRPC) and style (kebab-case file-naming).

Quick reference for common Git commands and workflows. Use when working with version control, committing changes, managing branches, or resolving Git issues. Covers daily Git operations, branching strategies, and troubleshooting.

Generate and review documentation for competition organizers using Diataxis framework. Use when writing docs for organizer workflows like creating competitions, managing divisions, scheduling heats, handling registrations, entering results, or managing volunteers/judges.

Expert guidance for Gitea self-hosted Git service including installation, configuration, repositories, webhooks, API usage, Docker deployment, and integration with CI/CD. Use this when working with Gitea Git hosting.

Rust development standards including cargo test, clippy, and rustfmt. Use when working with Rust files, Cargo.toml, or Rust tests.

Core skill activation protocol - establishes mandatory workflows for finding and applying skills before any task

Saves complete session state to STATUS.json for seamless continuation across conversations. Captures git context, in-progress tasks, service status, focus area, and next actions. Use at the end of work sessions, before context limits, or when switching to a different task. Do NOT use mid-task or for quick questions - the overhead is only worthwhile when you actually need to resume later.

Interactive UI theme generation when user needs help choosing colors/fonts.Generates cohesive themes based on brand personality using color harmony theory.Use when user asks for theme/color help OR building UI without design:- "What theme should I use?" "Help me pick colors" "Generate theme"- "What colors work well together?" "Suggest color palette"- User uncertain about design direction, needs aesthetic suggestions- Building UI/landing page with no design specs, needs complete themeKeywords: theme, color palette, colors, fonts, brand personality, color harmonyInteractive workflow: Ask personality → Present options → Generate custom theme.References pre-defined themes in .claude/themes/.Do NOT load for: User has clear aesthetic/colors, Figma/design file provided.Integrates with design-fundamentals: Generates themes following design principles.

Generate concise git commit messages from staged diffs. Use when the user asks for a commit message or wants help summarizing staged changes.

Use when launching a new product end-to-end from market research through post-launch monitoring.Orchestrates 15+ specialist agents across 5 phases in a 10-week coordinated workflow includingresearch, development, marketing, sales preparation, launch execution, and ongoing optimization.Employs hierarchical coordination with parallel execution for efficiency and comprehensive coverage.

Generate images using Google Gemini's image generation APIs via Python CLI. Use for "generate image", "create image", "gemini image", "AI image", or when needing AI image generation in Claude Code.

Context-driven development methodology for organized, spec-first coding. Use when:- Project has a `conductor/` directory- User mentions specs, plans, tracks, or context-driven development- Files like `conductor/tracks.md`, `conductor/product.md`, `conductor/workflow.md` exist- User asks about project status, implementation progress, or track management- User wants to organize development work with TDD practices- User invokes `/conductor-*` commands (setup, newtrack, implement, status, revert, validate, block, skip, revise, archive, export, refresh)- User mentions documentation is outdated or wants to sync context with codebase changesInteroperable with Gemini CLI extension and Claude Code commands.Integrates with Beads for persistent task memory across sessions.

Automatically generate comprehensive QA test plans when user mentions testing requirements, QA needs, or asks what should be tested. Analyzes code changes and features to create structured test scenarios. Invoke when user mentions "test plan", "QA", "what to test", "testing requirements", or "test scenarios".

This skill should be used when creating, modifying, or debugging Claude Code hooks. Triggers on phrases like "create a hook", "add a hook", "make a PreToolUse hook", "automate before tool runs", "block tool execution", "validate tool input", "log tool output", "hook for Write/Edit/Bash", "PostToolUse handler", "session start hook", or when working with files in .claude/hooks/ directory.

AI-powered PR Author Agent that transforms Observability Diff Plans into Pull Requests. Use when: (1) Generating instrumentation code from Scout Agent output, (2) Creating OTel configuration, correlation headers, lineage specs, (3) Scaffolding telemetry validation tests, (4) Creating GitHub/GitLab PRs with observability artifacts. Triggers: "generate PR from diff plan", "create instrumentation PR", "scaffold observability code", "generate OTel config", "create telemetry PR".

Generate GraphQL schemas, resolvers, and type definitions. Use when designing GraphQL APIs or documenting GraphQL schemas.

Complete Git version control workflow automation. USE WHEN user mentions commit, push, pull request, PR, branch, merge, rebase, stash, git status, staged files, unstaged changes, OR any version control operations. Handles conventional commits, security checks, and GitHub CLI integration.