sumik5
@sumik5
Public Skills
applying-design-guidelines
by sumik5
UI/UX design principles covering visual design, user experience fundamentals, practical interface design rules, and design theory fundamentals. Use when making design decisions, evaluating existing interfaces, or implementing UI components. Covers typography, color, motion, cognitive psychology, interaction patterns, and 101 practical Do/Don't rules. Also covers design theory foundations for engineers (concept building, typography theory, CRAP/Gestalt, layout theory, color theory). NOT for frontend codegen (designing-frontend), behavior design (applying-behavior-design), data charts (designing-data-visualizations), Tailwind (styling-with-tailwind), design systems (building-design-systems), or design thinking (practicing-design-thinking).
building-design-systems
by sumik5
Design system construction and governance methodology covering system foundations, pattern taxonomy, organizational adoption, pattern library operations, and UI pattern catalog (20+ interaction patterns). Use when architecting, evaluating, or restructuring a design system, planning organizational adoption, or building a pattern library. NOT for component styling (applying-design-guidelines), design-to-code (implementing-design), frontend codegen (designing-frontend), Tailwind config (styling-with-tailwind), or design thinking (practicing-design-thinking).
applying-behavior-design
by sumik5
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 applying-design-guidelines instead. For training program design and facilitation methodology, use designing-training instead. For human-centered design thinking process (user research, ideation, prototyping), use practicing-design-thinking instead.
designing-training
by sumik5
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→improving-presentations. For design thinking process methodology (empathize/define/ideate/prototype/test)→practicing-design-thinking.
converting-epub-images
by sumik5
Converts image-based EPUB files to Japanese text via LM Studio OCR. Use when user has an EPUB composed of scanned page images and wants plain text output. For skill creation from EPUB, use authoring-skills instead.
designing-frontend
by sumik5
Creates distinctive, production-grade frontend code with shadcn/ui integration. Use when implementing web components, pages, or applications requiring creative, polished UI code. Covers HTML/CSS/JS code generation and shadcn/ui component management. For Storybook story creation and component testing, use developing-storybook instead. For theoretical UI/UX design principles, use applying-design-guidelines 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.
developing-storybook
by sumik5
Storybook development guide covering CSF3 story writing, interaction testing (play function), accessibility testing (axe-core), visual regression testing, Next.js/React framework integration, MSW network mocking, addon ecosystem, and story-driven component development. MUST load when .stories.tsx/.ts files detected or Storybook setup/configuration needed. For general frontend UI implementation, use designing-frontend. For E2E browser testing, use testing-e2e-with-playwright. For React-specific concerns (internals, performance, RTL), use developing-react.
implementing-design
by sumik5
General design implementation principles for translating any visual design into production-ready code. Covers design system integration, visual parity validation, responsive implementation, accessibility, and component organization. Use when implementing designs from any source (screenshots, mockups, specs). For Figma-specific workflows with Figma MCP, use implementing-figma instead. For design system architecture, pattern language theory, and organizational adoption strategy, use building-design-systems instead.
converting-agents-to-codex
by sumik5
Converts Claude Code agent definitions (.md) to Codex multi-agent format (config.toml + agent .toml). Use when porting Claude Code agents to Codex CLI. Accepts a single agent file path or a folder path as argument. When a folder is given, uses Agent Teams API to process files in parallel (MAX 5 workers) for fast batch conversion. Detects existing entries in config.toml and agent .toml files; auto-handles diffs in batch mode. Always fetches latest spec from https://developers.openai.com/codex/multi-agent.
generating-google-slides
by sumik5
Generates Google Slides presentations from unstructured text via Google Apps Script slideData arrays. Use when creating presentations from meeting notes, proposals, or memos. For presentation content quality improvement, use improving-presentations instead. For frontend UI components, use designing-frontend; for LaTeX documents, use writing-latex instead.
developing-nextjs
by sumik5
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. For SaaS patterns (auth, payments, AI), use building-nextjs-saas. 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-logging. For Tailwind CSS methodology, component design patterns, and customization, use styling-with-tailwind.
developing-bash
by sumik5
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 managing-docker instead. For broader DevOps methodology, use practicing-devops instead.
developing-aws
by sumik5
AWS development guide covering serverless (Lambda, API Gateway, DynamoDB, Step Functions), CDK, EKS, SRE, cost optimization (FinOps/CCoE), security (IAM, VPC, KMS, GuardDuty), GenAI (Bedrock, RAG, Agents), databases (Aurora, DynamoDB, ElastiCache), data engineering (Glue, Athena, Redshift), developer tools (CodePipeline), Cloud Design Patterns (57 CDP), VPC architecture (subnet, CIDR, Transit Gateway), enterprise architecture (multi-account, Landing Zone, 14 business system patterns), and cloud migration strategies (7R, AWS MGN, database migration). 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. For GCP→developing-google-cloud, Terraform→developing-terraform, Docker→managing-docker, monitoring→designing-monitoring, RAG→building-rag-systems, LLMOps→practicing-llmops, serverless security→securing-serverless, logging→implementing-logging.
developing-api-spec-first
by sumik5
API Spec First development methodology covering spec writing, E2E test framework architecture, technical debt repayment, and defensive programming for APIs. Use when adopting spec-first API development, building E2E test frameworks for backend services, documenting undocumented APIs, or writing comprehensive API specifications. For HTTP REST API design patterns, use designing-web-apis instead. For testing strategy and test pyramid, use testing-web-apis instead.
designing-web-apis
by sumik5
Web API design best practices for endpoints, responses, HTTP spec usage, versioning, and security. Use when designing REST-style HTTP APIs or creating new endpoints. For framework-specific implementation (Express, NestJS), use respective framework skill; for microservices patterns, use architecting-microservices instead. For API usability vs maintenance trade-off analysis, use analyzing-software-tradeoffs. For spec-first development methodology and E2E test frameworks, use developing-api-spec-first instead.
implementing-figma
by sumik5
Comprehensive Figma MCP integration for design-to-code conversion. Covers all 13 Figma MCP tools, basic and advanced workflows (Figma Make, Code Connect, Design System Rules, design token sync), and visual validation. Use when converting Figma designs to code or managing design systems. Requires Figma MCP server. For general design implementation principles (non-Figma), use implementing-design instead.
conducting-ab-tests
by sumik5
A/B testing and online controlled experiment methodology covering experiment design, statistical analysis (p-values, confidence intervals, sample size), OEC formulation, trustworthiness validation (SRM, novelty effects), and experimentation platform architecture. Use when designing A/B tests, analyzing experiment results, or building experimentation infrastructure. For general software testing, use testing-code instead.
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.
architecting-micro-frontends
by sumik5
Micro-frontend architecture patterns covering vertical/horizontal split, composition strategies (Module Federation, iframe, Web Components, SSR, ESI), decision framework, and organizational adoption. Use when decomposing frontend monoliths, choosing micro-frontend composition patterns, or designing multi-team frontend architecture. For backend microservices patterns (Saga, granularity), use architecting-microservices instead. For socio-technical modernization strategy, use modernizing-architecture instead.
analyzing-software-tradeoffs
by sumik5
Comprehensive software design trade-off analysis covering code-level decisions (duplication, error handling, flexibility, optimization), API design (usability, versioning), distributed systems (consistency, delivery semantics), and meta-decisions (library selection, trend evaluation, date-time handling). Use when evaluating design alternatives, making architectural decisions, or reviewing trade-offs in existing systems. For specific clean code rules, use writing-clean-code; for microservices patterns, use architecting-microservices; for API endpoint design, use designing-web-apis.
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.
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 スキルを参照。
building-green-software
by sumik5
Comprehensive green software engineering guide covering carbon efficiency, energy efficiency, hardware efficiency, and carbon awareness. MUST load when designing systems with sustainability requirements or optimizing carbon footprint. Covers code efficiency patterns, operational efficiency, carbon-aware computing, green AI/ML, measurement methodologies, and the Green Software Maturity Matrix. For monitoring-specific patterns, use designing-monitoring instead. For microservices architecture decisions, use architecting-microservices instead.
building-adk-agents
by sumik5
Google ADK (Agent Development Kit) for building intelligent AI agents with Python. MUST load when google-adk is detected in requirements or pyproject.toml. Covers Agent taxonomy, Agent types (LlmAgent/Sequential/Parallel/Loop/Base), Tools (FunctionTool/OpenAPI/MCP), Multi-Agent orchestration, A2A Protocol (JSON-RPC/REST), Runner, Session, Artifact, Memory, State lifecycle, Context (Caching/Compaction), RAG (Corpus/Vector Search/Agentic), Grounding, Plugin System, Callbacks/Guardrails (6 types), SSE Streaming, Live API, UI Integration (CopilotKit/Streamlit/Slack), Code Execution, LLM Models (Gemini/LiteLLM/Anthropic), Deployment (Cloud Run/Vertex/GKE), CI/CD, Cost optimization, Security (IAM/Data privacy), Responsible AI. Distinct from developing-python (general) by focusing on ADK patterns.
building-rag-systems
by sumik5
Comprehensive RAG (Retrieval-Augmented Generation) system building guide covering data loading pipelines (11 source types including Word, PDF, CSV, audio, video, multimodal), data preparation (metadata enrichment, text quality enhancement, 5 chunking strategies from character to agentic), and full RAG architecture overview with Python. Use when building RAG applications, designing data ingestion pipelines, or implementing text chunking strategies. For Python language best practices, use developing-python instead. For LLMOps operational framework, use practicing-llmops. For JavaScript/LangChain.js RAG in web apps with Vercel AI SDK, see integrating-ai-web-apps.
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.
designing-monitoring
by sumik5
Designs monitoring and observability systems covering anti-patterns, design patterns, layer-based strategy (6 layers), alerting, on-call operations, incident management, telemetry pipeline architecture, observability concepts (structured events, core analysis loop), SLO-based reliability, sampling strategies, and observability maturity model. Use when designing monitoring strategy, setting up alerting, choosing monitoring tools, building observability systems, implementing SLOs, or adopting observability practices. For OpenTelemetry SDK/API implementation, use implementing-opentelemetry instead. For green software carbon metrics and sustainability monitoring, use building-green-software instead. For Google Cloud monitoring (Cloud Logging, Security Command Center, Cloud Run), use developing-google-cloud instead. For LLM-specific evaluation and monitoring, use practicing-llmops. For application logging design, structured logging, and log collection pipelines, use implementing-logging instead.
designing-relational-databases
by sumik5
Guides relational database design from requirements to implementation covering entity modeling, ER diagrams, normalization (1NF-BCNF), optimization, and PostgreSQL-specific implementation (microservices data architecture, ACID transactions, functions/stored procedures, AAA security). Use when designing database schemas, creating ER diagrams, normalizing tables, implementing SQL DDL, or developing PostgreSQL-backed applications. For database internals (storage engines, distributed systems), use understanding-database-internals instead. For SQL antipattern detection and avoidance, use avoiding-sql-antipatterns 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.
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.
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.
implementing-logging
by sumik5
アプリケーション・システムのログ設計・実装・収集・分析・運用の実践知識。 Use when: ログ出力コードを書く、ログ基盤を構築する、ログ分析・異常検知を実装する、セキュリティ監査に対応する。 書籍「実務で役立つ ログの教科書」（増井敏克著、翔泳社2025）の知見を凝縮。
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.
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.
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.
authoring-skills
by sumik5
Creates effective Claude Code Skills with proper structure, naming, and evaluation. Use when creating new skills, converting source material (Markdown/PDF/EPUB/URL/multiple files/folders) into skills, or reviewing skill usage analytics. Covers naming conventions, progressive disclosure, multi-file grouping, source conversion, and lifecycle management.
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.
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.
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.
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.
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.
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.
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.
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-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.
developing-react
by sumik5
React 19.x development guide covering internals (rendering, reconciliation, Fiber), performance optimization (47+ react-doctor rules, memoization, bundle size), UI animation patterns (CSS transitions, easing, hover/touch), and React Testing Library (RTL queries, interactions, TDD patterns). Use when package.json contains 'react' (without 'next'), or when working on React-specific concerns in any framework. For Next.js-specific features (App Router, Server Components, Cache Components), use developing-nextjs instead. For E2E testing with Playwright, use testing-e2e-with-playwright. For general testing methodology, use testing-code.
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.
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.
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.