Loading...
Loading...
Found 351 Skills
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.
Builds and queries code knowledge graph for dependency analysis, references, implementations, and architecture overview. Use when starting work on unfamiliar codebase or before refactoring.
Golang refactoring — the safe, at-scale process for restructuring existing Go code: a coverage-adaptive safety net, tool-driven behavior-preserving transforms (gopls Rename/Inline/Extract, `gofmt -r`, `eg`, `gopatch`, `go/analysis` fixers), the Fowler catalog mapped to Go, breaking import cycles, moving types across packages, and a human-in-the-loop workflow of small stacked PRs on a refactoring branch. Apply when code is hard to maintain, a function/type has grown too large, a code smell needs fixing, adding a feature is blocked by the current structure, or the user asks to clean up, refactor, or improve Go code — also for renaming at scale, extracting functions/interfaces, moving code between packages, splitting packages, or planning a multi-step refactor. Target styles owned elsewhere → See `samber/cc-skills-golang@golang-naming` (renames), `@golang-project-layout` (splits), `@golang-modernize` (idioms), `@golang-code-style` (control flow), `@golang-design-patterns` (patterns/DI).
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.
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.
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.
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.
Use when structuring or refactoring Convex codebases with Domain-Driven Design boundaries, repository abstractions, adapters for external APIs, and transaction-safe workflows.
Suggest refactoring opportunities to improve code structure and maintainability. Use when improving code design or reducing complexity.