コーディング規約、フレームワーク、リファクタリング、コードレビュー（1.5万 件）
Use when optimizing Convex database read bandwidth, documents-read cost, query indexes, full-table scans, function-level usage dashboard findings, or code that uses .filter(), unbounded .collect(), N+1 reads, or expensive reactive Convex queries.
日本語の概要は準備中です。原文の説明を表示しています。
Connect every external account NowStack Mobile needs (Convex, Expo/EAS, Apple Developer, Vercel, Stripe, Google Play) by acquiring PROGRAMMATIC API ACCESS for each, then doing everything automatically through that access. Use for "setup accounts", "connect my accounts", first-run onboarding, or when check-setup reports CLI/auth gaps. The skill obtains a token/key per service, stores it in the right place, and only asks the user for the irreducible manual steps (browser signup, 2FA, one-time key download). Every account is skippable.
日本語の概要は準備中です。原文の説明を表示しています。
Read and write the user's SaveIt.now bookmarks from the terminal or from JS/TS code, via the official `saveitnow` npm package (CLI + SDK). Handles its own install and API-key setup on first use. Use whenever the user mentions SaveIt, saveit.now, "my bookmarks", "my saved links", "my reading list", asks to save/bookmark a URL, to search what they saved, or to pick something to read.
日本語の概要は準備中です。原文の説明を表示しています。
Set up local iOS dev/build tooling for NowStack Mobile: Xcode, Simulator, CocoaPods, Watchman, mobile deps, and first `expo run:ios`. Use for `/ns ios local-setup`, legacy `/ns setup-ios`, simulator preview, or local TestFlight prerequisites. macOS only; signing is `/ns ios setup`.
日本語の概要は準備中です。原文の説明を表示しています。
Structured code review through the shared OpenClaw agent-skills installation.
日本語の概要は準備中です。原文の説明を表示しています。
Designs viral referral programs with incentive structures, sharing mechanics, and tracking. Covers one-sided, two-sided, tiered, and milestone models with viral coefficient calculations. Use when someone wants word-of-mouth growth, viral loops, invite programs, or says 'referral', 'viral loop', 'word of mouth', 'invite program', 'refer a friend', 'growth loop', 'referral incentive', 'affiliate program', 'ambassador program', 'get users to invite friends', or 'organic growth'. Even casual mentions like 'how do I get my users to spread the word' or 'can users invite others' should trigger this. Includes anti-fraud measures and copy templates for both referrer and referee. Use this whenever user-driven acquisition or viral mechanics are discussed.
日本語の概要は準備中です。原文の説明を表示しています。
Trigger when: (1) User mentions "manim" or "Manim Community" or "ManimCE", (2) Code contains `from manim import *`, (3) User runs `manim` CLI commands, (4) Working with Scene, MathTex, Create(), or ManimCE-specific classes. Best practices for Manim Community Edition - the community-maintained Python animation engine. Covers Scene structure, animations, LaTeX/MathTex, 3D with ThreeDScene, camera control, styling, and CLI usage. NOT for ManimGL/3b1b version (which uses `manimlib` imports and `manimgl` CLI).
日本語の概要は準備中です。原文の説明を表示しています。
Use the trackcn CLI to sync files, directories, commits, pull requests, and agent skills from GitHub into a codebase while preserving local edits. Read this before running trackcn commands or modifying trackcn-managed files.
日本語の概要は準備中です。原文の説明を表示しています。
Lightweight refactor: audit → plan → approve → implement in a single Opus context, no sub-agent fan-out. Behavior preservation is the goal — verifies tests still pass, optionally commits, and offers a separate /code-review pass at the end. Use by default; reach for /refactor only when the cleanup needs parallel fan-out or exceeds one context.
日本語の概要は準備中です。原文の説明を表示しています。
Refactoring pipeline: analyzes a target file or directory for code quality issues, plans safe incremental improvements, optionally writes tests first as a safety net, implements the changes, and reviews the result. Orchestrates refactor-planner → (test-writer) → parallel-task-orchestrator → code-reviewer.
日本語の概要は準備中です。原文の説明を表示しています。
Lightweight refactor: audit → plan → approve → implement in a single Opus context, no sub-agent fan-out. Behavior preservation is the goal — verifies tests still pass, optionally commits, and offers a separate /code-review pass at the end. Use by default; reach for /claude-setup:refactor only when the cleanup needs parallel fan-out or exceeds one context.
日本語の概要は準備中です。原文の説明を表示しています。
Project Ritoの開発ガイドラインと規約です。
Rust Token Killer (Codex CLI) の使用ガイドラインです。常にシェルコマンドを実行する際は rtk プレフィックスを付与します。
Search, analyze, and synthesize across all your Claude Code sessions. Ask "what did I try last time?" and get answers with resume links.
日本語の概要は準備中です。原文の説明を表示しています。
Write accessible HTML, CSS, and JavaScript that conforms to RAWeb 1.1 (Luxembourg Web Accessibility Framework, based on EN 301 549 / WCAG 2.1). Use when developing web interfaces, components, forms, navigation, or any front-end code that must meet Luxembourg accessibility law. Covers all 17 RAWeb themes with code-level guidance, accessible patterns, and anti-patterns. Default conformance target: Level AA.
日本語の概要は準備中です。原文の説明を表示しています。
Develop accessible mobile applications (iOS and Android) conforming to RAAM 1.1 (Luxembourg Mobile Accessibility Assessment Framework, based on EN 301 549 v3.2.1 / WCAG 2.1). Use when building native mobile apps, React Native, Flutter, or any mobile UI that must meet Luxembourg accessibility law. Covers all 15 RAAM themes with platform-specific code guidance. Default conformance target: Level AA.
日本語の概要は準備中です。原文の説明を表示しています。
文章を書く時の心得。ソースコードのコメント、PR概要欄、ドキュメント、wikiのどこに書く時も変わらない、解釈のブレを起こさない文の書き方と、強調記号とカッコ書きの扱いを定める。 ソースコードのコメント、PR概要欄、ドキュメント、wikiの文章を書く時、直す時、レビューする時に読み込む。
Provides instructions for installing and using the `android` CLI. The `android` command-line tool is a critical tool for Android development and helps you create new Android projects, run Android apps on devices, manage and interact with Android virtual devices (including screenshots and UI inspection), manage Android SDK components, look up official Android documentation, and discover and install official Android skills.
日本語の概要は準備中です。原文の説明を表示しています。
Helps developers integrate, debug, and resolve Play Engage SDK implementation issues. Use when adding Engage SDK support, generating publishing code, mapping data classes to entities, or fixing SDK-related errors.
日本語の概要は準備中です。原文の説明を表示しています。
Use ManagedCode.Orleans.SignalR when a distributed .NET application needs Orleans-based coordination of SignalR real-time messaging, hub delivery, and grain-driven push flows.
日本語の概要は準備中です。原文の説明を表示しています。
Use the free first-party `dotnet format` CLI for .NET formatting and analyzer fixes. Use when a .NET repo needs formatting commands, `--verify-no-changes` CI checks, or `.editorconfig`-driven code style enforcement.
日本語の概要は準備中です。原文の説明を表示しています。
Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. Use when a repo needs cyclomatic complexity checks, maintainability thresholds, or complexity-driven refactoring gates.
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `Roslynator` analyzer packages and optional CLI for .NET. Use when a repo wants broad C# static analysis, auto-fix flows, dead-code detection, optional CLI checks, or extra rules beyond the SDK analyzers.
日本語の概要は準備中です。原文の説明を表示しています。
Use `graphify-dotnet` to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships.
日本語の概要は準備中です。原文の説明を表示しています。