to-questionnaire
aws/graph-explorer/.agents/skills/to-questionnaire/SKILL.md
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
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.
aws/graph-explorer/.agents/skills/to-questionnaire/SKILL.md
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
aws/graph-explorer/.agents/skills/to-spec/SKILL.md
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
aws/graph-explorer/.agents/skills/to-tickets/SKILL.md
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
aws/graph-explorer/.agents/skills/triage/SKILL.md
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
aws/graph-explorer/.agents/skills/wait-what/SKILL.md
Stop. That last message did not land — re-pitch it.
aws/graph-explorer/.agents/skills/wayfinder/SKILL.md
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
aws/graph-explorer/.agents/skills/writing-for-agents/SKILL.md
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
aws/graph-explorer/.agents/skills/writing-great-skills/SKILL.md
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
aws/agentcore-cli/CLAUDE.md
This project keeps all agent instructions in AGENTS.md files. Always follow the rules in ./AGENTS.md, and when working in subdirectories, also check for a closer AGENTS.md in that directory tree.
aws/agentcore-cli/src/assets/AGENTS.md
This directory stores: The rendering logic is rooted in the AgentEnvSpec and must ALWAYS respect the configuration in the spec. For Container builds, BaseRenderer.render() automatically copies the container/<language>/ templates (Dockerfile, .dockerignore) into the agent directory when buildType === 'Container'.
aws/agentcore-cli/src/cli/commands/AGENTS.md
This file defines context around specific commands surfaced by the CLI and related functionalities Each command directory follows a standardized structure: The command.tsx file must be boring Commander registration only: If removing a command file would remove behavior, the design is wrong. Some commands have additional files for their specific needs:
aws/agentcore-cli/src/cli/templates/AGENTS.md
This directory contains the rendering logic for template processing. Template assets live in the assets/ directory at the repository root. The rendering logic is rooted in the AgentEnvSpec and must ALWAYS respect the configuration in the Spec. Tags defined in agentcore.json flow through to deployed CloudFormation resources. 1. createRenderer() selects a renderer based on framework/language 2. BaseRenderer.render() copies and renders the framework base template 3. If hasMemory, capability templates are layered on top 4. If buildType === 'Container', the container…
aws/agentcore-cli/src/cli/tui/AGENTS.md
The TUI is defined using the ink npm package which converts React definitions to terminal output. The TUI layer defines a full immersive app that takes over the running shell process. To accomidate users running arbitrary commands while using the TUI, the ! input serves as an escape. At a high level, the TUI should be thought of more as a unified app than a CLI. Nevertheless, business logic, async work, and process orchestration must live outside the UI and…
aws/agentcore-cli/src/schema/AGENTS.md
The schema module contains the high level schemas which serve as abstractions enabling a streamlined L3 implementation to model AgentCore resources. This module only houses schemas and zod validation logic. Schemas are modeled separately with types and interfaces for readability and clean imports. Zod validators take a dependency on the top level types and serve only validation. Schemas: The core interface for both CLI and the input props to the L3 CDK constructs. These schemas allow high-level definitions for agent…
aws/agentcore-cli/src/schema/llm-compacted/AGENTS.md
This directory contains manually maintained TypeScript type definitions optimized for LLM consumption. When Zod schemas in schemas/ are updated, manually update the corresponding file here: Every enum (union type) and regex pattern MUST be exactly correct. On every update: Incorrect enums or regex will cause agents to generate invalid JSON that fails validation.
aws/Trusted-Advisor-Tools/AWSQuotaIncreaseSupport/cdk/layers/skill_assets/skill_files/skills/aws-quota-increase-support/SKILL.md
Proactively manage AWS service quota increases for the customer's account. Monitor quota utilization via Service Quotas, request increases, track pending requests, and verify applied changes. This skill enables the agent to act as a persistent butler — continuously monitoring limits, pre-emptively requesting increases before quotas become blocking, and shepherding requests through to completion.
aws/smithy-go/AGENTS.md
smithy-go is the Go code generator and runtime for Smithy. It has two major components: 1. Codegen (codegen/) — A Smithy build plugin written in Java that generates Go client/server/shape code from Smithy models. 2. Runtime (./, top-level Go module) — The Go packages that generated code depends on at runtime. The primary downstream consumer is aws-sdk-go-v2. The codegen artifact version is published to Maven Central and bumped on each release. For local development against unreleased codegen changes, use publishToMavenLocal…
aws/aws-ofi-nccl/AGENTS.md
AWS OFI NCCL is a plugin that enables NVIDIA NCCL, AMD RCCL, and AWS Neuron applications to use libfabric as a network provider. It maps NCCL's connection-oriented transport APIs to libfabric's connection-less reliable interface (FIEPRDM). The project uses GNU autotools (autoconf, automake, libtool). If a compilecommands.json file does not exist, you should run make clean ; bear -- make in order to generate a compilecommands.json to build a database for clangd. Unit tests are in tests/unit/. They run without special…
aws/amazon-chime-sdk-ios/AmazonChimeSDK/AmazonChimeSDKTests/AGENTS.md
Tests use handwritten spies and the verification helpers in common/CommonTestCase.swift. Do not add Cuckoo, generated mocks, or method-specific verifier proxies without explicit approval. Avoid reintroducing equivalent boilerplate: Run the affected test class first, then run the complete suite before submitting broad test refactors:
aws/aws-sdk-net/.agents/skills/aws-sdk-net-devconfig/SKILL.md
Use when creating, validating, or reasoning about DevConfig files for AWS SDK for .NET changes, including deciding whether Core or Services entries are required, choosing patch vs minor bumps, and writing changelog messages.
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.