Documentation

Implement secure, consistent input validation on both client and server sides. Use this skill when validating form inputs, API request bodies, or user-provided data. When sanitizing input to prevent injection attacks (SQL, XSS, command injection). When writing allowlist-based validation, type checking, or business rule validation. When providing field-specific error messages to users.

This skill transfers focus tasks from the daily "@Today" note in Notion to Todoist. It should be used when the user wants to sync their daily focus tasks, import today's tasks from Notion, or create Todoist tasks from their daily planning note. Trigger phrases include "sync my focus tasks", "import today's tasks", "create tasks from my daily note", or "todays focus tasks".

Machine learning in Python with scikit-learn. Use when working with supervised learning (classification, regression), unsupervised learning (clustering, dimensionality reduction), model evaluation, hyperparameter tuning, preprocessing, or building ML pipelines. Provides comprehensive reference documentation for algorithms, preprocessing techniques, pipelines, and best practices.

Use when understanding external libraries, frameworks, or dependencies - provides workflows for finding and reading official documentation via Context7 instead of web search or source code reading

Best practices for writing Python tests - use when creating or improving test coverage

Expert in modern code design standards including SOLID principles, Clean Code patterns (KISS, YAGNI, DRY, TDA), design patterns, and pragmatic software design. **ALWAYS use when designing ANY classes/modules, implementing features, fixing bugs, refactoring code, or writing functions. ** Use proactively to ensure proper design, separation of concerns, simplicity, and maintainability. Triggers - "create class", "design module", "implement feature", "refactor code", "fix bug", "is this too complex", "apply SOLID", "keep it simple", "avoid over-engineering", writing any code.

Automatically generate Medium-style technical articles from projects, achievements, or workflows with consistent V>> voice and structure.

Generate API documentation from TypeScript source code for RSPress. Use when documenting package APIs, extracting types from source code, or creating function/class reference pages.

Maintain consistent coding style, formatting, and naming conventions across the entire codebase following DRY and YAGNI principles. Use this skill when writing or refactoring any code in any language or framework to ensure consistent indentation, naming patterns, function size, and code organization. Apply this skill when naming variables, functions, classes, or files, when formatting code with proper spacing and line breaks, when removing dead code or unused imports, when extracting duplicated logic into reusable functions, or when ensuring small focused functions that do one thing well. This skill ensures the entire codebase maintains uniform style through automated formatting tools (Prettier, Black, ESLint), follows established naming conventions (camelCase, PascalCase, snake_case), avoids code duplication, removes commented-out code, and prioritizes readability and maintainability over cleverness.

🔄 PHP-QA-CI TOOL ORCHESTRATOR - Automatic run→fix→run cycling for php-qa-ci tools.**ONLY for php-qa-ci pipeline tools** (./bin/qa -t toolname)NOT for ad-hoc tool execution outside php-qa-ci.Use when user requests QA tools via php-qa-ci:- "run phpstan", "use stan skills"- "run tests", "run phpunit"- "run rector", "run cs fixer"- "run allStatic", "run allCS"**CRITICAL**: MUST cycle automatically until tool reports clean OR escalation needed.DO NOT stop after one fix to ask "what next?" - KEEP CYCLING.Supports all php-qa-ci tools via ./bin/qa -t {toolname}:- phpstan (static analysis) - has fixer agent- phpunit (tests) - has fixer agent- rector (refactoring) - self-fixing, re-run until clean- fixer (code style) - self-fixing, re-run until clean- infection (mutation testing) - no auto-fix- allStatic/allCs/allTests - meta groupsAutomatically detects which tools have fixers and invokes them.**PERFORMS PREFLIGHT CHECK**: Invokes docs-conflict-checker agent to ensureproject documentation doesn

Creates risk-based test plans and strategies. Use when planning testing, defining test scope, or documenting QA approach.

Assists with writing and editing general prose using Strunk & White's Elements of Style and Wikipedia's AI writing detection guide. Use when composing articles, blog posts, or editing text for clarity and authenticity.

Always use Context7 MCP to fetch up-to-date library/API documentation before generating code that depends on external libraries or config. Use when the user asks for setup steps, configuration, or code involving third-party libraries. Prefer Context7 docs over memory. Include citations to the retrieved docs when possible.

Luda - Certified Scrum Master and Agile Coach with 8+ years experience. Use when planning/facilitating sprints, running standups/retrospectives/demos, tracking velocity and progress, removing blockers, coaching on Agile practices, or creating sprint documentation. Also responds to 'Luda' or /luda command.

Code tagging system using @FEAT, @COMP, @TYPE tags for easy discovery and navigation. Use when adding documentation tags or searching for related code across the codebase.

Standard Operating Procedure for /init-project phase. Guide one-time project setup with interactive questionnaire, brownfield codebase scanning, 8-document generation (overview, architecture, tech-stack, data, API, capacity, deployment, workflow), and cross-document consistency validation. Auto-trigger when user runs /init-project or mentions 'project setup', 'architecture documentation', or 'greenfield/brownfield initialization'.

Onboard new projects with standardized configuration and documentation

Pure Data reference documentation for audio patch development. Use when writing .pd patches, working with OSC/audio/sampling, or implementing Pure Data code.

Apply DRY (Don't Repeat Yourself) and KISS (Keep It Simple, Stupid) principles when writing, reviewing, or refactoring code. Use when eliminating duplication, simplifying complex logic, or evaluating abstraction timing.

Meta-skill that automates the 10-step improvement cycle - detects patterns, generates skills, creates commands, and triggers documentation. Use when user says "auto-improve", "detect inefficiency", or "generate skill".