dj-metadata-fixer

Set up and validate GitHub Copilot Agent Chat files for VS Code. Use when creating or reviewing .github/copilot-instructions.md, .github/instructions/*.instructions.md, .github/prompts/*.prompt.md, .github/agents/*.agent.md, or .github/skills/<name>/SKILL.md. Covers correct paths, frontmatter schemas, naming conventions, discovery behaviour, and diagnostic checks for all five VS Code Copilot file types.

Create a new implementation plan file for features, refactors, package upgrades, design changes, architecture decisions, or infrastructure work. Saves a structured Markdown plan to the /plan/ directory with phases, tasks, dependencies, test criteria, and risk analysis. Use when the user says "create a plan", "write a plan file", or "generate an implementation plan for X".

Toolkit for implementing and debugging advanced media metadata editing in DJ Metadata Fixer. Use when adding manual tag fields, mapping tags across MP3/MP4/MKV/WebM, improving metadata validation, fixing rename collisions, or refining per-file processing UX.

Generate fully executable implementation plans for new features, refactors, or architecture changes. Use when asked to plan, design phases, break down tasks, or create a roadmap. Produces machine-readable plans with atomic tasks, completion criteria, and zero ambiguity for autonomous AI or human execution.

Generate resilient Playwright Python tests using role-based locators, web-first assertions, and Pytest organisation. Use when writing, reviewing, or debugging UI or end-to-end tests with Playwright and Python. Covers locator strategy, assertion best practices, file organisation, fixture setup, and test execution strategy.

Apply secure coding practices based on OWASP Top 10 and security-by-default principles. Use when reviewing, writing, or auditing code for security vulnerabilities. Covers broken access control, injection prevention, cryptographic failures, secret management, authentication, dependency vulnerabilities, and SSRF. Always choose the more secure option and explain the reasoning.

Guide for creating effective VS Code agent skills, custom instructions, prompts, and agents. Use when building new SKILL.md files, writing .instructions.md files, defining .prompt.md or .agent.md files, or setting up a .github/ Copilot directory structure. Covers frontmatter schemas, path requirements, progressive disclosure, naming conventions, and VS Code discovery behaviour.

Structured six-phase software development workflow with requirements, design, tasks, and documentation artifacts. Use when starting any significant feature or refactor to ensure requirements are clearly defined, designs are planned, and implementations are validated. Phases are ANALYZE, DESIGN, IMPLEMENT, VALIDATE, REFLECT, HANDOFF. Maintains requirements.md, design.md, and tasks.md artifacts.

Implement task plans systematically with progressive tracking and change records. Use when executing a plan file from /plan/ or .copilot-tracking/plans/. Enforces reading the full plan first, implementing tasks in order, marking tasks complete, and updating a change log after every task. Covers plan analysis, implementation quality standards, progress validation, and release summary generation.

Systematically research and validate technical spikes through exhaustive documentation investigation and controlled experiments. Use when exploring an unknown technology, validating an approach before implementation, investigating a library or API, or when confidence is low before starting a significant feature. Continuously updates the spike document as a living research log with real-time findings, sources, and experimental results.