技術寫作

This skill should be used to update terminal window title with context. Triggers automatically at session start via hook. Also triggers on topic changes during conversation (debugging to docs, frontend to backend). Updates title with emoji + project + current topic.

Technical tutorial writing in modified DigitalOcean style. Use when (1) writing step-by-step technical tutorials, (2) creating documentation for code/applications, (3) explaining technical concepts procedurally, (4) working with Temporal applications/tutorials, or (5) the user asks to write, create, or help with a tutorial. Follows specific style constraints: friendly but formal tone, comprehensive explanations, code sandwich approach, assumes English is reader's second language, and never generates new code (only references provided code).

This skill should be used when moving from design to implementation. Triggers on "let's build", "implement this", "looks good let's code", "ready to implement". Presents options for parallel agent competition (cookoff), single subagent, or local implementation. Each agent creates own plan from shared design for genuine variation.

Central authority for Claude Code subagents (sub-agents). Covers agent file format, YAML frontmatter, tool access configuration, model selection (inherit, sonnet, haiku, opus), automatic delegation, agent lifecycle, resumption, command-line usage (/agents), Agent SDK programmatic agents, priority resolution, and built-in agents (Plan subagent). Assists with creating agents, configuring agent tools, understanding agent behavior, and troubleshooting agent issues. Delegates 100% to docs-management skill for official documentation.

Git 提交前文檔同步。觸發：docs、文檔、sync docs、發布。

RSpec testing patterns for Ruby and Rails. Use when writing tests, reviewing test code, or discussing testing strategy. Covers structure, naming, matchers, and external service stubbing.

Systematic code review skill checking documentation quality and promoting code reuse

Comprehensive Azure Data Factory knowledge base with official documentation sources, CI/CD methods, deployment patterns, and troubleshooting resources

Discipline epistemique stricte pour eliminer les derives cognitives de Claude. Activation SYSTEMATIQUE sur TOUTES les conversations. Impose: (1) Zero invention/supposition, (2) Honnetete absolue, (3) Vision holistique avec relecture du contexte, (4) Questions plutot que suppositions, (5) Remise en contexte perpetuelle avec checkpoints structures, (6) Documentation incrementielle sans doublons, (7) Vigilance workflow/CI-CD/securite, (8) TODO/plan obligatoire avant tout travail, (9) Documentation FR/EN scholar style signee Julien GELEE, (10) Zero credentials/API keys/donnees sensibles en clair. Posture ingenieur generaliste specialise IA.

Systematic approach to implementing new features in the Rust memory system following project conventions. Use when adding new functionality with proper testing and documentation.

Core documentation generation patterns and framework for Treasure Data pipeline layers. Provides shared templates, quality validation, testing framework, and Confluence integration used by all layer-specific documentation skills.

Central authority for Claude Code slash commands. Covers built-in commands, custom slash commands (project and personal), plugin commands, MCP slash commands, SlashCommand tool, frontmatter configuration, arguments ($ARGUMENTS, $1, $2), bash execution, file references, namespacing, and skills vs slash commands comparison. Assists with creating custom commands, configuring command behavior, understanding command types, and troubleshooting command issues. Delegates 100% to docs-management skill for official documentation.

Use when writing or modifying Lea code - pipe-oriented functional language with tree-walk interpreter

Move or rename a file while automatically updating all references in source code and documentation

Comprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills. Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, or troubleshooting skill activation issues. Delegates to docs-management skill for official documentation.

Professional technical writing and documentation skill for creating and maintaining comprehensive, accurate, and user-friendly documentation for codebases, APIs, deployment processes, and end-user guides.

C4 model architecture visualization and documentation

Comprehensive template and guidelines for documenting Field Agents including technical specifications, system prompts, tool specifications, user interactions, and standardized documentation structure

Automated contract verification, detection, and remediation across multiple languages using formal preconditions, postconditions, and invariants. This skill provides both reference documentation AND execution capabilities for the full PLAN -> CREATE -> VERIFY -> REMEDIATE workflow.

Single source of truth and librarian for ALL Duende Software documentation. Manages local documentation storage, scraping, discovery, and resolution. Use when finding, locating, searching, or resolving Duende documentation; discovering docs by keywords, category, tags, or natural language queries; scraping from llms-full.txt; managing index metadata (keywords, tags, aliases); or rebuilding index from filesystem. Run scripts to scrape, find, and resolve documentation. Handles doc_id resolution, keyword search, natural language queries, category/tag filtering, alias resolution, llms-full.txt parsing, markdown subsection extraction for internal use, hash-based drift detection, and comprehensive index maintenance.