| name | adapt |
| description | Analyzes a project and fills in AGENTS.md. Use after installing dot-agents or when project commands and conventions change. Triggers on: adapt, setup AGENTS, customize AGENTS. |
Adapt Skill
Analyze the current project and fill in AGENTS.md with project-specific information (tech stack, commands, conventions).
When to Use
Run this skill after installing dot-agents into a new project to customize the configuration.
Workflow
-
Analyze project structure
- Scan for configuration files (package.json, Cargo.toml, go.mod, pyproject.toml, etc.)
- Identify frameworks, libraries, and tools in use
- Find existing scripts/commands in config files
-
Detect conventions
- Look at code style (naming, formatting)
- Check for existing linter/formatter configs
- Identify testing patterns
-
Update AGENTS.md
- Fill in project name/overview
- List detected tech stack
- Extract commands from package.json scripts, Cargo.toml, Makefile, etc.
- Note any project-specific conventions observed
- Keep the
.agents/work/ and handoff-prompt workflow guidance intact
Example Output
After running, AGENTS.md should have these sections filled in:
## Overview
my-awesome-app - A Next.js web application with PostgreSQL backend
## Tech Stack
- Language: TypeScript
- Framework: Next.js 14
- Database: PostgreSQL with Prisma
- Testing: Jest, Playwright
## Commands
```bash
# Install
pnpm install
# Development
pnpm dev
# Build
pnpm build
# Test
pnpm test
pnpm test:e2e
# Lint/Format
pnpm lint
pnpm format
```
## Conventions
- Use kebab-case for file names
- Components in src/components/
- API routes in src/app/api/
## Agent Work
- Durable work lives in `.agents/work/<category>/<slug>/`
- Use `.agents/research/` only for reusable findings
- Ask for a handoff prompt before starting a fresh implementation thread
Checklist
