klod68/gen-scoped-instructions

name: gen-scoped-instructions description: "Use when a sub-project, module, or layer needs its own scoped AI coding instructions layered on top of the root instructions. Generates a .instructions.md with the correct applyTo glob, architecture decisions, conventions, and anti-patterns. Also invoke when the user mentions: scoped instructions, sub-project instructions, module instructions, feature instructions file. Domain: DevOps, AI Context. Level: Intermediate."

Generate a scoped instructions file for the sub-project: ${1:SubProjectName}.

Context

• Sub-project path: ${2:e.g. src/MyApp.Demo}
• Purpose (one sentence): ${3:e.g. Blazor Server demo app showcasing the library with in-memory data}
• Project type: ${4|Blazor Server,Razor Pages,MVC,Minimal API,Console,Class Library,MAUI|}
• Key differences from the main project: ${5:e.g. In-memory data only, no database; uses InMemory services}
• Explicit anti-patterns (things agents commonly do wrong here): ${6:e.g. Do not add database access, Do not reference production connection strings}

Output

Create .github/instructions/${1:lower}.instructions.md:

---
applyTo: "[glob matching files in ${2}]"
---

# ${1} — Agent Instructions

## Purpose
${3}

## Architecture
[3–5 decisions specific to this sub-project, not duplicating the main instructions]

## File Organization
| Directory | Purpose |
|---|---|

## Conventions
[Only conventions that differ from or extend the main copilot-instructions.md]

## Key Dependencies
[Packages and project references unique to this sub-project]

## What NOT to Do
[Each as a ❌ bullet — specific and actionable]

## Build & Run
\`\`\`powershell
dotnet run --project ${2}
\`\`\`

applyTo glob selection

Choose the pattern that matches only files in this sub-project:

| Sub-project type | Pattern | |---|---| | Folder name contains a keyword | **/*${1}*/**/* | | Specific project folder | ${2}/**/* | | Blazor files only | **/*.razor,**/*.razor.cs | | Test project | **/*Tests*/**/*.cs | | Migration files | **/Migrations/**/* |

Verify the pattern does not accidentally match files outside this sub-project.

Quality rules

• < 80 lines total — supplements the main instructions, does not replace them
• Differences only — do not repeat rules already in copilot-instructions.md
• Anti-patterns are specific — "Do not add database access" not "Follow good practices"
• Build command is copy-pasteable — exact path, no placeholders
• applyTo pattern is tested against the actual directory structure

Constraints

• Follow all rules in the workspace root instruction file
• The scoped file must not contradict the main instructions — only extend or restrict them
• If a restriction applies only to this sub-project (e.g., "no real data"), state it explicitly as a ❌ anti-pattern