Loading...
Loading...
Found 351 Skills
Builds and queries code knowledge graph for dependency analysis, references, implementations, and architecture overview. Use when starting work on unfamiliar codebase or before refactoring.
Modernize and improve legacy codebases while maintaining functionality. Use when you need to refactor old code, reduce technical debt, modernize deprecated patterns, or improve code maintainability without breaking existing behavior.
This skill should be used when the user asks to "simplify code", "clean up code", "refactor for clarity", "reduce complexity", "improve readability", "make this easier to maintain", or asks to simplify recently modified code.
For use when students **have completed WG-12 to WG-21** (single-file consolidation blueprint) and are working on **WG-22 Code Splitting** (`agent_core.py` + `main.py`). **First message in a new session**: Display PEAS brand screen and confirm readiness first; after confirmation, **lay out the context** before proceeding to requirement clarification. If **`prompts/` or `templates/`** are missing, copy them from `references/project_assets/` to the project root. Process: Spec Alignment (2d′) → Six-column Contract → **In-session Handoff Implementation** → Acceptance. Starting point: starter_main_wg21.py; Standard reference: reference_agent_core.py + reference_main.py. Triggers: peas-workshop-advanced-coach, PEAS workshop advanced coach, WG-22, code splitting coach, Agent.chat.
Refactor code for readability using DRY, meaningful names, and modularization.
Simplify and refine recently changed code for clarity, reuse, quality, and efficiency while preserving behavior.
Suggest refactoring opportunities to improve code structure and maintainability. Use when improving code design or reducing complexity.
Systematic code refactoring while preserving all external behavior. Use when identifying code smells, planning refactoring sequences, executing safe structural improvements, or validating behavior preservation. Includes code smell catalog (reference.md) and refactoring execution protocol.
Analyzes code statistics by language for project insight, CI/CD metrics, or before refactoring. Use this skill when understanding project composition, measuring change impact, or generating CI/CD metrics
Nuxt 3/4 performance optimization and architecture guidelines for building fast, maintainable full-stack applications. This skill should be used when writing, reviewing, or refactoring Nuxt code to ensure optimal patterns. Triggers on tasks involving data fetching, server routes, auto-imports, rendering modes, or Nuxt-specific features.
This skill should be used when the user wants to write, review, or refactor TypeScript code to follow industry best practices. Common triggers include "follow ts best practices", "review this typescript", "fix the typescript style", "make this idiomatic typescript", "apply typescript conventions", and "audit this ts file". Bakes in branded types, discriminated unions, ts-pattern for multi-branch logic, JSDoc on exports, kebab-case file naming, and *Params/*Options object-arg conventions. Skip when the user wants pure functional refactors (use ts-best-practices-functional) or is writing framework components (React/Vue/Svelte have different conventions).
Semantic code analysis via LSP. Navigate code (definitions, references, implementations), search symbols, preview refactorings, and get file outlines. Use for exploring unfamiliar codebases or performing safe refactoring.