文件

Update documentation with writing guideline enforcement, consolidation detection, and accuracy verification.Triggers: documentation update, docs update, ADR, docstrings, writing guidelines, readme update, debloat docsUse when: updating documentation after code changes, enforcing writing guidelines, maintaining ADRsDO NOT use when: README-specific updates - use update-readme instead.DO NOT use when: complex multi-file consolidation - use doc-consolidation.Use this skill for general documentation updates with built-in quality gates.

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.

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.

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.

Code quality practices: error handling, validation, logging, and DRY. Use when writing or reviewing code.

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 modularizationUse when: skills exceed 300 lines, multiple code blocks (10+) with similarfunctionality, heavy Python inline with markdown, functions >20 lines embeddedDO 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.

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.

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.

Generic template patterns and lifecycle stages for knowledge storage,configuration management, and structured documentation.Triggers: storage templates, lifecycle stages, maturity progression, namingconventions, knowledge storage, configuration templates, documentation patternsUse when: organizing knowledge storage, managing configuration lifecycle,creating structured documentation, establishing naming conventionsDO NOT use when: simple storage without lifecycle or structure needs.Consult this skill when designing storage and documentation systems.

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.

Generate program dashboards, GitHub-ready comment digests, and CSV summariessourced from Minister's tracker data.Triggers: initiative pulse, status report, weekly update, stakeholder briefing,github dashboard, blocker radar, initiative health, program metricsUse when: creating status reports, weekly updates, stakeholder briefings,generating GitHub comment digests, tracking initiative healthDO NOT use when: release gates/readiness - use release-health-gates.DO NOT use when: project planning - use spec-kit:speckit-orchestrator.Outputs markdown digests and CSV exports for GitHub issues and PRs.

Evaluate and improve Claude skill quality through auditing.Triggers: skill audit, quality review, compliance check, improvement suggestions,token usage analysis, skill evaluation, skill assessment, skill optimization,skill standards, skill metrics, skill performanceUse when: reviewing skill quality, preparing skills for production, auditingexisting skills, generating improvement recommendations, checking compliancewith standards, analyzing token efficiency, benchmarking skill performanceDO NOT use when: creating new skills from scratch - use modular-skills instead.DO NOT use when: writing prose for humans - use writing-clearly-and-concisely.DO NOT use when: need architectural design patterns - use modular-skills.Use this skill BEFORE shipping any skill to production. Check even if unsure.

Generate terminal recordings using VHS (Charmbracelet) tape files.Executes tape files to produce GIF outputs of terminal sessions.Triggers: terminal recording, vhs tape, terminal demo, cli demoUse when: creating terminal recordings for tutorials and documentation

Guide to effective Claude Code skill authoring using TDD methodology andpersuasion principles.Triggers: skill authoring, skill writing, new skill, TDD skills, skill creation,skill best practices, skill validation, skill deployment, skill complianceUse when: creating new skills from scratch, improving existing skills withlow compliance rates, learning skill authoring best practices, validatingskill quality before deployment, understanding what makes skills effectiveDO NOT use when: evaluating existing skills - use skills-eval instead.DO NOT use when: analyzing skill architecture - use modular-skills instead.DO NOT use when: writing general documentation for humans.YOU MUST write a failing test before writing any skill. This is the Iron Law.