Code Exemplars Blueprint Generator
Generate a tailored AI prompt so your agent scans the repo and writes an exemplars.md of on-pattern code for team standards.
Overview
Code Exemplars Blueprint Generator is an agent skill most often used in Ship/Review (also Build/Docs, Operate/Iterate) that builds a customizable scan prompt to produce exemplars.md from your codebase.
Install
npx skills add https://github.com/github/awesome-copilot --skill code-exemplars-blueprint-generatorWhat is this skill?
- Configurable PROJECT_TYPE across .NET, Java, JS/TS, React, Angular, Python, or auto-detect
- SCAN_DEPTH modes: Basic, Standard, Comprehensive
- CATEGORIZATION by pattern type, architecture layer, or file type
- Toggles for code snippets, per-category max examples, and explanatory comments
- Emits a ready-to-run scan prompt that targets an exemplars.md artifact
- Supports 7+ stack labels including Auto-detect, .NET, Java, JavaScript, TypeScript, React, Angular, Python
- Three scan depth levels: Basic, Standard, Comprehensive
- Default MAX_EXAMPLES_PER_CATEGORY=3 with three categorization modes
Adoption & trust: 8.6k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want consistent coding patterns across the repo but lack a single, agent-readable map of which files and patterns are the gold standard.
Who is it for?
Teams or solo devs standardizing multi-language repos and wanting repeatable exemplar documentation before review or onboarding.
Skip if: Replacing automated tests, security scans, or one-off fixes where you already have an approved style guide and no need to mine the repo.
When should I use this skill?
You need a customizable AI prompt to scan a codebase and identify high-quality code exemplars for standards and consistency.
What do I get? / Deliverables
You get a parameterized scan prompt and a defined exemplars.md structure so your agent can catalog high-quality examples by category and depth.
- Parameterized scan prompt for exemplars.md
- exemplars.md structure with categorized file references and optional snippets
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship/Review because the output is a standards map used before merges and during quality passes, even though you can run it earlier during build. Review subphase fits exemplar discovery and consistency checks that precede or accompany code review, not greenfield feature coding.
Where it fits
Document canonical React hook patterns before writing contributor guidelines.
Produce exemplars.md so the agent compares new PRs against known-good service layers.
Refresh exemplar categories after a large refactor to .NET minimal APIs.
How it compares
A prompt blueprint for exemplar mining—not a linter, formatter, or live MCP codebase indexer.
Common Questions / FAQ
Who is code-exemplars-blueprint-generator for?
Solo builders and small teams who use AI coding agents and need a repeatable way to document real-world pattern examples from their own repository.
When should I use code-exemplars-blueprint-generator?
During Ship review prep to feed code review, in Build/docs when documenting conventions, or in Operate/iterate when refactoring—whenever you need exemplars.md before agents touch new areas.
Is code-exemplars-blueprint-generator safe to install?
Review the Security Audits panel on this Prism page before installing; the skill only describes prompt generation, but executing the generated scan may read broad parts of your filesystem via your agent.
SKILL.md
READMESKILL.md - Code Exemplars Blueprint Generator
# Code Exemplars Blueprint Generator ## Configuration Variables ${PROJECT_TYPE="Auto-detect|.NET|Java|JavaScript|TypeScript|React|Angular|Python|Other"} <!-- Primary technology --> ${SCAN_DEPTH="Basic|Standard|Comprehensive"} <!-- How deeply to analyze the codebase --> ${INCLUDE_CODE_SNIPPETS=true|false} <!-- Include actual code snippets in addition to file references --> ${CATEGORIZATION="Pattern Type|Architecture Layer|File Type"} <!-- How to organize exemplars --> ${MAX_EXAMPLES_PER_CATEGORY=3} <!-- Maximum number of examples per category --> ${INCLUDE_COMMENTS=true|false} <!-- Include explanatory comments for each exemplar --> ## Generated Prompt "Scan this codebase and generate an exemplars.md file that identifies high-quality, representative code examples. The exemplars should demonstrate our coding standards and patterns to help maintain consistency. Use the following approach: ### 1. Codebase Analysis Phase - ${PROJECT_TYPE == "Auto-detect" ? "Automatically detect primary programming languages and frameworks by scanning file extensions and configuration files" : `Focus on ${PROJECT_TYPE} code files`} - Identify files with high-quality implementation, good documentation, and clear structure - Look for commonly used patterns, architecture components, and well-structured implementations - Prioritize files that demonstrate best practices for our technology stack - Only reference actual files that exist in the codebase - no hypothetical examples ### 2. Exemplar Identification Criteria - Well-structured, readable code with clear naming conventions - Comprehensive comments and documentation - Proper error handling and validation - Adherence to design patterns and architectural principles - Separation of concerns and single responsibility principle - Efficient implementation without code smells - Representative of our standard approaches ### 3. Core Pattern Categories ${PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect" ? `#### .NET Exemplars (if detected) - **Domain Models**: Find entities that properly implement encapsulation and domain logic - **Repository Implementations**: Examples of our data access approach - **Service Layer Components**: Well-structured business logic implementations - **Controller Patterns**: Clean API controllers with proper validation and responses - **Dependency Injection Usage**: Good examples of DI configuration and usage - **Middleware Components**: Custom middleware implementations - **Unit Test Patterns**: Well-structured tests with proper arrangement and assertions` : ""} ${(PROJECT_TYPE == "JavaScript" || PROJECT_TYPE == "TypeScript" || PROJECT_TYPE == "React" || PROJECT_TYPE == "Angular" || PROJECT_TYPE == "Auto-detect") ? `#### Frontend Exemplars (if detected) - **Component Structure**: Clean, well-structured components - **State Management**: Good examples of state handling - **API Integration**: Well-implemented service calls and data handling - **Form Handling**: Validation and submission patterns - **Routing Implementation**: Navigation and route configuration - **UI Components**: Reusable, well-structured UI elements - **Unit Test Examples**: Component and service tests` : ""} ${PROJECT_TYPE == "Java" || PROJECT_TYPE == "Auto-detect" ? `#### Java Exemplars (if detected) - **Entity Classes**: Well-designed JPA entities or domain models - **Service Implementations**: Clean service layer components - **Repository Patterns**: Data access implementations - **Controller/Resource Classes**: API endpoint implementa