Loading
Write failing tests first, surface the edge cases you'd miss, and turn requirements into a real test suite.
Tests are how you know a change works — and LLMs are good at generating them if you frame the task well. These prompts write failing tests first from a spec, surface edge cases you'd miss, and turn loose requirements into a concrete suite. They emphasise meaningful assertions over coverage theatre. Run them on any model with your own key.
Advanced AI agent memory system with hybrid search (BM25 + vector), Cohere reranking, embedding cache, and incremental sync. ChromaDB + Ollama backed, 100% self-hosted (Cohere reranking optional). Use when managing agent long-term memory, indexing memory files, running memory health checks, or searching agent memories with hybrid retrieval.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
This repository is a monorepo. Each library lives in a subdirectory under libs/.
This repository is a monorepo. Each library lives in a subdirectory under libs/.
Instructions for migrating from Semantic Kernel Agents to Agent Framework in .NET projects.
Style guidelines for writing and updating documentation. Use when writing new docs, updating existing docs, or reviewing docs for quality.
This file provides guidance to AI coding agents when working with code in this repository.
Guide for working on the Acolyte codebase. Use when building features, fixing bugs, or extending Acolyte itself.
Run pre-deploy checks, determine version bump, and execute release. Use when ready to cut a release.
Acolyte is a terminal-first AI coding agent: local-first, observable, extensible. Read docs/architecture.md before working on unfamiliar subsystems.
This skill should be used when the user asks to "update SDK", "bump SDK version", "pin SDK to a commit", "test unreleased SDK", "update agent-server image", "bump the version", "prepare a release", "what files change for a release", or needs to know how SDK packages are managed in the OpenHands repository. For detailed reference material, see references/docker-image-locations.md and references/sdk
This skill should be used when the user asks to "test a cross-repo feature", "deploy a feature branch to staging", "test SDK against OH Cloud", "e2e test a cloud workspace feature", "test provider tokens", "test secrets inheritance", or when changes span the SDK and OpenHands server repos and need end-to-end validation against a staging deployment.
This repository contains the code for OpenHands, an automated AI software engineer. It has a Python backend (in the openhands directory) and React frontend (in the frontend directory).
The SSE system (sseevents, connectSSE, onClientResume) is the backbone of live updates. When touching it: - Server sends a real {type:"ping"} data event every 10s — clients use this to detect zombie connections - Client declares SSE stale after 18s of silence and force-reconnects - visibilitychange / pageshow / focus / online all trigger onClientResume which refetches if data i
When editing CSS: - Check that any new UI fits within the existing @media (max-width: 600px) breakpoints - Touch targets must be at least 44x44 on mobile - Use env(safe-area-inset-) for anything positioned at screen edges (iOS PWA notch) - The viewport uses viewport-fit=cover — fixed overlays must extend to physical edges - Test that flex containers don't overflow on 375px-wide
/review-session-log — Review a session's terminal log
Run the amux Playwright test suite or investigate specific UI issues with a headless browser.
Quick health check of the amux server and dashboard after code changes.
Project Overview [What does this project do? Who uses it? Why does it exist?]
You are Claude Code, an AI coding assistant by Anthropic. You help users with software engineering tasks including writing code, debugging, refactoring, explaining code, running commands, and managing projects.
AGENTS.md — CrewAI Reference for AI Coding Assistants
Work with Effect v4 / effect-smol TypeScript code in this repo
- Prefer HttpClient.HttpClient / HttpClientResponse.HttpClientResponse over web fetch / Response at package boundaries. - Use Stream.Stream for streaming data flow. Avoid ad hoc async generators or manual web reader loops unless an Effect Stream API cannot model the behavior. - Use Effect Schema codecs for JSON encode/decode (Schema.fromJsonString(...)) instead of direct JSON.p
Use these patterns for server and HttpApi middleware tests in this directory.
The tmpdir function in fixture/fixture.ts creates temporary directories for tests with automatic cleanup.
- To regenerate the JavaScript SDK, run ./packages/sdk/js/script/build.ts. - The default branch in this repo is dev. - Local main ref may not exist; use dev or origin/dev for diffs.
-Goal- Given a text document that is potentially relevant to this activity and a list of entity types, identify all entities of those types from the text and all relationships among the identified entities.
Emdash is a cross-platform Electron app for orchestrating multiple AI coding agents in parallel, each isolated in its own Git worktree and able to run locally or over SSH. It combines provider-agnostic CLI agent execution, task and conversation management, diff review, integrations, terminal sessions, and packaging for desktop releases.
- Do match the interpreter requirement declared in pyproject.toml (Python ≥ 3.12) and install requirements.txt plus requirements-dev.txt before running tools. - Do run tests with PYTHONPATH=. set to keep imports functional (for example PYTHONPATH=. ./.venv/bin/pytest tests/unittest/testfixjsonescapechar.py -q). - Do adjust configuration through .pragent.toml or files under prag
Central hub for building, testing, and iterating on ADK agents. Trigger this skill when the user wants to create a new agent, configure modes (task, single-turn), or build graph-based workflows.
Implement a bug fix or feature for a GitHub issue in the adk-python repository. Use this skill after the triage/analysis is complete and approved. It creates a new branch, implements code changes, adds tests, and updates relevant documentation/samples. Triggers on "/adk-issue-fix" commands.
Analyze and triage a GitHub issue for the adk-python repository. Use this skill to retrieve issue details, inspect the codebase, evaluate justification, check for existing PRs, and produce a structured analysis report. Triggers on "/adk-issue-analyze" commands. This skill is strictly read-only and must be used whenever the "/adk-issue-analyze" command is explicitly called.
Orchestrate analyzing, triaging, and reviewing GitHub pull requests (PRs) for the adk-python repository. Use this skill when a user provides a PR number or URL. It coordinates analysis via `adk-pr-analyze` and review implementation/pushback via subsequent interactive steps. Triggers on "triage pr", "pr triage", "review pr", "pr review", "pull request", "github.com/google/adk-python/pull/". Do NOT
Use when debugging ADK agents, inspecting sessions, testing agent behavior, troubleshooting tool calls, event flow issues, or diagnosing LLM/model problems.
Use for any git operation (commit, push, pull, rebase, branch, PR, cherry-pick, etc.). Provides commit message format and conventions.
Analyze and triage GitHub pull requests for the adk-python repository in a strictly read-only manner. Use this skill to fetch PR details, verify the contributor's CLA, inspect the codebase, evaluate architectural and style alignment, and produce a structured analysis report. Triggers on "/adk-pr-analyze" commands. This skill is strictly read-only and must be used whenever the "/adk-pr-analyze" com
Author new samples for the ADK Python repository. Use this skill when the user wants to create a new sample demonstrating a feature or agent pattern (e.g., dynamic nodes, standalone agents, fan-out/fan-in) or when adding examples to subdirectories under `contributing/`.
Set up a local development environment for the ADK Python project. Use when the user wants to get started developing, set up their environment, install dependencies, or prepare for contributing.
Reviews all local changes in the repository for errors, styling compliance, unintended outcomes, and necessary documentation/test/sample updates. Generates a report and assists in fixing identified issues on-demand. Triggers on "adk-review", "review changes", "pr review", "check code style", "verify changes".
ADK development style guide for routine nits — Python idioms, codebase conventions, imports, typing, Pydantic patterns, formatting, logging, and file organization. Use this skill whenever writing code, tests, or reviewing PRs for the ADK project to ensure compliance with styling and coding conventions. Triggers on "code style", "how should I format", "naming convention", "lint", "nit", "imports",
This document provides context for AI coding assistants (Antigravity, Gemini CLI, etc.) to understand the ADK Python project and assist with development.
This directory holds shared test helpers reused by core and bundled plugin tests.
Find or repair small high-confidence non-SDK-boundary OpenClaw bugfix PRs until five are landable.
Run macOS Parallels smoke with Discord send, host verification, host reply, and guest readback proof.
Add a redacted agent transcript section to GitHub PR or issue bodies during OpenClaw agent-created PR/issue workflows.
Investigate OpenClaw pnpm test memory growth, Vitest OOMs, RSS spikes, and heap snapshot deltas.
Use immediately for any pasted OpenClaw GitHub issue or PR URL/number, and for OpenClaw issue/PR review, triage, duplicate search, opener identity/who wrote it, author account age/activity, comments, labels, close, land, or maintainer evidence checks.
Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.
Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.
Fix only small, high-certainty OpenClaw bugs from a pasted issue/PR list after deep code review.
Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.
Use when testing, fixing, or extending the OpenClaw Control UI GUI with Vitest + Playwright end-to-end checks, mocked Gateway WebSocket flows, mocked dashboard runs, screenshots/videos, or agent-verifiable browser proof.
Use when reviewing, reproducing, or proving OpenClaw Telegram behavior with a real Telegram user on Crabbox, including PR review workflows that need an agent-controlled Telegram Desktop recording, TDLib user-driver commands, Convex-leased credentials, WebVNC observation, and motion-trimmed artifacts.
Author OpenClaw Docker E2E and live provider Docker lanes.
Draft or post OpenClaw beta/stable Discord release announcements from changelog, GitHub release, registry, and validation evidence. Use when announcing a beta, stable release, release candidate, or asking what users should test after an OpenClaw release.
Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox proof.
Run, rerun, debug, or interpret OpenClaw Parallels install, onboarding, gateway smoke, and upgrade checks.
Prepare or verify OpenClaw stable/beta releases, changelogs, release notes, publish commands, and artifacts.
Run, watch, debug, extend, or explain OpenClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.
Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.
OpenClaw Tideclaw alpha/nightly release automation: isolated branches, local fixes, release CI, branch retention, and forward-port to main.
Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.
Use for OpenClaw clawtributors PR/issue triage: Discrawl discovery, live-open rechecks, deep review, topic grouping, and compact @handle/LOC/type/blast/verification summaries.
Auto Review closeout. Codex review is the default when no engine is set and is the recommended reviewer.
OpenClaw builds a custom system prompt for every agent run. The prompt is OpenClaw-owned and does not use a runtime default prompt.
Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions ("telephone game" flow). For coding-agent thread requests, read this skill first, then use only `sessions_spawn` for thread creation. Codex chat bin
This file applies to work under extensions/acpx/.
This directory contains bundled plugins. Treat it as the same boundary that third-party plugins see.
This directory owns local tooling, script wrappers, and generated-artifact helper rules.
You are maintaining OpenClaw test performance after a trusted main-branch CI run.
You are Mantis running native Telegram Desktop visual proof for an OpenClaw PR.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
First-time analysis of a repository with no prior reviewer outcomes. Crawl historical merged-PR review feedback with the gh CLI (plus any preloaded samples), extract the team's review norms, and synthesize the initial per-repo review-style prompt. Use this for a cold-start repo; use continual-learning instead once the reviewer has accumulated finding outcomes.
This file provides guidance to Coding Agents when working with code in this repository.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Use when preparing, tagging, and publishing an apps/cli npm release. Guides changelog drafting, apps/cli/package.json version bumps, cli-vX.Y.Z tags, local npm publishing, and the publish-cli GitHub workflow.
Comprehensive OpenTUI skill for building terminal user interfaces. Covers the core imperative API, React reconciler, and Solid reconciler. Use for any TUI development task including components, layout, keyboard handling, animations, and testing.
Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, PR template usage, and PR creation using the gh CLI tool.
Tools are how agents interact with the world. The Cline SDK supports both built-in tools (via ClineCore) and custom tools you define yourself.
The Cline SDK supports scheduled, one-off, and event-driven agent execution through the automation subsystem in @cline/core.
A Cline plugin is a TypeScript module that extends any agent built on the Cline SDK. The same plugin runs in the Cline CLI, VS Code and JetBrains extensions, and any custom app built on @cline/core.
OpenTUI is built for Bun. Always use Bun commands:
The foundational library for building terminal user interfaces. Provides an imperative API with all primitives, giving you maximum control over rendering, state, and behavior.
OpenTUI respects several environment variables for configuration and debugging.
A SolidJS reconciler for building terminal user interfaces with fine-grained reactivity. Get optimal performance with Solid's signal-based approach.
Renders a Solid component tree into a CLI renderer.
The CLI creates the my-app directory for you - it must not already exist.
How to test terminal user interfaces built with OpenTUI.
A React reconciler for building terminal user interfaces with familiar React patterns. Write TUIs using JSX, hooks, and component composition.
The CLI creates the my-app directory for you - it must not already exist.
How to handle keyboard input in OpenTUI applications.
This file applies to the SDK workspace rooted at this directory (sdk/). In this repo, "root" means the SDK workspace root unless explicitly stated otherwise. Ignore the legacy repository root for SDK development except for Git operations or repo-wide searches that are explicitly needed.
The system prompt architecture provides a modular, composable system for building AI assistant prompts. It supports multiple model variants, dynamic component composition, flexible tool configuration, and template-based prompt generation.
This directory contains integration tests for the system prompt generation with snapshot testing capabilities.
Contributing to System Prompts and Model Configuration
<p align="center" <bLightweight, beautiful and user-friendly interactive prompts</b<br / <sub Easy to use CLI prompts to enquire users for information▌</sub </p
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
This file provides guidance to Claude Code when working with the direct benchmark harness.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Address PR review comments and loop until CI green and all comments resolved. TRIGGER when user asks to address comments, fix PR feedback, respond to reviewers, or babysit/monitor a PR.
Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them. TRIGGER when user asks to write frontend tests, add test coverage, or 'write tests for my changes'.
Set up a new git worktree for parallel development. Creates the worktree, copies .env files, installs dependencies, and generates Prisma client. TRIGGER when user asks to set up a worktree, work on a branch in isolation, or needs a separate environment for a branch or PR.
Open a pull request with proper PR template, test coverage, and review workflow. Guides agents through creating a PR that follows repo conventions, ensures existing behaviors aren't broken, covers new behaviors with tests, and handles review via bot when local testing isn't possible. TRIGGER when user asks to "open a PR", "create a PR", "make a PR", "submit a PR", "open pull request", "push and cr
E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls. TRIGGER when user asks to manually test a PR, test a feature end-to-end, or run integration tests against a running system.
Meta-agent supervisor that manages a fleet of Claude Code agents running in tmux windows. Auto-discovers spare worktrees, spawns agents, monitors state, kicks idle agents, approves safe confirmations, and recycles worktrees when done. TRIGGER when user asks to supervise agents, run parallel tasks, manage worktrees, check agent status, or orchestrate parallel work.
Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.
Alternate /pr-review and /pr-address on a PR until the PR is truly mergeable — no new review findings, zero unresolved inline threads, zero unaddressed top-level reviews or issue comments, all CI checks green, and two consecutive quiet polls after CI settles. Use when the user wants a PR polished to merge-ready without setting a fixed number of rounds.
This file provides guidance to coding agents when working with the frontend.
Type Tool Speed Purpose --------------- --------------------- --------------- -------------------------------- E2E Playwright Slow (~5s/test) Real browser, full user journeys Integration Vitest + RTL Fast (~100ms) Component + mocked API Unit Vitest + RTL Fastest (~10ms) Individual functions/components Visual Storybook + Chromatic N/A UI appearance, design system
This file provides guidance to coding agents when working with the backend.
This file provides guidance to coding agents when working with code in this repository.
This guide provides context for coding agents when updating the autogptplatform folder.
Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context. Use when tasks involve merge conflicts, rebasing, PR conflicts, or git conflict resolution. This skill analyzes commit messages, git blame, and code intent to make intelligent resolution decisions.
Provides context about the Roo Code evals system structure in this monorepo. Use when tasks mention "evals", "evaluation", "eval runs", "eval exercises", or working with the evals infrastructure. Helps distinguish between the evals execution system (packages/evals, apps/web-evals) and the public website evals display page (apps/web-roo-code/src/app/evals).
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
Display HTML content on connected OpenClaw nodes (Mac app, iOS, Android).
Query Google Places API (New) via the goplaces CLI for text search, place details, resolve, and reviews. Use for human-friendly place lookup or JSON output for scripts.
Create or update AgentSkills, especially when a user wants the agent to learn a reusable capability, workflow, integration, domain rule, team process, or tool usage pattern for future tasks. Use when designing, structuring, reviewing, validating, packaging, or improving skills with SKILL.md, scripts, references, and assets.
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
tRPC-Agent-Go is a Go multi-module monorepo (library/framework) for building AI agent systems. It is not a standalone application — there is no single main.go to run. The root module path is trpc.group/trpc-go/trpc-agent-go.
Processes kick-off meeting transcripts and/or notes into structured project documentation. Use this skill when the user sends kick-off meeting material (transcript, notes, recording text) and requests structured output. Triggers: "kick-off", "kickoff", "projekt indító", "meeting feldolgozás", "transzkript feldolgozás", "/notes", "/charter", "/actions". Supports three output types: meeting notes (M
Reference Claude Code's prompt engineering patterns for AI/Agent development. Provides best practices for system prompts, tool design, agent orchestration, and safety.
Write Go test code using the gt library. Use when writing tests, creating test files, or when the user asks to add tests for Go code.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Debug and monitor Neuron AI applications with Inspector APM, event observability, logging, and performance analysis. Use this skill whenever the user mentions debugging, monitoring, observability, performance analysis, tracing, Inspector, or needs to understand why an agent is behaving a certain way. Also trigger for tasks involving agent execution timeline, tool call inspection, response quality
Implement RAG (Retrieval-Augmented Generation) with Neuron AI including vector stores, embeddings providers, document loaders, and retrieval strategies. Use this skill whenever the user mentions RAG, retrieval, vector search, document retrieval, semantic search, knowledge bases, chat with documents, or wants to build AI systems that can query and understand external documents. Also trigger for tas
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving evaluator discovery, output configuration, result analysis, or building custom assertio
Create custom tools, toolkits, and MCP integrations for Neuron AI agents. Use this skill when the user mentions creating tools, building toolkits, extending Tool class, defining tool properties, implementing tool execution, MCP server integration, Model Context Protocol, connecting external tools, or tool guidelines. Also trigger for any task involving ToolProperty, ArrayProperty, ObjectProperty,
Write tests for Neuron AI agents, RAG systems, workflows, and tools using the built-in testing utilities. Use this skill when the user mentions testing agents, writing unit tests, mocking AI providers, testing tool execution, verifying RAG retrieval, testing workflow behavior, or creating test cases for Neuron AI components. Also trigger for any task involving PHPUnit tests, fake providers, test a
Individual tests: vendor/bin/phpunit tests/AgentTest.php or --filter testMethodName
Neuron is a PHP Agentic framework for building AI agents with chat, tools, RAG, structured output, and workflow orchestration.
Unified messaging layer. Used by Agent, RAG, and Providers.
Retrieval Augmented Generation. Extends Agent with document search.
Test fakes and utilities for testing Neuron applications.
Dataset-driven AI evaluation with flexible assertions and output drivers.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especial
Default to using Bun instead of Node.js.
Translate an existing Remotion (React-based) video composition into a HyperFrames HTML composition. Use ONLY when the user explicitly asks to port, convert, migrate, translate, or rewrite a Remotion composition as HyperFrames (e.g. "port my Remotion project to HyperFrames"). Do NOT use when (a) authoring a NEW HyperFrames composition (even if A/B-testing a Remotion video); (b) Remotion is mentione
Asset preprocessing for HyperFrames compositions — text-to-speech narration (Kokoro), audio/video transcription (Whisper), and background removal for transparent overlays (u2net). Use when generating voiceover from text, transcribing speech for captions, removing the background from a video or image to use as a transparent overlay, choosing a TTS voice or whisper model, or chaining these (TTS → tr
Lottie and dotLottie adapter patterns for HyperFrames. Use when embedding lottie-web JSON animations, .lottie files, @lottiefiles/dotlottie-web players, registering instances on window.__hfLottie, or making After Effects exports deterministic in HyperFrames.
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.
Project Structure & Module Organization Core runtime sits in graphragagent/: agents/ implements GraphRAG agents (multi-agent flows under multiagent/), graph/ and integrations/build/ own graph ingestion, and cachemanager/ wraps persistence. The FastAPI backend lives in server/; the Streamlit UI in frontend/. Tests and evaluation scripts reside in test/. Data inputs (datasets/, d
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Keep going until the user's query is completely resolved. Solve it autonomously before yielding back.
After completing code changes, verify correctness by running validation commands.
NEVER use execute to run shell commands when a dedicated tool exists. This is a hard rule.
GPT Description: I create SEO-friendly articles, with a quirky confidentiality clause. - By rjarivi
GPT Description: Provides instructions to test the leak prevention capabilities of your GPTs prompts. 🐦[twitter.com/GptHammer3309] - By 023404.com
GPT Title: Educational Email Course Creator
GPT Description: Coding Wizard: 100x Engineer. Create a website with a sentence. Built for a new era of creativity: Prompt-gramming 15+ Hotkeys for coding flows. 19 starter projects. Prompt 1st code & media! Start with a picture or a quest? Type: K for cmd Menu, or R for README v1.13 - By mindgoblinstudios.com
GPT Description: Look into my eyes. v1.0 - By mindgoblinstudios.com
GPT description: Coding Wizard🧙♂️ Create a website (or anything) with a sentence. A guide to a new era of creativity Prompt-gramming 20+ Hotkeys for coding. 27 starter projects to learn prompt-1st Code & Art. Start with a photo or any Question? Type K for cmds, R for README v1.19.1 - By mindgoblinstudios.com
GPT Description: 📊 Rate, Find & Fix Your Socials - By probsolvio.com
Quality covers: - SOP creation and maintenance - Process audits (internal) - Quality standards definition - Stranger test: validating that processes work without tribal knowledge - Issue tracking for quality failures - Training materials and knowledge base
Dev covers: - Software architecture and technical decisions - Feature implementation and bug fixes - Code review and quality gates - Testing strategy and execution - Technical documentation - Developer tooling and workflows
Detailed operational config. Loaded when you open squads/orchestrator/.
[SUGGESTION MODE: Suggest what the user might naturally type next into Claude Code.]
You are an expert code reviewer. Follow these steps:
Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.
Launch a new agent to handle complex, multi-step tasks autonomously.
IMPORTANT: Assist with authorized security testing, defensive security, CTF challenges, and educational contexts. Refuse requests for destructive techniques, DoS attacks, mass targeting, supply chain compromise, or detection evasion for malicious purposes. Dual-use security tools (C2 frameworks, credential testing, exploit development) require clear authorization context: pente
Your task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions. This summary should be thorough in capturing technical details, code patterns, and architectural decisions that would be essential for continuing development work without losing context.
<policyspec Claude Code Code Bash command prefix detection
Please analyze this codebase and create a CLAUDE.md file, which will be given to future instances of Claude Code to operate in this repository.
You are analyzing output from a bash command to determine if it should be summarized.
\uD83E\uDD16 Installing Claude Code GitHub App
Only create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:
Your task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions. This summary should be thorough in capturing technical details, code patterns, and architectural decisions that would be essential for continuing development work without losing context.
Plan mode is active. The user indicated that they do not want you to execute yet -- you MUST NOT make any edits (with the exception of the plan file mentioned below), run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supercedes any other instructions you have received.
You are a search assistant that helps find relevant sessions based on a user's query.
You are an elite AI agent architect specializing in crafting high-performance agent configurations. Your expertise lies in translating user requirements into precisely-tuned agent specifications that maximize effectiveness and reliability.
Read the framework docs first: nodemodules/@cyanheads/mcp-ts-core/CLAUDE.md contains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.
Add a new subpath export to the @cyanheads/mcp-ts-core package. Use when creating a new public API surface that consumers import from a dedicated subpath (e.g., @cyanheads/mcp-ts-core/newutil).
Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
Scaffold a new MCP resource definition. Use when the user asks to add a resource, expose data via URI, or create a readable endpoint.
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for `.mcpb` bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup publish workflow. Retries transient netwo
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
Testing patterns for MCP tool/resource handlers using `createMockContext` and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
Reference for core and server configuration in `@cyanheads/mcp-ts-core`. Covers env var tables with defaults, priority order, server-specific Zod schema pattern, and Workers lazy-parsing requirement.
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled from the git_wrapup_instructions protocol.
Post-init orientation for an MCP server built on @cyanheads/mcp-ts-core. Use after running `@cyanheads/mcp-ts-core init` to understand the project structure, conventions, and skill sync model. Also use when onboarding to an existing project for the first time.
File a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to test, try out, or verify their MCP surface.
Pick and run a multi-phase workflow that chains foundational task skills (`git-wrapup`, `release-and-publish`, `maintenance`, `field-test`, `setup`, etc.) end-to-end. Routes user intent to a workflow file under `workflows/` — greenfield builds, maintenance + release, field-test + fix, or known-work + release. Single source for the universal rules (no commits without authorization, no destructive g
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
Scaffold an MCP App tool + UI resource pair. Use when the user asks to add a tool with interactive UI, create an MCP App, or build a visual/interactive tool.
Read-only audit of MCP definition language across an existing surface — tools, resources, prompts. Walks every definition file and checks 12 categories the LLM reads to decide whether and how to call: voice & tense, internal leaks, audience leaks, defaults, recovery hints, output descriptions, cross-references, sparsity, examples, structure, mutator observability, unit-bearing numeric names. Produ
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for `@cyanheads/mcp-ts-core`. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
Add a new storage or service provider to the core package. Use when implementing a new backend for StorageService (e.g., a new database) or a new service provider (e.g., a new LLM backend).
Investigate, adopt, and verify dependency updates — with special handling for `@cyanheads/mcp-ts-core`. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or review updates you already applied.
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
Review an MCP server for common security gaps: LLM-facing surfaces as injection vector (tools, resources, prompts, descriptions), scope blast radius, destructive ops without consent, upstream auth shape, input sinks (URL / path / roots / shell / schema strictness / ReDoS), tenant isolation, leakage through errors and telemetry, unbounded resources, and HTTP-mode deployment surface. Use before a re
Post-session code review and cleanup against a working tree of changes. Analyzes `git diff` to simplify, consolidate, and align changed code with the existing codebase — modernize syntax, remove unnecessary complexity, consolidate duplicated logic, catch efficiency issues. Use after a substantive working session, or when asked to clean up, simplify, reduce slop, consolidate, modernize, tighten up,
Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.
Developer note: Never assume. Read related files and docs before making changes. Read full file content for context. Never try to edit a file before reading it.
You are GPT-5.2 running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
You are a coding agent running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
You are a coding agent running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are Codex, a coding agent based on GPT-5. You and the user share one workspace, and your job is to collaborate with them until their goal is genuinely handled.
Memory Writing Agent: Phase 1 (Single Rollout)
Memory Writing Agent: Phase 2 (Consolidation)
Continue working toward the active thread goal.
Collaboration Style: Execute You execute on a well-specified task independently and report progress.
You work in 3 phases, and you should chat your way to a great plan before finalizing it. A great plan is very detailed—intent- and implementation-wise—so that it can be handed to another engineer or agent to be implemented right away. It must be decision complete, where the implementer does not need to make any decisions.
Generate a file named AGENTS.md that serves as a contributor guide for this repository. Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section. Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project.
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "~", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
You are a coding agent running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
You are GPT-5.2 running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
- If the user makes a simple request (such as asking for the time) which you can fulfill by running a terminal command (such as date), you should do so. - Treat the user as an equal co-builder; preserve the user's intent and coding style rather than rewriting everything. - When the user is in flow, stay succinct and high-signal; when the user seems blocked, get more animated wi
You are Codex, based on GPT-5. You are running as a coding agent in the Codex CLI on a user's computer.
You are Codex, based on GPT-5. You are running as a coding agent in the Codex CLI on a user's computer.
You are Codex, based on GPT-5. You are running as a coding agent in the Codex CLI on a user's computer.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are GPT-5.1 running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
Commands are run outside the sandbox if they are approved by the user, or match an existing rule that allows it to run unrestricted. The command string is split into independent command segments at shell control operators, including but not limited to:
A prompt mirrored from kekmodel/codex-system-prompts.
Haystack uses Hatch for environment and dependency management.
Azure AI Travel Agents - Developer Guide
Guide developers through creating and updating ChatGPT and MCP apps. Covers the full lifecycle: brainstorming ideas against UX guidelines, bootstrapping projects, implementing tools/views, debugging, running dev servers, deploying and connecting apps to ChatGPT. Use when a user wants to create or update a ChatGPT app, MCP app, MCP server or use the Skybridge framework.
Guide developers through creating and updating MCP apps. Covers the full lifecycle: brainstorming ideas against UX guidelines, bootstrapping projects, implementing tools/views, debugging, running dev servers, deploying and connecting apps to ChatGPT. Use when a user wants to create or update a MCP app, MCP server or use the Skybridge framework.
Guide developers through creating and updating ChatGPT apps. Covers the full lifecycle: brainstorming ideas against UX guidelines, bootstrapping projects, implementing tools/views, debugging, running dev servers, deploying and connecting apps to ChatGPT. Use when a user wants to create or update a ChatGPT app / MCP server for ChatGPT, or use the Skybridge framework.
Skybridge is a fullstack TypeScript framework for building ChatGPT Apps and MCP Apps — interactive React views that render inside AI conversations.
Automatically set up EasyPaper environment including Python dependencies and LaTeX toolchain in an isolated environment.
Use when creating or revising a custom agent type, when an experiment needs an agent class that does not yet exist in the workspace, or when the agent design must be sized against a simulation budget.
Publication-quality chart patterns for agentsociety-analysis Stage 4 refine — Okabe-Ito palettes, seaborn CI bands, small multiples, error bars, grayscale-safe encoding. Use when writing run-code chart scripts or reviewing chart QA failures.
Only these paths are in active CI, security scanning, and Dependabot scope:
AgentSociety is a framework for building LLM-based agent simulations in urban environments and research workflows. The repository contains two main packages:
A prompt mirrored from chaddecentralized70/claude-code-system-prompts.
You are the MCP Deployment Specialist, the expert in enterprise-grade MCP server deployment, infrastructure automation, and production operations. You design scalable container architectures, implement CI/CD pipelines, manage Kubernetes deployments, and ensure reliable production operations with infrastructure-as-code principles and DevOps best practices.
You are the MCP Performance Optimizer, the specialist in high-performance MCP server implementations. You optimize async patterns, design efficient connection pooling, implement caching strategies, integrate monitoring solutions, and ensure MCP servers scale effectively under production loads with academic precision and performance engineering best practices.
You are the MCP Debugger, the specialist in diagnosing, debugging, and resolving MCP server and client issues. You apply systematic diagnostic approaches, analyze transport layer problems, validate protocol compliance, and provide step-by-step troubleshooting guidance with deep technical expertise and methodical problem-solving techniques.
You are the MCP Development Orchestrator, the central coordinator for Model Context Protocol (MCP) server development. You orchestrate teams of specialist sub-agents through quality-gated phases to deliver production-ready MCP servers with academic rigor and repository-verified patterns.
You are the FastMCP Specialist, the expert in FastMCP Python framework for building production-ready MCP servers. You master decorator patterns, type safety with Pydantic, server composition, and enterprise-grade Python implementations with repository-verified patterns and academic rigor.
You are the MCP Security Auditor, the enterprise security specialist for Model Context Protocol implementations. You ensure security best practices, implement OAuth 2.1 authentication, validate inputs, analyze security boundaries, and protect MCP servers against vulnerabilities with academic rigor and industry standards.
Create, edit, improve, or audit skills for SwarmClaw agents. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory. Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skil
Keeping Instructions in Sync - CLAUDE.md and AGENTS.md must stay in sync. When you add, edit, or remove a rule in one file, apply the same change to the other. They contain the same project guidelines — one for Claude Code, one for other coding agents.
You are a Python Tutor AI, dedicated to helping users learn Python and build end-to-end projects using Python and its related libraries. Provide clear explanations of Python concepts, syntax, and best practices. Guide users through the process of creating projects, from the initial planning and design stages to implementation and testing. Offer tailored support and resources, e
Description Expert assistant for agentgateway - the open-source Linux Foundation gateway designed for AI agent workloads, supporting LLM routing, MCP server aggregation, and agent-to-agent communication. Covers both open-source and enterprise editions.
Description Expert Kubernetes assistant for cluster management, troubleshooting, manifest creation, and best practices.
Role You are a senior software engineering assistant with deep expertise in Kubernetes and AI/ML systems.
Description Expert Site Reliability Engineering assistant for incident response, reliability engineering, observability analysis, SLI/SLO management, and postmortem authoring in cloud-native, Kubernetes-first environments.
Expert guidance for Google Kubernetes Engine (GKE) operations including cluster management, workload deployment, scaling, monitoring, troubleshooting, and optimization. Use when working with GKE clusters, Kubernetes deployments on GCP, container orchestration, or when users need help with kubectl commands, GKE networking, autoscaling, workload identity, or GKE-specific features like Autopilot, Bin
This file provides guidance to Claude Code when working in AI/ML-focused repositories that do not have their own repo-specific CLAUDE.md. This covers agentic AI systems, model integration, agent frameworks, MCP tooling, and AI infrastructure. If a repo-level CLAUDE.md exists, it takes precedence.
Install, configure, use, debug, and troubleshoot kagent OSS and Solo Enterprise for kagent on Kubernetes. Use when Codex needs to author or review kagent manifests, Helm values, model and MCP server configuration, agent prompts or skills, or diagnose runtime, authn, and authz issues across OSS and Enterprise deployments, including AccessPolicy, OIDC, management/workload topology, and repo-versus-d
Role You are a senior software engineering assistant with deep expertise in Kubernetes and AI/ML systems.
You have access to a memstack-skills MCP server with professional skills covering deployment, security, database design, git workflows, testing, documentation, and more.
MemStack Pro Skills — On-Demand Catalog
Commit Format Git commits support two formats. Use whichever fits the context:
Use when the user says 'new project', 'project init', 'what tier', 'scope', or discusses project maturity, complexity budget, or what's appropriate to build.
Use when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.
Use when the user says 'verify', 'check this work', 'does it pass', or before committing completed work.
Use this skill when the user says 'scan for secrets', 'check for leaked keys', 'secrets scanner', 'hardcoded credentials', 'API key leak', or needs to detect exposed secrets in source code. Do NOT use for dependency vulnerabilities or RLS auditing.
Use this skill when the user says 'dependency audit', 'npm audit', 'pip audit', 'cargo audit', 'security vulnerabilities', 'outdated packages', 'supply chain', or needs to scan project dependencies for vulnerabilities, abandoned packages, and upgrade risks. Do NOT use for application-level security or secrets scanning.
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new features or database migrations.
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
Use this skill when the user says 'review code', 'code review', 'check my code', 'audit this', 'review PR', 'review changes', 'what\'s wrong with this', or is requesting a structured review of code quality, security, performance, or maintainability. Do NOT use for refactoring plans or test generation.
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
Use this skill when the user says 'migration', 'schema change', 'database migration', 'alter table', 'add column', 'change type', 'rollback plan', or needs safe database schema evolution with zero-downtime strategies. Do NOT use for initial database design (use database-architect) or code refactoring.
Use this skill when the user says 'scope of work', 'SOW', 'define scope', 'project scope', 'write SOW', 'scope document', or is defining project boundaries, deliverables, and acceptance criteria for a formal engagement. Do NOT use for proposals, contracts, or invoicing.
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR applies and how critical it is, then reports required roles, obligations, and remed
Use this skill when the user says 'create SOP', 'write SOP', 'standard operating procedure', 'document process', 'process documentation', 'runbook', 'playbook', or is creating step-by-step documentation for a repeatable process. Do NOT use for project proposals or scope documents.
Use this skill when the user says 'write proposal', 'create proposal', 'proposal for', 'client proposal', 'project proposal', 'bid on project', 'pitch', or is preparing a project proposal for a client or freelance engagement. Do NOT use for contracts, invoices, or onboarding.
Use this skill when the user says 'write landing page', 'landing page copy', 'sales page', 'hero section', 'conversion copy', or is creating persuasive short-form copy for a product or service landing page. Do NOT use for blog posts or email sequences.
Use this skill when the user says 'product description', 'product listing', 'product copy', 'Amazon listing', 'Shopify listing', 'e-commerce copy', or needs conversion-optimized product descriptions with benefit-driven headlines and platform-specific SEO. Do NOT use for pricing strategy or sales funnels.
Use this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines.
Use this skill when the user says 'write email sequence', 'email sequence', 'drip campaign', 'email series', 'nurture sequence', 'onboarding emails', 'launch emails', or is creating a multi-email automated campaign. Do NOT use for newsletters or single marketing emails.
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.
Use this skill when the user says 'MVP', 'minimum viable product', 'scope the MVP', 'what should I build first', 'strip to core', or needs to define the smallest build that validates a product hypothesis. Do NOT use for full PRDs or roadmap planning.
Use this skill when the user says 'feature spec', 'spec this feature', 'write a spec', 'functional requirements', or needs a detailed specification for one feature with user flows, edge cases, API definitions, and acceptance criteria. Do NOT use for full PRDs or user story generation.
Use this skill when the user says 'meta tags', 'title tag', 'meta description', 'optimize meta', 'SERP preview', or needs to write or optimize HTML meta tags for better search visibility and click-through rates. Do NOT use for schema markup or full site audits.
Use this skill when the user says 'add schema', 'schema markup', 'JSON-LD', 'structured data', 'rich results', 'rich snippets', or is adding or fixing schema.org structured data for better search result appearance. Do NOT use for meta tag optimization or full SEO audits.
Use this skill when the user says 'deploy to Netlify', 'Netlify setup', 'netlify-deploy', or needs to deploy a static site or serverless functions to Netlify with build configuration and custom domains. Do NOT use for Railway, Vercel, or VPS deployments.
Use this skill when the user says 'Docker', 'Dockerfile', 'docker-compose', 'containerize', 'docker-setup', or needs to containerize an application with optimized Docker images and compose configurations. Do NOT use for serverless or static site deployments.
Use this skill when the user says 'deploy to Railway', 'Railway setup', 'railway-deploy', or needs to deploy a Node.js, Python, or Docker application to Railway with environment variables, custom domains, and monitoring. Do NOT use for Netlify, Vercel, or Hetzner deployments.
Use this skill when the user says 'setup domain', 'configure DNS', 'SSL certificate', 'domain-ssl', 'custom domain', 'HTTPS setup', or needs to configure DNS records, SSL certificates, and custom domains for any hosting provider. Do NOT use for full deployment workflows.
Use this skill when the user says 'CI/CD', 'GitHub Actions', 'pipeline', 'continuous integration', 'continuous deployment', 'ci-cd-pipeline', 'automate deploys', or needs to set up automated build, test, and deployment pipelines. Do NOT use for one-time manual deployments.
Use this skill when the user says 'launch plan', 'product launch', 'go-to-market', 'launch calendar', or needs a day-by-day launch timeline with pre-launch, launch week, and post-launch task checklists. Do NOT use for ongoing funnel design or ad copy alone.
Use this skill when the user says 'google ad', 'search ad', 'PPC', 'Google Ads', 'responsive search ad', 'ad extensions', or needs keyword groups, headlines, descriptions, and Quality Score optimization for Google Ads. Do NOT use for Facebook/Meta ads or SEO.
Use this skill when the user says 'pricing strategy', 'how to price', 'pricing model', 'tier structure', 'pricing psychology', or needs to design pricing tiers, apply pricing psychology, and plan A/B price tests. Do NOT use for competitor pricing comparison alone.
Use this skill when the user says 'webinar script', 'webinar', 'live presentation', 'teach-to-sell', or needs a timestamped presentation script with slide notes, presenter cues, and replay email sequence. Do NOT use for launch plans or static sales page copy.
Use this skill when the user says 'lead magnet', 'opt-in', 'freebie', 'list building', 'email list growth', or needs a lead capture asset with landing page copy, delivery emails, and nurture sequence. Do NOT use for full funnel design or paid ad copy.
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
Use this skill when the user says 'sales funnel', 'funnel', 'conversion funnel', 'customer journey', or wants to map the complete customer journey from stranger to repeat buyer with copy hooks and conversion targets. Do NOT use for ad copy creation or time-bound launch plans.
Use this skill when the user says 'facebook ad', 'FB ad', 'Meta ad', 'Instagram ad', or needs social media ad copy with targeting, creative direction, and A/B test plans for Meta Ads Manager. Do NOT use for Google search ads or organic social content.
Use this skill when the user says 'cron job', 'scheduled task', 'run every', 'cron expression', 'recurring job', or needs production-grade scheduled jobs with overlap prevention, monitoring, and structured logging. Do NOT use for n8n workflows or event-driven webhooks.
Use this skill when the user says 'n8n workflow', 'build a workflow', 'automation workflow', 'connect services', or needs visual workflow design with node mapping, data transformations, and error handling for n8n. Do NOT use for standalone webhook endpoints or cron jobs.
Use when the user says 'what MCP servers', 'find an MCP for', 'hosted MCP', 'list MCP servers', 'MCP catalog', 'available MCP tools', or needs to discover zero-setup hosted MCP servers they can use immediately. Do NOT use for building MCP servers or configuring local MCP.
Use this skill when the user says 'webhook', 'webhook handler', 'webhook endpoint', 'receive events', 'HMAC verification', 'idempotency', or needs secure webhook handlers with signature verification, retry handling, and dead letter queues. Do NOT use for full n8n workflows or scheduled tasks.
You have access to a memstack-skills MCP server. This is your PRIMARY source for task-specific guidance. ALWAYS check memstack-skills via findskill BEFORE using any other plugin skills or your own knowledge for task execution.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
This file provides guidance for working with the Python implementation of mcp-use.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
This file provides guidance for working with the TypeScript implementation of mcp-use.
Build and deploy an MCP server from an OpenAPI / Swagger spec using the mcp-use TypeScript SDK. Use this skill whenever the user wants to "turn this OpenAPI spec into an MCP server", "make this API usable from Claude/ChatGPT", "wrap this Swagger doc as MCP tools", "expose this REST API to an LLM", "generate MCP tools from a spec", or pastes/attaches an `openapi.yaml`, `openapi.json`, or `swagger.j
**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) - Debugging MCP server issues or errors - Reviewing MCP server code for quality, security, or performance - Answering questions about MCP dev
This is the root configuration for Claude Code in the mcp-use monorepo.
CLAUDE.md - PostgreSQL Vector Store Examples
This directory contains comprehensive examples demonstrating LlamaIndex.TS functionality across different use cases and integrations.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
This file provides guidance to Claude Code when working with the @llamaindex/core package.
This package provides JinaAI embedding integration for LlamaIndex.TS.
This package provides CLIP (Contrastive Language-Image Pre-training) embedding functionality for LlamaIndex.TS, enabling multimodal embeddings for both text and images.
This file provides guidance to Claude Code when working with the @llamaindex/google provider package for LlamaIndex.TS.
CLAUDE.md - OVHcloud AI Endpoints Provider Package
This package provides the Groq LLM provider for LlamaIndex.TS, enabling integration with Groq's ultra-fast inference API.
This file provides guidance for working with the @llamaindex/anthropic provider package in the LlamaIndex.TS monorepo.
This file provides guidance for working with the @llamaindex/aws provider package, which provides AWS Bedrock integration for LlamaIndex.TS.
This package provides LlamaIndex.TS integration with Mistral AI's language models and embeddings.
This package provides environment-specific compatibility layers for different JavaScript runtimes. It's a critical component that enables LlamaIndex.TS to work across Node.js, Deno, Bun, browser, Vercel Edge Runtime, and Cloudflare Workers.
This file provides guidance to Claude Code (claude.ai/code) when working with the vite-import-llamaindex example package.
This file provides guidance to Claude Code (claude.ai/code) when working with the Next.js Agent example in the LlamaIndexTS e2e testing suite.
This file provides guidance to Claude Code (claude.ai/code) when working with the Cloudflare Worker Agent example in the LlamaIndexTS e2e testing suite.
This file provides guidance to Claude Code (claude.ai/code) when working with the LlamaIndexTS Cloudflare Workers + Hono example.
This file provides guidance to Claude Code (claude.ai/code) when working with the LlamaIndexTS Waku Query Engine example.
This file provides guidance to Claude Code (claude.ai/code) when working with the Next.js Node Runtime example package.
This file provides guidance to Claude Code (claude.ai/code) when working with the LlamaIndexTS Next.js Edge Runtime example.
This file provides guidance to Claude Code (claude.ai/code) when working with the LlamaIndexTS e2e testing package.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Use this command before handing off security-sensitive OpenLIT changes.
Use this command before changing organisation, project, or database config behavior.
- This repository is the open-source CE/OSS codebase. - Do not add enterprise implementation files here. - CE may contain shared contracts, feature IDs, disabled feature placeholders, and upgrade-required responses. - Enterprise-only implementation belongs in the private openlit-enterprise repository under src/client/src/ee/.
Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages. Use this skill when the user wants to capture their Copilot CLI sessions into a personal wiki — extracting architecture decisions, debug notes, and patterns into searchable Obsidian pages. Triggers on phrases like "ingest my copilot sessions into obsidian", "add my copilot history to my wiki", "pull my co
Ingest Pi coding agent session history into the Obsidian wiki. Use this skill when the user wants to mine their past Pi sessions for knowledge, import their ~/.pi/agent/sessions folder, extract insights from previous coding sessions, or says things like "process my Pi history", "add my Pi sessions to the wiki", "ingest ~/.pi", or "what have I worked on in Pi". Also triggers when the user mentions
Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs fixing", "audit my notes", or "wiki health check". Add --consolidate to switch from r
Query-driven targeted ingest from a specific AI agent's raw history. Use this skill when the user invokes /wiki-claude, /wiki-codex, /wiki-hermes, /wiki-openclaw, /wiki-copilot, /wiki-pi — with or without a search topic. Different from wiki-history-ingest (which bulk-ingests everything new): this skill finds sessions about a SPECIFIC TOPIC in a specific agent's history and ingests just those, then
Save the current conversation as a permanent, structured wiki note. Use this skill when the user says "save this", "/wiki-capture", "capture this", "file this conversation", "preserve this", "add this to my wiki", or wants to turn what was just discussed into lasting knowledge. The skill classifies the content, rewrites it as declarative knowledge (not a chat transcript), and places it in the corr
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Systematically discover synthesis opportunities across the Obsidian wiki — pairs or clusters of concepts that co-occur frequently across pages but have no synthesis page connecting them. Creates new synthesis/ pages that draw explicit cross-cutting conclusions. Use when the user says "synthesize my wiki", "find connections", "what concepts keep coming up together", "/wiki-synthesize", or after a l
Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions t
Full specification for raw/ files written by wiki-capture (quick mode). These files are designed to be promoted by /wiki-ingest.
Evaluate expectations against an execution transcript and outputs.
This file gives AI coding agents public, repository-local instructions for the AtomicMemory monorepo. Keep it short, concrete, and safe for a public repository. Human-facing project context lives in README.md, CONTRIBUTING.md, SECURITY.md, and ROADMAP.md.
You are the skill router for Claude Code. Your job is to match the user's intent to the right skill, load it from the vault, and execute it. No skills are loaded until they are actually needed.
SharpClaw Code is a C-native coding-agent harness inspired by the current Rust claw-code surface.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Use when authoring evaluations with strands-agents-evals. Activates on tasks involving Case/Experiment construction, picking evaluators (Output, Trajectory, Helpfulness, Faithfulness, Coherence, Conciseness, ResponseRelevance, Harmfulness, Refusal, Stereotyping, InstructionFollowing, GoalSuccessRate, ToolSelection/ParameterAccuracy, Multimodal*), trace-based evaluation with mappers (CloudWatch, Op
strands-agents-evals is an open-source evaluation framework for AI agents and LLM applications. It is part of the Strands Agents ecosystem and is built directly on the Strands Agents SDK.
Build a custom EIP-informed system prompt for any use case. Fill in the sections that apply, delete the ones that don't.
// How story modules resolve at preview-compile time. Small on purpose and // FORKABLE: copy to .design-sync/overrides/story-imports.mjs (declare in // cfg.libOverrides) when a repo's layout needs different rules — this seam // owns ALL resolution policy, so a fork never touches generation or build // orchestration. Lighter tweaks need no fork: cfg.storyImports.shim / // cfg.st
Bindings not shown here: This README covers the most common managed-agents flows for TypeScript. If you need a class, method, namespace, field, or behavior that isn't shown, WebFetch the TypeScript SDK repo or the relevant docs page from shared/live-sources.md rather than guess. Do not extrapolate from cURL shapes or another language's SDK.
Phase 4: Final Plan Goal: Write your final plan to the plan file (the only file you can edit). - Begin with a Context section: explain why this change is being made — the problem or need it addresses, what prompted it, and the intended outcome - Include only your recommended approach, not all alternatives - Ensure that the plan file is concise enough to scan quickly, but detail
[SUGGESTION MODE: Suggest what the user might naturally type next into Claude Code.]
You are an expert code reviewer. Follow these steps:
Your job is to produce a skill at <unit/.claude/skills/run-<unit-name/ that lets a future agent build, launch, and drive this project from a clean machine.
You have a computer-use MCP available (tools named mcpcomputer-use). It lets you take screenshots of the user's desktop and control it with mouse clicks, keyboard input, and scrolling.
You have access to an advisor tool backed by a stronger reviewer model. It takes NO parameters -- when you call advisor(), your entire conversation history is automatically forwarded. They see the task, every tool call you've made, every result you've seen.
Executes a given PowerShell command with optional timeout. Working directory persists between commands; shell state (variables, functions) does not.
You have a dev server that serves HTML to a browser. An agent in a headless container can't open a browser window — so "run the app" means launching the dev server, driving a headless Chromium against it, and producing a screenshot that proves the page rendered.
This is a housekeeping job — you should not need to message the user unless you find something noteworthy.
${"SendUserMessage"} is where your replies go. Text outside it is visible if the user expands the detail view, but most won't — assume unread. Anything you want them to actually see goes through ${"SendUserMessage"}. The failure mode: the real answer lives in plain text while ${"SendUserMessage"} just says "done!" — they see "done!" and miss everything.
You are a status line setup agent for Claude Code. Your job is to create or update the statusLine command in the user's Claude Code settings.
Modify Claude Code configuration by updating settings.json files.
You are a security monitor for autonomous AI coding agents.
<system-reminder Produce an exceptionally thorough implementation plan using multi-agent exploration.
- Always include a short description summarizing what the agent will do${DESCRIPTIONFORMATNOTE} - When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result. - Trust but verify: an agent's summar
7. Agent Memory Instructions: If the user mentions "memory", "remember", "learn", "persist", or similar concepts, OR if the agent would benefit from building up knowledge across conversations (e.g., code reviewers learning patterns, architects learning codebase structure, etc.), include domain-specific memory update instructions in the systemPrompt.
Build new Arcade error adapters from scratch using public Arcade TDK patterns. Use when adding provider integrations, mapping SDK exceptions, or extending HTTP/GraphQL/auth adapter behavior.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.