Technical Writing

Use this skill when creating, updating, or querying AI-optimized tracking artifacts (progress files, context notes, bug fixes, observation logs) in YAML+Markdown hybrid format for 95% token reduction. Invoke for: creating phase progress tracking, updating task status and blockers, querying pending work across phases, generating session handoff reports, validating artifact completeness, or migrating existing markdown files to hybrid format. Provides three embedded agents (artifact-tracker, artifact-query, artifact-validator) plus Python migration tools for efficient multi-phase project tracking.

Pre-commit validation checklist before staging and committing code. Use BEFORE every git commit to ensure code quality, tests pass, and documentation is updated. Triggers on "commit", "stage changes", "ready to commit", or when completing a feature or fix.

This skill should be used when the user asks to "write documentation", "create docs", "document code", "improve documentation", "documentation best practices", "diataxis", "technical writing", "API documentation", "user guide", mentions documentation quality, documentation structure, or needs guidance on software documentation standards and frameworks.

Python testing framework for writing simple, scalable, and powerful tests

Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, efficient JavaScript code. Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications.

Implement robust error handling with user-friendly messages, specific exception types, centralized error handling, and graceful degradation strategies across the application. Use this skill when writing error handling logic in any code file, implementing try-catch blocks, raising or throwing exceptions, or designing error response formats. Use this skill when validating input and failing fast with clear messages, implementing retry strategies for transient failures, ensuring proper resource cleanup in finally blocks, or creating centralized error handling middleware. Use this skill when working with API endpoints, service layers, data access code, or any code that could fail and needs proper error handling. Use this skill when designing error responses for users or implementing graceful fallback behaviors.

Generate QA steps for Jira tickets in German/English technical writing style

Integrated project management system with documentation, language initialization, and template optimization modules

Create and manage database migrations with reversible up/down methods, focused changes, and zero-downtime deployment considerations. Use this skill when creating or modifying migration files in directories like migrations/, db/migrate/, alembic/versions/, sequelize/migrations/, prisma/migrations/, or any database schema versioning folders. Use this when adding or altering database tables, columns, indexes, foreign keys, or constraints in migration scripts, implementing both up (apply changes) and down (rollback changes) methods for reversible migrations that allow safe rollbacks if deployments fail, writing migration scripts for ORMs and migration tools like Sequelize, Alembic, Django migrations, Rails migrations, TypeORM, Prisma migrations, Knex.js migrations, or any database migration framework, creating database indexes on large tables using concurrent creation options like CREATE INDEX CONCURRENTLY in PostgreSQL to avoid table locks that would block production traffic during deployment, separating schema

Technical documentation architect that creates comprehensive technical documentation (both short-form guides and long-form manuals) with architecture diagrams, design rationale, and implementation guides. Explains the what and the why.

This skill should be used for exploring codebases, looking up documentation, investigating how things work, and gathering context without making code changes. Use for "how does X work?", "find where Y is handled", or "explain Z" questions.

Skill for implementing frontend features following project conventions. Use when writing Vue components, creating UI, or refactoring frontend code. Loads all frontend rules from .claude/rules/frontend/.

Write bilingual blog articles for the personal website. Use when creating a new blog post, article, or writing content for the blog. Handles EN/ES translations, frontmatter, and content structure.

Validates that skills in this repository are accurately documented in the README. Use when verifying skill documentation or during pre-commit validation.

clerk expert with self-populating documentation

Generate comprehensive FAQs from common learner questions, analytics, discussion forums, and support tickets. Use for self-service support. Activates on "FAQ", "common questions", "help documentation", or "student support".

Index markdown documentation - headings, diagrams, tables, code blocks, links. Use for quick overview without reading full files.

End-to-end testing with Playwright for web applications. Use when writing E2E tests, browser automation, visual regression testing, or debugging test failures. Triggers on Playwright, E2E, browser testing, or test automation questions.

Create conference talk outlines and iA Presenter markdown slides using the Story Circle narrative framework. Use when structuring a tech talk, creating presentation slides, or organizing talk ideas into a story-driven format.

Create an educational MicroSim using the vis-network JavaScript library. Each MicroSim is a directory located in the /docs/sims folder. It has a main.html file that can be referenced with an iframe. The main.html file imports the main JavaScript code to run the educational MicroSim.