
UI design quality standards and principles for frontend implementation and code review. Use when (1) implementing UI from design specs or mockups, (2) reviewing frontend/UI code, (3) creating new UI components, (4) building user interfaces for web or mobile apps. Complements frontend-design skills with quality enforcement.
Iteratively improve agent-facing text instructions (skills, slash commands, task prompts, CLAUDE.md sections, code-generation prompts) by having a bias-free executor run them and evaluating from both sides (executor self-report + caller-side metrics). Repeat until improvement plateaus. Use immediately after creating or significantly revising a skill/prompt, or when unexpected agent behavior is suspected to stem from ambiguous instructions.
Pre-submission review for iOS App Store. Scans the codebase for common rejection reasons and generates a pass/fail report with fixes. Use this skill when the user mentions App Store submission, review, release, 審査, 提出, or phrases like "ready to submit", "before submitting to Apple", "submission review", "rejection check". Also trigger when the user is preparing a TestFlight build for external review or discussing App Store rejection issues. Supports Swift/SwiftUI, UIKit, and React Native projects with Apple IAP and RevenueCat.
Atlassian CLI (acli) for Jira operations. Use when (1) creating Jira tickets/issues, (2) updating or editing existing tickets, (3) searching Jira issues, (4) viewing ticket details, (5) managing work items programmatically. Provides correct syntax and ADF format for descriptions.
Guided feature development with harness engineering principles. Sprint contracts, architecture design, implementation, evaluation, and quality review. Use when building new features or significant enhancements.
Delegate an interrupt task to a background agent in an isolated worktree. The main session continues uninterrupted. The agent implements, commits, pushes, and creates a PR. Use when a quick fix or small task needs to happen without losing current context.
End-to-end workflow for finding content, app, service, or product opportunities where search demand is high but quality supply is low (trend arbitrage). Use when: finding content gaps, keyword opportunities, niche research, analyzing whether a topic or idea is worth pursuing, or competitive gap analysis.
Create viral X/Twitter posts based on the official X algorithm (Phoenix/Grok). Generates and improves posts optimized for maximum engagement. Use when (1) creating X posts for products, services, or information, (2) improving existing post drafts, (3) designing thread structures for long content.
E2E testing workflow for web applications using Chrome in Claude. Automates functional testing, bug detection, and GitHub Issue creation. Use when: (1) running functional tests on web apps, (2) verifying staging/production behavior, (3) finding bugs and creating Issues, (4) capturing UI behavior with screenshots
Conduct an attacker-perspective security review of a codebase, then ship the fixes as multiple non-conflicting pull requests in parallel using subagents and git worktrees. Verifies findings to filter false positives, plans fixes via file-occupation analysis to guarantee no merge conflicts, dispatches each fix to its own TDD-driven subagent in an isolated worktree, then pushes and opens one PR per fix. Use this whenever the user asks for a security audit, pentest, vulnerability review, attack surface analysis, or wants to "find vulnerabilities" / "review for security issues" in their own (or otherwise authorized) project, even if they don't say the word "pentest". Also use when the user already has a list of independent fixes (security or otherwise) and wants them shipped as parallel non-conflicting PRs without manually managing worktrees.
Research a repo/docs in parallel for a given topic and generate a disposable GFM+mermaid learning primer (Markdown). Triggers (Japanese): 「〜の学習資料を作って」 「オンボーディング資料がほしい」「〜をキャッチアップしたい」「primer 作って」. Output is not committed (defaults to repo-local `.ai/`, globally git-ignored); view with mo or any GFM+mermaid viewer.
Generate a 1-page purchase memo for a US or JP individual stock (ETF support in v1.1). Walks 5 phases — business, fundamentals, valuation, risks, verdict — and ends with deep-dive options. Use when (1) the user asks "should I buy <TICKER>?", (2) the user wants a fundamental review of a specific company, (3) the user pastes a 10-K / 有報 / IR URL and asks for an analysis. Skip for ETF / index / dividend-focused questions in v1.