Route broad or ambiguous life-sciences research requests to the right skills, normalize core entities, optionally parallelize independent evidence gathering with subagents when available, and synthesize a concise evidence-backed answer. Use when a user asks a general life-sciences question that could span multiple sources or analysis types.

Find ways to open up meaningful free time in Outlook Calendar. Use when the user wants to clear part of their schedule, make room for focus time, create a longer uninterrupted block, or see the smallest set of calendar changes that would give time back.

Clean up Outlook newsletters and recurring subscription email safely. Use when the user wants to unsubscribe, separate newsletters from human mail, move recurring senders into folders, or organize low-signal subscription traffic without losing important messages.

Plan and execute runtime-behavior investigations with temporary probe scripts, validation matrices, state controls, and findings-first reports. Use only when the user explicitly invokes this skill to verify actual runtime behavior beyond normal code-level checks, especially to uncover edge cases, undocumented behavior, or common failure modes in local or live integrations. A baseline smoke check is fine as an entry point, but do not stop at happy-path confirmation.

Fix the tiny credit-note formatting bug and rerun the exact targeted test command.

Guide for upgrading Stripe API versions and SDKs

Triage a Gmail inbox into actionable buckets such as urgent, needs reply soon, waiting, and FYI using connected Gmail data. Use when the user asks to triage the inbox, rank what needs attention, find what still needs a reply, or separate important mail from noise.

Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.

Build, run, and debug local macOS apps and desktop executables using shell-first Xcode and Swift workflows. Use when asked to build a Mac app, launch it, diagnose compiler or linker failures, inspect startup problems, or debug desktop-only runtime issues.

Edit SharePoint-hosted spreadsheet files while preserving workbook structure, formulas, and formatting. Use when the user wants to update a real spreadsheet in SharePoint rather than summarize extracted sheet text.

Build polished one-day Outlook Calendar briefs. Use when the user asks for today, tomorrow, or a specific date summary with an agenda, conflict flags, free windows, remaining-meeting readouts, or a calendar brief, and Outlook Calendar is available.

Vercel Flags guidance — feature flags platform with unified dashboard, Flags Explorer, gradual rollouts, A/B testing, and provider adapters. Use when implementing feature flags, experimentation, or staged rollouts.

Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.

Agent-specific guidance. Read `CLAUDE.md` first for repo map and commands.

This document provides comprehensive context and guidelines for AI agents working on this repository.

This `Agents.md` file provides detailed instructions for OpenAI Codex and other AI agents collaborating on this repository. It includes project structure, conventions, testing, and update policies.

> **TL;DR**

- `lib/` — Flutter/Dart source (features, services, widgets). Do not edit generated files (`*.g.dart`, `*.freezed.dart`).

This file contains build commands, code style guidelines, and development practices for agentic coding agents working in this netlab repository.

Look through the /docs folder to learn details about:

This is a Swift 6+ [client library](https://www.rabbitmq.com/client-libraries) for RabbitMQ heavily

This repository is organized as a set of AI skills plus validation tooling.

See [ARCHITECTURE.md](./ARCHITECTURE.md) for more information about how the code

This repository is a coding-interview practice workspace with a Tk/Ttk GUI for generating problem stubs, editing code, and running tests. Everything lives under `/Users/andrewzhao/Documents/coding_int

<skills_system priority="1">

This document provides guidance for AI agents working with the Neural Radar Development Kit (NRDK), a Python framework for developing, training, and evaluating machine learning models on radar spectru

This document provides essential guidelines for working with the Steeltoe codebase. For detailed build and test procedures, refer to the [GitHub workflows](.github/workflows/) which serve as the sourc

This repo is a **static web app** (no build step) plus **Playwright smoke tests**.

Understanding the multi-agent system

**Claude Code: Please execute all steps below to set up parallel AI agents for the ZMF Production Dashboard**

Someone built a multi-agent orchestration system for VS Code Copilot with dedicated agent files for each role. The economics are wild, but the architecture patterns are what I can't stop thinking about.

LLM-powered coding and shell assistants that use tools to help with development

LLMs excel at **synthesis and critique** when given **bounded, well-structured inputs**. This module wraps provider calls into **role-specific agents** (analysts, researchers, trader, risk) that all s

This guide focuses on general conventions for engineering collaboration, helping the team understand repository organization, development environment, credential management, and quality self-check pro

USB HID control for MSI MPG 491CQP monitor. Rust implementation.

BEGIN directory specific Llama-3-virtuoso" AGENTS.md , other input may regard other hierarchical directories.

This file provides instructions for AI agents and human contributors working in this codebase.

This document defines **strict behavioral, architectural, and coding constraints** for OpenAI Codex when contributing to this repository.

- `opentiler/`: Core app (Qt/PySide6 GUI, dialogs, exporter, settings, utils, viewer). Assets in `opentiler/assets/`.

- Install deps: `./scripts/setup.sh`

This file contains instructions for developers working on the Azure Search and OpenAI demo application. It covers the overall code layout, how to add new data, how to add new azd environment variables

Please use `uv run` instead of `python`.

The Phaser game source lives in `src/`, organised by feature (e.g., `core/` bootstraps the game, `scenes/` drives flow, `systems/` holds gameplay logic). Tests mirror the runtime folders under `tests/

**Purpose**: This document serves as the central coordination hub for LLM agents working on this project. It contains architectural decisions, development workflows, and agent-specific instructions.

This repository is a Hugo site using the PaperMod theme.

<!--

<!-- nx configuration start-->

This repository is organized as a monorepo with product-facing apps at the top level:

Agent Lab is a Gradio-based platform for testing AI agents across multiple models

- **`~/CLAUDE.md`** - Machine-specific context (computer name, network, etc.)