New Tool Instruction File
---
name: New tool instruction file
description: Suggest support for another AI tool or coding agent
title: "Add instruction file for <tool>"
labels: [documentation, enhancement]
---
## Tool
Name of the AI tool or coding agent:
## Why it should be supported
Explain who would use it and what token/context problem this instruction file should solve.
## Expected file location
Example: `.github/copilot-instructions.md`, `.cursor/rules/token-efficiency.mdc`, or another tool-specific path.
## Guidance to include
- Context hygiene rules:
- Model/tool routing notes:
- Log/output compression notes:
- Safety or accuracy caveats:
## Validation
- [ ] The instruction file is short and tool-specific.
- [ ] It links back to the canonical guidance in `guidelines/` where useful.
- [ ] It avoids fixed percentage token-saving claims unless measured.when to use it
Community prompt sourced from the open-source GitHub repo ravinperera/ai-token-efficiency-playbook (no explicit license). A "New Tool Instruction File" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
ravinperera/ai-token-efficiency-playbook · no explicit license
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar