One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
ToolJetSkillToolJet/ToolJet/.agents/skills/commit/SKILL.md
Create commits across ToolJet's root and submodule repos (server/ee, frontend/ee). Detects dirty repos, generates commit messages, and updates submodule pointers in the right order. Use when asked to commit changes. Often followed by create-pr.
ToolJetSkillToolJet/ToolJet/.agents/skills/merge/SKILL.md
Merge a source branch into the current branch across all ToolJet repos (root + server/ee + frontend/ee submodules). Handles conflicts, stashing, and submodule ordering. Use when asked to merge, sync with, or bring in changes from another branch.
ToolJetAGENTS.mdToolJet/ToolJet/frontend/AGENTS.md
ToolJet Frontend — Agent Context React + Webpack. Edition composition (webpack aliases, registries, `fetchEdition()`) is covered in the root `AGENTS.md` — this file covers conventions and App Builder architecture. ## Testing context Before adding
ToolJetAGENTS.mdToolJet/ToolJet/server/AGENTS.md
columns/tables over adding parallel structures. ### Widget config sync (CRITICAL) Server widget config (`src/modules/apps/services/widget-config/`) and frontend config (`frontend/src/AppBuilder/WidgetManager/widgets/`) must change together. If a config change moves, renames, or removes
HKUDSAGENTS.mdHKUDS/DeepTutor/AGENTS.md
textbook.pdf deeptutor memory show deeptutor serve --port 8001 # API server only deeptutor start # backend + frontend together ``` ## Key Files | Path | Purpose | | ------------------------------------------ | ------------------------------------ | | `deeptutor/runtime/orchestrator.py` | `ChatOrchestrator` — unified entry | | `deeptutor/runtime/launcher.py` | Backend + frontend lifecycle / port discovery
HKUDSSkillHKUDS/DeepTutor/SKILL.md
Configure, manage, and use DeepTutor through its CLI, including capabilities, knowledge bases, partners, memory, sessions, notebooks, providers, skills, and the server or Web app.
tinyhumansaiAGENTS.mdtinyhumansai/openhuman/AGENTS.md
Rust core. The core also exposes JSON-RPC and a CLI. Architecture: [overview](gitbooks/developing/architecture.md), [frontend](gitbooks/developing/architecture/frontend.md), [Tauri shell](gitbooks/developing/architecture/tauri-shell.md), and [agent harness](gitbooks/developing/architecture/agent-harness.md). ## Repository map | Path | Purpose | | --- | --- | | `app/src/` | Vite
wshobsonAGENTS.mdwshobson/agents/docs/agents.md
Agent | Model | Description | | --------------------------------------------------------------------------------------------- | ------ | ---------------------------------------------------------------------- | | [backend-architect](../plugins/backend-development/agents/backend-architect.md) | opus | RESTful API design, microservice boundaries, database schemas | | [frontend-developer](../plugins/multi-platform-apps/agents/frontend-developer.md) | sonnet | React components, responsive layouts, client-side state management | | [graphql-architect](../plugins/backend-development/agents/graphql-architect.md) | opus
PostHogAGENTS.mdPostHog/posthog/AGENTS.md
Changed files only: `hogli test --changed` - Lint: - Python: - `ruff check . --fix` and `ruff format .` - Frontend: `pnpm --filter=@posthog/frontend fix` (safe Oxlint fixes + Oxfmt; suggestion fixes are not applied). `format` runs
PostHogSkillPostHog/posthog/.agents/skills/adding-product-alerting/SKILL.md
Recommended repo-engineering guide when adding alerting to a PostHog product or extending the shared alerts platform. Routes lifecycle state machines, AlertPolicy, destinations, HogFunction dispatch, email, fixed-cadence and calendar scheduling, insight evaluation, the AlertWizard, and shared alert editor components. Use for product alert implementations, shared destination types, lifecycle or scheduling options, advanced alert settings, and platform alert infrastructure. Not for configuring alerts in an existing product.
PostHogSkillPostHog/posthog/.agents/skills/analyzing-experiment-query-performance/SKILL.md
Pull and interpret production experiment query-performance data from the staff-only `/api/debug_ch_queries` endpoints backing the `/experiments/staff` scene: slowest experiment queries, precompute read/build health, and preaggregation cache footprint. Covers prod-US and prod-EU via a `query_performance:read` personal API key, all query params, and response field semantics (exception codes, exposure paths, precompute skip reasons, job states). Use when investigating slow or failing experiment queries, precompute regressions, 307/159/241 errors, preaggregation table growth, or when asked how experiment query performance or the precompute rollout is doing in production.
PostHogSkillPostHog/posthog/.agents/skills/authoring-ci-workflows/SKILL.md
Use when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under `.github/` — new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, `timeout-minutes`, `paths` filters, caching, or runner choice. Covers PostHog's workflow-authoring conventions and the reasons behind them: the 500-runs/10s dispatch cap, shallow vs full clone, per-SHA push concurrency, dedicated App-token rate-limit buckets, and fork-safe secrets on a public repo. Points to the linters (`bin/hogli lint:workflows`, actionlint) that enforce the mechanical rules, and to the narrower skills for production deploys, secrets, and Depot runners. Not for debugging red CI (use debugging-ci-failures) or wiring a new secret end to end (use managing-github-actions-secrets).
PostHogSkillPostHog/posthog/.agents/skills/building-product-empty-states/SKILL.md
Guide for adding a product setup empty state — the skippable first-run screen a product scene shows until real data arrives, built on the shared ProductEmptyState component. Use when adding an empty state or first-run/setup screen to a product scene, declaring `emptyState` on a `SceneExport`, writing a product setup-status detection logic, building an animated example-data preview widget, or deciding between the scene-level `ProductEmptyState` gate and an inline `ProductIntroduction` panel. Covers the `productSetupStatusLogic` single-layer contract, real-data detection rules, local-only skip semantics, wizard commands, and design tokens.
PostHogSkillPostHog/posthog/.agents/skills/clickhouse-migrations/SKILL.md
ClickHouse migration patterns and rules. Use when creating or modifying ClickHouse migrations.
PostHogSkillPostHog/posthog/.agents/skills/debugging-local-replay/SKILL.md
Debugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local pipeline: SDK capture, Caddy proxy, capture-replay (Rust), Kafka, ingestion-sessionreplay (Node), recording-api (Node), SeaweedFS, and common failure modes like orphaned processes, stuck phrocs workers, and trigger misconfiguration.
PostHogSkillPostHog/posthog/.agents/skills/debugging-mcp-analytics/SKILL.md
Debug, support, and build PostHog MCP Analytics — product analytics for MCP servers (the `@posthog/mcp` and `posthog.mcp` SDKs plus the mcp_analytics product). Use when MCP analytics data looks wrong or missing ("events aren't showing", "intent clusters are empty", "sessions are missing", "per-tool numbers look wrong"), when writing queries over `$mcp_*` events by hand, or when doing feature work on the SDKs, the dashboard and its query runners, the self-instrumented MCP server, the `wizard mcp-analytics` install command, or the in-app onboarding. Covers the repo map, the `$mcp_*` vocabulary and where each property comes from, the rules that silently corrupt metrics when ignored, the end-to-end pipeline and where each stage breaks, and which repo to change. For reading the data rather than fixing it, prefer the `exploring-mcp-*` and `improving-mcp-tools` skills.
PostHogSkillPostHog/posthog/.agents/skills/developing-subscriptions/SKILL.md
Guides PostHog engineers through subscription product changes. Use when changing subscription resource types, destinations, schedules, delivery workflows, retry or automatic disable behavior, permissions, limits, AI summaries, AI prompt reports, delivery history, subscription APIs, MCP tools, or subscription management UI. Not for configuring an existing subscription through MCP.
PostHogSkillPostHog/posthog/.agents/skills/django-migrations/SKILL.md
Django migration patterns and safety workflow for PostHog. Use when creating, adjusting, or reviewing Django/Postgres migrations, including non-blocking index/constraint changes, multi-phase schema changes, data backfills, migration conflict rebasing, and product model moves that require SeparateDatabaseAndState. Also use for any deletion or removal of a model, table, column, product, or app — including deleting migration files or retiring a feature — even when no migration is written.
PostHogSkillPostHog/posthog/.agents/skills/fixing-flaky-tests/SKILL.md
Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when `hogli ci:insights` or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a flaky job, when asked to check Trunk Flaky Tests for a test, PR, or master, or when asked to deflake, stabilize, or fix a flaky Jest, pytest, or Playwright test. Core discipline: reproduce locally before changing anything, fix the root cause (never mask it with sleeps, retries, or bigger timeouts), and prove the fix with an N-run validation loop sized to the observed failure rate. Stabilizing is not the only valid outcome — the skill also gates whether the test should exist, so deleting a test that catches nothing real, or re-leveling one that flakes because of the level it runs at, are first-class endings.
PostHogSkillPostHog/posthog/.agents/skills/implementing-mcp-tools/SKILL.md
Guide for exposing PostHog product endpoints as MCP tools. Use when creating new or updating API endpoints, adding MCP tool definitions, scaffolding YAML configs, or writing serializers with good descriptions. Covers the full pipeline from Django serializer to generated TypeScript tool handler.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
