Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a comprehensive set of coding and documentation standards for various technology stacks by adding detailed instruction files and updating the main Copilot instructions. These changes establish clear, enforceable guidelines for code style, best practices, security, and project-specific conventions, tailored to different file types and frameworks. The most important changes are grouped below by theme.
1. Instruction Framework and File Mapping
.github/copilot-instructions.mddescribing an automated system that applies specific instruction files based on file patterns, ensuring that the correct coding standards are enforced for each technology stack. This includes a mapping table for instruction files and their applicable file globs.2. Technology-Specific Coding Standards
markdown.instructions.mdoutlining strict formatting, content, and validation rules for Markdown documents, including required YAML front-matter fields, heading structure, and line length limits.nodejs-javascript-vitest.instructions.mdwith ES2022+ standards, Node.js ESM usage, async/await requirements, Vitest testing rules, and documentation guidelines.python-mcp-server.instructions.mddetailing best practices for building Model Context Protocol servers, including usage of FastMCP, type hints, structured outputs, context management, and extensive code examples.python.instructions.mdspecifying PEP 8/257 compliance, type annotations, code style, edge case handling, and documentation examples.reactjs.instructions.mddefining modern React (v19+) best practices, TypeScript integration, component architecture, state management, styling, testing, accessibility, and security requirements.tailwind-v4-vite.instructions.mdwith installation, configuration, and usage guidelines for Tailwind v4 in Vite projects, emphasizing the new CSS-first configuration approach and removal of legacy files.3. Security and Best Practices
security-and-owasp.instructions.mdto enforce OWASP Top 10 and industry best practices across all languages and frameworks, covering access control, cryptography, injection prevention, secure configuration, authentication, and code review education.These changes provide a robust foundation for consistent, secure, and high-quality code across the project, with clear, automated enforcement of best practices for each technology and file type.