sumik5
@sumik5
Public Skills
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-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).
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.
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.
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.
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.
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.
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.
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.
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.
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-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.
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.
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.
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.
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.
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.