copilot-agents-dojo: Instructions file for GitHub Copilot

Copilot Instructions

Code Standards

Customize this section for your stack. Examples for common fighting styles:

TypeScript (Default Example)

• Always use TypeScript with strict: true
• Naming: camelCase for variables/functions, PascalCase for components/types
• Styling: Tailwind CSS + shadcn/ui components
• Testing: Write Vitest tests for every new component/logic
• Architecture: Next.js App Router, Server Actions, React Server Components when possible
• Security: Never commit secrets, use environment variables

Python

• Type hints on all function signatures
• Formatting: Black (line length 88)
• Testing: pytest with fixtures, aim for >80% coverage
• Linting: ruff or flake8
• Architecture: FastAPI or Django conventions as applicable
• Dependency management: pyproject.toml / requirements.txt pinned

Java

• Follow Google Java Style Guide
• Testing: JUnit 5 + Mockito for unit tests
• Build: Maven or Gradle (match existing project)
• Architecture: Spring Boot patterns, constructor injection
• Security: OWASP dependency check in CI

Go

• Follow standard library conventions and go fmt
• Testing: table-driven tests with testing package
• Error handling: explicit, no panic in library code
• Architecture: clean package boundaries, interfaces for testability

.NET

• Nullable reference types enabled
• Testing: xUnit + FluentAssertions
• Architecture: clean architecture, MediatR for CQRS if applicable
• Security: never log PII, use IOptions pattern for config

Pick your style. Delete the others or keep them as reference.

Superpowers Activated

At session start: read SOUL.md first — the identity charter defining who the agent is, how it reasons, and where its limits are — then load all skills from skills/. Follow the mandatory workflow. Never improvise.

See skills.md for the full skills index. Each skill is a self-contained folder under skills/ with a SKILL.md file. Load the relevant skill when its trigger conditions are met.