generate-tool-config
Skill253 starsChanged 11 months agoMITView on GitHub
Generate tool-specific configuration files (Cursor rules, Copilot instructions, Windsurf rules) from the .context/ documentation. Use when setting up a project for a specific AI coding tool.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-adrSkill
- new-domainSkill
- validate-contextSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Very specific: line 13
Create .cursor/rules/ directory with .mdc files:
- Very specific: line 16
Use alwaysApply: true only for general.mdc
- Distinctive: line 22
Keep under 50 lines (Copilot works best with concise instructions)
- Distinctive: line 27
Must stay under 6000 characters
- Very specific: line 35
Read .context/ai-rules.md and .context/architecture/patterns.md first
- Very specific: line 36
Keep generated files minimal.
- Distinctive: line 37
Follow each tool's format requirements exactly
- Distinctive: line 38
Test that file paths are correct relative to project root
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Generate AI tool configuration files from the existing .context/ documentation.
Target: $ARGUMENTS
For "cursor"
Create .cursor/rules/ directory with .mdc files:
general.mdc- Always-apply rules from@.context/ai-rules.md- One
.mdcper domain with appropriate glob patterns - Use
alwaysApply: trueonly forgeneral.mdc - Reference
.context/files with@syntax
For "copilot"
Create .github/copilot-instructions.md:
- Extract key rules from
.context/ai-rules.md - Keep under 50 lines (Copilot works best with concise instructions)
- Reference
.context/file paths for the agent to read
For "windsurf"
Create .windsurfrules:
- Must stay under 6000 characters
- Prioritize rules from
.context/ai-rules.mdand.context/architecture/patterns.md - Include file references for domain-specific context
For "all"
Generate all three above.
Rules
- Read
.context/ai-rules.mdand.context/architecture/patterns.mdfirst - Keep generated files minimal. Don't duplicate content, point to
.context/files - Follow each tool's format requirements exactly
- Test that file paths are correct relative to project root
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.

