測試與安全

Create clear, testable specifications with user stories and acceptance criteria.Triggers: spec writing, feature specification, requirements, user storiesUse when: creating new specifications or writing acceptance criteriaDO NOT use when: generating implementation tasks - use task-planning.

Reusable patterns and templates for Claude Code skill and hook development.Triggers: validation patterns, error handling, testing templates, workflow patterns,shared patterns, reusable templates, DRY patterns, common workflowsUse when: creating new skills or hooks that need consistent patterns, implementingvalidation logic, setting up error handling, creating test scaffolding,referencing standard workflow structuresDO NOT use when: pattern is specific to one skill only.DO NOT use when: pattern is still evolving - wait for stability.DO NOT use when: pattern is context-dependent requiring variations.Reference these patterns to validate consistency across the ecosystem.

Compose processing stages using a pipes-and-filters model for ETL, mediaprocessing, or compiler-like workloads.Triggers: pipeline architecture, pipes and filters, ETL, data transformation,stream processing, CI/CD pipeline, media processing, batch processingUse when: data flows through fixed sequence of transformations, stages can beindependently developed and tested, parallel processing of stages is beneficialDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: data flow isn't sequential or predictable.DO NOT use when: complex branching/merging logic dominates.Consult this skill when designing data pipelines or transformation workflows.

Orchestrate tutorial generation from VHS tapes and Playwright specs to dual-tone markdown with GIF recording.Triggers: tutorial update, gif generation, tape recording, update tutorial, regenerate gifs, tutorial manifestUse when: regenerating tutorial GIFs, updating documentation demos, creating tutorials from tape filesDO NOT use when: only updating text - use doc-updates.DO NOT use when: only capturing browser - use scry:browser-recording directly.

Evaluate public API surfaces against internal guidelines and external exemplars.Triggers: API review, API design, consistency audit, API documentation,versioning, surface inventory, exemplar researchUse when: reviewing API design, auditing consistency, governing documentation,researching API exemplarsDO NOT use when: architecture review - use architecture-review.DO NOT use when: implementation bugs - use bug-review.Use this skill for API surface evaluation and design review.

Python testing with pytest, fixtures, mocking, and TDD workflows.Triggers: pytest, unit tests, test fixtures, mocking, TDD, test suite, coverage,test-driven development, testing patterns, parameterized testsUse when: writing unit tests, setting up test suites, implementing TDD,configuring pytest, creating fixtures, async testingDO NOT use when: evaluating test quality - use pensive:test-review instead.DO NOT use when: infrastructure test config - use leyline:pytest-config.Consult this skill for Python testing implementation and patterns.

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.

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

System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.

CQRS and Event Sourcing for auditability, read/write separation, and temporal queries.Triggers: CQRS, event sourcing, audit trail, temporal queriesUse when: read/write scaling differs or audit trail requiredDO NOT use when: simple CRUD - use architecture-paradigms first.

Functional Core, Imperative Shell: isolate deterministic logic from side effects for testability.Triggers: functional core, imperative shell, pure functions, testabilityUse when: business logic is entangled with I/O or tests are brittleDO NOT use when: simple scripting without complex logic.

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

Standardized pytest configuration for plugin development with shared test patterns.Triggers: pytest configuration, conftest, fixtures, test setupUse when: setting up pytest for plugin development or creating fixtures

Monitor and optimize CPU/GPU usage with load measurement and cost-effectivevalidation strategies.Triggers: CPU usage, GPU usage, performance, load monitoring, build performance,training, resource consumption, test suite, compilationUse when: session starts (auto-load with token-conservation), planning buildsor training that could pin CPUs/GPUs for >1 minute, retrying failed resource-heavy commandsDO NOT use when: simple operations with no resource impact.DO NOT use when: quick single-file operations.Use this skill BEFORE resource-intensive operations. Establish baselines proactively.

Configure GitHub Actions workflows for CI/CD (test, lint, typecheck, publish)

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.

Authentication patterns for external services: API keys, OAuth, token management, verification.Triggers: authentication, API keys, OAuth, token management, credentialsUse when: integrating external services or implementing authentication flows

Master Python asyncio, concurrent programming, and async/await patternsfor high-performance applications.Triggers: asyncio, async/await, coroutines, concurrent programming, async API,I/O-bound, websockets, background tasks, semaphores, async context managersUse when: building async APIs, concurrent systems, I/O-bound applications,implementing rate limiting, async context managersDO NOT use when: CPU-bound optimization - use python-performance instead.DO NOT use when: testing async code - use python-testing async module.Consult this skill for async Python patterns and concurrency.