jaktestowac/awesome-copilot-for-testers / plugins/creating-instructions/skills/creating-instructions
creating-instructions
VerifiedCreates GitHub Copilot instruction files for VS Code, including repository guidance and scoped `.instructions.md` rules. Use when encoding project conventions, choosing `applyTo` patterns, or shipping install-ready instruction examples with rationale and guardrails.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.8 KB |
| resources/copilot-instructions.example.md | markdown | 2.6 KB |
| resources/copilot-instructions.template.md | markdown | 1.7 KB |
| resources/custom-instructions.example.instructions.md | markdown | 1.5 KB |
| resources/custom-instructions.template.instructions.md | markdown | 849 B |
| resources/instructions-quality-checklist.md | markdown | 1.7 KB |
resources/custom-instructions.template.instructions.md
View on GitHub---
description: 'Instructions for <scope>. Use when working on <files-or-folder>.'
applyTo: '<glob-pattern>'
title: '<Human friendly title>'
name: '<kebab-case-name>'
---
## Scope
- Applies to: `<file pattern or folder>`
- Goal: `<what behavior this instruction should reinforce>`
## Rules
- **Prefer** `<preferred approach>` because <reason>.
- **Avoid** `<anti-pattern>` because <consequence>.
- Keep `<artifact type>` in `<location>`.
- Name `<artifact>` as `<convention>`.
### Preferred pattern
```ts
// Replace with a project-specific example that demonstrates the preferred pattern.
```
### Avoid
```ts
// Replace with a project-specific example that demonstrates the anti-pattern.
```
## Notes
- Scripts Copilot should prefer: `<npm run ...>`
- Files to inspect first: `<path>`, `<path>`
- Remove this section if it adds no value.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |