This repository now features a comprehensive GitHub Copilot integration with:
- 6 Custom Agents - Specialized AI experts for different development tasks
- 6 Agent Skills - Reusable patterns and best practices (December 2025 feature)
- GitHub MCP Insiders - Advanced features including Copilot coding agent tools
Understanding the hierarchy helps you use the right tool for each job:
┌─────────────────────────────────────────────────────────────┐
│ CUSTOM INSTRUCTIONS (.github/copilot-instructions.md) │
│ Project-wide defaults, coding standards, setup guides │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ CUSTOM AGENTS (.github/agents/*.md) │
│ Specialized experts with domain knowledge and tools │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ AGENT SKILLS (.github/skills/*/SKILL.md) │
│ Reusable patterns, rules, and best practices │
└─────────────────────────────────────────────────────────────┘
| Feature | Purpose | Example |
|---|---|---|
| Custom Instructions | Project setup, coding standards | "Use TypeScript strict mode" |
| Custom Agents | Domain expertise for tasks | "Use game-developer for Three.js work" |
| Agent Skills | Reusable patterns/rules | "How to test Three.js components" |
Expert in product analysis and GitHub issue creation
Improvements:
- ✅ Added 6 GitHub Copilot assignment methods (basic, advanced, custom instructions, direct PR, stacked PRs, job tracking)
- ✅ Complete GitHub MCP Insiders documentation
- ✅ Enhanced issue creation templates
- ✅ ISMS compliance verification checklist
- ✅ Skills integration (all 6 skills)
Growth: 420 → 950 lines (+126%)
Use for:
- Product quality analysis
- Creating GitHub issues
- Coordinating specialized agents
- ISMS compliance verification
Expert in Three.js game development with React
Improvements:
- ✅ 60fps performance enforcement rules
- ✅ useFrame optimization patterns with delta time
- ✅ Instanced mesh for particles (>10 objects)
- ✅ Strict TypeScript for 3D components
- ✅ References react-threejs-game skill
Growth: 77 → 440 lines (+471%)
Use for:
- Three.js components
- 3D game mechanics
- WebGL rendering
- Game loop implementation
Expert in React 19 and UI development
Improvements:
- ✅ React 19 specific patterns (useTransition, useDeferredValue)
- ✅ WCAG 2.1 AA accessibility compliance
- ✅ Strict TypeScript (no
anytypes ever) - ✅ Performance optimization (useMemo, useCallback)
- ✅ References documentation-standards skill
Growth: 62 → 500 lines (+706%)
Use for:
- React UI components
- TypeScript interfaces
- Accessibility compliance
- Performance optimization
Expert in comprehensive testing strategies
Improvements:
- ✅ 80%+ coverage enforcement (95% for security code)
- ✅ Deterministic test patterns (mocked time/random)
- ✅ Three.js testing with canvas mocking
- ✅ React Testing Library best practices
- ✅ References testing-strategy skill
Growth: 81 → 520 lines (+542%)
Use for:
- Unit tests with Vitest
- E2E tests with Cypress
- Test coverage improvement
- Three.js component testing
Expert in security, compliance, and supply chain
Improvements:
- ✅ OSSF Scorecard ≥8.0, SLSA Level 3, SBOM ≥7.0 enforcement
- ✅ License compliance (only MIT, Apache-2.0, BSD, ISC)
- ✅ OWASP Top 10 secure coding rules
- ✅ XSS prevention with sanitization
- ✅ References security-by-design and isms-compliance skills
Growth: 107 → 580 lines (+442%)
Use for:
- Security reviews
- Dependency audits
- License compliance
- ISMS policy alignment
Expert in technical documentation
Improvements:
- ✅ Complete JSDoc patterns (@param, @returns, @example)
- ✅ Mermaid diagram templates (architecture, flows, ISMS)
- ✅ ISMS documentation structure
- ✅ Architecture Decision Records (ADR)
- ✅ References documentation-standards skill
Growth: 93 → 540 lines (+480%)
Use for:
- README files
- API documentation
- JSDoc comments
- Mermaid diagrams
High-level security principles and enforcement
Key Rules:
- Never commit secrets or credentials
- Validate and sanitize ALL user input
- Use parameterized queries (never string concatenation)
- Implement proper authentication & authorization
- Handle errors securely (no stack traces to users)
- Use cryptography correctly (established libraries)
- Secure dependencies (npm audit, license check)
- Implement security headers (CSP, X-Frame-Options)
- Log security events (never sensitive data)
- Follow Secure Development Policy
Examples: 5 complete code examples with anti-patterns
ISMS policy alignment verification
Key Rules:
- Reference appropriate ISMS policies in all security code
- Follow ISO 27001:2022, NIST CSF 2.0, CIS Controls v8.1
- Maintain security documentation with policy links
- Implement required security controls with control IDs
- Verify compliance before PR approval
- Document security architecture decisions
- Maintain traceability to ISMS requirements
- Include policy references in commit messages
- Update security docs when policies change
- Align features with ISMS Policy Mapping
ISMS Policies: 10 core policies referenced
Three.js game development patterns
Key Rules:
- Use @react-three/fiber for declarative 3D scenes
- Implement game loops with useFrame and delta time
- Type all Three.js refs explicitly (
useRef<THREE.Mesh>) - Target 60fps (use Chrome DevTools Performance)
- Use InstancedMesh for >10 similar objects
- Optimize re-renders (useMemo for expensive calculations)
- Dispose resources in useEffect cleanup
- Handle events with onPointerOver/onPointerOut
- Use proper lighting for visibility
- Test with Three.js mocks
Examples: 8 complete patterns with anti-patterns
Comprehensive testing patterns
Key Rules:
- Aim for 80%+ coverage (95% for security code)
- Write deterministic tests (mock Date.now(), Math.random())
- Test behavior, not implementation
- Use React Testing Library user-centric queries
- Mock external dependencies with Vitest
- Test Three.js with canvas mocking
- Use Cypress for critical E2E flows
- Follow "arrange, act, assert" pattern
- Group related tests with describe blocks
- Run tests before every commit
Examples: 15 complete test patterns
Clear technical documentation
Key Rules:
- Use complete JSDoc (@param, @returns, @throws, @example)
- Include working code examples (tested)
- Create Mermaid diagrams for architecture
- Reference ISMS policies appropriately
- Maintain README with setup instructions
- Write Architecture Decision Records (ADR)
- Keep docs synchronized with code
- Use consistent terminology
- Include troubleshooting sections
- Follow markdown best practices
Examples: 10 documentation templates
React and Three.js optimization
Key Rules:
- Minimize React re-renders (useMemo, useCallback)
- Optimize useFrame (avoid state updates)
- Use InstancedMesh for particles/crowds
- Profile with Chrome DevTools Performance
- Reduce bundle size (code splitting, tree shaking)
- Optimize Three.js geometry (lower polygon counts)
- Dispose resources properly
- Use texture atlases for multiple textures
- Implement Level of Detail (LOD)
- Target 60fps consistently
Examples: 12 optimization patterns
The product-task-agent documents 6 methods for assigning work to GitHub Copilot:
gh copilot assign <issue-number>gh copilot assign <issue-number> --base-ref feature/branch-nameUse for: Stacked PRs, feature branches
gh copilot assign <issue-number> --custom-instructions "Follow patterns in src/components/"Use for: Providing specific context
gh pr create --assign-copilot --title "Add feature" --body "Description"gh pr create --assign-copilot --agent security-architect --title "Security fix"Use for: Using specific agent for PR
gh copilot status <job-id>Use for: Monitoring Copilot progress
# PR 1: Foundation
gh pr create --assign-copilot --title "Step 1: Data models" --base main
# PR 2: Build on PR 1
gh copilot assign <issue-2> --base-ref copilot/issue-1
# PR 3: Final integration
gh pr create --assign-copilot --title "Step 3: API" --base copilot/issue-2Prompt:
@workspace Use the game-developer agent to create a particle system
with 100 particles using InstancedMesh for performance.
What happens:
- Custom Instructions → TypeScript strict mode, project structure
- game-developer agent → Three.js expertise, 60fps enforcement
- react-threejs-game skill → InstancedMesh pattern
- performance-optimization skill → 60fps optimization rules
Result: Optimized particle system with proper TypeScript, 60fps target
Prompt:
@workspace Use test-engineer to add tests for the Player component
with 80%+ coverage including Three.js canvas interactions.
What happens:
- Custom Instructions → Vitest setup, test location
- test-engineer agent → Testing expertise, coverage enforcement
- testing-strategy skill → Three.js testing patterns, mocking
- react-threejs-game skill → useFrame testing patterns
Result: Comprehensive tests with Three.js mocking, 80%+ coverage
Prompt:
@workspace Use security-specialist to review this authentication code
for OWASP Top 10 vulnerabilities and ISMS compliance.
What happens:
- Custom Instructions → TypeScript strict mode
- security-specialist agent → Security expertise, OSSF enforcement
- security-by-design skill → Defense-in-depth patterns
- isms-compliance skill → Policy references
Result: Security review with OWASP checklist, ISMS policy references
| Task | Agent | Skills Applied |
|---|---|---|
| Product analysis | product-task-agent | All 6 skills |
| Three.js components | game-developer | react-threejs-game, performance-optimization |
| React UI | frontend-specialist | documentation-standards, performance-optimization |
| Writing tests | test-engineer | testing-strategy |
| Security review | security-specialist | security-by-design, isms-compliance |
| Documentation | documentation-writer | documentation-standards, isms-compliance |
New Feature:
- product-task-agent → Analyze and create issue
- game-developer / frontend-specialist → Implement
- test-engineer → Add tests
- security-specialist → Security review
- documentation-writer → Update docs
Bug Fix:
- test-engineer → Add failing test
- game-developer / frontend-specialist → Fix
- test-engineer → Verify test passes
- security-specialist → Check for security implications
Performance Optimization:
- game-developer → Profile and identify bottlenecks
- frontend-specialist → Optimize React re-renders
- test-engineer → Add performance tests
- documentation-writer → Document optimizations
| Metric | Before | After | Growth / Status |
|---|---|---|---|
| Custom Agents | 1,040 lines | 3,530 lines | +239% |
| Agent Skills | 0 | 2,469 lines | NEW! |
| Total Lines | 1,040 | 5,999 lines | Informational only* |
| Rules per Agent | ~3 | ~10 | +233% |
| Examples per Agent | ~2 | ~8 | +300% |
| Checklists | 0 | 6 | NEW! |
| Decision Frameworks | 0 | 24 | NEW! |
* Total lines of configuration are tracked for context only and are not used as a quality metric. Prefer outcome metrics such as reduced clarifying questions or increased autonomous task completion.
- ✅ Autonomy: Decision frameworks reduce questioning by ~80%
- ✅ Consistency: Enforcement rules ensure uniform output
- ✅ Compliance: 100% ISMS policy coverage
- ✅ Performance: 60fps enforcement, 80%+ test coverage
- ✅ Security: OSSF ≥8.0, SLSA L3, SBOM ≥7.0
- Review skills for accuracy (Dec, Mar, Jun, Sep)
- Update agents when patterns evolve
- Sync with ISMS policy updates
- Add new skills as patterns emerge
- Update examples with latest patterns
- Fix reported issues
- Improve documentation
- Add community feedback
- Update isms-compliance skill
- Update security-specialist agent
- Update documentation-writer agent
- Cross-reference new policies
- Create
.github/skills/skill-name/directory - Create
SKILL.mdwith YAML frontmatter - Write 10 enforceable rules
- Add 5-10 examples with anti-patterns
- Test with GitHub Copilot
- Update skills README
- Submit PR for review
- Identify improvement area
- Add decision frameworks
- Add enforcement rules
- Add examples
- Reference relevant skills
- Test with Copilot
- Submit PR for review
Remember: Skills teach patterns, agents apply expertise, and custom instructions set defaults. Together, they create a comprehensive AI-assisted development experience! 🚀