Skill UI

Used to verify the actual billing reality, revenue, and pricing mechanics—such as team billing, quotas, and refunds—based on underlying product code, rather than sales documents or simple customer fixes. This skill separates billing facts, customer impact, and the true product implementation logic.

Craft production-ready frontend pages, dashboards, or components with a clear visual point of view; focus on typography, color, motion, and layout so the experience feels intentional instead of generic.

This skill file acts as a Japanese translation placeholder for the 'product-capability' module. It indicates that the localized content is currently under development and not functional. Users should refer to the original English skill file for the core functionality and detailed implementation.

A robust, production-tested pattern for coordinating multiple specialized AI agents. The orchestrator decomposes complex tasks, routes them to the most suitable specialist, prevents redundant or conflicting work (anti-duplication), and enforces mandatory quality gates (e.g., running tests, checking file diffs) to verify results before marking a task as complete. It also includes heartbeat monitoring for task progress.

Build and leverage online communities to drive product growth and brand loyalty. Covers community strategy, Discord/Slack growth, brand advocate programs, community-led growth, and turning customers into evangelists.

Guides systematic root-cause debugging when tests fail, builds break, or behavior unexpectedly changes. It covers stop-the-line discipline, a triage checklist, git bisection for regressions, minimal reproduction, root-cause fixes, regression tests, and end-to-end verification. Ideal for turning confusing errors into reliable recovery workflows.

A comprehensive skill for generating non-generic, professional frontend interfaces, perfect for landing pages, portfolios, and product redesigns. This agent enforces a strict design methodology: reading the user's brief (audience, vibe, constraints) first, configuring global design dials (variance, motion, density), and recommending real, industry-standard design systems (like Material or Fluent UI) to ensure the output is always polished and contextually appropriate.

Comprehensive guide for implementing Firebase Authentication in Flutter apps. Covers setup, auth state management, email/password sign-in, social login, error handling, and security best practices for production-ready auth flows.

This skill focuses on building production-quality, accessible, and responsive user interfaces. It involves creating components, implementing layouts, and managing state while adhering to design systems and WCAG standards. The goal is to avoid generic AI aesthetics and ensure the UI looks like it was built by a professional engineer. It covers component architecture, state management strategies, and design system adherence for high-quality web applications.

A comprehensive guide for setting up production-grade CI/CD pipelines for Go projects using GitHub Actions. It covers all critical stages: unit testing (with race detection), linting, static application security testing (SAST), vulnerability scanning, automated dependency updates (Dependabot/Renovate), Docker image builds, and automated releases via GoReleaser. Ideal for DevOps engineers establishing or improving Go project quality gates.

This skill provides comprehensive guidance on idiomatic Go patterns for building production-ready, robust applications. It covers best practices like functional options, proper constructor design, resource management (timeouts, graceful shutdown), error handling, concurrency patterns, and architectural styles (DDD, Hexagonal). Use it when structuring complex Go APIs, defining service boundaries, or auditing existing code for common anti-patterns and performance pitfalls.

This skill provides comprehensive guidelines for writing idiomatic, robust, and production-ready error handling in Go. It covers best practices for error creation, proper wrapping using `%w`, inspection techniques with `errors.Is` and `errors.As`, adhering to the single handling rule, and utilizing structured logging with `slog`. Use it when auditing, reviewing, or writing new Go code to ensure reliable error propagation and logging.