Files

Giancarmine Salucci 50289d7ae2 feat(service-worker): complete service worker registration fix implementation

✅ All 169 tests passing
✅ Service worker registration working correctly
✅ Push notifications enabled
✅ Test environment properly isolated

Final implementation includes:
- Fixed vite.config.ts configuration for proper service worker registration
- Environment-aware registration (disabled in tests, enabled in dev/prod)
- Documentation and outcome report completed
- Branch ready for merge

Refs: docs/plans/FixServiceWorkerDevRegistrationIssues.md

2025-12-22 04:59:36 +01:00

2.8 KiB

Raw Blame History

Instructions

In this file i'm providing instructions for GitHub Copilot on how to assist me while coding in this project.

Context

Read the .system/constants.md

Available Skills

This project has reusable skills that can be invoked by agents to perform common tasks. Load the skills from the .system/skills/.

Custom Commands

This project uses custom agent commands to streamline feature development and planning. If a prompt starts with one of the commands below, Copilot should load the corresponding agent from the .system/agents/ directory and execute its workflow.

@Vi - Analyst Agent (Planning)

Command: @Vi <feature description>

Purpose: Loads the analyst agent from .system/agents/analyst.md to create a comprehensive execution plan for a given feature request.

What it does:

Analyzes the feature request
Creates a detailed execution plan with user stories
Documents acceptance criteria and technical specifications
Identifies dependencies and risk assessment
Generates a PLAN_FILE at docs/plans/<outcome-name>.md

Example Usage:

@Vi Add a new enemy type that shoots homing missiles with adaptive difficulty scaling

Workflow: Always use @Vi first when you want to plan a complex feature or enhancement.

@dev - Developer Agent (Implementation)

Command: @dev <outcome_name>

Purpose: Loads the developer agent from .system/agents/developer.md to implement the execution plan created by @Vi and deliver production-ready code.

What it does:

Reads the PLAN_FILE from docs/plans/<outcome-name>.md
Creates a feature branch for isolated development
Implements each story with code, testing, and documentation
Verifies implementation against original requirements
Generates an OUTCOME_FILE at docs/outcomes/<outcome-name>.md

Parameters:

<outcome_name>: The outcome name in the format used in the PLAN_FILE (e.g., "FirstPersonSpaceShooter", "EnhancedGameplayFeatures")