Loading...
Loading...
Found 15 Skills
Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt.
Generates a comprehensive and best-practice-oriented .editorconfig file based on project analysis and user preferences.
Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.
Audit and fix filename and naming conventions for consistency. Use when reviewing file names, component names, or export naming across the codebase.
Verify logic diagrams against source code. Check line-number accuracy, Mermaid syntax, node completeness, and side effect documentation. Runs as independent Critic in fork context. Use when: verify logic, check logic diagram, validate phase 2, re-verify-logic.
Apply language-agnostic naming conventions using the A/HC/LC pattern. Use when naming variables, functions, or reviewing code for naming consistency.
Sub-agent powered code reviews spanning correctness, tests, consistency, and fit
Enforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.
Run Intent validation and sync checks. Triggers intent-validate and intent-sync agents. Use /intent-check for full check, or /intent-check --validate/--sync for specific checks.
Audit code for DRY violations, dead code, complexity, and consistency issues. Read-only analysis with actionable recommendations. Use before PR or for code quality review. Triggers: review maintainability, code quality, DRY, refactor review.
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
Cross-Layer Check