Copilot Instructions Blueprint Generator
Generate a codebase-grounded copilot-instructions.md so GitHub Copilot follows your real stack versions, architecture, and patterns instead of generic assumptions.
Overview
Copilot Instructions Blueprint Generator is an agent skill most often used in Build (also Validate scope, Ship review) that produces a comprehensive, evidence-based copilot-instructions.md for GitHub Copilot.
Install
npx skills add https://github.com/github/awesome-copilot --skill copilot-instructions-blueprint-generatorWhat is this skill?
- Technology-agnostic blueprint with configurable PROJECT_TYPE, architecture style, quality focus, docs level, and testing
- Explicit mandate to derive rules only from observed codebase patterns—no invented stack or version assumptions
- Structured output scaffold: priority guidelines, core instruction sections, and version-accurate technology guidance
- Supports auto-detect and multi-stack projects (.NET, Java, JS/TS, React, Angular, Python, mixed)
- Aligns Copilot output with semantic versioning choices and documentation/testing requirements you select
- 6 configuration dimensions (project type, architecture, quality, docs, testing, versioning)
Adoption & trust: 8.6k installs on skills.sh; 34.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Copilot keeps suggesting code that ignores your real architecture, dependency versions, and team conventions because you never wrote grounded agent instructions.
Who is it for?
Repos where Copilot is already in use and you need one authoritative instructions file after a stack audit or team onboarding.
Skip if: Greenfield repos with almost no code to analyze yet, or teams that only use Claude/Cursor rules without GitHub Copilot.
When should I use this skill?
You need a comprehensive copilot-instructions.md grounded in analyzed codebase patterns for GitHub Copilot.
What do I get? / Deliverables
You get a structured copilot-instructions.md derived from actual project patterns so Copilot-generated changes align with your standards on the next coding session.
- copilot-instructions.md blueprint content
- Priority guidelines and core instruction structure
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is build/agent-tooling because the deliverable is persistent AI pair-programming instructions tied to how the repo is actually written. Agent-tooling fits best: copilot-instructions.md is project-level procedural knowledge for an coding agent, not application UI or runtime backend logic.
Where it fits
Decide which architecture and testing rules Copilot must follow before the MVP implementation sprint.
Author copilot-instructions.md after scanning existing services and frontend packages for real patterns.
Fold documentation-level requirements into Copilot guidance so new modules match comment and README norms.
Refresh instructions when review keeps catching the same Copilot mistakes on layering or test placement.
How it compares
Use instead of hand-waving a short .github/copilot-instructions.md from memory or copying a generic template from another stack.
Common Questions / FAQ
Who is copilot-instructions-blueprint-generator for?
Solo and indie builders (and small teams) shipping with GitHub Copilot who need instructions that mirror their real codebase—not generic best practices.
When should I use copilot-instructions-blueprint-generator?
During Build when adding agent tooling; during Validate when scoping how AI will help implement the MVP; and during Ship review prep when you want consistent AI-assisted patches before merge.
Is copilot-instructions-blueprint-generator safe to install?
Review the Security Audits panel on this Prism page and inspect the skill bundle in your repo before granting agent file access; do not paste secrets into generated instruction drafts.
SKILL.md
READMESKILL.md - Copilot Instructions Blueprint Generator
# Copilot Instructions Blueprint Generator ## Configuration Variables ${PROJECT_TYPE="Auto-detect|.NET|Java|JavaScript|TypeScript|React|Angular|Python|Multiple|Other"} <!-- Primary technology --> ${ARCHITECTURE_STYLE="Layered|Microservices|Monolithic|Domain-Driven|Event-Driven|Serverless|Mixed"} <!-- Architectural approach --> ${CODE_QUALITY_FOCUS="Maintainability|Performance|Security|Accessibility|Testability|All"} <!-- Quality priorities --> ${DOCUMENTATION_LEVEL="Minimal|Standard|Comprehensive"} <!-- Documentation requirements --> ${TESTING_REQUIREMENTS="Unit|Integration|E2E|TDD|BDD|All"} <!-- Testing approach --> ${VERSIONING="Semantic|CalVer|Custom"} <!-- Versioning approach --> ## Generated Prompt "Generate a comprehensive copilot-instructions.md file that will guide GitHub Copilot to produce code consistent with our project's standards, architecture, and technology versions. The instructions must be strictly based on actual code patterns in our codebase and avoid making any assumptions. Follow this approach: ### 1. Core Instruction Structure ```markdown # GitHub Copilot Instructions ## Priority Guidelines When generating code for this repository: 1. **Version Compatibility**: Always detect and respect the exact versions of languages, frameworks, and libraries used in this project 2. **Context Files**: Prioritize patterns and standards defined in the .github/copilot directory 3. **Codebase Patterns**: When context files don't provide specific guidance, scan the codebase for established patterns 4. **Architectural Consistency**: Maintain our ${ARCHITECTURE_STYLE} architectural style and established boundaries 5. **Code Quality**: Prioritize ${CODE_QUALITY_FOCUS == "All" ? "maintainability, performance, security, accessibility, and testability" : CODE_QUALITY_FOCUS} in all generated code ## Technology Version Detection Before generating code, scan the codebase to identify: 1. **Language Versions**: Detect the exact versions of programming languages in use - Examine project files, configuration files, and package managers - Look for language-specific version indicators (e.g., <LangVersion> in .NET projects) - Never use language features beyond the detected version 2. **Framework Versions**: Identify the exact versions of all frameworks - Check package.json, .csproj, pom.xml, requirements.txt, etc. - Respect version constraints when generating code - Never suggest features not available in the detected framework versions 3. **Library Versions**: Note the exact versions of key libraries and dependencies - Generate code compatible with these specific versions - Never use APIs or features not available in the detected versions ## Context Files Prioritize the following files in .github/copilot directory (if they exist): - **architecture.md**: System architecture guidelines - **tech-stack.md**: Technology versions and framework details - **coding-standards.md**: Code style and formatting standards - **folder-structure.md**: Project organization guidelines - **exemplars.md**: Exemplary code patterns to follow ## Codebase Scanning Instructions When context files don't provide specific guidance: 1. Identify similar files to the one being modified or created 2. Analyze patterns for: - Naming conventions - Code organization - Error handling - Logging approaches - Documentation style - Testing patterns 3. Follow the most consistent patterns found in the codebase 4. When conflicting patterns exist, prioritize patterns in newer files or files with higher test coverage 5. Never introduce patterns not found in the exis