Repository Specific.instructions
---
applyTo: '**/*'
description: 'Repository-specific instructions for the AIM template repository'
---
# Repository-Specific Instructions
This is the source repository for AIM (AI Agent Instruction Modules).
## Repository Context
- **Purpose**: Maintain modular AI agent instruction templates
- **Language**: PowerShell (tests), Markdown (instructions)
- **Distribution**: Git-based cloning via copy-paste prompts
## Development Guidelines
### Modifying Instruction Files
When editing files in `instruction-templates/`:
1. Maintain YAML frontmatter with required fields:
- `applyTo`: Glob patterns for file matching (e.g., `'**/*'` or `'**/*.ps1'`)
- `description`: Brief description of the instruction file
2. Keep instructions generic and universal:
- Avoid organization-specific references
- Use placeholder examples (`<owner>`, `<repo>`)
- Focus on best practices applicable to any project
3. Use the `.instructions.md` file extension for all instruction files
4. Follow Markdown conventions in `markdown.instructions.md`
### Adding New Instruction Files
1. Create the file in `instruction-templates/` with `.instructions.md` extension
2. Add YAML frontmatter with `applyTo` and `description`
3. Update `AGENTS.template.md` to list the new file
4. Update `AGENTS.md` to match the template
5. Run tests to validate
### Testing Changeswhen to use it
Community prompt sourced from the open-source GitHub repo tablackburn/ai-agent-instruction-modules (MIT). A "Repository Specific.instructions" 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
codingcommunitydeveloper
source
tablackburn/ai-agent-instruction-modules · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions