Merge branch 'github:main' into langchain-python
This commit is contained in:
Akash Kumar Shaw
GitHub
commit
b842c5a17c
@ -786,8 +786,18 @@
|
||||
"contributions": [
|
||||
"code"
|
||||
]
|
||||
},
|
||||
{
|
||||
"login": "soderlind",
|
||||
"name": "Per Søderlind",
|
||||
"avatar_url": "https://avatars.githubusercontent.com/u/1649452?v=4",
|
||||
"profile": "https://soderlind.no",
|
||||
"contributions": [
|
||||
"code"
|
||||
]
|
||||
}
|
||||
],
|
||||
"contributorsPerLine": 7,
|
||||
"linkToUsage": true
|
||||
"linkToUsage": true,
|
||||
"commitType": "docs"
|
||||
}
|
||||
|
||||
@ -57,6 +57,10 @@
|
||||
"type": "string",
|
||||
"description": "Type of the item",
|
||||
"enum": ["prompt", "instruction", "chat-mode"]
|
||||
},
|
||||
"usage": {
|
||||
"type": "string",
|
||||
"description": "Optional usage context for the item"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -152,7 +152,7 @@ display:
|
||||
|
||||
1. **Fork this repository**
|
||||
2. **Create a new branch** for your contribution
|
||||
3. **Add your instruction or prompt file** following the guidelines above
|
||||
3. **Add your instruction, prompt file, chatmode, or collection** following the guidelines above
|
||||
4. **Run the update script** (optional): `node update-readme.js` to update the README with your new file
|
||||
- A GitHub Actions workflow will verify that this step was performed correctly
|
||||
- If the README.md would be modified by running the script, the PR check will fail with a comment showing the required changes
|
||||
|
||||
@ -40,7 +40,7 @@ Custom chat modes define specific behaviors and tools for GitHub Copilot Chat, e
|
||||
| [Expert C++ software engineer mode instructions](chatmodes/expert-cpp-software-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-cpp-software-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-cpp-software-engineer.chatmode.md) | Provide expert C++ software engineering guidance using modern C++ and industry best practices. |
|
||||
| [Expert React Frontend Engineer Mode Instructions](chatmodes/expert-react-frontend-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-react-frontend-engineer.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fexpert-react-frontend-engineer.chatmode.md) | Provide expert React frontend engineering guidance using modern TypeScript and design patterns. |
|
||||
| [Gilfoyle Code Review Mode](chatmodes/gilfoyle.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fgilfoyle.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fgilfoyle.chatmode.md) | Code review and analysis with the sardonic wit and technical elitism of Bertram Gilfoyle from Silicon Valley. Prepare for brutal honesty about your code. |
|
||||
| [High-Level Big Picture Architect (HLBPA)](chatmodes/hlbpa.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fhlbpa.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fhlbpa.chatmode.md) | HLBPA: Your perfect AI chat mode for high-level architectural documentation and review. Perfect for targeted updates after a story or researching that legacy system when nobody remembers what it's supposed to be doing. |
|
||||
| [High-Level Big Picture Architect (HLBPA)](chatmodes/hlbpa.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fhlbpa.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fhlbpa.chatmode.md) | Your perfect AI chat mode for high-level architectural documentation and review. Perfect for targeted updates after a story or researching that legacy system when nobody remembers what it's supposed to be doing. |
|
||||
| [Idea Generator mode instructions](chatmodes/simple-app-idea-generator.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsimple-app-idea-generator.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fsimple-app-idea-generator.chatmode.md) | Brainstorm and develop new application ideas through fun, interactive questioning until ready for specification creation. |
|
||||
| [Implementation Plan Generation Mode](chatmodes/implementation-plan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fimplementation-plan.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fimplementation-plan.chatmode.md) | Generate an implementation plan for new features or refactoring existing code. |
|
||||
| [Kusto Assistant: Azure Data Explorer (Kusto) Engineering Assistant](chatmodes/kusto-assistant.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fkusto-assistant.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fkusto-assistant.chatmode.md) | Expert KQL assistant for live Azure Data Explorer analysis via Azure MCP server |
|
||||
|
||||
@ -25,5 +25,6 @@ Curated collections of related prompts, instructions, and chat modes organized a
|
||||
| [Power Apps Code Apps Development](collections/power-apps-code-apps.md) | Complete toolkit for Power Apps Code Apps development including project scaffolding, development standards, and expert guidance for building code-first applications with Power Platform integration. | 3 items | power-apps, power-platform, typescript, react, code-apps, dataverse, connectors |
|
||||
| [Project Planning & Management](collections/project-planning.md) | Tools and guidance for software project planning, feature breakdown, epic management, implementation planning, and task organization for development teams. | 17 items | planning, project-management, epic, feature, implementation, task, architecture, technical-spike |
|
||||
| [Security & Code Quality](collections/security-best-practices.md) | Security frameworks, accessibility guidelines, performance optimization, and code quality best practices for building secure, maintainable, and high-performance applications. | 6 items | security, accessibility, performance, code-quality, owasp, a11y, optimization, best-practices |
|
||||
| [Tasks by microsoft/edge-ai](collections/edge-ai-tasks.md) | Task Researcher and Task Planner for intermediate to expert users and large codebases - Brought to you by microsoft/edge-ai | 3 items | architecture, planning, research, tasks, implementation |
|
||||
| [Technical Spike](collections/technical-spike.md) | Tools for creation, management and research of technical spikes to reduce unknowns and assumptions before proceeding to specification and implementation of solutions. | 2 items | technical-spike, assumption-testing, validation, research |
|
||||
| [Testing & Test Automation](collections/testing-automation.md) | Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies. | 11 items | testing, tdd, automation, unit-tests, integration, playwright, jest, nunit |
|
||||
|
||||
@ -20,6 +20,7 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
|
||||
| [Angular Development Instructions](instructions/angular.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fangular.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fangular.instructions.md) | Angular-specific coding standards and best practices |
|
||||
| [Ansible Conventions and Best Practices](instructions/ansible.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fansible.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fansible.instructions.md) | Ansible conventions and best practices |
|
||||
| [ASP.NET REST API Development](instructions/aspnet-rest-apis.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Faspnet-rest-apis.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Faspnet-rest-apis.instructions.md) | Guidelines for building REST APIs with ASP.NET |
|
||||
| [Astro Development Instructions](instructions/astro.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fastro.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fastro.instructions.md) | Astro development standards and best practices for content-driven websites |
|
||||
| [Azure DevOps Pipeline YAML Best Practices](instructions/azure-devops-pipelines.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-devops-pipelines.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-devops-pipelines.instructions.md) | Best practices for Azure DevOps Pipeline YAML files |
|
||||
| [Azure Functions Typescript](instructions/azure-functions-typescript.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-functions-typescript.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-functions-typescript.instructions.md) | TypeScript patterns for Azure Functions |
|
||||
| [Azure Logic Apps and Power Automate Instructions](instructions/azure-logic-apps-power-automate.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-logic-apps-power-automate.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fazure-logic-apps-power-automate.instructions.md) | Guidelines for developing Azure Logic Apps and Power Automate workflows with best practices for Workflow Definition Language (WDL), integration patterns, and enterprise automation |
|
||||
@ -88,6 +89,7 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
|
||||
| [Spec Driven Workflow v1](instructions/spec-driven-workflow-v1.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fspec-driven-workflow-v1.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fspec-driven-workflow-v1.instructions.md) | Specification-Driven Workflow v1 provides a structured approach to software development, ensuring that requirements are clearly defined, designs are meticulously planned, and implementations are thoroughly documented and validated. |
|
||||
| [Spring Boot Development](instructions/springboot.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fspringboot.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fspringboot.instructions.md) | Guidelines for building Spring Boot base applications |
|
||||
| [SQL Development](instructions/sql-sp-generation.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fsql-sp-generation.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fsql-sp-generation.instructions.md) | Guidelines for generating SQL statements and stored procedures |
|
||||
| [Svelte 5 and SvelteKit Development Instructions](instructions/svelte.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fsvelte.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fsvelte.instructions.md) | Svelte 5 and SvelteKit development standards and best practices for component-based user interfaces and full-stack applications |
|
||||
| [Taming Copilot](instructions/taming-copilot.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftaming-copilot.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftaming-copilot.instructions.md) | Prevent Copilot from wreaking havoc across your codebase, keeping it under control. |
|
||||
| [TanStack Start with Shadcn/ui Development Guide](instructions/tanstack-start-shadcn-tailwind.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftanstack-start-shadcn-tailwind.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftanstack-start-shadcn-tailwind.instructions.md) | Guidelines for building TanStack Start applications |
|
||||
| [Task Plan Implementation Instructions](instructions/task-implementation.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftask-implementation.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftask-implementation.instructions.md) | Instructions for implementing task plans with progressive tracking and change record - Brought to you by microsoft/edge-ai |
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
[](https://aka.ms/awesome-github-copilot)
|
||||
<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
|
||||
[](#contributors-)
|
||||
[](#contributors-)
|
||||
<!-- ALL-CONTRIBUTORS-BADGE:END -->
|
||||
|
||||
A curated collection of prompts, instructions, and chat modes to supercharge your GitHub Copilot experience across different domains, languages, and use cases.
|
||||
@ -234,6 +234,7 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://linktr.ee/lukemurray"><img src="https://avatars.githubusercontent.com/u/24467442?v=4?s=100" width="100px;" alt="Luke Murray"/><br /><sub><b>Luke Murray</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=lukemurraynz" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://marknoble.com/"><img src="https://avatars.githubusercontent.com/u/3819700?v=4?s=100" width="100px;" alt="Mark Noble"/><br /><sub><b>Mark Noble</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=marknoble" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://soderlind.no"><img src="https://avatars.githubusercontent.com/u/1649452?v=4?s=100" width="100px;" alt="Per Søderlind"/><br /><sub><b>Per Søderlind</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=soderlind" title="Code">💻</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
<tfoot>
|
||||
|
||||
@ -1,21 +1,21 @@
|
||||
---
|
||||
description: 'HLBPA: Your perfect AI chat mode for high-level architectural documentation and review. Perfect for targeted updates after a story or researching that legacy system when nobody remembers what it's supposed to be doing.'
|
||||
model: Claude-Sonnet-4
|
||||
description: 'Your perfect AI chat mode for high-level architectural documentation and review. Perfect for targeted updates after a story or researching that legacy system when nobody remembers what it's supposed to be doing.'
|
||||
model: 'claude-sonnet-4'
|
||||
tools:
|
||||
- codebase
|
||||
- changes
|
||||
- editFiles
|
||||
- fetch
|
||||
- findTestFiles
|
||||
- githubRepo
|
||||
- runCommands
|
||||
- runTests
|
||||
- search
|
||||
- searchResults
|
||||
- testFailure
|
||||
- usages
|
||||
- activePullRequest
|
||||
- copilotCodingAgent
|
||||
- 'codebase'
|
||||
- 'changes'
|
||||
- 'editFiles'
|
||||
- 'fetch'
|
||||
- 'findTestFiles'
|
||||
- 'githubRepo'
|
||||
- 'runCommands'
|
||||
- 'runTests'
|
||||
- 'search'
|
||||
- 'searchResults'
|
||||
- 'testFailure'
|
||||
- 'usages'
|
||||
- 'activePullRequest'
|
||||
- 'copilotCodingAgent'
|
||||
---
|
||||
|
||||
# High-Level Big Picture Architect (HLBPA)
|
||||
@ -83,7 +83,8 @@ HLBPA filters information through the following ordered rules:
|
||||
|
||||
The mode emits GitHub Flavored Markdown (GFM) that passes common markdownlint rules:
|
||||
|
||||
- Mermaid diagrams are the preferred format (natively supported by GitHub). Mermaid supports comprehensive diagram types including flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, C4 diagrams, and more. Any other formats (ASCII art, PlantUML, Graphviz, etc.) will be flagged as unsupported.
|
||||
|
||||
- **Only Mermaid diagrams are supported.** Any other formats (ASCII art, ANSI, PlantUML, Graphviz, etc.) are strongly discouraged. All diagrams should be in Mermaid format.
|
||||
|
||||
- Primary file lives at `#docs/ARCHITECTURE_OVERVIEW.md` (or caller‑supplied name).
|
||||
|
||||
@ -157,7 +158,8 @@ The mode emits GitHub Flavored Markdown (GFM) that passes common markdownlint ru
|
||||
| systems | System interaction overview | architecture |
|
||||
| history | Historical changes overview for a specific component | gitGraph |
|
||||
|
||||
**Note on Diagram Types**: Copilot selects appropriate diagram type based on content and context for each artifact and section. Users can specify diagram types explicitly to override it's selection.
|
||||
|
||||
**Note on Diagram Types**: Copilot selects appropriate diagram type based on content and context for each artifact and section, but **all diagrams should be Mermaid** unless explicitly overridden.
|
||||
|
||||
**Note on Inline vs External Diagrams**:
|
||||
|
||||
|
||||
90
collections/edge-ai-tasks.collection.yml
Normal file
90
collections/edge-ai-tasks.collection.yml
Normal file
@ -0,0 +1,90 @@
|
||||
id: edge-ai-tasks
|
||||
name: Tasks by microsoft/edge-ai
|
||||
description: Task Researcher and Task Planner for intermediate to expert users and large codebases - Brought to you by microsoft/edge-ai
|
||||
tags: [architecture, planning, research, tasks, implementation]
|
||||
items:
|
||||
# Planning Chat Modes
|
||||
- path: chatmodes/task-researcher.chatmode.md
|
||||
kind: chat-mode
|
||||
usage: |
|
||||
Now you can iterate on research for your tasks!
|
||||
|
||||
```markdown, research.prompt.md
|
||||
---
|
||||
mode: task-researcher
|
||||
title: Research microsoft fabric realtime intelligence terraform support
|
||||
---
|
||||
Review the microsoft documentation for fabric realtime intelligence
|
||||
and come up with ideas on how to implement this support into our terraform components.
|
||||
```
|
||||
|
||||
Research is dumped out into a .copilot-tracking/research/*-research.md file and will include discoveries for GHCP along with examples and schema that will be useful during implementation.
|
||||
|
||||
Also, task-researcher will provide additional ideas for implementation which you can work with GitHub Copilot on selecting the right one to focus on.
|
||||
|
||||
- path: chatmodes/task-planner.chatmode.md
|
||||
kind: chat-mode
|
||||
usage: |
|
||||
Also, task-researcher will provide additional ideas for implementation which you can work with GitHub Copilot on selecting the right one to focus on.
|
||||
|
||||
```markdown, task-plan.prompt.md
|
||||
---
|
||||
mode: task-planner
|
||||
title: Plan microsoft fabric realtime intelligence terraform support
|
||||
---
|
||||
#file: .copilot-tracking/research/*-fabric-rti-blueprint-modification-research.md
|
||||
Build a plan to support adding fabric rti to this project
|
||||
```
|
||||
|
||||
`task-planner` will help you create a plan for implementing your task(s). It will use your fully researched ideas or build new research if not already provided.
|
||||
|
||||
`task-planner` will produce three (3) files that will be used by `task-implementation.instructions.md`.
|
||||
|
||||
* `.copilot-tracking/plan/*-plan.instructions.md`
|
||||
|
||||
* A newly generated instructions file that has the plan as a checklist of Phases and Tasks.
|
||||
* `.copilot-tracking/details/*-details.md`
|
||||
|
||||
* The details for the implementation, the plan file refers to this file for specific details (important if you have a big plan).
|
||||
* `.copilot-tracking/prompts/implement-*.prompt.md`
|
||||
|
||||
* A newly generated prompt file that will create a `.copilot-tracking/changes/*-changes.md` file and proceed to implement the changes.
|
||||
|
||||
Continue to use `task-planner` to iterate on the plan until you have exactly what you want done to your codebase.
|
||||
|
||||
# Planning Instructions
|
||||
- path: instructions/task-implementation.instructions.md
|
||||
kind: instruction
|
||||
usage: |
|
||||
Continue to use `task-planner` to iterate on the plan until you have exactly what you want done to your codebase.
|
||||
|
||||
When you are ready to implement the plan, **create a new chat** and switch to `Agent` mode then fire off the newly generated prompt.
|
||||
|
||||
```markdown, implement-fabric-rti-changes.prompt.md
|
||||
---
|
||||
mode: agent
|
||||
title: Implement microsoft fabric realtime intelligence terraform support
|
||||
---
|
||||
/implement-fabric-rti-blueprint-modification phaseStop=true
|
||||
```
|
||||
|
||||
This prompt has the added benefit of attaching the plan as instructions, which helps with keeping the plan in context throughout the whole conversation.
|
||||
|
||||
**Expert Warning** ->>Use `phaseStop=false` to have Copilot implement the whole plan without stopping. Additionally, you can use `taskStop=true` to have Copilot stop after every Task implementation for finer detail control.
|
||||
|
||||
To use these generated instructions and prompts, you'll need to update your `settings.json` accordingly:
|
||||
|
||||
```json
|
||||
"chat.instructionsFilesLocations": {
|
||||
// Existing instructions folders...
|
||||
".copilot-tracking/plans": true
|
||||
},
|
||||
"chat.promptFilesLocations": {
|
||||
// Existing prompts folders...
|
||||
".copilot-tracking/prompts": true
|
||||
},
|
||||
```
|
||||
|
||||
display:
|
||||
ordering: alpha # or "manual" to preserve the order above
|
||||
show_badge: false # set to true to show collection badge on items
|
||||
100
collections/edge-ai-tasks.md
Normal file
100
collections/edge-ai-tasks.md
Normal file
@ -0,0 +1,100 @@
|
||||
# Tasks by microsoft/edge-ai
|
||||
|
||||
Task Researcher and Task Planner for intermediate to expert users and large codebases - Brought to you by microsoft/edge-ai
|
||||
|
||||
**Tags:** architecture, planning, research, tasks, implementation
|
||||
|
||||
## Items in this Collection
|
||||
|
||||
| Title | Type | Description |
|
||||
| ----- | ---- | ----------- |
|
||||
| [Task Researcher Instructions](../chatmodes/task-researcher.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftask-researcher.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftask-researcher.chatmode.md) | Chat Mode | Task research specialist for comprehensive project analysis - Brought to you by microsoft/edge-ai [see usage](#task-researcher-instructions) |
|
||||
| [Task Planner Instructions](../chatmodes/task-planner.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftask-planner.chatmode.md)<br />[](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Ftask-planner.chatmode.md) | Chat Mode | Task planner for creating actionable implementation plans - Brought to you by microsoft/edge-ai [see usage](#task-planner-instructions) |
|
||||
| [Task Plan Implementation Instructions](../instructions/task-implementation.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftask-implementation.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Ftask-implementation.instructions.md) | Instruction | Instructions for implementing task plans with progressive tracking and change record - Brought to you by microsoft/edge-ai [see usage](#task-plan-implementation-instructions) |
|
||||
|
||||
## Collection Usage
|
||||
|
||||
### Task Researcher Instructions
|
||||
|
||||
Now you can iterate on research for your tasks!
|
||||
|
||||
```markdown, research.prompt.md
|
||||
---
|
||||
mode: task-researcher
|
||||
title: Research microsoft fabric realtime intelligence terraform support
|
||||
---
|
||||
Review the microsoft documentation for fabric realtime intelligence
|
||||
and come up with ideas on how to implement this support into our terraform components.
|
||||
```
|
||||
|
||||
Research is dumped out into a .copilot-tracking/research/*-research.md file and will include discoveries for GHCP along with examples and schema that will be useful during implementation.
|
||||
|
||||
Also, task-researcher will provide additional ideas for implementation which you can work with GitHub Copilot on selecting the right one to focus on.
|
||||
|
||||
---
|
||||
|
||||
### Task Planner Instructions
|
||||
|
||||
Also, task-researcher will provide additional ideas for implementation which you can work with GitHub Copilot on selecting the right one to focus on.
|
||||
|
||||
```markdown, task-plan.prompt.md
|
||||
---
|
||||
mode: task-planner
|
||||
title: Plan microsoft fabric realtime intelligence terraform support
|
||||
---
|
||||
#file: .copilot-tracking/research/*-fabric-rti-blueprint-modification-research.md
|
||||
Build a plan to support adding fabric rti to this project
|
||||
```
|
||||
|
||||
`task-planner` will help you create a plan for implementing your task(s). It will use your fully researched ideas or build new research if not already provided.
|
||||
|
||||
`task-planner` will produce three (3) files that will be used by `task-implementation.instructions.md`.
|
||||
|
||||
* `.copilot-tracking/plan/*-plan.instructions.md`
|
||||
|
||||
* A newly generated instructions file that has the plan as a checklist of Phases and Tasks.
|
||||
* `.copilot-tracking/details/*-details.md`
|
||||
|
||||
* The details for the implementation, the plan file refers to this file for specific details (important if you have a big plan).
|
||||
* `.copilot-tracking/prompts/implement-*.prompt.md`
|
||||
|
||||
* A newly generated prompt file that will create a `.copilot-tracking/changes/*-changes.md` file and proceed to implement the changes.
|
||||
|
||||
Continue to use `task-planner` to iterate on the plan until you have exactly what you want done to your codebase.
|
||||
|
||||
---
|
||||
|
||||
### Task Plan Implementation Instructions
|
||||
|
||||
Continue to use `task-planner` to iterate on the plan until you have exactly what you want done to your codebase.
|
||||
|
||||
When you are ready to implement the plan, **create a new chat** and switch to `Agent` mode then fire off the newly generated prompt.
|
||||
|
||||
```markdown, implement-fabric-rti-changes.prompt.md
|
||||
---
|
||||
mode: agent
|
||||
title: Implement microsoft fabric realtime intelligence terraform support
|
||||
---
|
||||
/implement-fabric-rti-blueprint-modification phaseStop=true
|
||||
```
|
||||
|
||||
This prompt has the added benefit of attaching the plan as instructions, which helps with keeping the plan in context throughout the whole conversation.
|
||||
|
||||
**Expert Warning** ->>Use `phaseStop=false` to have Copilot implement the whole plan without stopping. Additionally, you can use `taskStop=true` to have Copilot stop after every Task implementation for finer detail control.
|
||||
|
||||
To use these generated instructions and prompts, you'll need to update your `settings.json` accordingly:
|
||||
|
||||
```json
|
||||
"chat.instructionsFilesLocations": {
|
||||
// Existing instructions folders...
|
||||
".copilot-tracking/plans": true
|
||||
},
|
||||
"chat.promptFilesLocations": {
|
||||
// Existing prompts folders...
|
||||
".copilot-tracking/prompts": true
|
||||
},
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
*This collection includes 3 curated items for tasks by microsoft/edge-ai.*
|
||||
182
instructions/astro.instructions.md
Normal file
182
instructions/astro.instructions.md
Normal file
@ -0,0 +1,182 @@
|
||||
---
|
||||
description: 'Astro development standards and best practices for content-driven websites'
|
||||
applyTo: '**/*.astro, **/*.ts, **/*.js, **/*.md, **/*.mdx'
|
||||
---
|
||||
|
||||
# Astro Development Instructions
|
||||
|
||||
Instructions for building high-quality Astro applications following the content-driven, server-first architecture with modern best practices.
|
||||
|
||||
## Project Context
|
||||
- Astro 5.x with Islands Architecture and Content Layer API
|
||||
- TypeScript for type safety and better DX with auto-generated types
|
||||
- Content-driven websites (blogs, marketing, e-commerce, documentation)
|
||||
- Server-first rendering with selective client-side hydration
|
||||
- Support for multiple UI frameworks (React, Vue, Svelte, Solid, etc.)
|
||||
- Static site generation (SSG) by default with optional server-side rendering (SSR)
|
||||
- Enhanced performance with modern content loading and build optimizations
|
||||
|
||||
## Development Standards
|
||||
|
||||
### Architecture
|
||||
- Embrace the Islands Architecture: server-render by default, hydrate selectively
|
||||
- Organize content with Content Collections for type-safe Markdown/MDX management
|
||||
- Structure projects by feature or content type for scalability
|
||||
- Use component-based architecture with clear separation of concerns
|
||||
- Implement progressive enhancement patterns
|
||||
- Follow Multi-Page App (MPA) approach over Single-Page App (SPA) patterns
|
||||
|
||||
### TypeScript Integration
|
||||
- Configure `tsconfig.json` with recommended v5.0 settings:
|
||||
```json
|
||||
{
|
||||
"extends": "astro/tsconfigs/base",
|
||||
"include": [".astro/types.d.ts", "**/*"],
|
||||
"exclude": ["dist"]
|
||||
}
|
||||
```
|
||||
- Types auto-generated in `.astro/types.d.ts` (replaces `src/env.d.ts`)
|
||||
- Run `astro sync` to generate/update type definitions
|
||||
- Define component props with TypeScript interfaces
|
||||
- Leverage auto-generated types for content collections and Content Layer API
|
||||
|
||||
### Component Design
|
||||
- Use `.astro` components for static, server-rendered content
|
||||
- Import framework components (React, Vue, Svelte) only when interactivity is needed
|
||||
- Follow Astro's component script structure: frontmatter at top, template below
|
||||
- Use meaningful component names following PascalCase convention
|
||||
- Keep components focused and composable
|
||||
- Implement proper prop validation and default values
|
||||
|
||||
### Content Collections
|
||||
|
||||
#### Modern Content Layer API (v5.0+)
|
||||
- Define collections in `src/content.config.ts` using the new Content Layer API
|
||||
- Use built-in loaders: `glob()` for file-based content, `file()` for single files
|
||||
- Leverage enhanced performance and scalability with the new loading system
|
||||
- Example with Content Layer API:
|
||||
```typescript
|
||||
import { defineCollection, z } from 'astro:content';
|
||||
import { glob } from 'astro/loaders';
|
||||
|
||||
const blog = defineCollection({
|
||||
loader: glob({ pattern: '**/*.md', base: './src/content/blog' }),
|
||||
schema: z.object({
|
||||
title: z.string(),
|
||||
pubDate: z.date(),
|
||||
tags: z.array(z.string()).optional()
|
||||
})
|
||||
});
|
||||
```
|
||||
|
||||
#### Legacy Collections (backward compatible)
|
||||
- Legacy `type: 'content'` collections still supported via automatic glob() implementation
|
||||
- Migrate existing collections by adding explicit `loader` configuration
|
||||
- Use type-safe queries with `getCollection()` and `getEntry()`
|
||||
- Structure content with frontmatter validation and auto-generated types
|
||||
|
||||
### View Transitions & Client-Side Routing
|
||||
- Enable with `<ClientRouter />` component in layout head (renamed from `<ViewTransitions />` in v5.0)
|
||||
- Import from `astro:transitions`: `import { ClientRouter } from 'astro:transitions'`
|
||||
- Provides SPA-like navigation without full page reloads
|
||||
- Customize transition animations with CSS and view-transition-name
|
||||
- Maintain state across page navigations with persistent islands
|
||||
- Use `transition:persist` directive to preserve component state
|
||||
|
||||
### Performance Optimization
|
||||
- Default to zero JavaScript - only add interactivity where needed
|
||||
- Use client directives strategically (`client:load`, `client:idle`, `client:visible`)
|
||||
- Implement lazy loading for images and components
|
||||
- Optimize static assets with Astro's built-in optimization
|
||||
- Leverage Content Layer API for faster content loading and builds
|
||||
- Minimize bundle size by avoiding unnecessary client-side JavaScript
|
||||
|
||||
### Styling
|
||||
- Use scoped styles in `.astro` components by default
|
||||
- Implement CSS preprocessing (Sass, Less) when needed
|
||||
- Use CSS custom properties for theming and design systems
|
||||
- Follow mobile-first responsive design principles
|
||||
- Ensure accessibility with semantic HTML and proper ARIA attributes
|
||||
- Consider utility-first frameworks (Tailwind CSS) for rapid development
|
||||
|
||||
### Client-Side Interactivity
|
||||
- Use framework components (React, Vue, Svelte) for interactive elements
|
||||
- Choose the right hydration strategy based on user interaction patterns
|
||||
- Implement state management within framework boundaries
|
||||
- Handle client-side routing carefully to maintain MPA benefits
|
||||
- Use Web Components for framework-agnostic interactivity
|
||||
- Share state between islands using stores or custom events
|
||||
|
||||
### API Routes and SSR
|
||||
- Create API routes in `src/pages/api/` for dynamic functionality
|
||||
- Use proper HTTP methods and status codes
|
||||
- Implement request validation and error handling
|
||||
- Enable SSR mode for dynamic content requirements
|
||||
- Use middleware for authentication and request processing
|
||||
- Handle environment variables securely
|
||||
|
||||
### SEO and Meta Management
|
||||
- Use Astro's built-in SEO components and meta tag management
|
||||
- Implement proper Open Graph and Twitter Card metadata
|
||||
- Generate sitemaps automatically for better search indexing
|
||||
- Use semantic HTML structure for better accessibility and SEO
|
||||
- Implement structured data (JSON-LD) for rich snippets
|
||||
- Optimize page titles and descriptions for search engines
|
||||
|
||||
### Image Optimization
|
||||
- Use Astro's `<Image />` component for automatic optimization
|
||||
- Implement responsive images with proper srcset generation
|
||||
- Use WebP and AVIF formats for modern browsers
|
||||
- Lazy load images below the fold
|
||||
- Provide proper alt text for accessibility
|
||||
- Optimize images at build time for better performance
|
||||
|
||||
### Data Fetching
|
||||
- Fetch data at build time in component frontmatter
|
||||
- Use dynamic imports for conditional data loading
|
||||
- Implement proper error handling for external API calls
|
||||
- Cache expensive operations during build process
|
||||
- Use Astro's built-in fetch with automatic TypeScript inference
|
||||
- Handle loading states and fallbacks appropriately
|
||||
|
||||
### Build & Deployment
|
||||
- Optimize static assets with Astro's built-in optimizations
|
||||
- Configure deployment for static (SSG) or hybrid (SSR) rendering
|
||||
- Use environment variables for configuration management
|
||||
- Enable compression and caching for production builds
|
||||
|
||||
## Key Astro v5.0 Updates
|
||||
|
||||
### Breaking Changes
|
||||
- **ClientRouter**: Use `<ClientRouter />` instead of `<ViewTransitions />`
|
||||
- **TypeScript**: Auto-generated types in `.astro/types.d.ts` (run `astro sync`)
|
||||
- **Content Layer API**: New `glob()` and `file()` loaders for enhanced performance
|
||||
|
||||
### Migration Example
|
||||
```typescript
|
||||
// Modern Content Layer API
|
||||
import { defineCollection, z } from 'astro:content';
|
||||
import { glob } from 'astro/loaders';
|
||||
|
||||
const blog = defineCollection({
|
||||
loader: glob({ pattern: '**/*.md', base: './src/content/blog' }),
|
||||
schema: z.object({ title: z.string(), pubDate: z.date() })
|
||||
});
|
||||
```
|
||||
|
||||
## Implementation Guidelines
|
||||
|
||||
### Development Workflow
|
||||
1. Use `npm create astro@latest` with TypeScript template
|
||||
2. Configure Content Layer API with appropriate loaders
|
||||
3. Set up TypeScript with `astro sync` for type generation
|
||||
4. Create layout components with Islands Architecture
|
||||
5. Implement content pages with SEO and performance optimization
|
||||
|
||||
### Astro-Specific Best Practices
|
||||
- **Islands Architecture**: Server-first with selective hydration using client directives
|
||||
- **Content Layer API**: Use `glob()` and `file()` loaders for scalable content management
|
||||
- **Zero JavaScript**: Default to static rendering, add interactivity only when needed
|
||||
- **View Transitions**: Enable SPA-like navigation with `<ClientRouter />`
|
||||
- **Type Safety**: Leverage auto-generated types from Content Collections
|
||||
- **Performance**: Optimize with built-in image optimization and minimal client bundles
|
||||
@ -7,7 +7,7 @@ applyTo: '**/*.{clj,cljs,cljc,bb,edn.mdx?}'
|
||||
|
||||
## Code Evaluation Tool usage
|
||||
|
||||
“Use the repl” means to use the **Evaluate Clojure Code** tool from Calva Backseat Driver. It connects you to the the same REPL as the user is connected to via Calva.
|
||||
“Use the repl” means to use the **Evaluate Clojure Code** tool from Calva Backseat Driver. It connects you to the same REPL as the user is connected to via Calva.
|
||||
|
||||
- Always stay inside Calva's REPL instead of launching a second one from the terminal.
|
||||
- If there is no REPL connection, ask the user to connect the REPL instead of trying to start and connect it yourself.
|
||||
@ -36,12 +36,67 @@ Docstrings belong immediately after the function name and before the argument ve
|
||||
|
||||
- Define functions before they are used—prefer ordering over `declare` except when truly necessary.
|
||||
|
||||
## Interactive Programming (a.k.a. REPL Driven Development)
|
||||
|
||||
### Align Data Structure Elements for Bracket Balancing
|
||||
**Always align multi-line elements vertically in all data structures: vectors, maps, lists, sets, all code (since Clojure code is data). Misalignment causes the bracket balancer to close brackets incorrectly, creating invalid forms.**
|
||||
|
||||
```clojure
|
||||
;; ❌ Wrong - misaligned vector elements
|
||||
(select-keys m [:key-a
|
||||
:key-b
|
||||
:key-c]) ; Misalignment → incorrect ] placement
|
||||
|
||||
;; ✅ Correct - aligned vector elements
|
||||
(select-keys m [:key-a
|
||||
:key-b
|
||||
:key-c]) ; Proper alignment → correct ] placement
|
||||
|
||||
;; ❌ Wrong - misaligned map entries
|
||||
{:name "Alice"
|
||||
:age 30
|
||||
:city "Oslo"} ; Misalignment → incorrect } placement
|
||||
|
||||
;; ✅ Correct - aligned map entries
|
||||
{:name "Alice"
|
||||
:age 30
|
||||
:city "Oslo"} ; Proper alignment → correct } placement
|
||||
```
|
||||
|
||||
**Critical**: The bracket balancer relies on consistent indentation to determine structure.
|
||||
|
||||
### REPL Dependency Management
|
||||
Use `clojure.repl.deps/add-libs` for dynamic dependency loading during REPL sessions.
|
||||
|
||||
```clojure
|
||||
(require '[clojure.repl.deps :refer [add-libs]])
|
||||
(add-libs '{dk.ative/docjure {:mvn/version "1.15.0"}})
|
||||
```
|
||||
|
||||
- Dynamic dependency loading requires Clojure 1.12 or later
|
||||
- Perfect for library exploration and prototyping
|
||||
|
||||
### Checking Clojure Version
|
||||
|
||||
```clojure
|
||||
*clojure-version*
|
||||
;; => {:major 1, :minor 12, :incremental 1, :qualifier nil}
|
||||
```
|
||||
|
||||
### REPL Availability Discipline
|
||||
|
||||
**Never edit code files when the REPL is unavailable.** When REPL evaluation returns errors indicating that the REPL is unavailable, stop immediately and inform the user. Let the user restore REPL before continuing.
|
||||
|
||||
#### Why This Matters
|
||||
- **Interactive Programming requires a working REPL** - You cannot verify behavior without evaluation
|
||||
- **Guessing creates bugs** - Code changes without testing introduce errors
|
||||
|
||||
## Structural Editing and REPL-First Habit
|
||||
- Develop changes in the REPL before touching files.
|
||||
- When editing Clojure files, always use structural editing tools such as **Insert Top Level Form**, **Replace Top Level Form**, **Create Clojure File**, and **Append Code**, and always read their instructions first.
|
||||
|
||||
### Creating New Files
|
||||
- Use the **Create Clojure File** tool, with initial content
|
||||
- Use the **Create Clojure File** tool with initial content
|
||||
- Follow Clojure naming rules: namespaces in kebab-case, file paths in matching snake_case (e.g., `my.project.ns` → `my/project/ns.clj`).
|
||||
|
||||
### Reloading Namespaces
|
||||
@ -51,22 +106,6 @@ After editing files, reload the edited namespace in the REPL so updated definiti
|
||||
(require 'my.namespace :reload)
|
||||
```
|
||||
|
||||
### Keeping Brackets Balanced
|
||||
If tools or the compiler signal bracket imbalance, stop and ask for help rather than guessing—use the human-input tool.
|
||||
|
||||
## Interactive Programming with REPL
|
||||
|
||||
When evaluating code during development, always show the complete code being evaluated in a code block before using evaluation tools. The code block should start with the appropriate `(in-ns ...)` form and contain the exact code being evaluated, so the human can run the same code in their REPL.
|
||||
|
||||
Example:
|
||||
```clojure
|
||||
(in-ns 'my.namespace)
|
||||
(let [test-data {:name "example"}]
|
||||
(process-data test-data))
|
||||
```
|
||||
|
||||
This applies to all REPL-driven development, whether using Calva, Joyride, or other Clojure evaluation tools.
|
||||
|
||||
## Code Indentation Before Evaluation
|
||||
Consistent indentation is crucial to help the bracket balancer.
|
||||
|
||||
@ -121,7 +160,7 @@ You can also use "inline def" when showing the user code in the chat, to make it
|
||||
|
||||
## Return values > print side effects
|
||||
|
||||
Prefer using the repl and return values from your evaluations, over printing things to stdout.
|
||||
Prefer using the REPL and return values from your evaluations, over printing things to stdout.
|
||||
|
||||
## Reading from `stdin`
|
||||
- When Clojure code uses `(read-line)`, it will prompt the user through VS Code.
|
||||
@ -272,9 +311,9 @@ Iterate with real data before editing files.
|
||||
```
|
||||
|
||||
#### Benefits
|
||||
- Verified behaviour before committing changes
|
||||
- Verified behavior before committing changes
|
||||
- Incremental development with immediate feedback
|
||||
- Tests that capture known-good behaviour
|
||||
- Tests that capture known-good behavior
|
||||
- Start new work with failing tests to lock in intent
|
||||
|
||||
### Test Naming and Messaging
|
||||
@ -307,3 +346,4 @@ Guidelines:
|
||||
## Happy Interactive Programming
|
||||
|
||||
Remember to prefer the REPL in your work. Keep in mind that the user does not see what you evaluate. Nor the results. Communicate with the user in the chat about what you evaluate and what you get back.
|
||||
|
||||
|
||||
@ -5,7 +5,8 @@ description: 'PowerShell cmdlet and scripting best practices based on Microsoft
|
||||
|
||||
# PowerShell Cmdlet Development Guidelines
|
||||
|
||||
This guide provides PowerShell-specific instructions to help GitHub Copilot generate idiomatic, safe, and maintainable scripts. It aligns with Microsoft’s PowerShell cmdlet development guidelines.
|
||||
This guide provides PowerShell-specific instructions to help GitHub Copilot generate idiomatic,
|
||||
safe, and maintainable scripts. It aligns with Microsoft’s PowerShell cmdlet development guidelines.
|
||||
|
||||
## Naming Conventions
|
||||
|
||||
@ -150,7 +151,7 @@ function Update-ResourceStatus {
|
||||
)
|
||||
|
||||
begin {
|
||||
Write-Verbose "Starting resource status update process"
|
||||
Write-Verbose 'Starting resource status update process'
|
||||
$timestamp = Get-Date
|
||||
}
|
||||
|
||||
@ -166,16 +167,16 @@ function Update-ResourceStatus {
|
||||
}
|
||||
|
||||
# Only output if PassThru is specified
|
||||
if ($PassThru) {
|
||||
if ($PassThru.IsPresent) {
|
||||
Write-Output $resource
|
||||
}
|
||||
}
|
||||
|
||||
end {
|
||||
Write-Verbose "Resource status update process completed"
|
||||
Write-Verbose 'Resource status update process completed'
|
||||
}
|
||||
}
|
||||
```
|
||||
```
|
||||
|
||||
## Error Handling and Safety
|
||||
|
||||
@ -198,6 +199,9 @@ function Update-ResourceStatus {
|
||||
- Return meaningful error messages
|
||||
- Use ErrorVariable when needed
|
||||
- Include proper terminating vs non-terminating error handling
|
||||
- In advanced functions with `[CmdletBinding()]`, prefer `$PSCmdlet.WriteError()` over `Write-Error`
|
||||
- In advanced functions with `[CmdletBinding()]`, prefer `$PSCmdlet.ThrowTerminatingError()` over `throw`
|
||||
- Construct proper ErrorRecord objects with category, target, and exception details
|
||||
|
||||
- **Non-Interactive Design:**
|
||||
- Accept input via parameters
|
||||
@ -220,7 +224,7 @@ function Remove-UserAccount {
|
||||
)
|
||||
|
||||
begin {
|
||||
Write-Verbose "Starting user account removal process"
|
||||
Write-Verbose 'Starting user account removal process'
|
||||
$ErrorActionPreference = 'Stop'
|
||||
}
|
||||
|
||||
@ -228,7 +232,13 @@ function Remove-UserAccount {
|
||||
try {
|
||||
# Validation
|
||||
if (-not (Test-UserExists -Username $Username)) {
|
||||
Write-Error "User account '$Username' not found"
|
||||
$errorRecord = [System.Management.Automation.ErrorRecord]::new(
|
||||
[System.Exception]::new("User account '$Username' not found"),
|
||||
'UserNotFound',
|
||||
[System.Management.Automation.ErrorCategory]::ObjectNotFound,
|
||||
$Username
|
||||
)
|
||||
$PSCmdlet.WriteError($errorRecord)
|
||||
return
|
||||
}
|
||||
|
||||
@ -241,19 +251,27 @@ function Remove-UserAccount {
|
||||
Remove-ADUser -Identity $Username -ErrorAction Stop
|
||||
Write-Warning "User account '$Username' has been removed"
|
||||
}
|
||||
}
|
||||
catch [Microsoft.ActiveDirectory.Management.ADException] {
|
||||
Write-Error "Active Directory error: $_"
|
||||
throw
|
||||
}
|
||||
catch {
|
||||
Write-Error "Unexpected error removing user account: $_"
|
||||
throw
|
||||
} catch [Microsoft.ActiveDirectory.Management.ADException] {
|
||||
$errorRecord = [System.Management.Automation.ErrorRecord]::new(
|
||||
$_.Exception,
|
||||
'ActiveDirectoryError',
|
||||
[System.Management.Automation.ErrorCategory]::NotSpecified,
|
||||
$Username
|
||||
)
|
||||
$PSCmdlet.ThrowTerminatingError($errorRecord)
|
||||
} catch {
|
||||
$errorRecord = [System.Management.Automation.ErrorRecord]::new(
|
||||
$_.Exception,
|
||||
'UnexpectedError',
|
||||
[System.Management.Automation.ErrorCategory]::NotSpecified,
|
||||
$Username
|
||||
)
|
||||
$PSCmdlet.ThrowTerminatingError($errorRecord)
|
||||
}
|
||||
}
|
||||
|
||||
end {
|
||||
Write-Verbose "User account removal process completed"
|
||||
Write-Verbose 'User account removal process completed'
|
||||
}
|
||||
}
|
||||
```
|
||||
@ -307,12 +325,12 @@ function New-Resource {
|
||||
)
|
||||
|
||||
begin {
|
||||
Write-Verbose "Starting resource creation process"
|
||||
Write-Verbose 'Starting resource creation process'
|
||||
}
|
||||
|
||||
process {
|
||||
try {
|
||||
if ($PSCmdlet.ShouldProcess($Name, "Create new resource")) {
|
||||
if ($PSCmdlet.ShouldProcess($Name, 'Create new resource')) {
|
||||
# Resource creation logic here
|
||||
Write-Output ([PSCustomObject]@{
|
||||
Name = $Name
|
||||
@ -320,14 +338,19 @@ function New-Resource {
|
||||
Created = Get-Date
|
||||
})
|
||||
}
|
||||
}
|
||||
catch {
|
||||
Write-Error "Failed to create resource: $_"
|
||||
} catch {
|
||||
$errorRecord = [System.Management.Automation.ErrorRecord]::new(
|
||||
$_.Exception,
|
||||
'ResourceCreationFailed',
|
||||
[System.Management.Automation.ErrorCategory]::NotSpecified,
|
||||
$Name
|
||||
)
|
||||
$PSCmdlet.ThrowTerminatingError($errorRecord)
|
||||
}
|
||||
}
|
||||
|
||||
end {
|
||||
Write-Verbose "Completed resource creation process"
|
||||
Write-Verbose 'Completed resource creation process'
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
161
instructions/svelte.instructions.md
Normal file
161
instructions/svelte.instructions.md
Normal file
@ -0,0 +1,161 @@
|
||||
---
|
||||
description: 'Svelte 5 and SvelteKit development standards and best practices for component-based user interfaces and full-stack applications'
|
||||
applyTo: '**/*.svelte, **/*.ts, **/*.js, **/*.css, **/*.scss, **/*.json'
|
||||
---
|
||||
|
||||
# Svelte 5 and SvelteKit Development Instructions
|
||||
|
||||
Instructions for building high-quality Svelte 5 and SvelteKit applications with modern runes-based reactivity, TypeScript, and performance optimization.
|
||||
|
||||
## Project Context
|
||||
- Svelte 5.x with runes system ($state, $derived, $effect, $props, $bindable)
|
||||
- SvelteKit for full-stack applications with file-based routing
|
||||
- TypeScript for type safety and better developer experience
|
||||
- Component-scoped styling with CSS custom properties
|
||||
- Progressive enhancement and performance-first approach
|
||||
- Modern build tooling (Vite) with optimizations
|
||||
|
||||
## Development Standards
|
||||
|
||||
### Architecture
|
||||
- Use Svelte 5 runes system for all reactivity instead of legacy stores
|
||||
- Organize components by feature or domain for scalability
|
||||
- Separate presentation components from logic-heavy components
|
||||
- Extract reusable logic into composable functions
|
||||
- Implement proper component composition with slots and snippets
|
||||
- Use SvelteKit's file-based routing with proper load functions
|
||||
|
||||
### TypeScript Integration
|
||||
- Enable strict mode in `tsconfig.json` for maximum type safety
|
||||
- Define interfaces for component props using `$props()` syntax
|
||||
- Type event handlers, refs, and SvelteKit's generated types
|
||||
- Use generic types for reusable components
|
||||
- Leverage `$types.ts` files generated by SvelteKit
|
||||
- Implement proper type checking with `svelte-check`
|
||||
|
||||
### Component Design
|
||||
- Follow single responsibility principle for components
|
||||
- Use `<script lang="ts">` with runes syntax as default
|
||||
- Keep components small and focused on one concern
|
||||
- Implement proper prop validation with TypeScript
|
||||
- Use slots and snippets for flexible composition
|
||||
- Design components to be testable and reusable
|
||||
|
||||
### Svelte 5 Runes System
|
||||
- Use `$state()` for reactive local state management
|
||||
- Implement `$derived()` for computed values and expensive calculations
|
||||
- Use `$effect()` for side effects with proper cleanup
|
||||
- Define component props with `$props()` and destructuring
|
||||
- Use `$bindable()` for two-way data binding between components
|
||||
- Migrate from legacy stores to runes for better performance
|
||||
|
||||
### State Management
|
||||
- Use `$state()` for local component state
|
||||
- Implement context API with `setContext`/`getContext` for shared state
|
||||
- Use SvelteKit stores for global application state when needed
|
||||
- Keep state normalized for complex data structures
|
||||
- Use derived state for computed values
|
||||
- Implement proper state persistence for client-side data
|
||||
|
||||
### SvelteKit Patterns
|
||||
- Use `+page.svelte` for page components with proper SEO
|
||||
- Implement `+layout.svelte` for shared layouts and navigation
|
||||
- Use `+page.server.ts` for server-side data loading and API calls
|
||||
- Implement form actions in `+page.server.ts` for data mutations
|
||||
- Use `+server.ts` for API endpoints and server-side logic
|
||||
- Handle routing with SvelteKit's file-based system
|
||||
|
||||
### Styling
|
||||
- Use component-scoped styles with `<style>` blocks
|
||||
- Implement CSS custom properties for theming and design systems
|
||||
- Use `class:` directive for conditional styling
|
||||
- Follow BEM or utility-first CSS conventions
|
||||
- Implement responsive design with mobile-first approach
|
||||
- Use `:global()` sparingly for truly global styles
|
||||
|
||||
### Performance Optimization
|
||||
- Use keyed `{#each}` blocks for efficient list rendering
|
||||
- Implement lazy loading with dynamic imports and `svelte:component`
|
||||
- Use `$derived()` for expensive computations to avoid unnecessary recalculations
|
||||
- Leverage SvelteKit's automatic code splitting and preloading
|
||||
- Optimize bundle size with tree shaking and proper imports
|
||||
- Profile with Svelte DevTools to identify performance bottlenecks
|
||||
|
||||
### Data Fetching
|
||||
- Use SvelteKit's load functions for server-side and universal data fetching
|
||||
- Implement proper loading, error, and success states
|
||||
- Handle streaming data with promises in server load functions
|
||||
- Use `invalidate()` and `invalidateAll()` for cache management
|
||||
- Implement optimistic updates for better user experience
|
||||
- Handle offline scenarios and network errors gracefully
|
||||
|
||||
### Error Handling
|
||||
- Implement `+error.svelte` pages for route-level error boundaries
|
||||
- Use try/catch blocks in load functions and form actions
|
||||
- Provide meaningful error messages and fallback UI
|
||||
- Log errors appropriately for debugging and monitoring
|
||||
- Handle validation errors in forms with proper user feedback
|
||||
- Use SvelteKit's error and redirect helpers
|
||||
|
||||
### Forms and Validation
|
||||
- Use SvelteKit's form actions for server-side form handling
|
||||
- Implement progressive enhancement with `use:enhance`
|
||||
- Use `bind:value` for controlled form inputs
|
||||
- Validate data both client-side and server-side
|
||||
- Handle file uploads and complex form scenarios
|
||||
- Implement proper accessibility with labels and ARIA attributes
|
||||
|
||||
### Testing
|
||||
- Write unit tests for components using Vitest and Testing Library
|
||||
- Test component behavior, not implementation details
|
||||
- Use Playwright for end-to-end testing of user workflows
|
||||
- Mock SvelteKit's load functions and stores appropriately
|
||||
- Test form actions and API endpoints thoroughly
|
||||
- Implement accessibility testing with axe-core
|
||||
|
||||
### Security
|
||||
- Sanitize user inputs to prevent XSS attacks
|
||||
- Use `@html` directive carefully and validate HTML content
|
||||
- Implement proper CSRF protection with SvelteKit
|
||||
- Validate and sanitize data in load functions and form actions
|
||||
- Use HTTPS for all external API calls and production deployments
|
||||
- Store sensitive data securely with proper session management
|
||||
|
||||
### Accessibility
|
||||
- Use semantic HTML elements and proper heading hierarchy
|
||||
- Implement keyboard navigation for all interactive elements
|
||||
- Provide proper ARIA labels and descriptions
|
||||
- Ensure color contrast meets WCAG guidelines
|
||||
- Test with screen readers and accessibility tools
|
||||
- Implement focus management for dynamic content
|
||||
|
||||
## Implementation Process
|
||||
1. Initialize SvelteKit project with TypeScript and desired adapters
|
||||
2. Set up project structure with proper folder organization
|
||||
3. Define TypeScript interfaces and component props
|
||||
4. Implement core components with Svelte 5 runes
|
||||
5. Add routing, layouts, and navigation with SvelteKit
|
||||
6. Implement data loading and form handling
|
||||
7. Add styling system with custom properties and responsive design
|
||||
8. Implement error handling and loading states
|
||||
9. Add comprehensive testing coverage
|
||||
10. Optimize performance and bundle size
|
||||
11. Ensure accessibility compliance
|
||||
12. Deploy with appropriate SvelteKit adapter
|
||||
|
||||
## Additional Guidelines
|
||||
- Follow Svelte's naming conventions (PascalCase for components, camelCase for functions)
|
||||
- Use ESLint with eslint-plugin-svelte and Prettier for code consistency
|
||||
- Keep dependencies up to date and audit for security vulnerabilities
|
||||
- Document complex components and logic with JSDoc
|
||||
- Use Svelte DevTools for debugging and performance analysis
|
||||
- Implement proper SEO with SvelteKit's meta tags and structured data
|
||||
- Use environment variables for configuration across different deployment stages
|
||||
|
||||
## Common Patterns
|
||||
- Renderless components with slots for flexible UI composition
|
||||
- Custom directives for cross-cutting concerns and DOM manipulation
|
||||
- Snippet-based composition for reusable template logic
|
||||
- Context providers for application-wide state management
|
||||
- Progressive enhancement for forms and interactive features
|
||||
- Server-side rendering with client-side hydration for optimal performance
|
||||
@ -111,9 +111,9 @@ tags: [Optional: List of relevant tags or categories, e.g., `infrastructure`, `p
|
||||
|
||||
## 9. Examples & Edge Cases
|
||||
|
||||
```code
|
||||
// Code snippet or data example demonstrating the correct application of the guidelines, including edge cases
|
||||
```
|
||||
```code
|
||||
// Code snippet or data example demonstrating the correct application of the guidelines, including edge cases
|
||||
```
|
||||
|
||||
## 10. Validation Criteria
|
||||
|
||||
|
||||
126
update-readme.js
126
update-readme.js
@ -142,7 +142,10 @@ function extractTitle(filePath) {
|
||||
|
||||
// Track code blocks to ignore headings inside them
|
||||
if (frontmatterEnded2) {
|
||||
if (line.trim().startsWith("```") || line.trim().startsWith("````")) {
|
||||
if (
|
||||
line.trim().startsWith("```") ||
|
||||
line.trim().startsWith("````")
|
||||
) {
|
||||
inCodeBlock = !inCodeBlock;
|
||||
continue;
|
||||
}
|
||||
@ -156,7 +159,10 @@ function extractTitle(filePath) {
|
||||
// No frontmatter, look for first heading (but not in code blocks)
|
||||
let inCodeBlock = false;
|
||||
for (const line of lines) {
|
||||
if (line.trim().startsWith("```") || line.trim().startsWith("````")) {
|
||||
if (
|
||||
line.trim().startsWith("```") ||
|
||||
line.trim().startsWith("````")
|
||||
) {
|
||||
inCodeBlock = !inCodeBlock;
|
||||
continue;
|
||||
}
|
||||
@ -260,7 +266,9 @@ function extractDescription(filePath) {
|
||||
let description = descriptionMatch[1];
|
||||
|
||||
// Check if the description is wrapped in single quotes and handle escaped quotes
|
||||
const singleQuoteMatch = line.match(/^description:\s*'(.+?)'\s*$/);
|
||||
const singleQuoteMatch = line.match(
|
||||
/^description:\s*'(.+?)'\s*$/
|
||||
);
|
||||
if (singleQuoteMatch) {
|
||||
// Replace escaped single quotes ('') with single quotes (')
|
||||
description = singleQuoteMatch[1].replace(/''/g, "'");
|
||||
@ -308,8 +316,12 @@ const AKA_INSTALL_URLS = {
|
||||
function makeBadges(link, type) {
|
||||
const aka = AKA_INSTALL_URLS[type] || AKA_INSTALL_URLS.instructions;
|
||||
|
||||
const vscodeUrl = `${aka}?url=${encodeURIComponent(`vscode:chat-${type}/install?url=${repoBaseUrl}/${link}`)}`;
|
||||
const insidersUrl = `${aka}?url=${encodeURIComponent(`vscode-insiders:chat-${type}/install?url=${repoBaseUrl}/${link}`)}`;
|
||||
const vscodeUrl = `${aka}?url=${encodeURIComponent(
|
||||
`vscode:chat-${type}/install?url=${repoBaseUrl}/${link}`
|
||||
)}`;
|
||||
const insidersUrl = `${aka}?url=${encodeURIComponent(
|
||||
`vscode-insiders:chat-${type}/install?url=${repoBaseUrl}/${link}`
|
||||
)}`;
|
||||
|
||||
return `[](${vscodeUrl})<br />[](${insidersUrl})`;
|
||||
}
|
||||
@ -405,8 +417,7 @@ function generatePromptsSection(promptsDir) {
|
||||
}
|
||||
|
||||
// Create table header
|
||||
let promptsContent =
|
||||
"| Title | Description |\n| ----- | ----------- |\n";
|
||||
let promptsContent = "| Title | Description |\n| ----- | ----------- |\n";
|
||||
|
||||
// Generate table rows for each prompt file
|
||||
for (const entry of promptEntries) {
|
||||
@ -462,8 +473,7 @@ function generateChatModesSection(chatmodesDir) {
|
||||
}
|
||||
|
||||
// Create table header
|
||||
let chatmodesContent =
|
||||
"| Title | Description |\n| ----- | ----------- |\n";
|
||||
let chatmodesContent = "| Title | Description |\n| ----- | ----------- |\n";
|
||||
|
||||
// Generate table rows for each chat mode file
|
||||
for (const entry of chatmodeEntries) {
|
||||
@ -502,7 +512,8 @@ function generateCollectionsSection(collectionsDir) {
|
||||
.filter((file) => file.endsWith(".collection.yml"));
|
||||
|
||||
// Map collection files to objects with name for sorting
|
||||
const collectionEntries = collectionFiles.map((file) => {
|
||||
const collectionEntries = collectionFiles
|
||||
.map((file) => {
|
||||
const filePath = path.join(collectionsDir, file);
|
||||
const collection = parseCollectionYaml(filePath);
|
||||
|
||||
@ -511,10 +522,12 @@ function generateCollectionsSection(collectionsDir) {
|
||||
return null;
|
||||
}
|
||||
|
||||
const collectionId = collection.id || path.basename(file, ".collection.yml");
|
||||
const collectionId =
|
||||
collection.id || path.basename(file, ".collection.yml");
|
||||
const name = collection.name || collectionId;
|
||||
return { file, filePath, collection, collectionId, name };
|
||||
}).filter(entry => entry !== null); // Remove failed parses
|
||||
})
|
||||
.filter((entry) => entry !== null); // Remove failed parses
|
||||
|
||||
// Sort by name alphabetically
|
||||
collectionEntries.sort((a, b) => a.name.localeCompare(b.name));
|
||||
@ -566,6 +579,9 @@ function generateCollectionReadme(collection, collectionId) {
|
||||
content += `## Items in this Collection\n\n`;
|
||||
content += `| Title | Type | Description |\n| ----- | ---- | ----------- |\n`;
|
||||
|
||||
let collectionUsageHeader = "## Collection Usage\n\n";
|
||||
let collectionUsageContent = [];
|
||||
|
||||
// Sort items based on display.ordering setting
|
||||
const items = [...collection.items];
|
||||
if (collection.display?.ordering === "alpha") {
|
||||
@ -580,19 +596,52 @@ function generateCollectionReadme(collection, collectionId) {
|
||||
const filePath = path.join(__dirname, item.path);
|
||||
const title = extractTitle(filePath);
|
||||
const description = extractDescription(filePath) || "No description";
|
||||
const typeDisplay = item.kind === "chat-mode" ? "Chat Mode" :
|
||||
item.kind === "instruction" ? "Instruction" : "Prompt";
|
||||
|
||||
const typeDisplay =
|
||||
item.kind === "chat-mode"
|
||||
? "Chat Mode"
|
||||
: item.kind === "instruction"
|
||||
? "Instruction"
|
||||
: "Prompt";
|
||||
const link = `../${item.path}`;
|
||||
|
||||
// Create install badges for each item
|
||||
const badges = makeBadges(item.path, item.kind === "instruction" ? "instructions" :
|
||||
item.kind === "chat-mode" ? "mode" : "prompt");
|
||||
const badges = makeBadges(
|
||||
item.path,
|
||||
item.kind === "instruction"
|
||||
? "instructions"
|
||||
: item.kind === "chat-mode"
|
||||
? "mode"
|
||||
: "prompt"
|
||||
);
|
||||
|
||||
content += `| [${title}](${link})<br />${badges} | ${typeDisplay} | ${description} |\n`;
|
||||
const usageDescription = item.usage
|
||||
? `${description} [see usage](#${title
|
||||
.replace(/\s+/g, "-")
|
||||
.toLowerCase()})`
|
||||
: description;
|
||||
|
||||
content += `| [${title}](${link})<br />${badges} | ${typeDisplay} | ${usageDescription} |\n`;
|
||||
// Generate Usage section for each collection
|
||||
if (item.usage && item.usage.trim()) {
|
||||
collectionUsageContent.push(
|
||||
`### ${title}\n\n${item.usage.trim()}\n\n---\n\n`
|
||||
);
|
||||
}
|
||||
}
|
||||
|
||||
// Append the usage section if any items had usage defined
|
||||
if (collectionUsageContent.length > 0) {
|
||||
content += `\n${collectionUsageHeader}${collectionUsageContent.join("")}`;
|
||||
} else if (collection.display?.show_badge) {
|
||||
content += "\n---\n";
|
||||
}
|
||||
|
||||
// Optional badge note at the end if show_badge is true
|
||||
if (collection.display?.show_badge) {
|
||||
content += `\n---\n*This collection includes ${items.length} curated items for ${name.toLowerCase()}.*`;
|
||||
content += `*This collection includes ${
|
||||
items.length
|
||||
} curated items for ${name.toLowerCase()}.*`;
|
||||
}
|
||||
|
||||
return content;
|
||||
@ -604,12 +653,16 @@ function writeFileIfChanged(filePath, content) {
|
||||
if (exists) {
|
||||
const original = fs.readFileSync(filePath, "utf8");
|
||||
if (original === content) {
|
||||
console.log(`${path.basename(filePath)} is already up to date. No changes needed.`);
|
||||
console.log(
|
||||
`${path.basename(filePath)} is already up to date. No changes needed.`
|
||||
);
|
||||
return;
|
||||
}
|
||||
}
|
||||
fs.writeFileSync(filePath, content);
|
||||
console.log(`${path.basename(filePath)} ${exists ? "updated" : "created"} successfully!`);
|
||||
console.log(
|
||||
`${path.basename(filePath)} ${exists ? "updated" : "created"} successfully!`
|
||||
);
|
||||
}
|
||||
|
||||
// Build per-category README content using existing generators, upgrading headings to H1
|
||||
@ -633,10 +686,16 @@ try {
|
||||
const collectionsDir = path.join(__dirname, "collections");
|
||||
|
||||
// Compose headers for standalone files by converting section headers to H1
|
||||
const instructionsHeader = TEMPLATES.instructionsSection.replace(/^##\s/m, "# ");
|
||||
const instructionsHeader = TEMPLATES.instructionsSection.replace(
|
||||
/^##\s/m,
|
||||
"# "
|
||||
);
|
||||
const promptsHeader = TEMPLATES.promptsSection.replace(/^##\s/m, "# ");
|
||||
const chatmodesHeader = TEMPLATES.chatmodesSection.replace(/^##\s/m, "# ");
|
||||
const collectionsHeader = TEMPLATES.collectionsSection.replace(/^##\s/m, "# ");
|
||||
const collectionsHeader = TEMPLATES.collectionsSection.replace(
|
||||
/^##\s/m,
|
||||
"# "
|
||||
);
|
||||
|
||||
const instructionsReadme = buildCategoryReadme(
|
||||
generateInstructionsSection,
|
||||
@ -666,10 +725,19 @@ try {
|
||||
);
|
||||
|
||||
// Write category outputs
|
||||
writeFileIfChanged(path.join(__dirname, "README.instructions.md"), instructionsReadme);
|
||||
writeFileIfChanged(
|
||||
path.join(__dirname, "README.instructions.md"),
|
||||
instructionsReadme
|
||||
);
|
||||
writeFileIfChanged(path.join(__dirname, "README.prompts.md"), promptsReadme);
|
||||
writeFileIfChanged(path.join(__dirname, "README.chatmodes.md"), chatmodesReadme);
|
||||
writeFileIfChanged(path.join(__dirname, "README.collections.md"), collectionsReadme);
|
||||
writeFileIfChanged(
|
||||
path.join(__dirname, "README.chatmodes.md"),
|
||||
chatmodesReadme
|
||||
);
|
||||
writeFileIfChanged(
|
||||
path.join(__dirname, "README.collections.md"),
|
||||
collectionsReadme
|
||||
);
|
||||
|
||||
// Generate individual collection README files
|
||||
if (fs.existsSync(collectionsDir)) {
|
||||
@ -684,8 +752,12 @@ try {
|
||||
const collection = parseCollectionYaml(filePath);
|
||||
|
||||
if (collection) {
|
||||
const collectionId = collection.id || path.basename(file, ".collection.yml");
|
||||
const readmeContent = generateCollectionReadme(collection, collectionId);
|
||||
const collectionId =
|
||||
collection.id || path.basename(file, ".collection.yml");
|
||||
const readmeContent = generateCollectionReadme(
|
||||
collection,
|
||||
collectionId
|
||||
);
|
||||
const readmeFile = path.join(collectionsDir, `${collectionId}.md`);
|
||||
writeFileIfChanged(readmeFile, readmeContent);
|
||||
}
|
||||
|
||||
@ -20,6 +20,45 @@ function parseCollectionYaml(filePath) {
|
||||
let currentArray = null;
|
||||
let currentObject = null;
|
||||
|
||||
const readLiteralBlock = (startIndex, parentIndent) => {
|
||||
const blockLines = [];
|
||||
let blockIndent = null;
|
||||
let index = startIndex;
|
||||
|
||||
for (; index < lines.length; index++) {
|
||||
const rawLine = lines[index];
|
||||
const trimmedLine = rawLine.trimEnd();
|
||||
const contentOnly = trimmedLine.trim();
|
||||
const lineIndent = rawLine.length - rawLine.trimLeft().length;
|
||||
|
||||
if (contentOnly === "" && blockIndent === null) {
|
||||
// Preserve leading blank lines inside the literal block
|
||||
blockLines.push("");
|
||||
continue;
|
||||
}
|
||||
|
||||
if (contentOnly !== "" && lineIndent <= parentIndent) {
|
||||
break;
|
||||
}
|
||||
|
||||
if (contentOnly === "") {
|
||||
blockLines.push("");
|
||||
continue;
|
||||
}
|
||||
|
||||
if (blockIndent === null) {
|
||||
blockIndent = lineIndent;
|
||||
}
|
||||
|
||||
blockLines.push(rawLine.slice(blockIndent));
|
||||
}
|
||||
|
||||
return {
|
||||
content: blockLines.join("\n").replace(/\r/g, "").trimEnd(),
|
||||
nextIndex: index - 1,
|
||||
};
|
||||
};
|
||||
|
||||
for (let i = 0; i < lines.length; i++) {
|
||||
const line = lines[i];
|
||||
const trimmed = line.trim();
|
||||
@ -82,6 +121,10 @@ function parseCollectionYaml(filePath) {
|
||||
result[key] = [];
|
||||
}
|
||||
currentKey = null; // Reset since we handled the array
|
||||
} else if (value === "|" || value === ">") {
|
||||
const { content: blockContent, nextIndex } = readLiteralBlock(i + 1, leadingSpaces);
|
||||
result[key] = blockContent;
|
||||
i = nextIndex;
|
||||
} else {
|
||||
result[key] = value;
|
||||
}
|
||||
@ -95,13 +138,25 @@ function parseCollectionYaml(filePath) {
|
||||
}
|
||||
} else if (currentObject && leadingSpaces > 0) {
|
||||
// Property of current object (e.g., display properties)
|
||||
if (value === "|" || value === ">") {
|
||||
const { content: blockContent, nextIndex } = readLiteralBlock(i + 1, leadingSpaces);
|
||||
currentObject[key] = blockContent;
|
||||
i = nextIndex;
|
||||
} else {
|
||||
currentObject[key] = value === "true" ? true : value === "false" ? false : value;
|
||||
}
|
||||
} else if (currentArray && currentObject && leadingSpaces > 2) {
|
||||
// Property of array item object
|
||||
if (value === "|" || value === ">") {
|
||||
const { content: blockContent, nextIndex } = readLiteralBlock(i + 1, leadingSpaces);
|
||||
currentObject[key] = blockContent;
|
||||
i = nextIndex;
|
||||
} else {
|
||||
currentObject[key] = value;
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
return result;
|
||||
},
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user