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.example.md
View on GitHub# Copilot Instructions
This repository contains end-to-end, API, and support tooling for a product quality platform.
Use the rules below as the default operating agreement for GitHub Copilot changes in this workspace.
## Repository at a glance
- **Purpose**: maintain reliable regression coverage for the checkout, billing, and notification domains
- **Primary stack**: Node.js 22, TypeScript, Playwright, Vitest, REST APIs, GitHub Actions
- **Top-level folders**:
- `tests/e2e/` - browser-based user journeys and smoke coverage
- `tests/api/` - API regression suites and contract-focused checks
- `tests/fixtures/` - reusable fixtures, test data builders, and setup helpers
- `src/support/` - shared clients, utilities, schemas, and domain helpers
- `.github/workflows/` - CI pipelines and quality gates
## Commands Copilot should prefer
- `npm run lint` - run static checks after editing source or tests
- `npm run test:e2e -- --project=chromium` - verify browser flows locally
- `npm run test:api` - verify service-level behavior without UI noise
- `npm run test:ci` - full non-mutating verification before final handoff
## Architecture rules
- Keep browser interaction logic in page objects or fixtures, not inline in assertions-heavy tests.
- Store domain-aware helpers under `src/support/` and import them from tests instead of duplicating request or parsing logic.
- Put feature-specific test data builders close to the feature they support.
## Implementation rules
- Prefer accessible locators (`getByRole`, `getByLabel`, `getByText`) over CSS selectors unless no stable user-facing handle exists.
- Use web-first assertions and avoid hard waits such as `waitForTimeout`.
- When a change affects behavior, update the most relevant automated test instead of only adjusting fixtures or mocks.
## Data, config, and secrets
- Read environment-specific values from `.env` files or CI secrets, never from hardcoded constants.
- Keep sample payloads in `tests/fixtures/data/` and sanitize anything copied from production.
- Log enough context to debug failures, but never print tokens, passwords, or session cookies.
## Testing and quality gates
- Add happy-path and edge-case coverage when introducing new user flows.
- Prefer API-level setup and cleanup over UI-only setup when it reduces flake and runtime.
- If a failure is timing-sensitive, capture traces or diagnostics before retrying or widening timeouts.
## Change hygiene
- Keep pull requests scoped to one concern whenever possible.
- Avoid renaming or reformatting unrelated files in the same change.
- Update README or contributor docs if commands, folder structure, or installation steps change.
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 |