chore: upstream copilot instructions (#492)

Author: DerekRoberts

.github/copilot-instructions.md

@@ -0,0 +1,36 @@
+<!--
+✏️ PROJECT-SPECIFIC INSTRUCTIONS
+📝 Customize this file for your project needs
+-->
+
+# Project Copilot Instructions
+
+> For instructions see [copilot-upstream.md](./copilot-upstream.md)
+
+## Project Configuration
+
+**Do not modify `.github/copilot-upstream.md`, which is managed and updated upstream.  Instead edit this file for project-specific instructions.**
+
+Use these technologies:
+- Next.js 14 with TypeScript
+- PostgreSQL for database
+- Node.js >= 18.0.0
+- OpenAPI for API design
+
+Follow these conventions:
+- API endpoints: kebab-case
+- React components: PascalCase
+- Database: Always use parameterized queries
+
+Project-specific rules:
+- Python: 4 spaces (override BC Gov standard)
+- APIs: Additional validation for public endpoints
+- Branches: feature/JIRA-123-description
+
+Never:
+- Create duplicate files
+- Remove existing documentation
+- Override error handling
+- Bypass security checks
+- Generate non-compliant code
+- Modify or remove the UPSTREAM MANAGED header at the top of `.github/copilot-upstream.md`

.github/copilot-upstream.md

@@ -0,0 +1,52 @@
+<!--
+🔒 UPSTREAM MANAGED - DO NOT MODIFY
+⚙️ Standard instructions for GitHub Copilot (AI coding assistant)
+
+Use this file by including it in VS Code settings (.vscode/settings.json):
+```jsonc
+{
+  "github.copilot.chat.codeGeneration.useInstructionFiles": true,
+  "github.copilot.chat.codeGeneration.instructions": [
+    {
+      "file": ".github/copilot-upstream.md"
+    }
+  ]
+}
+```
+-->
+
+You are a coding assistant for BC Government projects. Follow these guidelines:
+
+When writing code:
+- Use 2 spaces for indentation in all files
+- Write variables and functions in camelCase
+- Keep functions small, focused, and testable
+- Add error handling for all async operations
+- Follow security guidelines in SECURITY.md
+- Include JSDoc comments for functions and classes
+- Write unit tests using AAA pattern (Arrange-Act-Assert)
+- Preserve existing patterns in the codebase
+- Use modern language features appropriately
+
+For security and compliance:
+- Never generate credentials or secrets
+- Always validate user inputs
+- Use parameterized queries for databases
+- Follow BC Government compliance standards
+- Add input validation on public endpoints
+- Check for performance impacts
+- Review generated code for security implications
+
+When documenting:
+- Keep JSDoc comments up to date
+- Document complex logic clearly
+- Preserve existing documentation structure
+- Include usage examples for APIs
+- Use consistent Markdown formatting
+
+Never:
+- Create duplicate files
+- Remove existing documentation
+- Override error handling
+- Bypass security checks
+- Generate non-compliant code

.vscode/settings.json

@@ -0,0 +1,8 @@
+{
+  "github.copilot.chat.codeGeneration.useInstructionFiles": true,
+  "github.copilot.chat.codeGeneration.instructions": [
+    {
+      "file": ".github/copilot-upstream.md"
+    }
+  ]
+}