tools
/tools
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 man
- Author
- ai-driven-dev ↗
- Repository
- framework ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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 man
Original author 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 man
How it works
- What goes in
- How
- Public surface
- How it's tested
SKILL.md preview
--- 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.
Files in this package (5)
- SKILL.md 4 KB
- references/build-contract.md 5 KB
- references/capability-conventions.md 2 KB
- references/content-rewrite.md 3 KB
- references/plugins-capability.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ai-driven-dev/framework | 90 | MIT |
| skillberry-ai/cap-evolve | 100 | Apache-2.0 |
| soneta/soneta-erp-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version fdd2a006742f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90translate
Builds the canonical-source-to-target-native translation pipeline under src/contexts/translate/ — target-aware content transforms, the plugin content translator, and the build strategies behind `aidd translate` and `aidd sync`. Use when adding a target-aware transform, changing… - 90distribution
Owns where plugin and marketplace content comes from and how it is fetched, under src/contexts/distribution/ — marketplace registration, catalog parsing, and the ports/adapters that reach git and HTTP. Use when adding a new marketplace source kind, a catalog parser for a foreign… - 100cli-commands
Use when adding or modifying CLI command (`but` commands) under `crates/but/src`. - 100tooling-engineer
Use this agent when you need to build or enhance developer tools including CLIs, code generators, build tools, and IDE extensions. - 90migrasutra-ide-bridge
Use when migration work needs the cross-ide integration specialist: package portable skills for supported IDEs and independently test each host adapter and permissions. - 100atomr-agents-tools
Use when authoring or modifying a `Tool` / `RichTool`, designing a tool's `ToolDescriptor` schema, returning a `ToolReturn::Command`, wiring tools into an `Agent`'s `ToolStrategy`, or using built-in tools (`HandoffTool`, `WriteMemoryTool`, `RecallMemoryTool`). Triggers on `impl…