sumik5
@sumik5
Public Skills
architecting-data
by sumik5
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-microservices instead. For DDD domain modeling, use applying-domain-driven-design instead. For database engine internals, use understanding-database-internals instead. For relational DB schema design, use designing-relational-databases instead. For GCP-specific data services (BigQuery, Dataflow, Dataproc), use developing-google-cloud instead.
designing-data-visualizations
by sumik5
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 applying-design-guidelines instead. For technical diagrams (flowcharts, architecture), use mermaid-diagrams instead.
developing-with-ai
by sumik5
AI-assisted development methodology covering prompt engineering, context engineering, code generation workflows, quality assurance, collaborative debugging, and agent collaboration patterns. 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, or coordinating multi-agent development workflows. For AI copywriting techniques, use crafting-ai-copywriting instead. For testing-specific AI techniques (test data generation, exploratory testing with AI, test planning with AI), use testing-code AI references instead. For organizational AI development security strategy (trust frameworks, governance, AI-SPM), use securing-ai-development instead. For PM-specific Claude Code workflows (codebase investigation, feedback synthesis, competitive analysis, requirements generation), use using-claude-code-as-pm instead. For LLM application production operations, use practicing-llmops.
automating-browser
by sumik5
Browser Agent CLIによるブラウザ操作自動化（セマンティックロケーター、状態永続化、ネットワーク傍受）。 Use when automating browser interactions via agent-browser CLI (NOT for E2E testing). E2Eテストは testing-e2e-with-playwright スキルを参照。
developing-python
by sumik5
Modern Python development guide covering project setup, tooling, Pythonic best practices and exercise patterns (file I/O, data manipulation, function design, OOP composition, iterators, comprehension idioms), OOP design principles, GoF design patterns, and software engineering process (SDLC, system modeling, methodologies, project implementation patterns, CI/CD, API design). MUST load when pyproject.toml or requirements.txt is detected. Covers Python 3.13 + uv + ruff + mypy, FastAPI/FastMCP, pytest, Docker, Effective Python items (idioms, data structures, concurrency, testing), software design (encapsulation, Demeter's Law, LSP, Design by Contract, behavioral/creational/structural patterns in Python), and SE practices (SDLC phases, Scrum/Kanban, system architecture, code organization, data persistence, API framework comparison, deployment strategies). For language-agnostic clean code principles, use writing-clean-code. For application logging design and structured logging patterns, use implementing-logging.
applying-semantic-versioning
by sumik5
Semantic Versioning 2.0.0仕様に基づくバージョン判断ガイド。MAJOR/MINOR/PATCH判定、プレリリース・ビルドメタデータ、範囲指定を提供。 REQUIRED for all version-related decisions. Use when determining version bumps, creating releases, or managing dependencies.
implementing-logging
by sumik5
アプリケーション・システムのログ設計・実装・収集・分析・運用の実践知識。 Use when: ログ出力コードを書く、ログ基盤を構築する、ログ分析・異常検知を実装する、セキュリティ監査に対応する。 書籍「実務で役立つ ログの教科書」（増井敏克著、翔泳社2025）の知見を凝縮。
developing-google-cloud
by sumik5
Google Cloud development guide covering Cloud Run (architecture, scaling, CI/CD), GCP security (IAM, VPC, KMS, DLP, SCC, Zero Trust, Chronicle), data engineering (BigQuery, Dataflow, data pipelines, governance), network engineering (VPC, load balancing, CDN, Traffic Director), and Memorystore (Redis/Memcached, cache patterns, resilience). MUST load when Dockerfile is detected with google-cloud packages, when cloudbuild.yaml is present, or when working with BigQuery, Dataflow, Dataproc, Cloud Interconnect, or Memorystore. For Docker-specific patterns, use managing-docker instead. For general monitoring design, use designing-monitoring instead. For code-level security (OWASP, CodeGuard), use securing-code instead. For data architecture patterns (CQRS, event sourcing), use architecting-data instead. For AWS development, use developing-aws instead. For serverless security (GCS hacking, Cloud Run abuse), use securing-serverless instead. For application logging, use implementing-logging.
authoring-agents
by sumik5
Creates specialized Tachikoma sub-agent definitions (.md files in agents/) with proper frontmatter, skills pre-loading, and domain-specific instructions. Use when creating new agents, modifying existing agent definitions, or adding specialized Tachikoma variants. For skill creation, use authoring-skills instead. For agent runtime behavior, see implementing-as-tachikoma.
enforcing-type-safety
by sumik5
REQUIRED for all TypeScript/Python code. Automatically load when writing type annotations or handling external data. Any/any types strictly prohibited. Enforces strict mode configuration and type guard implementation.
implementing-dynamic-authorization
by sumik5
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.
architecting-microservices
by sumik5
Microservices architectural patterns covering CQRS, Event Sourcing, 8 Saga pattern variants, distributed transactions, service granularity decisions, data ownership, workflow orchestration, and contract design. Use when designing microservices architecture, choosing transaction strategies, or deciding service granularity. Covers messaging, resilience, security, reuse, and data access patterns. For migration strategy and trade-off analysis methodology, use modernizing-architecture instead. For DDD domain modeling, use applying-domain-driven-design instead. For frontend decomposition patterns (micro-frontends), use architecting-micro-frontends instead. For green/sustainable microservices trade-offs and carbon-efficient architecture, use building-green-software instead. For data architecture patterns (read-side optimization, caching strategies), use architecting-data instead.
crafting-ai-copywriting
by sumik5
AI-assisted copywriting with 15 prompt techniques leveraging psychological triggers. Use when creating marketing copy, blog titles, ad headlines, or social media posts. Focuses on prompt engineering to generate compelling copy. For eliminating AI patterns from text, use writing-effective-prose instead.
building-multi-tenant-saas
by sumik5
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 building-nextjs-saas instead.
avoiding-sql-antipatterns
by sumik5
Identifies and prevents common SQL database design mistakes across logical design, physical design, query construction, and application development. Use when designing database schemas, writing SQL queries, reviewing data models, or implementing database-backed features. Covers 25 named antipatterns with detection signals, solutions, and exception cases. For code-level security (input validation, XSS, OWASP), use securing-code instead. For database model selection and data architecture decisions, use understanding-database-internals instead. For positive relational database design methodology (entity modeling, normalization process), use designing-relational-databases instead.
developing-fullstack-javascript
by sumik5
Full-stack JavaScript development covering backend (NestJS/Express), frontend (React), deployment (CI/CD), and quality. MUST load when package.json contains Express, NestJS, or similar backend frameworks. Covers API design, state management, caching, and testing. For application logging design and structured logging patterns, use implementing-logging.
building-nextjs-saas
by sumik5
Builds full-stack AI SaaS applications with Next.js App Router. Use when implementing SaaS features like authentication, payment integration, credit-based billing, or AI API integration. For Next.js fundamentals, use developing-nextjs; for enterprise multi-tenancy, use building-multi-tenant-saas instead.
developing-terraform
by sumik5
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 managing-docker instead. For broader DevOps methodology and IaC tool comparison, use practicing-devops instead. For AWS CDK (TypeScript/Python IaC), use developing-aws instead.
developing-mcp
by sumik5
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 plugin-dev:mcp-integration instead. For MCP integration with Vercel AI SDK in web apps, see integrating-ai-web-apps.
implementing-opentelemetry
by sumik5
OpenTelemetry implementation for distributed system observability covering instrumentation API/SDK and Collector deployment. Use when implementing tracing, metrics, or logging with OpenTelemetry. Covers Collector pipelines, semantic conventions, and organizational adoption strategies. For monitoring strategy, alerting design, telemetry pipeline architecture, observability concepts, SLOs, and sampling strategies, use designing-monitoring instead. For application-level logging design and log collection architecture beyond OTel Logs Signal, use implementing-logging.
creating-flashcards
by sumik5
Creates Anki flashcards from EPUB/PDF files by converting to markdown, auto-detecting content structure, and batch-importing via Anki MCP. Use when converting textbooks, question banks, or study materials into spaced repetition flashcards. For Anki MCP setup and direct card management, use using-anki-mcp instead.
implementing-as-tachikoma
by sumik5
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.
developing-go
by sumik5
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-logging.
applying-domain-driven-design
by sumik5
Domain-Driven Design methodology covering strategic design (Bounded Context, Ubiquitous Language, Context Mapping), tactical patterns (Domain Model, Event Sourcing, CQRS), practical adoption (heuristics, EventStorming), and operational data decomposition with polyglot database selection. Use when designing domain boundaries, choosing business logic implementation patterns, decomposing monolithic data, or aligning software architecture with business strategy. For socio-technical architecture modernization and trade-off analysis, use modernizing-architecture instead. For microservices distributed patterns (Saga, messaging, granularity), use architecting-microservices instead. For data architecture read-side patterns and caching strategies, use architecting-data instead.