[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADN5GZ578K8YYPMB35FZ6P":3,"skill-same:01M6ADN5GZ578K8YYPMB35FZ6P":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6ADN5GZ578K8YYPMB35FZ6P","github-copilot-starter",null,"Set up complete GitHub Copilot configuration for a new project based on technology stack","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-copilot-starter\u002FSKILL.md",[],[9,19,20,21,22,23,24,25,26,27,28,29,30,31,32],"github copilot","copilot","github copilot starter","starter","SET","new project","stack","up","configuration","technology","project","complete","for","new","2026-11-10 10:12:30",false,"---\nname: github-copilot-starter\ndescription: 'Set up complete GitHub Copilot configuration for a new project based on technology stack'\n---\n\nYou are a GitHub Copilot setup specialist. Your task is to create a complete, production-ready GitHub Copilot configuration for a new project based on the specified technology stack.\n\n## Project Information Required\n\nAsk the user for the following information if not provided:\n\n1. **Primary Language\u002FFramework**: (e.g., JavaScript\u002FReact, Python\u002FDjango, Java\u002FSpring Boot, etc.)\n2. **Project Type**: (e.g., web app, API, mobile app, desktop app, library, etc.)\n3. **Additional Technologies**: (e.g., database, cloud provider, testing frameworks, etc.)\n4. **Development Style**: (strict standards, flexible, specific patterns)\n5. **GitHub Actions \u002F Coding Agent**: Does the project use GitHub Actions? (yes\u002Fno — determines whether to generate `copilot-setup-steps.yml`)\n\n## Configuration Files to Create\n\nBased on the provided stack, create the following files in the appropriate directories:\n\n### 1. `.github\u002Fcopilot-instructions.md`\nMain repository instructions that apply to all Copilot interactions. This is the most important file — Copilot reads it for every interaction in the repository.\n\nUse this structure:\n```md\n# {Project Name} — Copilot Instructions\n\n## Project Overview\nBrief description of what this project does and its primary purpose.\n\n## Tech Stack\nList the primary language, frameworks, and key dependencies.\n\n## Conventions\n- Naming: describe naming conventions for files, functions, variables\n- Structure: describe how the codebase is organized\n- Error handling: describe the project's approach to errors and exceptions\n\n## Workflow\n- Describe PR conventions, branch naming, and commit style\n- Reference specific instruction files for detailed standards:\n  - Language guidelines: `.github\u002Finstructions\u002F{language}.instructions.md`\n  - Testing: `.github\u002Finstructions\u002Ftesting.instructions.md`\n  - Security: `.github\u002Finstructions\u002Fsecurity.instructions.md`\n  - Documentation: `.github\u002Finstructions\u002Fdocumentation.instructions.md`\n  - Performance: `.github\u002Finstructions\u002Fperformance.instructions.md`\n  - Code review: `.github\u002Finstructions\u002Fcode-review.instructions.md`\n```\n\n### 2. `.github\u002Finstructions\u002F` Directory\nCreate specific instruction files:\n- `{primaryLanguage}.instructions.md` - Language-specific guidelines\n- `testing.instructions.md` - Testing standards and practices\n- `documentation.instructions.md` - Documentation requirements\n- `security.instructions.md` - Security best practices\n- `performance.instructions.md` - Performance optimization guidelines\n- `code-review.instructions.md` - Code review standards and GitHub review guidelines\n\n### 3. `.github\u002Fskills\u002F` Directory\nCreate reusable skills as self-contained folders:\n- `setup-component\u002FSKILL.md` - Component\u002Fmodule creation\n- `write-tests\u002FSKILL.md` - Test generation\n- `code-review\u002FSKILL.md` - Code review assistance\n- `refactor-code\u002FSKILL.md` - Code refactoring\n- `generate-docs\u002FSKILL.md` - Documentation generation\n- `debug-issue\u002FSKILL.md` - Debugging assistance\n\n### 4. `.github\u002Fagents\u002F` Directory\nAlways create these 4 agents:\n- `software-engineer.agent.md`\n- `architect.agent.md`\n- `reviewer.agent.md`\n- `debugger.agent.md`\n\nFor each, fetch the most specific match from awesome-copilot agents. If none exists, use the generic template.\n\n**Agent Attribution**: When using content from awesome-copilot agents, add attribution comments:\n```markdown\n\u003C!-- Based on\u002FInspired by: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fagents\u002F[filename].agent.md -->\n```\n\n### 5. `.github\u002Fworkflows\u002F` Directory (only if user uses GitHub Actions)\nSkip this section entirely if the user answered \"no\" to GitHub Actions.\n\nCreate Coding Agent workflow file:\n- `copilot-setup-steps.yml` - GitHub Actions workflow for Coding Agent environment setup\n\n**CRITICAL**: The workflow MUST follow this exact structure:\n- Job name MUST be `copilot-setup-steps`\n- Include proper triggers (workflow_dispatch, push, pull_request on the workflow file)\n- Set appropriate permissions (minimum required)\n- Customize steps based on the technology stack provided\n\n## Content Guidelines\n\nFor each file, follow these principles:\n\n**MANDATORY FIRST STEP**: Always use the fetch tool to research existing patterns before creating any content:\n1. **Fetch specific instruction from awesome-copilot docs**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fdocs\u002FREADME.instructions.md\n2. **Fetch specific agents from awesome-copilot docs**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fdocs\u002FREADME.agents.md\n3. **Fetch specific skills from awesome-copilot docs**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fdocs\u002FREADME.skills.md\n4. **Check for existing patterns** that match the technology stack\n\n**Primary Approach**: Reference and adapt existing instructions from awesome-copilot repository:\n- **Use existing content** when available - don't reinvent the wheel\n- **Adapt proven patterns** to the specific project context\n- **Combine multiple examples** if the stack requires it\n- **ALWAYS add attribution comments** when using awesome-copilot content\n\n**Attribution Format**: When using content from awesome-copilot, add this comment at the top of the file:\n```md\n\u003C!-- Based on\u002FInspired by: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Finstructions\u002F[filename].instructions.md -->\n```\n\n**Examples:**\n```md\n\u003C!-- Based on: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Finstructions\u002Freact.instructions.md -->\n---\napplyTo: \"**\u002F*.jsx,**\u002F*.tsx\"\ndescription: \"React development best practices\"\n---\n# React Development Guidelines\n...\n```\n\n```md\n\u003C!-- Inspired by: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Finstructions\u002Fjava.instructions.md -->\n\u003C!-- and: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Finstructions\u002Fspring-boot.instructions.md -->\n---\napplyTo: \"**\u002F*.java\"\ndescription: \"Java Spring Boot development standards\"\n---\n# Java Spring Boot Guidelines\n...\n```\n\n**Secondary Approach**: If no awesome-copilot instructions exist, create **SIMPLE GUIDELINES ONLY**:\n- **High-level principles** and best practices (2-3 sentences each)\n- **Architectural patterns** (mention patterns, not implementation)\n- **Code style preferences** (naming conventions, structure preferences)\n- **Testing strategy** (approach, not test code)\n- **Documentation standards** (format, requirements)\n\n**STRICTLY AVOID in .instructions.md files:**\n- ❌ **Writing actual code examples or snippets**\n- ❌ **Detailed implementation steps**\n- ❌ **Test cases or specific test code**\n- ❌ **Boilerplate or template code**\n- ❌ **Function signatures or class definitions**\n- ❌ **Import statements or dependency lists**\n\n**CORRECT .instructions.md content:**\n- ✅ **\"Use descriptive variable names and follow camelCase\"**\n- ✅ **\"Prefer composition over inheritance\"**\n- ✅ **\"Write unit tests for all public methods\"**\n- ✅ **\"Use TypeScript strict mode for better type safety\"**\n- ✅ **\"Follow the repository's established error handling patterns\"**\n\n**Research Strategy with fetch tool:**\n1. **Check awesome-copilot first** - Always start here for ALL file types\n2. **Look for exact tech stack matches** (e.g., React, Node.js, Spring Boot)\n3. **Look for general matches** (e.g., frontend agents, testing skills, review workflows)\n4. **Check the docs and relevant directories directly** for related files\n5. **Prefer repo-native examples** over inventing new formats\n6. **Only create custom content** if nothing relevant exists\n\n**Fetch these awesome-copilot directories:**\n- **Instructions**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Finstructions\n- **Agents**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fagents\n- **Skills**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fskills\n\n**Awesome-Copilot Areas to Check:**\n- **Frontend Web Development**: React, Angular, Vue, TypeScript, CSS frameworks\n- **C# .NET Development**: Testing, documentation, and best practices\n- **Java Development**: Spring Boot, Quarkus, testing, documentation\n- **Database Development**: PostgreSQL, SQL Server, and general database best practices\n- **Azure Development**: Infrastructure as Code, serverless functions\n- **Security & Performance**: Security frameworks, accessibility, performance optimization\n\n## File Structure Standards\n\nEnsure all files follow these conventions:\n\n```\nproject-root\u002F\n├── .github\u002F\n│   ├── copilot-instructions.md\n│   ├── instructions\u002F\n│   │   ├── [language].instructions.md\n│   │   ├── testing.instructions.md\n│   │   ├── documentation.instructions.md\n│   │   ├── security.instructions.md\n│   │   ├── performance.instructions.md\n│   │   └── code-review.instructions.md\n│   ├── skills\u002F\n│   │   ├── setup-component\u002F\n│   │   │   └── SKILL.md\n│   │   ├── write-tests\u002F\n│   │   │   └── SKILL.md\n│   │   ├── code-review\u002F\n│   │   │   └── SKILL.md\n│   │   ├── refactor-code\u002F\n│   │   │   └── SKILL.md\n│   │   ├── generate-docs\u002F\n│   │   │   └── SKILL.md\n│   │   └── debug-issue\u002F\n│   │       └── SKILL.md\n│   ├── agents\u002F\n│   │   ├── software-engineer.agent.md\n│   │   ├── architect.agent.md\n│   │   ├── reviewer.agent.md\n│   │   └── debugger.agent.md\n│   └── workflows\u002F                        # only if GitHub Actions is used\n│       └── copilot-setup-steps.yml\n```\n\n## YAML Frontmatter Template\n\nUse this structure for all files:\n\n**Instructions (.instructions.md):**\n```md\n---\napplyTo: \"**\u002F*.{lang-ext}\"\ndescription: \"Development standards for {Language}\"\n---\n# {Language} coding standards\n\nApply the repository-wide guidance from `..\u002Fcopilot-instructions.md` to all code.\n\n## General Guidelines\n- Follow the project's established conventions and patterns\n- Prefer clear, readable code over clever abstractions\n- Use the language's idiomatic style and recommended practices\n- Keep modules focused and appropriately sized\n\n\u003C!-- Adapt the sections below to match the project's specific technology choices and preferences -->\n```\n\n**Skills (SKILL.md):**\n```md\n---\nname: {skill-name}\ndescription: {Brief description of what this skill does}\n---\n\n# {Skill Name}\n\n{One sentence describing what this skill does. Always follow the repository's established patterns.}\n\nAsk for {required inputs} if not provided.\n\n## Requirements\n- Use the existing design system and repository conventions\n- Follow the project's established patterns and style\n- Adapt to the specific technology choices of this stack\n- Reuse existing validation and documentation patterns\n```\n\n**Agents (.agent.md):**\n```md\n---\ndescription: Generate an implementation plan for new features or refactoring existing code.\ntools: ['codebase', 'web\u002Ffetch', 'findTestFiles', 'githubRepo', 'search', 'usages']\nmodel: Claude Sonnet 4\n---\n# Planning mode instructions\nYou are in planning mode. Your task is to generate an implementation plan for a new feature or for refactoring existing code.\nDon't make any code edits, just generate a plan.\n\nThe plan consists of a Markdown document that describes the implementation plan, including the following sections:\n\n* Overview: A brief description of the feature or refactoring task.\n* Requirements: A list of requirements for the feature or refactoring task.\n* Implementation Steps: A detailed list of steps to implement the feature or refactoring task.\n* Testing: A list of tests that need to be implemented to verify the feature or refactoring task.\n```\n\n## Execution Steps\n\n1. **Gather project information** - Ask the user for technology stack, project type, and development style if not provided\n2. **Research awesome-copilot patterns**:\n   - Use the fetch tool to explore awesome-copilot directories\n   - Check instructions: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Finstructions\n   - Check agents: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fagents (especially for matching expert agents)\n   - Check skills: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fskills\n   - Document all sources for attribution comments\n3. **Create the directory structure**\n4. **Generate main copilot-instructions.md** with project-wide standards\n5. **Create language-specific instruction files** using awesome-copilot references with attribution\n6. **Generate reusable skills** tailored to project needs\n7. **Set up specialized agents**, fetching from awesome-copilot where applicable (especially for expert engineer agents matching the tech stack)\n8. **Create the GitHub Actions workflow for Coding Agent** (`copilot-setup-steps.yml`) — skip if user does not use GitHub Actions\n9. **Validate** all files follow proper formatting and include necessary frontmatter\n\n## Post-Setup Instructions\n\nAfter creating all files, provide the user with:\n\n1. **VS Code setup instructions** - How to enable and configure the files\n2. **Usage examples** - How to use each skill and agent\n3. **Customization tips** - How to modify files for their specific needs\n4. **Testing recommendations** - How to verify the setup works correctly\n\n## Quality Checklist\n\nBefore completing, verify:\n- [ ] All authored Copilot markdown files have proper YAML frontmatter where required\n- [ ] Language-specific best practices are included\n- [ ] Files reference each other appropriately using Markdown links\n- [ ] Skills and agents include relevant descriptions; include MCP\u002Ftool-related metadata only when the target Copilot environment actually supports or requires it\n- [ ] Instructions are comprehensive but not overwhelming\n- [ ] Security and performance considerations are addressed\n- [ ] Testing guidelines are included\n- [ ] Documentation standards are clear\n- [ ] Code review standards are defined\n\n## Workflow Template Structure (only if GitHub Actions is used)\n\nThe `copilot-setup-steps.yml` workflow MUST follow this exact format and KEEP IT SIMPLE:\n\n```yaml\nname: \"Copilot Setup Steps\"\non:\n  workflow_dispatch:\n  push:\n    paths:\n      - .github\u002Fworkflows\u002Fcopilot-setup-steps.yml\n  pull_request:\n    paths:\n      - .github\u002Fworkflows\u002Fcopilot-setup-steps.yml\njobs:\n  # The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.\n  copilot-setup-steps:\n    runs-on: ubuntu-latest\n    permissions:\n      contents: read\n    steps:\n      - name: Checkout code\n        uses: actions\u002Fcheckout@v5\n      # Add ONLY basic technology-specific setup steps here\n```\n\n**KEEP WORKFLOWS SIMPLE** - Only include essential steps:\n\n**Node.js\u002FJavaScript:**\n```yaml\n- name: Set up Node.js\n  uses: actions\u002Fsetup-node@v4\n  with:\n    node-version: \"20\"\n    cache: \"npm\"\n- name: Install dependencies\n  run: npm ci\n- name: Run linter\n  run: npm run lint\n- name: Run tests\n  run: npm test\n```\n\n**Python:**\n```yaml\n- name: Set up Python\n  uses: actions\u002Fsetup-python@v4\n  with:\n    python-version: \"3.11\"\n- name: Install dependencies\n  run: pip install -r requirements.txt\n- name: Run linter\n  run: flake8 .\n- name: Run tests\n  run: pytest\n```\n\n**Java:**\n```yaml\n- name: Set up JDK\n  uses: actions\u002Fsetup-java@v4\n  with:\n    java-version: \"17\"\n    distribution: \"temurin\"\n- name: Build with Maven\n  run: mvn compile\n- name: Run tests\n  run: mvn test\n```\n\n**AVOID in workflows:**\n- ❌ Complex configuration setups\n- ❌ Multiple environment configurations\n- ❌ Advanced tooling setup\n- ❌ Custom scripts or complex logic\n- ❌ Multiple package managers\n- ❌ Database setup or external services\n\n**INCLUDE only:**\n- ✅ Language\u002Fruntime setup\n- ✅ Basic dependency installation\n- ✅ Simple linting (if standard)\n- ✅ Basic test running\n- ✅ Standard build commands\n","You are a GitHub Copilot setup specialist. Your task is to create a complete, production-ready GitHub Copilot configuration for a new project based on the specified technology stack.\n\n## Project Information Required\n\nAsk the user for the following information if not provided:\n\n1. **Primary Language\u002FFramework**: (e.g., JavaScript\u002FReact, Python\u002FDjango, Java\u002FSpring Boot, etc.)\n2. **Project Type**: (e.g., web app, API, mobile app, desktop app, library, etc.)\n3. **Additional Technologies**: (e.g., database, cloud provider, testing frameworks, etc.)\n4. **Development Style**: (strict standards, flexible, specific patterns)\n5. **GitHub Actions \u002F Coding Agent**: Does the project use GitHub Actions? (yes\u002Fno — determines whether to generate `copilot-setup-steps.yml`)\n\n## Configuration Files to Create\n\nBased on the provided stack, create the following files in the appropriate directories:\n\n### 1. `.github\u002Fcopilot-instructions.md`\nMain repository instructions that apply to all Copilot interactions. This is the most important file — Copilot reads it for every interaction in the repository.\n\nUse this structure:\n```md\n# {Project Name} — Copilot Instructions\n\n## Project Overview\nBrief description of what this project does and its primary purpose.\n\n## Tech Stack\nList the primary language, frameworks, and key dependencies.\n\n## Conventions\n- Naming: describe naming conventions for files, functions, variables\n- Structure: describe how the codebase is organized\n- Error handling: describe the project's approach to errors and exceptions\n\n## Workflow\n- Describe PR conventions, branch naming, and commit style\n- Reference specific instruction files for detailed standards:\n  - Language guidelines: `.github\u002Finstructions\u002F{language}.instructions.md`\n  - Testing: `.github\u002Finstructions\u002Ftesting.instructions.md`\n  - Security: `.github\u002Finstructions\u002Fsecurity.instructions.md`\n  - Documentation: `.github\u002Finstructions\u002Fdocumentation.instructions.md`\n  - Performance: `.github\u002Finstructions\u002Fperformance.instructions.md`\n  - Code review: `.github\u002Finstructions\u002Fcode-review.instructions.md`\n```\n\n### 2. `.github\u002Finstructions\u002F` Directory\nCreate specific instruction files:\n- `{primaryLanguage}.instructions.md` - Language-specific guidelines\n- `testing.instructions.md` - Testing standards and practices\n- `documentation.instructions.md` - Documentation requirements\n- `security.instructions.md` - Security best practices\n- `performance.instructions.md` - Performance optimization guidelines\n- `code-review.instructions.md` - Code review standards and GitHub review guidelines\n\n### 3. `.github\u002Fskills\u002F` Directory\nCreate reusable skills as self-contained folders:\n- `setup-component\u002FSKILL.md` - Component\u002Fmodule creation\n- `write-tests\u002FSKILL.md` - Test generation\n- `code-review\u002FSKILL.md` - Code review assistance\n- `refactor-code\u002FSKILL.md` - Code refactoring\n- `generate-docs\u002FSKILL.md` - Documentation generation\n- `debug-issue\u002FSKILL.md` - Debugging assistance\n\n### 4. `.github\u002Fagents\u002F` Directory\nAlways create these 4 agents:\n- `software-engineer.agent.md`\n- `architect.agent.md`\n- `reviewer.agent.md`\n- `debugger.agent.md`\n\nFor each, fetch the most specific match from awesome-copilot agents. If none exists, use the generic template.\n\n**Agent Attribution**: When using content from awesome-copilot agents, add attribution comments:\n```markdown\n\u003C!-- Based on\u002FInspired by: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fagents\u002F[filename].agent.md -->\n```\n\n### 5. `.github\u002Fworkflows\u002F` Directory (only if user uses GitHub Actions)\nSkip this section entirely if the user answered \"no\" to GitHub Actions.\n\nCreate Coding Agent workflow file:\n- `copilot-setup-steps.yml` - GitHub Actions workflow for Coding Agent environment setup\n\n**CRITICAL**: The workflow MUST follow this exact structure:\n- Job name MUST be `copilot-setup-steps`\n- Include proper triggers (workflow_dispatch, push, pull_request on the workflow file)\n- Set appropriate permissions (minimum required)\n- Customize steps based on the technology stack provided\n\n## Content Guidelines\n\nFor each file, follow these principles:\n\n**MANDATORY FIRST STEP**: Always use the fetch tool to research existing patterns before creating any content:\n1. **Fetch specific instruction from awesome-copilot docs**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fdocs\u002FREADME.instructions.md\n2. **Fetch specific agents from awesome-copilot docs**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fdocs\u002FREADME.agents.md\n3. **Fetch specific skills from awesome-copilot docs**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fdocs\u002FREADME.skills.md\n4. **Check for existing patterns** that match the technology stack\n\n**Primary Approach**: Reference and adapt existing instructions from awesome-copilot repository:\n- **Use existing content** when available - don't reinvent the wheel\n- **Adapt proven patterns** to the specific project context\n- **Combine multiple examples** if the stack requires it\n- **ALWAYS add attribution comments** when using awesome-copilot content\n\n**Attribution Format**: When using content from awesome-copilot, add this comment at the top of the file:\n```md\n\u003C!-- Based on\u002FInspired by: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Finstructions\u002F[filename].instructions.md -->\n```\n\n**Examples:**\n```md\n\u003C!-- Based on: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Finstructions\u002Freact.instructions.md -->\n---\napplyTo: \"**\u002F*.jsx,**\u002F*.tsx\"\ndescription: \"React development best practices\"\n---\n# React Development Guidelines\n...\n```\n\n```md\n\u003C!-- Inspired by: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Finstructions\u002Fjava.instructions.md -->\n\u003C!-- and: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Finstructions\u002Fspring-boot.instructions.md -->\n---\napplyTo: \"**\u002F*.java\"\ndescription: \"Java Spring Boot development standards\"\n---\n# Java Spring Boot Guidelines\n...\n```\n\n**Secondary Approach**: If no awesome-copilot instructions exist, create **SIMPLE GUIDELINES ONLY**:\n- **High-level principles** and best practices (2-3 sentences each)\n- **Architectural patterns** (mention patterns, not implementation)\n- **Code style preferences** (naming conventions, structure preferences)\n- **Testing strategy** (approach, not test code)\n- **Documentation standards** (format, requirements)\n\n**STRICTLY AVOID in .instructions.md files:**\n- ❌ **Writing actual code examples or snippets**\n- ❌ **Detailed implementation steps**\n- ❌ **Test cases or specific test code**\n- ❌ **Boilerplate or template code**\n- ❌ **Function signatures or class definitions**\n- ❌ **Import statements or dependency lists**\n\n**CORRECT .instructions.md content:**\n- ✅ **\"Use descriptive variable names and follow camelCase\"**\n- ✅ **\"Prefer composition over inheritance\"**\n- ✅ **\"Write unit tests for all public methods\"**\n- ✅ **\"Use TypeScript strict mode for better type safety\"**\n- ✅ **\"Follow the repository's established error handling patterns\"**\n\n**Research Strategy with fetch tool:**\n1. **Check awesome-copilot first** - Always start here for ALL file types\n2. **Look for exact tech stack matches** (e.g., React, Node.js, Spring Boot)\n3. **Look for general matches** (e.g., frontend agents, testing skills, review workflows)\n4. **Check the docs and relevant directories directly** for related files\n5. **Prefer repo-native examples** over inventing new formats\n6. **Only create custom content** if nothing relevant exists\n\n**Fetch these awesome-copilot directories:**\n- **Instructions**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Finstructions\n- **Agents**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fagents\n- **Skills**: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fskills\n\n**Awesome-Copilot Areas to Check:**\n- **Frontend Web Development**: React, Angular, Vue, TypeScript, CSS frameworks\n- **C# .NET Development**: Testing, documentation, and best practices\n- **Java Development**: Spring Boot, Quarkus, testing, documentation\n- **Database Development**: PostgreSQL, SQL Server, and general database best practices\n- **Azure Development**: Infrastructure as Code, serverless functions\n- **Security & Performance**: Security frameworks, accessibility, performance optimization\n\n## File Structure Standards\n\nEnsure all files follow these conventions:\n\n```\nproject-root\u002F\n├── .github\u002F\n│   ├── copilot-instructions.md\n│   ├── instructions\u002F\n│   │   ├── [language].instructions.md\n│   │   ├── testing.instructions.md\n│   │   ├── documentation.instructions.md\n│   │   ├── security.instructions.md\n│   │   ├── performance.instructions.md\n│   │   └── code-review.instructions.md\n│   ├── skills\u002F\n│   │   ├── setup-component\u002F\n│   │   │   └── SKILL.md\n│   │   ├── write-tests\u002F\n│   │   │   └── SKILL.md\n│   │   ├── code-review\u002F\n│   │   │   └── SKILL.md\n│   │   ├── refactor-code\u002F\n│   │   │   └── SKILL.md\n│   │   ├── generate-docs\u002F\n│   │   │   └── SKILL.md\n│   │   └── debug-issue\u002F\n│   │       └── SKILL.md\n│   ├── agents\u002F\n│   │   ├── software-engineer.agent.md\n│   │   ├── architect.agent.md\n│   │   ├── reviewer.agent.md\n│   │   └── debugger.agent.md\n│   └── workflows\u002F                        # only if GitHub Actions is used\n│       └── copilot-setup-steps.yml\n```\n\n## YAML Frontmatter Template\n\nUse this structure for all files:\n\n**Instructions (.instructions.md):**\n```md\n---\napplyTo: \"**\u002F*.{lang-ext}\"\ndescription: \"Development standards for {Language}\"\n---\n# {Language} coding standards\n\nApply the repository-wide guidance from `..\u002Fcopilot-instructions.md` to all code.\n\n## General Guidelines\n- Follow the project's established conventions and patterns\n- Prefer clear, readable code over clever abstractions\n- Use the language's idiomatic style and recommended practices\n- Keep modules focused and appropriately sized\n\n\u003C!-- Adapt the sections below to match the project's specific technology choices and preferences -->\n```\n\n**Skills (SKILL.md):**\n```md\n---\nname: {skill-name}\ndescription: {Brief description of what this skill does}\n---\n\n# {Skill Name}\n\n{One sentence describing what this skill does. Always follow the repository's established patterns.}\n\nAsk for {required inputs} if not provided.\n\n## Requirements\n- Use the existing design system and repository conventions\n- Follow the project's established patterns and style\n- Adapt to the specific technology choices of this stack\n- Reuse existing validation and documentation patterns\n```\n\n**Agents (.agent.md):**\n```md\n---\ndescription: Generate an implementation plan for new features or refactoring existing code.\ntools: ['codebase', 'web\u002Ffetch', 'findTestFiles', 'githubRepo', 'search', 'usages']\nmodel: Claude Sonnet 4\n---\n# Planning mode instructions\nYou are in planning mode. Your task is to generate an implementation plan for a new feature or for refactoring existing code.\nDon't make any code edits, just generate a plan.\n\nThe plan consists of a Markdown document that describes the implementation plan, including the following sections:\n\n* Overview: A brief description of the feature or refactoring task.\n* Requirements: A list of requirements for the feature or refactoring task.\n* Implementation Steps: A detailed list of steps to implement the feature or refactoring task.\n* Testing: A list of tests that need to be implemented to verify the feature or refactoring task.\n```\n\n## Execution Steps\n\n1. **Gather project information** - Ask the user for technology stack, project type, and development style if not provided\n2. **Research awesome-copilot patterns**:\n   - Use the fetch tool to explore awesome-copilot directories\n   - Check instructions: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Finstructions\n   - Check agents: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fagents (especially for matching expert agents)\n   - Check skills: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fskills\n   - Document all sources for attribution comments\n3. **Create the directory structure**\n4. **Generate main copilot-instructions.md** with project-wide standards\n5. **Create language-specific instruction files** using awesome-copilot references with attribution\n6. **Generate reusable skills** tailored to project needs\n7. **Set up specialized agents**, fetching from awesome-copilot where applicable (especially for expert engineer agents matching the tech stack)\n8. **Create the GitHub Actions workflow for Coding Agent** (`copilot-setup-steps.yml`) — skip if user does not use GitHub Actions\n9. **Validate** all files follow proper formatting and include necessary frontmatter\n\n## Post-Setup Instructions\n\nAfter creating all files, provide the user with:\n\n1. **VS Code setup instructions** - How to enable and configure the files\n2. **Usage examples** - How to use each skill and agent\n3. **Customization tips** - How to modify files for their specific needs\n4. **Testing recommendations** - How to verify the setup works correctly\n\n## Quality Checklist\n\nBefore completing, verify:\n- [ ] All authored Copilot markdown files have proper YAML frontmatter where required\n- [ ] Language-specific best practices are included\n- [ ] Files reference each other appropriately using Markdown links\n- [ ] Skills and agents include relevant descriptions; include MCP\u002Ftool-related metadata only when the target Copilot environment actually supports or requires it\n- [ ] Instructions are comprehensive but not overwhelming\n- [ ] Security and performance considerations are addressed\n- [ ] Testing guidelines are included\n- [ ] Documentation standards are clear\n- [ ] Code review standards are defined\n\n## Workflow Template Structure (only if GitHub Actions is used)\n\nThe `copilot-setup-steps.yml` workflow MUST follow this exact format and KEEP IT SIMPLE:\n\n```yaml\nname: \"Copilot Setup Steps\"\non:\n  workflow_dispatch:\n  push:\n    paths:\n      - .github\u002Fworkflows\u002Fcopilot-setup-steps.yml\n  pull_request:\n    paths:\n      - .github\u002Fworkflows\u002Fcopilot-setup-steps.yml\njobs:\n  # The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.\n  copilot-setup-steps:\n    runs-on: ubuntu-latest\n    permissions:\n      contents: read\n    steps:\n      - name: Checkout code\n        uses: actions\u002Fcheckout@v5\n      # Add ONLY basic technology-specific setup steps here\n```\n\n**KEEP WORKFLOWS SIMPLE** - Only include essential steps:\n\n**Node.js\u002FJavaScript:**\n```yaml\n- name: Set up Node.js\n  uses: actions\u002Fsetup-node@v4\n  with:\n    node-version: \"20\"\n    cache: \"npm\"\n- name: Install dependencies\n  run: npm ci\n- name: Run linter\n  run: npm run lint\n- name: Run tests\n  run: npm test\n```\n\n**Python:**\n```yaml\n- name: Set up Python\n  uses: actions\u002Fsetup-python@v4\n  with:\n    python-version: \"3.11\"\n- name: Install dependencies\n  run: pip install -r requirements.txt\n- name: Run linter\n  run: flake8 .\n- name: Run tests\n  run: pytest\n```\n\n**Java:**\n```yaml\n- name: Set up JDK\n  uses: actions\u002Fsetup-java@v4\n  with:\n    java-version: \"17\"\n    distribution: \"temurin\"\n- name: Build with Maven\n  run: mvn compile\n- name: Run tests\n  run: mvn test\n```\n\n**AVOID in workflows:**\n- ❌ Complex configuration setups\n- ❌ Multiple environment configurations\n- ❌ Advanced tooling setup\n- ❌ Custom scripts or complex logic\n- ❌ Multiple package managers\n- ❌ Database setup or external services\n\n**INCLUDE only:**\n- ✅ Language\u002Fruntime setup\n- ✅ Basic dependency installation\n- ✅ Simple linting (if standard)\n- ✅ Basic test running\n- ✅ Standard build commands\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fgithub-copilot-starter",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add github\u002Fawesome-copilot --skill github-copilot-starter",{"tool":54,"command":55},"bunx","bunx skills add github\u002Fawesome-copilot --skill github-copilot-starter",{"tool":57,"command":58},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill github-copilot-starter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-copilot-starter\u002FSKILL.md",true,[],[63,97,123,153,187,204],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":77,"publishedAt":33},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[69,74],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":75,"categoryName":76,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000023","Skill与智能体开发",[78,79,80,81,29,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96],"supabase","rls","supabase rls","supabase rls policies","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"publishedAt":33},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[103],{"categoryNo":75,"categoryName":76,"taxonomyType":72,"taxonomyTypeDesc":73},[105,106,107,23,108,109,31,110,111,112,113,114,115,116,117,118,119,120,121,122],"distribution","skill distribution audit","audit","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":135,"publishedAt":33},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[130],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[136,137,138,139,140,141,31,29,142,143,144,145,146,147,148,93,149,150,151,152],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":164,"publishedAt":33},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[160,163],{"categoryNo":161,"categoryName":162,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},[165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,82,180,181,182,183,184,31,185,186],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":200,"publishedAt":33},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[195,196,199],{"categoryNo":161,"categoryName":162,"taxonomyType":72,"taxonomyTypeDesc":73},{"categoryNo":197,"categoryName":198,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":75,"categoryName":76,"taxonomyType":72,"taxonomyTypeDesc":73},[201,23,174,202,203],"resemble detect","https","identity",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":208,"sourceHtmlUrl":209,"categories":210,"keywords":215,"publishedAt":33},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[211,214],{"categoryNo":212,"categoryName":213,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":75,"categoryName":76,"taxonomyType":72,"taxonomyTypeDesc":73},[216,217,218,219,137,83,9,107,220,221,202,222,223,224,225,226,227,228,229,230,231,232,91,233,234,235,236],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]