Development

Record browser sessions using Playwright for web UI tutorials.Captures video of browser interactions that can be converted to GIF.Triggers: browser recording, playwright, web demo, ui recordingUse when: creating browser-based tutorials showing web UI interactions

Shared testing quality metrics and standards for cross-plugin use. Referencedby pensive:test-review and parseltongue:python-testing.Triggers: testing standards, quality metrics, coverage thresholds, test quality,anti-patterns, testing best practices, quality gatesUse when: evaluating test quality, setting coverage thresholds, identifyingtesting anti-patterns, establishing quality standardsDO NOT use when: simple scripts without quality requirements.Consult this skill when establishing testing quality standards.

Employ the Hexagonal (Ports & Adapters) pattern to decouple domain logic frominfrastructure, maximizing flexibility and testability.Triggers: hexagonal architecture, ports and adapters, infrastructure independence,dependency inversion, clean architecture, domain isolation, adapter pattern,infrastructure abstraction, database independence, framework independenceUse when: designing systems with strong business logic separation, anticipatinginfrastructure changes, needing easy mocking for tests, building portable domain codeDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: building simple CRUD apps without complex domain logic.Consult this skill when implementing hexagonal patterns or migrating to port-based design.

Systematic methodology to reduce skill file size through externalization, consolidation, and progressive loading patterns. Triggers: large skill, skill optimization, skill size, 300 lines, inline code, skill refactoring, skill context reduction, skill modularization Use when: skills exceed 300 lines, multiple code blocks (10+) with similar functionality, heavy Python inline with markdown, functions >20 lines embedded DO NOT use when: skill is under 300 lines and well-organized. DO NOT use when: creating new skills - use modular-skills instead. Consult this skill when skills-eval shows "Large skill file" warnings.

Design skills as modular building blocks for predictable token usage.Triggers: skill design, skill architecture, modularization, token optimization,skill structure, refactoring skills, new skill creation, skill complexityUse when: creating new skills that will be >150 lines, breaking down complexmonolithic skills, planning skill architecture, refactoring overlapping skills,reviewing skill maintainability, designing skill module structureDO NOT use when: evaluating existing skill quality - use skills-eval instead.DO NOT use when: writing prose for humans - use writing-clearly-and-concisely.DO NOT use when: need improvement recommendations - use skills-eval.Use this skill BEFORE creating any new skill. Check even if unsure.

Security practices including secrets management, input validation, SSRF prevention, and production hardening. Use for security-sensitive code.

Asynchronous event-based communication to decouple producers/consumers for scalability and resilience.Triggers: event-driven, message queue, pub/sub, asynchronous processingUse when: real-time workloads or multiple subsystems react to same eventsDO NOT use when: simple request-response patterns suffice.

Data-grid architecture for high-traffic stateful workloads with linear scalability.Triggers: space-based, data grid, in-memory, linear scaling, high trafficUse when: traffic overwhelms database nodes or linear scalability neededDO NOT use when: data doesn't fit in memory or simpler caching would work.

Workflow rules for task execution, respecting user code, and git commits. Use when planning or executing development tasks.

Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.

Post-process video files and generate optimized GIFs.Converts webm/mp4 to GIF with configurable quality settings.Triggers: gif conversion, video to gif, optimize gif, webm to gifUse when: converting browser recordings to GIF format, optimizing GIF file size

detailed development workflow with modular patterns for git, code review, testing, documentation, and deployment

Declarative release readiness checklist that mirrors GitHub checks,deployment issues, and documentation requirements.Triggers: release gates, release readiness, deployment checklist, release review,quality signals, rollout scorecard, QA handshake, deployment gatesUse when: preparing releases, validating deployment gates, conducting releasereviews, embedding release gate snippets in PRsDO NOT use when: weekly status updates - use github-initiative-pulse.DO NOT use when: code reviews - use pensive review skills.Standardizes release approvals with GitHub-aware checklists.

Foundational workflow for preparing and structuring detailed reviews(architecture, API, code quality).Triggers: review workflow, structured review, review scaffolding, evidence capture,review preparation, analysis framework, review templateUse when: starting any detailed review workflow, needing consistent structurefor capturing context and findings, ensuring comparable review outputsDO NOT use when: quick catchup without formal review - use catchup.DO NOT use when: diff-focused analysis - use diff-analysis.Use this skill at the BEGINNING of any detailed review for consistent structure.

Model system responsibilities across clients, servers, and optional peer-to-peernodes for traditional distributed applications.Triggers: client-server, web architecture, mobile backend, API design, thin client,thick client, peer-to-peer, P2P, offline-first, synchronizationUse when: traditional web/mobile applications with centralized services,clear separation between client and server responsibilities neededDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: peer-to-peer dominates - consider dedicated P2P patterns.Consult this skill when designing client-server systems or API architectures.

Structured file enumeration and content analysis for understanding codebasestructure before reviews or refactoring.Triggers: file analysis, codebase structure, directory mapping, hotspot detection,code exploration, file enumeration, structure mapping, module boundariesUse when: before architecture reviews to understand file organization, exploringunfamiliar codebases to map structure, estimating scope for refactoring or migrationDO NOT use when: general code exploration - use the Explore agent.DO NOT use when: searching for specific patterns - use Grep directly.Provides structural context for downstream review and refactoring workflows.

Update and maintain tests following TDD/BDD principles with detailedquality assurance.Triggers: test updates, test maintenance, test generation, TDD workflow,BDD patterns, test coverage, pytest, test enhancement, quality assuranceUse when: updating existing tests, generating new tests for features,enhancing test quality, ensuring detailed coverage, pre-commit validationDO NOT use when: auditing test suites - use pensive:test-review.DO NOT use when: writing production code - focus on implementation first.Run git-workspace-review first to understand which tests need updates.

Process external resources into actionable knowledge with evaluation, storage, and application decisions.Triggers: knowledge intake, article evaluation, paper review, external resourceUse when: user shares links to articles, papers, or external resourcesDO NOT use when: searching existing knowledge - use knowledge-locator.

Analyze and enhance Makefiles for complete user functionality coverage.Triggers: Makefile analysis, Makefile gaps, missing targets, plugin release,Makefile coverage, build targets, make dogfood, plugin qualityUse when: analyzing Makefile completeness before releasing plugins, identifyinggaps during plugin maintenance, scoring Makefiles against best practices,verifying Makefiles support standard developer workflowsDO NOT use when: writing initial Makefiles from scratch.DO NOT use when: debugging specific build target failures.DO NOT use when: creating custom non-standard build systems.Use this skill BEFORE releasing any plugin to verify Makefile coverage.

JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.