Loading...
Loading...
Found 22 Skills
Discovers how analytics tracking calls are actually written in this codebase — the concrete SDK calls, function signatures, and import patterns used to send events. Use this skill whenever you need to understand the existing analytics instrumentation patterns before adding new tracking, when someone asks "how do we track events here?", "show me the analytics setup", "what's the analytics pattern in this codebase?", or any time the instrument-events or discover-event-surfaces skills are about to run and you need to know the correct coding style to follow. Outputs a deduplicated list of patterns with generalized examples and the file paths where each pattern appears, plus the dominant event and property naming conventions inferred from those call sites. Always use this skill before writing any analytics instrumentation code.
Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.
Enforce consistent React component naming conventions using domain + role patterns. Use when creating, reviewing, or refactoring components.
Reviews code changes for reuse, composition, codebase consistency, and slop. Use when asked to review PRs/diffs, check code reuse, composition, cleanliness, or whether code fits the codebase.
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.
Sub-agent powered code reviews spanning correctness, tests, consistency, and fit
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.
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
Cross-Layer Check
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.
Detects and enforces project-specific coding conventions by analyzing existing codebase patterns. Learns naming conventions, folder structure, test organization, and coding style from the existing code. Load when: "conventions", "coding standards", "project patterns", "enforce style", "detect patterns", "learn conventions", "code consistency".
Generates a comprehensive and best-practice-oriented .editorconfig file based on project analysis and user preferences.