Frontend

Design skills as modular building blocks for predictable token usage. Triggers: skill design, skill architecture, modularization, token optimization, skill structure, refactoring skills, new skill creation, skill complexity Use when: creating new skills that will be >150 lines, breaking down complex monolithic skills, planning skill architecture, refactoring overlapping skills, reviewing skill maintainability, designing skill module structure DO NOT use when: evaluating existing skill quality - use skills-eval instead. DO NOT use when: writing prose for humans - use writing-clearly-and-concisely. DO NOT use when: need improvement recommendations - use skills-eval. Use this skill BEFORE creating any new skill. Check even if unsure.

Asynchronous event-based communication to decouple producers/consumers for scalability and resilience. Triggers: event-driven, message queue, pub/sub, asynchronous processing Use when: real-time workloads or multiple subsystems react to same events DO NOT use when: simple request-response patterns suffice.

Transform tool-heavy workflows into MCP code execution patterns for token savings and optimized processing. Triggers: MCP, code execution, tool chain, data pipeline, tool transformation, batch processing, workflow optimization Use when: >3 tools chained sequentially, large datasets (>10k rows), large files (>50KB), context usage >25% DO NOT use when: simple tool calls that don't chain. DO NOT use when: context pressure is low and tools are fast. Use this skill BEFORE building complex tool chains. Optimize proactively.

Systematically uncover and fix bugs using language-specific expertise and reproducible evidence. Triggers: bug hunting, defect detection, debugging, fix verification, bug fix, regression check, error investigation, defect documentation Use when: deep bug hunting needed, documenting defects, verifying fixes, systematic debugging required DO NOT use when: test coverage audit - use test-review instead. DO NOT use when: architecture issues - use architecture-review. Use this skill for systematic bug hunting with evidence trails.

Detect codebase bloat through progressive analysis: dead code, duplication, complexity, and documentation bloat. Triggers: bloat detection, dead code, code cleanup, duplication, redundancy, codebase health, technical debt, unused code Use when: preparing for refactoring, context usage is high, quarterly maintenance, pre-release cleanup DO NOT use when: actively developing new features, time-sensitive bug fixes. DO NOT use when: codebase is < 1000 lines (insufficient scale for bloat). Progressive 3-tier detection: quick scan → targeted analysis → deep audit.

Evaluate and upgrade test suites with TDD/BDD rigor, coverage tracking, and quality assessment. Triggers: test audit, test coverage, test quality, TDD, BDD, test gaps, test improvement, coverage analysis, test remediation Use when: auditing test suites, analyzing coverage gaps, improving test quality, evaluating TDD/BDD compliance DO NOT use when: writing new tests - use parseltongue:python-testing. DO NOT use when: updating existing tests - use sanctum:test-updates. Use this skill for test suite evaluation and quality assessment.

Scope-focused PR code review that validates against original requirements and routes out-of-scope findings to GitHub issues. Triggers: PR review, pull request review, scope validation, requirement compliance, backlog triage, code review, blocking issues Use when: reviewing PRs, validating against requirements, triaging findings to backlog, preventing overengineering DO NOT use when: preparing PRs - use pr-prep instead. DO NOT use when: deep code review - use pensive:unified-review. Use this skill for scope-focused PR reviews.

detailed hook evaluation framework for Claude Code and Agent SDK hooks. Triggers: hook audit, hook security, hook performance, hook compliance, SDK hooks, hook evaluation, hook benchmarking, hook vulnerability Use when: auditing existing hooks for security vulnerabilities, benchmarking hook performance, implementing hooks using Python SDK, understanding hook callback signatures, validating hooks against compliance standards DO NOT use when: deciding hook placement - use hook-scope-guide instead. DO NOT use when: writing hook rules from scratch - use hookify instead. DO NOT use when: validating plugin structure - use validate-plugin instead. Use this skill BEFORE deploying hooks to production.

Update documentation with writing guideline enforcement, consolidation detection, and accuracy verification. Triggers: documentation update, docs update, ADR, docstrings, writing guidelines, readme update, debloat docs Use when: updating documentation after code changes, enforcing writing guidelines, maintaining ADRs DO NOT use when: README-specific updates - use update-readme instead. DO NOT use when: complex multi-file consolidation - use doc-consolidation. Use this skill for general documentation updates with built-in quality gates.

Declarative release readiness checklist that mirrors GitHub checks, deployment issues, and documentation requirements. Triggers: release gates, release readiness, deployment checklist, release review, quality signals, rollout scorecard, QA handshake, deployment gates Use when: preparing releases, validating deployment gates, conducting release reviews, embedding release gate snippets in PRs DO NOT use when: weekly status updates - use github-initiative-pulse. DO NOT use when: code reviews - use pensive review skills. Standardizes release approvals with GitHub-aware checklists.

Competence in data analytics and machine learning, enabling developers to build data-driven features and integrate AI/ML capabilities.

TDD方法論に従ってテストを作成します。テストファイルの配置（コロケーション）、命名規則、テスト構造のベストプラクティスに従います。React/TypeScript、Go、Rustで適切なパターンを使い分けます。「テストを書いて」「テストを作成」「単体テストを追加」などのリクエストで起動します。

Use when user wants to execute long-running tasks that require multiple sessions to complete. This skill manages task decomposition, progress tracking, and autonomous execution using Codex non-interactive mode with auto-continuation. Trigger phrases include autonomous, long-running task, multi-session, 自主执行, 长时任务, autonomous skill.

Command-line tool for managing TiddlyWiki files. Use when working with TiddlyWiki (.html) files, tiddlers, or when the user mentions TiddlyWiki operations.

Generate images using Nano Banana Pro (Gemini 3 Pro Preview). Use when creating app icons, logos, UI graphics, marketing banners, social media images, illustrations, diagrams, or any visual assets. Supports reference images for style transfer and character consistency. Triggers include phrases like 'generate an image', 'create a graphic', 'make an icon', 'design a logo', 'create a banner', 'same style as', 'keep the style', or any request needing visual content.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Expert guidance on Swift Concurrency concepts. Use when working with async/await, Tasks, actors, MainActor, Sendable, isolation domains, or debugging concurrency compiler errors. Helps write safe concurrent Swift code.

Guide for creating, auditing, and packaging Claude Code skills. This skill should be used when building new skills, improving existing skills, understanding skill structure, or packaging skills for distribution.

Follow consistent project structure, clear documentation, version control best practices, environment configuration, dependency management, code review processes, and feature flag usage for maintainable team development. Use this skill when organizing project files and directories, writing or updating documentation (README files, architecture docs, contribution guidelines), managing dependencies (package.json, requirements.txt, Gemfile), configuring environment variables, implementing feature flags, writing commit messages, creating pull/merge requests, or establishing team development workflows. Apply when setting up project structure, documenting setup instructions, managing configuration files, maintaining changelogs, or implementing development conventions. Use for any task involving project organization, team collaboration standards, or development workflow best practices.

Comprehensive guide to troubleshooting Pulumi TypeScript errors, infrastructure issues, and best practices - covers common errors, Outputs handling, AWS Beanstalk deployment, and cost optimization