Conduct a focused reliability assessment based on the Well-Architected Framework Reliability pillar. Use when user says "reliability review", "wa reliability", or "check reliability". Analyzes resilience patterns, data reliability, infrastructure resilience, and recovery capabilities.
Read a prototype GDD and generate a phased implementation roadmap with concrete tasks, organized by implementation phases with specific deliverables and test criteria.
Comprehensive BOQ (Bill of Quantities) creation and management for construction projects. This skill should be used when Claude needs to: (1) Create new BOQ files with standard work categories, (2) Add items to existing BOQ, (3) Manage construction cost estimates with material and labor breakdowns, (4) Generate Thai construction project cost sheets with proper formatting
セッションコンテキストを表示。タブを離れて戻ってきた時に「何をやっていたか」「何を依頼したか」「次に何をすべきか」を思い出すために使用。
ローカルサーバーで起動している Marp スライドを視覚的に検証し、レイアウト問題を自動修正するスキル。「スライドをレビュー」「Marp スライドの視覚的チェック」「スライドのレイアウトを確認」「プレゼン資料の見た目を検証」などのリクエストでトリガーします。テキストの切れ目、重なり、配置問題、コントラスト不足、はみ出し、余白不足などの視覚的問題を検出・修正します。
Log the current coding session to project memory. Use at the end of a session to record accomplishments, decisions, and follow-ups. Triggers on: log this session, save session, end session, record what we did.
This skill provides patterns for identifying, categorizing, and tracking technical debt. It includes scoring methodologies, YAML schemas for tracking files, and strategies for systematic debt resolution.
Comprehensive guide to incident severity classification and response requirements
Use when you have a spec or requirements for a multi-step task, before touching code. Creates detailed implementation plans with bite-sized tasks.
Cette skill devrait être utilisée pour réviser des présentations PowerPoint selon les standards de conseil (McKinsey, BCG), avec analyse de la structure, clarté, design, storytelling et conformité DSFR. Utiliser quand l'utilisateur demande une révision, analyse ou amélioration de présentation, avec ajout de commentaires directement dans les slides.
Perform organisational mining and handover-of-work analysis with privacy-aware controls.
개발 문서 통합 관리 시스템. 개발 방향, 진행 상황, 계획, 변경 사항, 피드백을 체계적으로 기록하고 관리. "문서 시스템", "개발 기록", "방향 설정", "회고", "변경 이력" 키워드에 반응.
Reasoning frameworks and problem decomposition techniques. Use when planning implementation, evaluating arguments, estimating scope, decomposing complex tasks, or applying first principles thinking.
Triage extension for requirements findings during plan-finalize phase
Create ATOMIC implementation plan for a single frontend task. Each step has exact code and verification command. IMPORTANT: This skill creates MICRO-LEVEL atomic steps, NOT macro architecture plans. For architecture planning or feature scoping, use EnterPlanMode instead. Use this skill when: - Running /frontend.plan command - User explicitly asks for "atomic steps", "step-by-step plan with verification" - Have a specific task from docs/reference/frontend/tasks/ and need implementation steps - Need granular steps: Setup (create files) → Implementation (write code) → Test (verify) → Commit DO NOT use for: - Architecture planning (use EnterPlanMode) - General development planning - Feature scoping or estimation Output: Present plan to user (not saved to file), each step includes Files, Action, and Verify command.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
List Beads tasks that are ready to start (no open blockers)
