Loading...
Loading...
Found 391 Skills
Clean Code principles, professional practices, and workflows for TypeScript developers. Based on Robert C. Martin's "Clean Code" and "The Clean Coder" books. IMPORTANT: When this skill is active, always load and consult the reference files (rules.md, examples.md) before giving advice or writing code. Reference content takes precedence over general knowledge. Use this skill when: - Writing TypeScript/JavaScript code - Reviewing code or pull requests - Refactoring existing code - Following test-driven development (TDD) - Fixing bugs with proper test coverage - Planning test strategy for features - Estimating tasks accurately - Handling deadlines and commitments professionally - Working effectively with teams
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.
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.
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.
Refactor code for readability using DRY, meaningful names, and modularization.
Clean Code practices for TypeScript/JavaScript. Identify code smells, apply refactoring patterns, and write maintainable code. Use when reviewing code quality, refactoring messy code, or ensuring code follows best practices. Triggers on requests like "clean up this code", "refactor for readability", "identify code smells", or "make this more maintainable".
Orchestrate large-scale TYPO3 code changes across multiple files in parallel. Migrations, bulk TCA modernization, Fluid template refactoring, hook-to-event conversions, namespace renames, and extension-wide upgrades. Decomposes work into independent units, executes them, and verifies with tests. Use when working with batch, migrate, bulk, mass refactor, convert all, upgrade all, rename across, find and replace, parallel, codemod, TYPO3 migration.
Simplify and refine recently changed code for clarity, reuse, quality, and efficiency while preserving behavior.
Refactors route handlers into service layer with clean boundaries, dependency injection, testability, and separation of concerns. Provides service interfaces, folder structure, testing strategy, and migration plan. Use when refactoring "fat controllers", "business logic", "service layer", or "architecture cleanup".
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.
Analyze Python code for style improvements including naming, structure, nesting, and cognitive load reduction
Agent Review workflows and best practices for catching bugs before merging. Use for reviewing agent-generated code and local changes.