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/copilot-instructions.template.md
View on GitHub# Copilot Instructions Template
Use this template for repository-wide GitHub Copilot guidance.
Only keep information that should matter for most tasks in the repository.
## Repository at a glance
- **Purpose**: <what this repository exists to do>
- **Primary stack**: <languages, runtimes, frameworks, key tools>
- **Top-level folders**:
- `<folder>/` - <responsibility>
- `<folder>/` - <responsibility>
## Commands Copilot should prefer
- `<script or task>` - <when to use it>
- `<script or task>` - <when to use it>
- `<script or task>` - <verification step>
## Architecture rules
- Keep `<layer>` separate from `<layer>`.
- Add new `<artifact>` files under `<path>`.
- Reuse existing patterns from `<path>` before inventing a new abstraction.
## Implementation rules
- Prefer `<preferred pattern>` over `<avoided pattern>` because <reason>.
- Keep public APIs <style or stability rule>.
- When editing tests, follow `<test strategy>`.
## Data, config, and secrets
- Read configuration from `<config location>`.
- Never hardcode secrets; use `<approved mechanism>`.
- When environment variables are required, document them in `<path>`.
## Testing and quality gates
- Run `<command>` after changing `<scope>`.
- Add or update tests in `<path>` when behavior changes.
- Prefer `<assertion strategy>` over `<anti-pattern>`.
## Change hygiene
- Keep diffs small and focused.
- Do not reformat unrelated files.
- Update docs when public behavior, setup, or contributor workflows change.
## Notes for future editors
- Remove sections that are not useful.
- Replace placeholders with repository facts, not general advice.
- Split out scoped rules into `*.instructions.md` files when they stop being universally relevant.
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 |