Frontend

Systematically uncover and fix bugs using language-specific expertise andreproducible evidence.Triggers: bug hunting, defect detection, debugging, fix verification, bug fix,regression check, error investigation, defect documentationUse when: deep bug hunting needed, documenting defects, verifying fixes,systematic debugging requiredDO 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 codeUse when: preparing for refactoring, context usage is high, quarterly maintenance, pre-release cleanupDO 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 remediationUse when: auditing test suites, analyzing coverage gaps, improving testquality, evaluating TDD/BDD complianceDO 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 androutes out-of-scope findings to GitHub issues.Triggers: PR review, pull request review, scope validation, requirement compliance,backlog triage, code review, blocking issuesUse when: reviewing PRs, validating against requirements, triaging findingsto backlog, preventing overengineeringDO 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 vulnerabilityUse when: auditing existing hooks for security vulnerabilities, benchmarkinghook performance, implementing hooks using Python SDK, understanding hookcallback signatures, validating hooks against compliance standardsDO 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 docsUse when: updating documentation after code changes, enforcing writing guidelines, maintaining ADRsDO 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.

Design and construct virtual memory palaces for spatial knowledge organizationusing mnemonic techniques.Triggers: memory palace, spatial organization, mnemonic, knowledge architecture,domain mapping, layout design, memory structure, recall enhancementUse when: creating new memory palace structures, organizing complex domains,designing spatial layouts for knowledge retentionDO NOT use when: quick knowledge search - use knowledge-locator instead.DO NOT use when: session-specific context - use session-palace-builder.Consult this skill when designing permanent memory palace structures.

Reusable patterns and templates for Claude Code skill and hook development.Triggers: validation patterns, error handling, testing templates, workflow patterns,shared patterns, reusable templates, DRY patterns, common workflowsUse when: creating new skills or hooks that need consistent patterns, implementingvalidation logic, setting up error handling, creating test scaffolding,referencing standard workflow structuresDO NOT use when: pattern is specific to one skill only.DO NOT use when: pattern is still evolving - wait for stability.DO NOT use when: pattern is context-dependent requiring variations.Reference these patterns to validate consistency across the ecosystem.

Python testing with pytest, fixtures, mocking, and TDD workflows.Triggers: pytest, unit tests, test fixtures, mocking, TDD, test suite, coverage,test-driven development, testing patterns, parameterized testsUse when: writing unit tests, setting up test suites, implementing TDD,configuring pytest, creating fixtures, async testingDO NOT use when: evaluating test quality - use pensive:test-review instead.DO NOT use when: infrastructure test config - use leyline:pytest-config.Consult this skill for Python testing implementation and patterns.

Analyze and enhance Makefiles for complete user functionality coverage.Triggers: Makefile analysis, Makefile gaps, missing targets, plugin release,Makefile coverage, build targets, make dogfood, plugin qualityUse when: analyzing Makefile completeness before releasing plugins, identifyinggaps during plugin maintenance, scoring Makefiles against best practices,verifying Makefiles support standard developer workflowsDO NOT use when: writing initial Makefiles from scratch.DO NOT use when: debugging specific build target failures.DO NOT use when: creating custom non-standard build systems.Use this skill BEFORE releasing any plugin to verify Makefile coverage.

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.

Write consistent, maintainable CSS following the project's methodology (Tailwind, BEM, utility classes, CSS modules) with design system adherence and performance optimization. Use this skill when writing or modifying styles, CSS files, utility classes, CSS-in-JS, styled components, or any styling code. Apply when working with .css, .scss, .module.css files, Tailwind utility classes, styled-components, CSS modules, design tokens (colors, spacing, typography), framework-specific styling approaches, optimizing CSS for production, implementing CSS purging or tree-shaking, or avoiding style overrides. Use for any task involving visual styling, layout styling, design system implementation, or CSS organization.