new-adapter
Skill37 starsChanged 9 months agoUnlicenseView on GitHub
Add support for a new AI tool with adapters, CLI, completion, and tests.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ingsergiovt/claude-code-hexagonal-kittheir own version, first seen Nov 1, 2026
- anthril/vibe-guardtheir own version, first seen Apr 4, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- anthril/vibe-guard★ 2same name
- ingsergiovt/claude-code-hexagonal-kit★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/knowledge-base/RULE.mdCursor rule
- .cursor/rules/project/RULE.mdCursor rule
- summarize-sessionSkill
- sync-readmeSkill
- update-docsSkill
- update-knowledge-baseSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Before starting, gather this information:
- Very specific: line 17
Default source directory (e.g., .windsurf/rules/)
- Distinctive: line 44
Import the new adapter
- Very specific: line 50
Add tool section to ProjectConfig interface
- Very specific: line 51
Add tool to SourceDirConfig interface if needed
- Distinctive: line 56
Add tool subcommand group
- Distinctive: line 62
Add tool to completion types
- Very specific: line 66
Update bash/zsh/fish completion scripts
- Distinctive: line 72
Test add/remove operations
- Distinctive: line 73
Test config path resolution
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
New Adapter
Instructions
Complete workflow for adding support for a new AI tool to AIS.
Prerequisites
Before starting, gather this information:
- Tool name (e.g., "windsurf", "mcp")
- Rule/config types supported (e.g., rules, commands, skills)
- Default source directory (e.g.,
.windsurf/rules/) - Target directory (usually same as source)
- File mode:
fileordirectory
Steps
1. Create Adapter File
Create src/adapters/<tool>-<type>.ts:
import { createBaseAdapter } from './base.js';
export const myToolAdapter = createBaseAdapter({
name: '<tool>-<type>',
tool: '<tool>',
subtype: '<type>',
configPath: ['<tool>', '<type>'],
defaultSourceDir: '.<tool>/<type>',
targetDir: '.<tool>/<type>',
mode: 'directory', // or 'file'
});2. Register Adapter
In src/adapters/index.ts:
- Import the new adapter
- Register in
DefaultAdapterRegistryconstructor
3. Update Project Config
In src/project-config.ts:
- Add tool section to
ProjectConfiginterface - Add tool to
SourceDirConfiginterface if needed
4. Wire CLI Commands
In src/cli/register.ts:
- Add tool subcommand group
- Register add/remove/install/import commands
5. Update Completion
In src/completion.ts:
- Add tool to completion types
- Add subtype completions
In src/completion/scripts.ts:
- Update bash/zsh/fish completion scripts
6. Add Tests
Create src/__tests__/<tool>-<type>.test.ts:
- Test adapter properties
- Test add/remove operations
- Test config path resolution
7. Update Documentation
- README.md: Add to supported sync types table
- README_ZH.md: Sync changes (use
/sync-readme) - CLAUDE.md: Update if architectural changes
8. Verify
# Build
npm run build
# Run tests
npm test
# Test manually
node dist/index.js <tool> <type> add <name>
node dist/index.js <tool> <type> remove <name>Checklist
- Adapter file created
- Adapter registered
- ProjectConfig updated
- CLI commands wired
- Completion updated
- Tests written and passing
- README.md updated
- README_ZH.md synced
- Manual testing complete
Examples
Request: Add support for a new AI tool with rules and skills Result: Complete adapter implementation with tests passing
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

