sumik5
70 verified skills70 total stars
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
data-ai1
implementing-as-tachikoma
Operates as Tachikoma Agent (Implementation Worker) performing actual code implementation. Use when receiving task assignments from Claude Code for implementation work, test creation, or documentation. Adapts to frontend, backend, or testing roles based on task assignment.
development1
gws-slides
Google Slides: Read and write presentations.
development1
implementing-dynamic-authorization
Dynamic authorization design covering ABAC, ReBAC, PBAC models and Cedar policy language. Use when designing access control systems, choosing authorization models, or writing Cedar policies. Distinct from securing-code (code-level) by focusing on authorization model selection and policy-based access control.
development1
managing-keycloak
Comprehensive Keycloak identity and access management guide covering OIDC/SAML protocols, SSO, Realms, Clients, Users, Roles, authentication flows, MFA, authorization policies, JWT token management, application integration (Java/Node.js/Spring Boot), Docker/Kubernetes deployment, clustering, and SPI extensions. MUST load when keycloak.json, keycloak.conf, or Keycloak-related dependencies are detected. For general security practices, use securing-code instead. For Cedar/ABAC/ReBAC authorization models, use implementing-dynamic-authorization instead.
tools1
practicing-devops
DevOps実践ガイド（進化3ステージ・IaCツール選定・オーケストレーション・CI/CD・コンテナ管理）。 Use when practicing DevOps, selecting IaC tools, designing CI/CD pipelines, or managing Docker/Podman containers. Docker/Podman、マルチステージビルド、Compose、セキュリティ強化を含む。 For continuous delivery philosophy, CD maturity assessment, and deployment pipeline design principles, see CONTINUOUS-DELIVERY.md subfile. For project foundations, team organization, and developer habits, use practicing-software-engineering instead. For monitoring and observability design, use implementing-observability instead. For GCP CI/CD and GKE container orchestration, use developing-google-cloud instead. For GPU-optimized Docker/Kubernetes environment tuning (NVIDIA Container Toolkit, MPS, MIG), use designing-genai-patterns instead.
tools1
building-design-systems
Design system construction, governance, Figma implementation, and practical launch/adoption methodology covering system foundations, pattern taxonomy (CEV naming), organizational adoption (consensus building, proposal templates), pattern library operations, UI pattern catalog (20+ patterns), Figma variable/token architecture, incremental launch, buy-in strategies, content creation, CI/CD automation, update notification framework (6 steps), operational ownership patterns, case studies, and self-assessment. Use when architecting, evaluating, or restructuring a design system, planning organizational adoption, building a pattern library, constructing a design system within Figma, starting a DS from scratch, or creating design system content. NOT for component styling (applying-design-guidelines), design-to-code (implementing-design), frontend codegen (designing-frontend), or Tailwind config (styling-with-tailwind).
tools1
applying-behavior-design
Behavioral design methodology for products that change user behavior using CREATE Action Funnel (Cue, Reaction, Evaluation, Ability, Timing) and three strategies (cheat, habit, conscious action). Use when designing product features that aim to change user habits, increase engagement, or guide users toward beneficial actions. For visual UI/UX design principles, use designing-ux instead. For training program design and facilitation methodology, use designing-training instead. For human-centered design thinking process (user research, ideation, prototyping), use designing-ux instead.
development1
implementing-design
Comprehensive design-to-code implementation skill covering general design principles, Figma MCP integration, and Figma UI design workflows. General: design system integration, visual parity validation, responsive implementation, accessibility. Figma MCP (13 tools): basic/advanced workflows (Figma Make, Code Connect, Design System Rules, design token sync), visual validation. Figma UI design: wireframe→prototype→detailed design→handoff workflow, 8pt grid, component-driven design, UIStack (5 states), style naming conventions, engineer collaboration. Use when implementing designs from any source (screenshots, mockups, Figma URLs, specs) or when designing mobile UI in Figma and preparing design handoff. Requires Figma MCP server for Figma-specific code generation workflows. For design system architecture and organizational adoption strategy, use building-design-systems instead.
tools1
applying-clean-architecture
Clean Architecture and Domain-Driven Design (DDD) unified guide covering the Dependency Rule, concentric layer model (Entities, Use Cases, Interface Adapters, Frameworks & Drivers), component principles (REP/CCP/CRP, ADP/SDP/SAP), Screaming Architecture, Humble Objects, and DDD strategic/tactical patterns (Bounded Context, Ubiquitous Language, Context Mapping, Value Object, Entity, Aggregate, Event Sourcing, CQRS, Saga, data decomposition). Use when designing application layer structure, enforcing dependency rules, separating business logic from frameworks/UI/databases, modeling complex domains with DDD patterns, or mapping Bounded Contexts to Clean Architecture layers. For code-level clean practices, use writing-clean-code. For distributed/infrastructure patterns, use architecting-infrastructure. For evolutionary architecture and microservices intro, see ARCHITECTURE-EVOLUTION.md. For project foundations and team practices, use practicing-software-engineering.
development1
automating-browser
Browser Agent CLIによるブラウザ操作自動化（セマンティックロケーター、状態永続化、ネットワーク傍受）。 Use when automating browser interactions via agent-browser CLI (NOT for E2E testing). E2Eテストは testing-e2e-with-playwright スキルを参照。
tools1
chronicle
Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request, where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle or asks what you can see from the screen.
testing1
creating-content
コンテンツ制作統合スキル。AIコピーライティング（15テクニック＋心理的トリガーでマーケティングコピー・ブログタイトル・広告見出し・SNS投稿を生成）とAIデザインクリエイティブ（バナー・SNS・ポスター等の広告ビジュアル制作プロンプト設計）を統合。 Use when creating marketing copy, blog titles, ad headlines, social media posts, or generating visual creatives (banners, social images, posters) with AI tools. For eliminating AI smell from text use writing-effective-prose. For UI/UX design principles use designing-ux. For presentations use creating-slides. For LaTeX → writing-latex.
tools1
architecting-infrastructure
Vendor-neutral infrastructure and system architecture patterns. Infrastructure: 127 patterns for availability (HA, DR, backup), security, performance/scalability, operations, network/storage configuration, and cloud. Modernization: socio-technical strategy, domain redesign, trade-off analysis (code/API/system/meta levels). Microservices: CQRS, Event Sourcing, Saga, distributed transactions, service granularity, data ownership, resilience, messaging. Use when designing infrastructure, evaluating non-functional requirements, modernizing legacy systems, making architectural trade-offs, or designing microservices.
development1
building-multi-tenant-saas
Multi-tenant SaaS architecture covering deployment models, tenant isolation, and data partitioning. Use when designing SaaS platforms or evaluating silo vs pool strategies. Covers identity, onboarding, tiering, and operations. For Next.js single-tenant SaaS (auth, payments), use developing-nextjs instead.
development1
designing-training
Training program design and facilitation methodology covering needs analysis (participant analysis, stakeholder mapping), KSA framework, instructional design theory (ADDIE, TOTE, Gagné, mastery learning), objective setting, activity catalog, training operations (instructor, space, logistics), brain science principles (7±2 rule, long-term memory, habit formation), learner-centered facilitation (90/20/8 rule, EAT), online/hybrid delivery, skill map creation, and training material development. Use when designing training programs, facilitating workshops, creating training materials, building skill maps, or managing training operations. For behavior design→applying-behavior-design. For presentation content→creating-slides. For design thinking process methodology (empathize/define/ideate/prototype/test)→designing-ux.
development1
creating-countdown-icons
カウントダウンアプリ用アプリアイコン（512×512 PNG）を絵文字・背景パレット選択の対話フローで生成するスキル。テキスト・絵文字・斜めストライプ背景を組み合わせたデザインアイコンを出力し、clean版とプレビュー版（白数字重ね）の2枚を提供する。 Use when creating app icons for countdown apps, generating text-based app icons with emoji, selecting icon designs interactively, or producing 512x512 PNG icons with diagonal striped backgrounds. 絵文字候補4択 → 背景パレット4択の対話フローで、ユーザーの意図に合ったアイコンを段階的に確定する。詳細な手順は INSTRUCTIONS.md を参照。
development1
designing-ux
UXデザイン総合ガイド（認知心理学・UIガイドライン・グラフィック基礎・デザイン思考・AIエクスペリエンス設計・Webビジュアルデザイン実践・UXメソッド実践）。 Use when designing user experiences, UI, conducting design thinking workshops, designing AI interfaces, creating web page layouts and visual designs, defining web design concepts using functionality/emotionality frameworks, or implementing UX methods such as usability evaluations, prototyping, user research, journey mapping, and organizational UX adoption. デザイン思考（d.school 5ステップ）、AIインターフェース設計（メンタルモデル、Copilotパターン）、Webレイアウト・配色・UIコンポーネント・モーションデザイン、Webデザイン機能性7軸・情緒性6軸フレームワーク、デザインコンセプト立案プロセス、レイアウト実践パターン（即応用可能な判断パターン集）、イメージワードシステム（デザイン方向性の言語化・共有手法）、クリエイティブプロセスパターン（プロの制作プロセス・発想法・試作サイクル）を含む。実践メソッド（PRACTICE-*）としてユーザビリティ評価・プロトタイピング・構造化シナリオ法・ユーザーリサーチ・カスタマージャーニーマップ・組織導入戦略を含む。
development1
designing-data-visualizations
Comprehensive data visualization principles covering chart type selection, color scales, design best practices, and data storytelling. Use when creating charts, dashboards, or any visual data representation. For UI/UX design principles, use designing-ux instead. For technical diagrams (flowcharts, architecture), use creating-diagrams instead.
testing1
developing-with-ai
AI-assisted development methodology covering prompt engineering, context engineering, code generation workflows, quality assurance, collaborative debugging, agent collaboration patterns, LLM dialogue design patterns (8 conversational patterns, Grammar of Intention), team LLM adoption workshops, and role-specific augmentation (Dev/PO/Coach/Manager). MUST load when working with AI coding tools or discussing AI-assisted development practices. Use when crafting prompts for code generation, managing AI context, reviewing AI-generated code, coordinating multi-agent workflows, or designing structured LLM dialogues.
tools1
integrating-ai-web-apps
Comprehensive guide to integrating generative AI into web applications using Vercel AI SDK, LangChain.js, and MCP with React/Next.js. Use when building AI-powered web features (streaming chat, RAG, tool calling, structured data generation) in JavaScript/TypeScript projects. For RAG system internals, use designing-genai-patterns. For MCP protocol development, use developing-mcp. For Next.js framework specifics, use developing-nextjs. For Python LangChain/LangGraph agent development, use building-ai-agents. For framework-agnostic GenAI design patterns (32 patterns covering content control through safety guardrails), use designing-genai-patterns.
tools1
mastering-typescript
Comprehensive TypeScript guide covering type system, advanced patterns, design patterns (GoF Creational/Structural/Behavioral), functional/reactive programming, framework integration, and 83 best practice decision criteria. MUST load when working in TypeScript projects detected by tsconfig.json. Covers Generics, Conditional Types, type inference, type design, SOLID/DDD in TypeScript, anti-patterns, and practical migration tips. Includes type safety rules (any prohibition, type guards, strict mode) formerly in enforcing-type-safety. Includes IDE-driven workflow and common TypeScript pitfalls (TT-PRACTICAL-WORKFLOW). Includes TSDoc/TypeDoc documentation generation workflow (CC-DOCUMENTATION).
development1
writing-clean-code
REQUIRED for all code implementations. Automatically load when writing or reviewing any code. Covers SOLID principles, MAPPER principles with 25 code smell categories, practical refactoring, software design laws, the 4 rules of simple design, 66 code smell heuristics, formatting principles, and boundary management patterns. Language-agnostic clean code guide. For language-specific practices, use developing-go, mastering-typescript, or developing-python. For architecture-level clean design, use applying-clean-architecture. For legacy code refactoring, see CHANGEABLE-CODE.md subfile. For refactoring mindset (spikes, feature toggles, structural discovery), see REFACTORING-MINDSET.md reference.
development1
developing-terraform
Terraform IaC development with HCL syntax, module design, state management, and Terragrunt wrapper patterns. MUST load when .tf files or terragrunt.hcl are detected, or go.mod contains 'terraform'. Covers AWS/GCP infrastructure patterns and mise task automation. For Docker infrastructure, use practicing-devops instead. For broader DevOps methodology and IaC tool comparison, use practicing-devops instead. For AWS CDK (TypeScript/Python IaC), use developing-aws instead.
tools1
authoring-plugins
Claude Code Plugin (Agent / Skill / Command) authoring guide. Use when creating, modifying, or reviewing plugin components. Includes Agent Skills standard (agentskills.io) + Claude Code extensions, context: fork applicability matrix, name/description constraint validation, and spec-freshness checks.
tools1
architecting-data
Data architecture patterns covering read-side optimization (replicas, materialized views, CQRS, CDC, event sourcing), domain-based decomposition, polyglot persistence, and caching strategies (cache-aside, read-through, write-through, write-around). Use when designing data flow architecture, choosing read scalability strategies, or implementing caching for enterprise systems. For microservices patterns (Saga, granularity), use architecting-infrastructure instead. For DDD domain modeling, use applying-clean-architecture instead. For database engine internals, use developing-databases instead. For relational DB schema design, use developing-databases instead. For GCP-specific data services (BigQuery, Dataflow, Dataproc), lakehouse (BigLake, Dataplex), and BigQuery advanced operations (editions, HA/DR), use developing-google-cloud instead.
development1
practicing-software-engineering
Comprehensive SW engineering practices covering project foundations (fast feedback, small steps, DORA metrics), team organization (Team Topologies, 4 types), pair programming (4 patterns), developer habits (GREAT framework), IC effectiveness mindset (outcomes vs outputs, strategic prioritization), career-stage skills (junior to staff, IC vs management), cross-functional influence (PM/design, authority-free leadership), 20 anti-patterns (15 individual + 5 team-level), sustainable performance (burnout, remote work), and AI-enhanced workflows (daily AI, 90-day rollout). Use when starting projects, organizing teams, for IC effectiveness, career growth, or team AI culture.
development1
evaluating-with-promptfoo
LLM evaluation and red-teaming toolkit using promptfoo. Covers promptfooconfig.yaml configuration, 40+ assertion types (deterministic, model-graded, RAG), provider setup (OpenAI, Anthropic, Google, Ollama, HTTP, custom JS/Python), red teaming (134+ plugins, jailbreak strategies, compliance frameworks), CLI commands, caching, and CI/CD integration. Use when writing promptfooconfig.yaml, designing LLM test suites, running adversarial red team evaluations, or integrating LLM quality gates in CI/CD. Detects: promptfooconfig.yaml or promptfoo in package.json. For general LLMOps operations, use designing-genai-patterns. For general test methodology (TDD/AAA), use testing-code.
tools1
building-ai-agents
AIエージェント構築ガイド（LangChain/LangGraph・Google ADK・リアルタイムマルチモーダル）。 Use when building AI agents with LangChain, LangGraph, Google ADK, or Gemini Live API. フレームワーク選択、ツール定義、マルチエージェント、A2A、リアルタイム音声/動画を含む。
development1
practicing-product-management
プロダクトマネジメント総合ガイド（基礎・AIプロダクト・A/Bテスト・成長戦略・GPM・PLG・カスタマーサクセス・Claude Code PM活用）。 Use when practicing product management, managing AI products, designing experiments, growth product management, PLG strategy, customer success, or using Claude Code as PM tool. AARRR海賊指標、AIプロダクトライフサイクル、MLプロダクト化、AI統合戦略、オンライン実験設計、PM調査パターン、GPM実践、リテンション戦略、拡張収益を含む。 For engineer-focused user story writing techniques (templates, common mistakes, splitting), use writing-user-stories instead.
tools1
creating-slides
HTMLスライド作成スキル。slides repoの3層分離モデル（Engine/Theme/Content）に基づく16:9 HTMLプレゼンデッキの作成・テーマカスタマイズ・ソース素材変換をガイド。認知科学・ロジック構築（接続関係診断・基本ロジック図）・ストーリーテリング・聴衆分析・スライドデザイン・ビジュアルデザイン実践・提案書構成術・デリバリー（実践Tips集含む）・準備プロセスの9リファレンスで品質を担保。国際学会・学術研究発表（Q&A・ネットワーキング・ポスター発表・英語表現・発音）向け専門リファレンス6本も収録。 Use when creating HTML slide decks, converting source materials to slides, customizing slide themes, initializing new slide projects, or preparing international conference presentations and academic research talks. Delegates actual slide creation to tachikoma-slide agent. For presentation quality improvement (storytelling, delivery, engagement) use designing-training. For text polishing use writing-effective-prose. For marketing copy use creating-content. For proposal structure (ロジック3つの力, MECE, メッセージマップ) see QUALITY-PROPOSAL-CONSTRUCTION.md. For academic presentations, see ACADEMIC-* refs (Q&A mastery, research structure, networking, poster) and ENGLISH-* refs (expressions, pronunciation).
development1
designing-frontend
Creates distinctive, production-grade frontend code with shadcn/ui integration, object-oriented UI (OOUI) methodology, and micro-frontend architecture patterns. Use when implementing web components, pages, or applications requiring creative, polished UI code; when designing UI structure using object-oriented approach (object extraction, view/navigation patterns, layout pattern selection); or when architecting micro-frontend systems (team splitting, Module Federation, BFF patterns, migration strategy, Conway's Law application). For Storybook story creation and component testing, use developing-react instead. For theoretical UI/UX design principles, use designing-ux instead. For Tailwind CSS methodology, component design patterns, and design system construction, use styling-with-tailwind instead. For design system methodology (pattern language, organizational strategy, UI pattern catalog, anti-patterns), use building-design-systems instead.
development1
developing-aws
AWS development guide covering serverless (Lambda, API Gateway, DynamoDB), CDK, EKS, ECS/Fargate, SRE, FinOps, security (IAM, VPC, KMS, GuardDuty), GenAI (Bedrock, RAG), databases (Aurora, ElastiCache), data engineering (Glue, Athena, Redshift), 57 Cloud Design Patterns, VPC architecture, enterprise architecture (multi-account, Landing Zone, Cognito), cloud migration (7R, DMS), and HA/fault tolerance. Use when working with AWS services, CDK infrastructure, or serverless applications. MUST load when working with AWS services, detected by aws-cdk or @aws-sdk in package.json, cdk.json, samconfig.toml, serverless.yml, template.yaml (SAM), or eksctl configs.
development1
developing-go
Comprehensive Go development guide covering clean code practices, design patterns (GoF/concurrency/DDD), and internals (type system/memory/reflection). MUST load when go.mod is detected or Go code is being written. Covers naming, error handling, concurrency, testing, project structure, function design, data structures, refactoring strategies, GoF patterns, architectural patterns, type system internals, and performance optimization. For application logging design and structured logging patterns, use implementing-observability.
development1
developing-databases
Comprehensive database development guide covering relational design (ER modeling, normalization, PostgreSQL implementation), SQL antipatterns (25 patterns with detection signals and solutions), database internals (storage engines B-tree/LSM, distributed systems, consensus algorithms), and PostgreSQL operations (server config, extensions, query tuning, MVCC/VACUUM, backup/PITR, replication/HA, monitoring). Use when designing database schemas, writing SQL queries, reviewing data models, choosing storage engines, tuning PostgreSQL performance, managing backup/replication, or debugging distributed system behavior. Replaces: designing-relational-databases, avoiding-sql-antipatterns, understanding-database-internals.
tools1
developing-python
Modern Python development guide covering project setup, tooling, Pythonic best practices, OOP design principles, GoF design patterns, SE process, and type safety. MUST load when pyproject.toml or requirements.txt is detected. Covers Python 3.13 + uv + ruff + mypy, FastAPI/FastMCP, pytest, Docker, Effective Python idioms, software design patterns (encapsulation, LSP, Design by Contract), SE practices (SDLC, Scrum/Kanban, CI/CD, deployment), type safety rules (Any prohibition, TypedDict, Protocol, dataclass), Architecture Patterns (Repository, Unit of Work, Aggregates, Domain Events, CQRS, Event-Driven Architecture), and DDD Tactical Patterns (Value Object, Entity, Aggregate Root). For language-agnostic clean code principles, use writing-clean-code. For application logging design, use implementing-observability. For Clean Architecture in Python, see references/CA-PYTHON.md. For general Clean Architecture principles, use applying-clean-architecture.
tools1
developing-mcp
Comprehensive MCP (Model Context Protocol) development guide covering architecture (Host/Client/Server roles, Tools/Resources/Prompts, Control Segregation), server and client implementation with TypeScript SDK, protocol specification (JSON-RPC 2.0, stdio/Streamable HTTP), and security threats (Tool Poisoning, Shadowing, Rug Pull, Prompt Injection). MUST load when building MCP servers or clients. For Claude Code plugin MCP configuration, use authoring-plugins instead. For MCP integration with Vercel AI SDK in web apps, see integrating-ai-web-apps. For consuming MCP tools from LangGraph agents, see building-ai-agents.
tools1
implementing-observability
Unified observability guide covering monitoring system design (anti-patterns, 6-layer strategy, alerting, SLOs, telemetry pipelines, observability maturity model), OpenTelemetry implementation (tracing/metrics/logs API/SDK, Collector deployment, semantic conventions), logging design (structured logging, collection pipelines, analysis, anomaly detection, security compliance), and observability engineering practices (core analysis loop, debugging, ODD, build-vs-buy ROI, CI/CD observability, high-cardinality data). Use when designing monitoring strategy, implementing OpenTelemetry instrumentation, building log pipelines, setting up alerts, establishing SLO-based reliability, or adopting observability practices. Replaces: designing-monitoring, implementing-opentelemetry, implementing-logging.
development1
developing-react
React 19.x development guide covering internals (rendering, reconciliation, Fiber), design patterns (Container/Presenter, HOC, Render Props, Compound Components), state management (useState to Zustand/TanStack Query, nuqs/Jotai), error handling (ErrorBoundary, React 19 error APIs), accessibility (ARIA, focus management, keyboard navigation, WCAG 2.1 AA), performance optimization (react-doctor, React Compiler, memoization), UI animation patterns (CSS transitions, easing), React Testing Library (RTL queries, interactions, TDD patterns), and Storybook (CSF3, interaction testing, a11y). Also covers React Router, auth/RBAC, i18n, OpenAPI, and production architecture. Use when package.json contains 'react' (without 'next'), or when working on React-specific concerns in any framework.
development1
managing-claude-md
Manages CLAUDE.md creation, improvement, and maintenance following 8 core principles (size limits, progressive disclosure, essential elements, living documentation). Use when starting new projects, reviewing existing CLAUDE.md, or when Claude repeatedly makes the same mistakes. For skill file authoring, use authoring-plugins instead.
tools1
converting-content
コンテンツ変換ガイド（画像ベースEPUB→テキストOCR変換・LM Studio英日翻訳）。 Use when converting image-based EPUBs to text or translating content with LM Studio. pandoc、recognize-image.py OCR、ローカルLLM翻訳ワークフローを含む。
documentation1
designing-genai-patterns
32 production-grade GenAI design patterns covering content control (Logits Masking, Grammar, Style Transfer), RAG architecture, model capabilities (Chain of Thought, Adapter Tuning), reliability (LLM-as-Judge, Reflection, Prompt Optimization), agentic systems (Tool Calling, Multiagent Collaboration), deployment optimization (SLM, Prompt Caching, Inference Optimization), safety guardrails (Self-Check, Guardrails), RAG implementation (11 source types, chunking, vector stores), and LLMOps/AgentOps (maturity L0–2, Tool/Agent Registry, Memory Governance, LLM metrics, LLMSecOps). Also covers AI performance (GPU/CUDA, LLM inference) via PERF- references. Use when designing GenAI applications, choosing RAG strategies, implementing agent architectures, optimizing LLM reliability, or operating AI systems in production. For web AI (Vercel AI SDK, LangChain.js), use integrating-ai-web-apps. For GCP-specific ML (BigQuery ML, Vertex AI), use developing-google-cloud.
tools1
orchestrating-teams
Agent Teamオーケストレーション（チーム編成・タチコマ並列起動・進捗管理）。 Use when multiple files need parallel changes with independent concerns (2+ files, frontend+backend, UI+API+test). Triggers: 複数ファイル並列変更、マルチ関心事開発、フロントエンド+バックエンド同時変更。
development1
developing-bash
Comprehensive Bash shell scripting and automation guide covering fundamentals, control flow, I/O pipelines, process control, system administration automation, testing/debugging, security, design patterns, and penetration testing automation (Nmap, web scanning, exploitation, Wi-Fi assessment, reporting). MUST load when .sh files are detected or shell scripts are being written. For Docker-specific patterns, use practicing-devops instead. For broader DevOps methodology, use practicing-devops instead.
tools1
writing-effective-prose
Unified writing craft guide: prose fundamentals, AI smell detection (always active), technical docs (7Cs), engineering design docs, academic writing (Harvard, dissertation), tech blog writing, Japanese prose craft, clarity/explanation techniques, web/digital writing, UX copywriting, FAQ writing, revision (no-revision/first-aid), writing mindset and career, persuasive business documents, sensory writing with five senses, README creation, and Zenn publishing. REQUIRED for all text output — AI smell check is always active regardless of document type. Use when writing, reviewing, proofreading, or creating any document (technical docs, articles, engineering design documents (requirements specs, system design docs), reports, slides, emails, academic papers, dissertations, university reports, graduation theses, business documents, web content, FAQ/help docs, design specs, README.md files, Zenn tech articles). For LaTeX → writing-latex. For presentations → creating-slides.
development1
creating-flashcards
Creates Anki flashcards from EPUB/PDF files via Anki MCP Server, covering MCP setup, deck/note-type management, and bulk import with HTML formatting. Use when converting textbooks, question banks, or study materials into spaced repetition flashcards, or when managing Anki cards via MCP tools. Covers full workflow: MCP setup → file conversion → content analysis → batch card creation. For MCP server/client development, use developing-mcp instead.
tools1
securing-ai-development
Organizational security strategy for AI-powered software development covering trust frameworks, adaptive guardrails, AI-BOM, AI-SPM, governance models, and cross-functional ownership. Use when establishing security controls for AI coding assistants, agentic systems, or AI-accelerated SDLC workflows. For code-level security (OWASP, CodeGuard), use securing-code instead. For AI development methodology (prompts, context engineering), use developing-with-ai instead. For LLM-specific security (prompt injection, LLMSecOps), use designing-genai-patterns.
development1
orchestrating-codex
Codex CLI統合スキル（基本操作・プランレビュー・Agentオーケストレーション）。 Use when using Codex for code consultation, plan review, or orchestrating Codex agents in Wave parallel execution. Triggers: "codex", "codexと相談", "codexでレビュー", "codexでオーケストレーション"。Wave計画に基づき自然言語でagentを同時起動し、config.tomlのmax_threadsで並列度を宣言的に制御する。 For agent conversion to Codex format, use converting-agents-to-codex instead.
tools1
creating-diagrams
ダイアグラム作成ガイド（Mermaid構文・draw.io MCP・24種類のダイアグラム対応）。 Use when creating diagrams, charts, or visual documentation with Mermaid or draw.io. C4モデル、ER図、シーケンス図、フローチャート、ガントチャート等を含む。
tools1
applying-semantic-versioning
Semantic Versioning 2.0.0仕様に基づくバージョン判断ガイド。MAJOR/MINOR/PATCH判定、プレリリース・ビルドメタデータ、範囲指定を提供。 REQUIRED for all version-related decisions. Use when determining version bumps, creating releases, or managing dependencies.
testing1
testing-e2e-with-playwright
Playwright E2Eテストの設計・実装・運用ガイド。 Use when writing, reviewing, or maintaining E2E tests with @playwright/test. playwright.config.* 検出時に自動ロード。testing-code（テスト全般）とは異なりPlaywright E2E固有のパターンに特化。
development1
compressing-epub-images
EPUB ファイル内の画像（主にスキャン本の JPEG）を再エンコード・リサイズしてファイルサイズを削減するスキル。AskUserQuestion で圧縮レベル選択フローを提供し、実測サンプリングから予測サイズを提示してからユーザーに選ばせる。 Use when: EPUB ファイルが大きく画像圧縮で削減したい時、スキャン本（画像ベース EPUB）の容量を減らしたい時、Kindle などの電子書籍リーダーに転送する前にサイズ最適化したい時。 画像ベース EPUB（スキャン本）と通常 EPUB の両方に対応。書誌情報・xhtml・css は触らず画像のみ再エンコード。
development1
writing-latex
LaTeX document creation for Japanese academic reports. MUST load when .tex files are detected. Covers upLaTeX + dvipdfmx setup, minted code highlighting with Japanese font support, equations, figures, tables, and cover pages.
development1
writing-user-stories
Guides effective user story creation for software projects covering story templates (As a.../I want.../So that...), common mistakes, technical requirements to story conversion, acceptance criteria writing, and story splitting techniques. Use when writing user stories, converting technical requirements to stories, or improving backlog quality. For product management practices (PRD, roadmap, prioritization), use practicing-product-management instead.
testing1
developing-fullstack-javascript
Full-stack JavaScript development covering backend (NestJS/Express), frontend (React), deployment (CI/CD), and quality; also covers JavaScript language fundamentals (types, closures, prototypes, async/await, modules, and metaprogramming). MUST load when package.json contains Express, NestJS, or similar backend frameworks. Covers API design, state management, caching, and testing. Also use when working with JavaScript language-level concerns — type coercion, scoping, this binding, Promise patterns, Proxy/Reflect, or iterator protocols. Also covers V8 engine internals (hidden classes, inline caches, string/number repr), event loop model, JS/Node error model, and Express 5 + Drizzle ORM CRUD APIs.
development1
developing-firebase
Firebase platform development guide covering Authentication (email/social/session), Firestore & Realtime Database (modeling/queries/security rules), Cloud Storage, Cloud Functions (triggers/scheduling), Hosting, Analytics (events/BigQuery), FCM push notifications, Remote Config, Test Lab, Performance Monitoring, Dynamic Links, App Distribution, AdMob, and Extensions. MUST load when firebase, @firebase, or firebase-admin packages detected, or firebaseConfig/firebase.json/firestore.rules files present. For GCP infra→developing-google-cloud. For Next.js integration→developing-nextjs. For REST API design→developing-web-apis.
tools1
researching-libraries
Researches existing libraries before implementation to prevent reinventing the wheel. REQUIRED before writing any new functionality. Use when evaluating npm packages, pip packages, Go modules, or any third-party libraries to find and evaluate existing solutions.
development1
securing-code
REQUIRED after all code implementations. Automatically load when implementation is complete to run CodeGuard security check. Covers input validation, secrets management, OWASP top 10 countermeasures, authentication/authorization patterns, web penetration testing (reconnaissance, attack techniques, bypass methods), and serverless security (IAM/storage/functions across AWS/GCP/Azure, 17 threat categories, supply chain attacks). Use when implementing any code, handling external input, or developing serverless applications (Lambda, Cloud Run, Azure Functions). For dynamic authorization model design (ABAC/ReBAC/Cedar), use implementing-dynamic-authorization instead. For organizational AI development security strategy (trust frameworks, governance, AI-BOM), use securing-ai-development instead. For security logging patterns and compliance logging, use implementing-observability.
development1
testing-code
REQUIRED for all feature implementations. Automatically load when writing or reviewing tests. Enforces TDD approach with AAA pattern, actual/expected variables, and 100% coverage goal for business logic. Covers Vitest, Jest, Playwright, and AI-augmented testing strategies. Includes the Four Pillars of good tests (regression protection, refactoring resistance, fast feedback, maintainability), three testing styles (output/state/communication-based), code classification, and test anti-patterns. For RTL patterns, use developing-react. For Web API testing, use developing-web-apis. For A/B testing, use practicing-product-management. For TDD mindset/ATDD/BDD, see TESTING-PRACTICES.md. For project foundations and team organization, use practicing-software-engineering.
development1
using-serena
Token-efficient structured development via /serena command. Use when implementing components, APIs, system designs, tests, bug fixes, or optimizations with structured problem-solving approach. Available for Claude Code本体 and all Agents including Tachikoma.
development1
writing-conventional-commits
Conventional Commits 1.0.0仕様に基づくコミットメッセージフォーマットガイド。type/scope/BREAKING CHANGEの判定とSemVerとの対応を提供。 REQUIRED for all commit messages and version descriptions. Use when writing git commit messages.
tools1
developing-nextjs
Next.js 16.x development guide covering App Router, Server Components, Turbopack, React Compiler, proxy.ts, Cache Components, opt-in caching APIs (updateTag/revalidateTag/refresh), strict TypeScript, Tailwind CSS 4.x, Prisma 7.x, Zod 4.x, Vitest 4.x, Playwright, Docker. MUST load when package.json contains 'next' or next.config.* is detected. For React-specific concerns (internals, performance rules, animation, RTL testing), use developing-react. SaaS構築パターン（認証・決済・AI統合）を含む。 For AI integration with Vercel AI SDK and LangChain.js, use integrating-ai-web-apps. For application logging design and structured logging patterns, use implementing-observability. For Tailwind CSS methodology, component design patterns, and customization, use styling-with-tailwind. For Firebase platform details (Auth/Firestore/Rules)→developing-firebase. For React Router based routing/rendering and client-side auth/i18n architecture, use developing-react.
tools1
developing-google-cloud
Google Cloud guide: Cloud Run, GCP security (IAM/VPC/KMS/Zero Trust), data engineering (BigQuery/Dataflow/pipelines/governance/lakehouse), networking (VPC/LB/CDN), Memorystore, enterprise architecture, compute selection (GCE/GKE/GAE/Run/Functions), GKE, GAE, monitoring (SLO/SLI), BigQuery analytics (SQL/window functions/GA4), BigQuery ops (editions/HA-DR/slots), workflow (Composer/Dataform/Data Fusion), BI (Looker/Looker Studio/BI Engine), ingestion (DTS/Datastream CDC/GA4), real-time (Pub/Sub/Dataflow streaming), ML (BigQuery ML/Vertex AI/GIS). MUST load when google-cloud packages, cloudbuild.yaml, BigQuery/Dataflow/Memorystore/Looker/Dataplex detected. For Docker→practicing-devops. For monitoring→implementing-observability. For OWASP→securing-code. For CQRS→architecting-data. For AWS→developing-aws. For GenAI→designing-genai-patterns. For Firebase (Auth/Firestore/Storage/Functions/Hosting)→developing-firebase.
development1
developing-web-apis
Web API development guide covering design (endpoints, responses, HTTP spec, versioning, security), spec-first methodology (spec writing, E2E test framework architecture, technical debt repayment), and testing strategy (design testing, contract testing, automation, performance, security testing). Use when designing REST APIs, writing API specs, adopting spec-first development, or building API test strategies. For framework-specific implementation (Express, NestJS), use respective framework skill. For microservices patterns and trade-off analysis of API usability vs maintenance, use architecting-infrastructure instead.
tools1
reviewing-code
コードレビューガイドライン（PR構成・効果的コメント・トーン原則・CodeRabbit統合）。 Use when reviewing code, creating PRs, or using CodeRabbit for automated review. 3原則（客観性・具体性・明確なアウトカム）、自動修正ループを含む。
development1
solving-algorithms
Comprehensive algorithm and data structure reference for competitive programming covering sorting, searching, trees, graphs, dynamic programming, computational geometry, and number theory with complexity analysis and language-agnostic implementations. Use when solving algorithmic problems, optimizing code for time/space complexity, or implementing classic data structures (stack, queue, heap, BST, union-find). For database-specific data structures (B-tree, LSM), use developing-databases instead.
development1
converting-agents-to-codex
Claude Code Agent定義（.md）をCodex subagent定義（agents/*.toml）に変換するガイド。 フィールドマッピング・developer_instructions変換・skills.config展開・検証手順・よくある失敗パターンを網羅。 Use when converting Claude Code agents to Codex format, migrating agent definitions, or setting up Codex subagents. Triggers: "agentをcodexに変換", "codex agent変換", "agent migration"。
development1
searching-web
Web検索統合スキル。Exa MCP（第一優先）による高度検索（7カテゴリ: Company, Code, People, Financial Report, Research Paper, Personal Site, Tweet/X）と、gemini CLI（フォールバック）による複雑なクエリ検索を統合。 Use when performing web searches, researching technologies, companies, people, academic papers, or social media. Load Exa MCP first; fall back to gemini CLI when Exa is unavailable. MUST load as first-choice search tool. context7 for library docs, deepwiki for GitHub wiki, WebSearch built-in as last resort.
tools1
using-next-devtools
Next.js development integration tools via next-devtools MCP. MUST load when working on Next.js projects detected by package.json. Provides diagnostics, version upgrades, Cache Components optimization, and automatic error fixes. Primary tool for Next.js tasks.
tools1
styling-with-tailwind
Tailwind CSS styling methodology covering utility-first philosophy, v4 CSS-first config, utility/modifier reference, component design patterns, customization (plugins, presets, JS API), migration strategies, and design system construction with design tokens. Use when styling web applications with Tailwind CSS or making CSS architecture decisions. For frontend code generation with shadcn/ui and Storybook, use designing-frontend instead. For general UI/UX design principles, use designing-ux instead. For design system strategy beyond CSS (pattern language, organizational adoption, UI pattern catalog, measurement), use building-design-systems instead.
tools1