generate-tool-config
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: generate-tool-config
description: Generate tool-specific configuration files (Cursor rules, Copilot instructions, Windsurf rules)…
category: documentation
runtime: no special runtime
---
# generate-tool-config output preview
## PART A: Task fit
- Use case: 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. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Target: $ARGUMENTS / For "cursor" / For "copilot"” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Target: $ARGUMENTS / For "cursor" / For "copilot"” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Target: $ARGUMENTS / For "cursor" / For "copilot"”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: generate-tool-config
description: Generate tool-specific configuration files (Cursor rules, Copilot instructions, Windsurf rules)…
category: documentation
source: tomevault-io/skills-registry
---
# generate-tool-config
## When to use
- Generate tool-specific configuration files (Cursor rules, Copilot instructions, Windsurf rules) from the .context/ doc…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Target: $ARGUMENTS / For "cursor" / For "copilot"” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "generate-tool-config" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Target: $ARGUMENTS / For "cursor" / For "copilot"
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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
Source: andrefigueira/.context — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review