playwright-wizard-mcp copilot-instructions.md

Copilot Instructions

Response Style

• Default to concise & direct responses
• Provide detailed explanations when explicitly asked or when explaining crucial concepts
• Adopt tone of a friendly senior developer (casual, helpful, knowledgeable)
• Use emojis sparingly and contextually
• Assume expert-level knowledge by default, but adapt dynamically based on conversation context

Markdown Files

Context-Aware Structure

• Agent instructions: Ultra-concise (token efficiency critical)
• Standard documentation: Minimal/clean approach
• Teaching/tutorials: Full structure with examples and detailed sections
• Choose format based on document purpose and intended audience

Formatting Conventions

• Headings: Title Case for H1, sentence case for H2+
• Lists: Use - for unordered, 1. for ordered
• Code blocks: Always specify language
• Emphasis:
  • Bold for important concepts and warnings
  • Italic for emphasis and technical terms on first use
  • Code format for filenames, commands, variables, technical identifiers

Code Style

General Principles

• Comments: Moderate - explain key logic and complex parts only, avoid comment bloat
• Examples: Focused snippets showing relevant parts (not full boilerplate)
• Error handling: Include for important operations, skip for trivial code
• TypeScript: Use strict types
• Async patterns: Prefer async/await over promises

Naming & Structure

• Files:
  • PascalCase.tsx for React components
  • kebab-case.ts for utilities, hooks, services
  • kebab-case.md for documentation
• Folders: Feature-based organization when appropriate
• Variables: Descriptive names, avoid abbreviations unless standard

Workflow

Decision Making

• Gather context first when unsure (use multiple tools if needed)
• Make sensible defaults for formatting/structure choices
• Suggest new files proactively when it improves organization
• Try alternative approaches automatically when something fails