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.example.instructions.md
View on GitHub---
description: 'Playwright fixture instructions for shared setup, domain helpers, and reusable test bootstrapping.'
applyTo: 'tests/**/*.{spec.ts,fixture.ts}'
title: 'Playwright Fixture Instructions'
name: 'playwright-fixture-instructions'
---
## Scope
- Applies to: `tests/` Playwright spec files and fixture files
- Goal: keep setup reusable, explicit, and easy to debug
## Rules
- Keep browser or session setup in fixtures instead of repeating it inline in each test.
- Expose domain actions or page objects from fixtures when raw `page` usage would leak too much setup detail into tests.
- Generate unique test data per test and clean it up through API helpers when possible.
- Keep one primary responsibility per fixture so test failures remain explainable.
### Preferred pattern
```ts
import { test as base } from '@playwright/test';
import { CheckoutPage } from '../pages/checkout.page';
export const test = base.extend<{ checkoutPage: CheckoutPage }>({
checkoutPage: async ({ page }, use) => {
await use(new CheckoutPage(page));
},
});
```
### Avoid
```ts
test('checkout flow', async ({ page }) => {
const checkoutPage = new CheckoutPage(page);
await page.goto('/checkout');
await page.getByRole('textbox', { name: 'Email' }).fill('person@example.com');
// repeated bootstrapping appears in multiple tests
});
```
## Notes
- Prefer `tests/fixtures/` for shared setup.
- Check existing fixture names before creating a new one.
- Use `npm run test:e2e -- --grep <scenario>` for fast local verification while iterating.
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 |