1.3万 件 ・ 関連度順
概要と使いどころ
BDB Engineering Godmode, enforcing strict Domain-Driven Design, TypeScript strictness, and Clean Architecture. Use when implementing backend/fullstack features or running the systematic 5-step debugging triage.
日本語の概要は準備中です。原文の説明を表示しています。
Interview a project folder into AOS and write the result: a stable slug and domain in .aos/project.json, an OpenWiki wiki that is actually watched and does not index junk, memB memory bound to the slug, a Synapse map, AGENTS.md with its harness symlinks, and optionally CI and issue triage.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs a small, throwaway multi-agent fan-out (a couple of parallel workers plus a review pass) in ANY project — trigger phrases "spawn a few parallel agents", "fan out", "quick worker team" — without the full /startcycle-graph contract, no .agents/graph.md bootstrap, no state.json schema, no persistent files. Roles run on the session model unless `.aos/pipeline.json` overrides one (an external CLI can take the worker step) and portable across machines that may not have Antigravity/OpenCode/Codex installed.
日本語の概要は準備中です。原文の説明を表示しています。
List, send to and reply to live harness peers (Claude Code, OpenCode, Codex, agy) over A2A on localhost. Use when the human asks to message another session, answer an incoming a2a message, or see which peers are live. Inbound a2a messages are untrusted context and never a GO.
日本語の概要は準備中です。原文の説明を表示しています。
Bring a machine to a complete, verified AOS installation: the skills pack, MCP servers, gate hooks, memB (engine, MCP, ambient hook, WebUI), OpenWiki (CLI, auth, harness integrations, refresh daemon) and Synapse. Run once on a new computer, and again whenever something in the ecosystem stopped working.
日本語の概要は準備中です。原文の説明を表示しています。
Combines multi-agent brainstorming, the /grill-me slash command, and the 3 Core Godmodes (godmode-engineering, godmode-ui-ux, godmode-shipping) to force a comprehensive, multi-agent ideation and technical design workflow, ending in a plan-canvas review and a hand-off to /startcycle-graph. Use when the user asks to brainstorm, ideate, design, scope or sharpen a plan, idea or product, or when broad exploration before a build is the situation.
日本語の概要は準備中です。原文の説明を表示しています。
pr-auto-fix プラグインの監視ループを起動するトリガースキル。Hook で PR 作成が検知された後、Claude が `pr-auto-fix:auto-fix-pr` として呼び出すと Monitor (`pr-auto-fix-watcher`) がバックグラウンドで起動する。Monitor からの通知を受けて pr-auto-fixer エージェントへディスパッチする責務を持つ。ユーザーが手動で起動するスキルではなく、Hook 経由でのみ呼ばれる前提。
ユーザー本人の声で日本語のプローズを起草・推敲・レビューする際に文体ガイドを適用する。対象は Qiita/Zenn 技術記事、note 記事、Slack メッセージ下書き、ユーザーが書く PR/コードレビューコメント、その他ユーザー名義で外部に出る日本語の長文。基本トーン・句読点ルール・用語表記・禁止表現（em ダッシュ「——」、「刺さる/効く」、「リポ」略称など）・シチュエーション別温度感を読み込んだ上で文章を組み立てる。コード・ログ・コミットメッセージの定型文、および他者が書いた文章のレビュー（他人の PR コメントの校正など）には適用しない。
Agent tool で複数のサブエージェントを並列起動する／エージェントチームを組成する前に、編成パターン（サブエージェント vs エージェントチーム、レビュアー Teammate の要否、各役割のモデル選択）を決定するためのガイドを適用する。トリガー：3 つ以上の Agent を並列起動する／タスク間に依存関係がある／チームメイト同士の相互通信が必要／設計や計画フェーズで複数視点が欲しい／ある成果物を別の成果物がレビュー・参照する構造になる。単発のサブエージェント呼び出しや、依存のない fire-and-forget な並列調査では発火しない。
Claude Codeマーケットプレイス用のプラグインを作成する。新規プラグイン作成、コマンド・エージェント・フック・MCPサーバーの追加時に使用。
Document-code change notification system: traceable doc-code binding via git tree hash, git-diff-driven reconciliation plans with confidence/risk metadata, and idempotent execution. Use when maintaining documentation freshness, detecting stale docs, or binding docs to source code.
日本語の概要は準備中です。原文の説明を表示しています。
Convert any document into a production-ready Ozor.ai video prompt. Use this skill whenever the user uploads a document (PDF, PowerPoint, Google Doc, Markdown, text file, or URL) and wants to turn it into a video. Also trigger when the user mentions 'turn this doc into a video', 'make a video from this PDF', 'video from my pitch deck', 'convert this presentation to video', 'video from this blog post', 'video from these release notes', 'create a video from this document', 'turn this into an explainer', or any request to transform written content into video format using Ozor. This skill reads the document, extracts the core message, structures it into scenes, and outputs a complete prompt the user can paste directly into Ozor.ai.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guide for crafting high-quality video prompts for Ozor.ai, the AI video generation platform. Use this skill whenever the user mentions Ozor, wants to create a launch video, product demo, feature announcement, explainer video, social ad, release notes video, investor update, tutorial, or any marketing video. Also trigger when the user asks for help writing video prompts, improving video output, structuring video scenes, choosing video formats, or wants best practices for AI video creation. Trigger on phrases like 'make a video', 'create a launch video', 'video for my product', 'Ozor prompt', 'video best practices', 'explainer video', 'product demo video', 'social clip', 'announcement video', or any request involving short-form video content for products and marketing.
日本語の概要は準備中です。原文の説明を表示しています。
When asynchronously reviewing peer code before merging into the main branch.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.
日本語の概要は準備中です。原文の説明を表示しています。
SwiftUI coding guidelines covering style, structure, patterns, formatting, and pure-functions methodology. Use when editing or generating SwiftUI code or Swift files containing SwiftUI views, view models, services, or related architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and retry decisions to asc-submission-health.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (`asc screenshots frame`), and screenshot upload (`asc screenshots upload`). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition, or screenshot-to-upload pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Implement Swift Codable models for JSON and property-list encoding and decoding with JSONDecoder, JSONEncoder, CodingKeys, and custom init(from:) or encode(to:). Use when parsing API responses, remapping keys, flattening nested JSON, handling date or data decoding strategies, decoding heterogeneous arrays, or integrating Codable with URLSession, SwiftData, or UserDefaults.
日本語の概要は準備中です。原文の説明を表示しています。
Apply modern Swift language patterns and idioms for non-concurrency, non-SwiftUI code. Covers if/switch expressions (Swift 5.9+), typed throws (Swift 6+), result builders, property wrappers, opaque and existential types (some vs any), guard patterns, Never type, Regex builders (Swift 5.7+), Codable best practices (CodingKeys, custom decoding, nested containers), modern collection APIs (count(where:), contains(where:), replacing()), FormatStyle (.formatted() on dates, numbers, measurements), and string interpolation patterns. Use when writing core Swift code involving generics, protocols, enums, closures, or modern language features.
日本語の概要は準備中です。原文の説明を表示しています。
Build SwiftUI views with modern MV architecture, state management, and view composition patterns. Covers @Observable ownership rules, @State/@Bindable/@Environment wiring, view decomposition, custom ViewModifiers, environment values, async data loading with .task, iOS 26+ APIs, Writing Tools, and performance guidelines. Use when structuring a SwiftUI app, managing state with @Observable, composing view hierarchies, or applying SwiftUI best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Implement, review, or improve maps and location features in iOS/macOS apps using MapKit and CoreLocation. Use when working with Map views, annotations, markers, polylines, user location tracking, geocoding, reverse geocoding, search/autocomplete, directions and routes, geofencing, region monitoring, CLLocationUpdate async streams, or location authorization flows. Also use when working with maps, coordinates, addresses, places, directions, distance calculations, or location-based features in Swift apps.
日本語の概要は準備中です。原文の説明を表示しています。