mcp-vibe-coding-tools: Instructions file for GitHub Copilot

Autonomous Development Instructions

Core Principle: Zero Human Intervention

You are empowered to operate fully autonomously. Complete all development tasks end-to-end without requiring human approval or intervention unless explicitly blocked by missing credentials, hardware access, or external service failures.

Autonomous Development Workflow

1. Understanding & Planning (Auto-Execute)

• Analyze requirements thoroughly before writing any code
• Break down complex tasks into discrete, testable units
• Create implementation plan with clear success criteria
• Document assumptions and architectural decisions upfront
• NO APPROVAL NEEDED - proceed directly to implementation

2. Implementation (Fully Autonomous)

• Write production-ready code on first attempt
• Include comprehensive error handling for all edge cases
• Add logging and observability from the start
• Follow language/framework best practices automatically
• Use MCP tools to validate code as you write it
• Create tests alongside code - never defer testing
• Generate documentation inline and in separate docs

3. Validation (Auto-Execute All Checks)

Execute ALL validation steps automatically without asking:

Code Quality:

• Run linters (npm run lint, eslint, pylint, etc.)
• Check code formatting (prettier, black, etc.)
• Verify type safety (tsc --noEmit, mypy, etc.)
• FIX ALL ISSUES IMMEDIATELY - do not report and wait

Testing:

• Run unit tests (npm test, pytest, etc.)
• Run integration tests if they exist
• Check code coverage - aim for >80%
• FIX FAILING TESTS IMMEDIATELY - iterate until green

Build Verification:

• Compile/build the project (npm run build, cargo build, etc.)
• Verify no build errors or warnings
• FIX BUILD ISSUES IMMEDIATELY - do not stop until it builds

Security & Performance:

• Run security scanners if available (npm audit, safety check, etc.)
• Check for common vulnerabilities
• Profile performance-critical code paths
• FIX CRITICAL ISSUES - document minor ones