universal-dev-skills

Progress tracking in project artifacts -- plan, task, and BDD spec documents. Use after completing each phase of any workflow (feature, refactor, bug-fix), at checkpoints during audit passes, when adding or updating behavioral specs, or when the user asks to update project status.

Commit message format rules. Use whenever staging, committing, or describing changes -- including when the user asks to commit, when preparing a PR, or when writing a changelog entry. NOTE: Never commit autonomously. Always prepare a message and ask for user approval before committing.

Ruff and Pyright configuration standards for Python projects. Use when setting up a new Python project, auditing an existing project's tooling config, or applying linting/type-checking fixes. Covers pyproject.toml settings, taskipy tasks, and pre-commit hooks.

Structured workflow for refactoring existing code without changing observable behavior. Use when restructuring abstractions, extracting ports or adapters, converting inheritance to protocols, or adapting callers to new interfaces -- any change where the goal is structural improvement, not new capability. NOT for new features or enhancements (use feature-workflow). NOT for bug fixes.

Tool and terminal decisions for every task. Use for any request involving file reads or edits, running tests, executing searches, git commands, or terminal work -- even when the user does not mention tool choice. Determines whether to use VS Code integrations, MCP tools, or terminal commands.

Read FIRST, before skill-compliance and all other skills. Defines the emission protocol for all skill activity. Every skill loaded in a session must emit skill.invoked immediately after being read. Every completed skill must emit skill.completed. Timestamps are reviewed for compliance.

Read immediately after the telemetry skill. Before performing any task, identify the task type, the files being modified, and the relevant languages or subprojects, then load the right skills and references and confirm them to the user. Use at the start of every task, after telemetry.

Feedback loop procedure for implementing BDD test modules. Use when implementing a spec doc -- covering one test module from spec to type-checker-clean, self-audited output.

Structured workflow for diagnosing and fixing defects -- cases where the system behaves differently from intent. Use when a bug has been reported or discovered. NOT for new features or enhancements (use feature-workflow). NOT for structural improvements to correct code (use refactor-workflow). NOT for typo corrections, formatting, or comment-only changes.

Suppression pragma policy and common code quality antipatterns. Use whenever writing, editing, or reviewing production code or test code -- any task where the agent might add a suppression comment (type-ignore, noqa, pragma no-cover, eslint-disable, SuppressWarnings, etc.) or encounter one that should be fixed. Cross-cutting: applies alongside language-specific standards skills.

Systematic audit of code against structural quality rules -- mock boundaries, test-only API pollution, suppression pragmas, and BDD conventions. Use when auditing a codebase or set of files for quality violations, during Phase 4 of feature-workflow, during Phase 3 of refactor-workflow, or as a standalone quality review task.

Spec-before-code feature development workflow. Use when the user requests a new feature, enhancement, or non-trivial change -- anything that adds or modifies behavior, including requests phrased as add, implement, build, or create. NOT for pure refactoring that preserves existing behavior (use refactor-workflow). NOT for defects where the system diverges from intent (use bug-fix-workflow). NOT for typo corrections, formatting, or comment-only changes.

Document templates for various workflows, including feature and refactor workflows. Use when creating a plan, spec, or design note -- read the relevant template file from references/ rather than reproducing structure from memory.

BDD test conventions for this repository. Use when writing, modifying, or reviewing test files, including creating tests for new features and adding coverage specs. ALSO use when running coverage checks, reporting coverage results, or auditing code coverage -- this skill defines the 100% coverage requirement and remediation procedure.

Roslyn analyzer, .editorconfig, and build configuration standards for C# / .NET projects. Use when setting up a new .NET project, auditing an existing project's tooling config, or applying lint/type-checking fixes. Covers the dotnet CLI, xUnit, FluentAssertions, and pre-commit hooks.

Checkstyle, SpotBugs, and Java compiler configuration standards for Java projects. Use when setting up a new Java project, auditing an existing project's tooling config, or applying lint/type-checking fixes. Covers Maven and Gradle configuration, static analysis, JUnit 5, and pre-commit hooks.

ESLint, TypeScript compiler, and Jest configuration standards for TypeScript projects. Use when setting up a new TypeScript project, auditing an existing project's tooling config, or applying lint/type-checking fixes. Covers tsconfig.json, ESLint flat config, Jest setup, and Husky pre-commit hooks.