tools · ai-driven-dev — Claude Code skill: what it does, how to install
Defines AI assistant and IDE profiles, build contracts, and capability interfaces under src/contexts/tools/ in the framework.
MIT ★ 571 updated 2026-10-29
npx skills add ai-driven-dev/framework --skill tools -a claude-codeWhat tools does
The skill configures target platforms inside src/contexts/tools/. Each supported assistant or editor lives as an AiTool<C> or IdeToolConfig object in profiles/<tool>/profile.ts, where C defines the exact intersection of Has* capability interfaces. Profiles supply target metadata, rewriteContent transformation rules, and build contracts for aidd translate.
Boundary rules are strictly enforced: outside contexts cannot import modules until added to PUBLIC_MODULES in context-boundary.arch.test.ts. Barrel index.ts files are prohibited across the codebase. Moving tool-specific logic outside the profile directory will fail the architecture ratchet tests.
This skill does not execute the canonical-to-native translation pipeline, which belongs to translate. Manifest distribution and install orchestration are handled by separate contexts.
What it helps with
- Add an AI tool or IDE profile under
src/contexts/tools/ - Configure a
ToolBuildContractforaidd translate - Define a new
Has*capability class indomain/contracts.ts - Implement custom
rewriteContentlogic for a target platform
Example prompts for the agent
- Add a new IDE profile under
src/contexts/tools/and define its build contract - Create a new capability class in
domain/capabilities/with strict readonly parameters - Update
rewriteContentfor the target tool profile inprofile.ts
How to install tools
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill tools -a claude-code2Manually: put the files in place
~/.claude/skills/tools/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/tools/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill tools -a codex2Manually: put the files in place
.agents/skills/tools/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill tools -a cursor2Manually: put the files in place
.cursor/skills/tools/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework cli/.claude/skills/tools2Manually: put the files in place
.github/skills/tools/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill tools -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path cli/.claude/skills/toolsManually: put the files in place
.devin/skills/tools/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill tools -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about tools
How to install tools in Claude Code?
Run npx skills add ai-driven-dev/framework --skill tools -a claude-code. The skill file is placed in ~/.claude/skills/tools/SKILL.md.
What does the tools skill do?
It configures how target AI tools and IDEs are modeled inside the framework repository. It manages tool profiles, capability classes, and build contracts.
When should you avoid using the tools skill?
Do not use it to run translation pipelines, distribute plugins, or orchestrate installations. Those concerns are delegated to translate, distribution, and framework.
Source text
SKILL.md · MIT
--- name: tools description: > Defines or modifies what the project targets, under src/contexts/tools/ — an AI/IDE tool profile, its build contract, the content-translation capability classes it composes (agents/skills/commands/rules/hooks), and its own native-plugin adapter. Use when adding a new AI or IDE tool, changing a tool's Has* capability intersection, adding or modifying a capability class, or declaring a tool's `aidd translate` build contract. Do NOT use for the canonical-to-native translation pipeline itself — use `translate`. Do NOT use for where plugin content comes from — use `distribution`. Do NOT use for manifest or install orchestration — use `framework`. --- # Tools `tools` is what the project targets and how each target is configured. Every AI assistant and IDE the CLI supports is one `AiTool<C>` or `IdeToolConfig` object in `contexts/tools/domain/profiles/<tool>/profile.ts`, where `C` is the intersection of `Has*` capability interfaces the tool actually supports. `translate` depends on `tools` (never the reverse) to call the tool's own `rewriteContent` and to read its build contract — a tool profile is data and behavior the rest of the CLI is handed, not a place that reaches out to fetch or install anything itself. ## What goes in | Concept | Location | |---|---| | A tool's identity, capabilities, content-rewrite | `domain/profiles/<tool>/profile.ts` | | A tool's `aidd translate` build behavior | `domain/profiles/<tool>/build.ts` (only if the tool is a build target) | | A string transform used by exactly one profile | that profile's own directory | | A string transform shared by ≥2 profiles | `domain/formats/` | | A content-translation capability class (agents/skills/commands/rules/hooks) | `domain/capabilities/` + a `Has*` entry in `contracts.ts` | | Catalog/manifest shaping shared by ≥2 tools' build contracts | `domain/marketplace-catalog.ts` | | A port only `tools` needs | `domain/ports/` | | A tool's own plugin-CLI driver | `infrastructure/` | ## How - `AiTool<C>` fields: read `domain/contracts.ts`. A list copied here aged at every field. - `Has*` interfaces live in `contracts.ts`, always `readonly`, never optional — a tool either includes `Has<Name>` in its `C` intersection or does not have the field at all. Guard presence with `"name" in tool.capabilities`, never `instanceof`. - `rewriteContent(content)` is one way, per tool, with no reverse and no shared base helper. See `references/content-rewrite.md`. - A capability class ends in `Capability`, takes one params object, all fields `readonly`, throws `CapabilityConfigError` (from `kernel/errors.ts`) on an invalid combination, carries no application/infrastructure imports. See `references/capability-conventions.md`. - `PluginsCapability` has three modes (`native`, `flat`, `unsupported`) and a `translationMode` (`marketplace` | `flat` | `null`) — see `references/plugins-capability.md`. - Build behavior is ONE artifact-symmetric `ToolBuildContract` per tool, read by the two mode-generic orchestrators (`MarketplaceBuildStrategy`, `FlatBuildStrategy`) in `translate` — never a per-tool strategy class, never a per-tool or per-artifact-kind branch in an orchestrator. See `references/build-contract.md`. - `registerTool(config)` is called once, at the bottom of `profile.ts`, never from a use-case. - Follow the port/adapter rule in `.claude/rules/00-architecture/` for the shape of a port and its adapter, and the shared-module rule there before promoting a helper out of a single profile. ## Public surface Nothing outside `contexts/tools/` may import a module this context has not declared public — `tests/architecture/context-boundary.arch.test.ts` holds the list (`PUBLIC_MODULES.tools`). A new module is invisible to `translate` and `framework` until it is added there; there is no `index.ts` and there never will be (barrels are forbidden by the export rule in `.claude/rules/01-standards/`). ## How it's tested - `tests/contexts/tools/` mirrors `src/contexts/tools/` — one profile's `profile.ts`/`build.ts` gets a unit test asserting the `AiTool<C>` type is satisfied and each rewrite rule holds. - `tests/architecture/tool-addition-cost.arch.test.ts` ratchets how many files outside a new tool's own directory must change to add it — keep new tool-specific logic inside the profile. - See the `test` skill for tier conventions; capability/format round-trip tests are unit-tier.
© ai-driven-dev · MIT · ai-driven-dev/framework
Similar skills
All skills for Agent setup: memory, context, orchestration →tools by other authors comes first.