Content & Media

Complete guide for writing Claude Code and SDK hooks with security-first design.Triggers: hook creation, hook writing, PreToolUse, PostToolUse, UserPromptSubmit,tool validation, logging hooks, context injection, workflow automationUse when: creating new hooks for tool validation, logging operations for audit,injecting context before prompts, enforcing project-specific workflows,preventing dangerous operations in productionDO NOT use when: logic belongs in core skill - use Skills instead.DO NOT use when: complex multi-step workflows needed - use Agents instead.DO NOT use when: behavior better suited for custom tool.Use this skill BEFORE writing any hook. Check even if unsure.

Consolidates ephemeral LLM-generated markdown files into permanent documentation.Triggers: consolidate docs, untracked reports, ephemeral files, git cleanup,report consolidation, knowledge extraction, REPORT.md files, ANALYSIS.md filesUse when: you have untracked *_REPORT.md or *_ANALYSIS.md files, git statusshows markdown artifacts that shouldn't be committed, preparing PR and needto clean up working artifacts, preserving insights from code reviewsDO NOT use when: files are already in docs/ or skills/ locations.DO NOT use when: files are intentionally temporary scratch notes.DO NOT use when: source files have no extractable value.Merges valuable content into permanent documentation, then deletes source files.

Code design patterns: pure functions, immutability, composition, and async. Use when designing code or functions.

Generic weighted scoring and threshold-based decision framework for evaluatingartifacts against configurable criteria.Triggers: evaluation, scoring, quality gates, decision framework, rubrics,weighted criteria, threshold decisions, artifact evaluationUse when: implementing evaluation systems, creating quality gates, designingscoring rubrics, building decision frameworksDO NOT use when: simple pass/fail without scoring needs.Consult this skill when building evaluation or scoring systems.

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.

Design and construct virtual memory palaces for spatial knowledge organizationusing mnemonic techniques.Triggers: memory palace, spatial organization, mnemonic, knowledge architecture,domain mapping, layout design, memory structure, recall enhancementUse when: creating new memory palace structures, organizing complex domains,designing spatial layouts for knowledge retentionDO NOT use when: quick knowledge search - use knowledge-locator instead.DO NOT use when: session-specific context - use session-palace-builder.Consult this skill when designing permanent memory palace structures.

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.

Serverless FaaS for event-driven workloads with minimal infrastructure management.Triggers: serverless, FaaS, Lambda, event-driven, pay-per-useUse when: workloads are event-driven with bursty trafficDO NOT use when: long-running processes or stateful operations required.

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.

Combine multiple media assets (GIFs, videos) into composite tutorials.Supports vertical/horizontal layouts and sequential stitching.Triggers: combine media, stitch gifs, composite, merge recordingsUse when: combining terminal and browser recordings into a single tutorial

Guide to deciding whether to escalate from a lower model (haiku/sonnet) toa higher model (sonnet/opus).Triggers: model escalation, haiku to sonnet, sonnet to opus, reasoning depth,task complexity, model selection, capability trade-offUse when: evaluating whether to escalate models, facing genuine complexityrequiring deeper reasoning, novel patterns with no existing solutions,high-stakes decisions requiring capability investmentDO NOT use when: thrashing without investigation - investigate root cause first.DO NOT use when: time pressure alone - urgency doesn't change task complexity.DO NOT use when: "just to be safe" - assess actual complexity instead.NEVER escalate without investigation first. This is the Iron Law.

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.

Build a minimal, stable core system that loads plug-ins to provide featurevariability and extensibility for platform development.Triggers: microkernel, plugin architecture, plugin system, extensibility,platform design, IDE architecture, marketplace, core system, plugin loaderUse when: building platforms, IDEs, or marketplaces with third-party extensions,core stability is critical while features vary, plugin isolation is neededDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: no extensibility requirements exist.DO NOT use when: plugin isolation overhead isn't justified.Consult this skill when designing plugin architectures or building platforms.

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.

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.

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