DevOps

Use when troubleshooting Atmos configuration, deployment errors, or unexpected behavior. Covers debug logging, describing stacks/components, interpreting errors, and common issues with stack resolution and Atmos functions.

Use when wiring cross-component dependencies in stack YAML. Covers !terraform.state syntax for passing outputs between components without remote-state lookups.

Building, rendering library docs, and deploying docs.cloudposse.com. Use when working with the Docusaurus build process or regenerating auto-generated content.

CSS styles, color themes, and visual conventions for docs.cloudposse.com. Use when styling components, mermaid diagrams, or working with site theming.

Verifies builds, recovers from errors, and applies review fixes. Use when user mentions ビルド, build, 検証, verify, エラー復旧, error recovery, 指摘を適用, apply fixes, テスト実行, tests fail, lint errors occur, CI breaks, テスト失敗, lintエラー, 型エラー, ビルドエラー, CIが落ちた. Do NOT load for: 実装作業, レビュー, セットアップ, 新機能開発.

UI/UX design guidelines for interactions, animation, layout, accessibility, and visual design. Use when building UI components, designing user experiences, or implementing user-facing features.

Write tests following TDD principles. Use when implementing features, fixing bugs, or adding test coverage. Covers e2e, integration, and unit testing patterns.

Semantic search for memory. Use to find solutions, patterns, or context from Chroma Cloud.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Aggregates and summarizes the latest AI news from multiple sources including AI news websites and web search. Provides concise news briefs with direct links to original articles. Activates when user asks for 'today's AI news', 'AI updates', 'latest AI developments', or mentions wanting a 'daily AI briefing'.

Guides systematic code refactoring following the DRY (Don't Repeat Yourself) principle. Use when user asks to eliminate code duplication, refactor repetitive code, apply DRY principle, or mentions code smells like copy-paste, magic numbers, or repeated logic. Implements a 4-step workflow from identifying repetition to verified refactoring.

Systematic approach for creating minimal-change, reversible implementation plans. Claude invokes this skill when transforming requirements/research into executable blueprints. Emphasizes simplicity, safety, and clear verification steps.

Validates KCL Crossplane compositions with comprehensive checks including formatting, syntax validation, and rendering tests. Automatically activates when working with KCL files, Crossplane compositions, or before commits touching infrastructure/base/crossplane/configuration/. Prevents CI failures and catches critical bugs like the mutation pattern.

Create distributable Python packages with proper structure and publishing.Triggers: Python packaging, pyproject.toml, uv, pip, PyPI, distribution, CLI tools,entry points, package structure, publishingUse when: creating Python packages, configuring pyproject.toml, setting upentry points, publishing to PyPI, CI/CD for packagesDO NOT use when: testing packages - use python-testing instead.DO NOT use when: optimizing package performance - use python-performance.Consult this skill for Python package creation and distribution.

Transform project brief into detailed, testable specifications using spec-driven development methodology

Generate phased, dependency-ordered tasks from specs. Identifies parallelization opportunities.Triggers: task planning, dependency ordering, phased breakdown, parallel tasksUse when: converting specifications to implementation tasksDO NOT use when: writing specifications - use spec-writing.

Spatial indexing and retrieval system for finding information within memorypalaces using multi-modal search.Triggers: knowledge search, find information, locate concept, recall, spatialquery, cross-reference, discovery, memory retrieval, pr review search,past decisions, review patternsUse when: searching for stored knowledge, cross-referencing concepts,discovering connections, retrieving from palaces, finding past PR decisionsDO NOT use when: creating new palace structures - use memory-palace-architect.DO NOT use when: processing new external resources - use knowledge-intake.Consult this skill when searching or navigating stored knowledge.

Generate language-specific Makefile with common development targets

Context-aware progressive module loading with hub-and-spoke pattern for token optimization.Triggers: progressive loading, lazy loading, hub-spoke, module selectionUse when: optimizing skill loading or reducing upfront context usage

Construct temporary, session-specific memory palaces for complex projectsand conversations.Triggers: session context, project memory, conversation state, temporary storage,session palace, context preservation, complex project, extended conversationUse when: working on complex multi-step projects, preserving context acrossinterruptions, tracking session-specific stateDO NOT use when: permanent knowledge structures needed - use memory-palace-architect.DO NOT use when: searching existing knowledge - use knowledge-locator.Consult this skill for session-scoped temporary knowledge structures.