3,775 件 ・ 関連度順
概要と使いどころ
Generates complete technical tutorials from prerequisites and environment setup to core steps, troubleshooting, and a final cheatsheet. Trigger on requests to write a tutorial, create a setup guide, organize steps for beginners, or keywords like step-by-step, quickstart, or how-to guide.
日本語の概要は準備中です。原文の説明を表示しています。
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or tutorial", "API reference", "docstrings", "CLI help text", "changelog or release notes", "migration guide", or "our docs are confusing". Also use it when writing docs from code, rewriting a doc for clarity, fixing headings, procedures, or code samples, or enforcing consistent voice and terminology across a docs set — prefer it over editing documentation unaided. Covers reader and doc-type fit, second person and active voice, procedures, headings, lists and tables, code samples and placeholders, link text, notices, the word list, timeless docs, and accessibility. For code comments and naming, see clean-code. For marketing or landing-page copy, see storybrand-messaging.
日本語の概要は準備中です。原文の説明を表示しています。
When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Write a CONTRIBUTING guide that helps people contribute to an open-source project without friction. Use when asked to write a CONTRIBUTING.md, set up contribution guidelines, or make a repo welcoming to contributors. Produces a clear guide: how to set up, the contribution workflow, standards, PR expectations, and how to get help — lowering the barrier to a first PR.
日本語の概要は準備中です。原文の説明を表示しています。
Extract a brand's visual and verbal identity into an applicable guideline kit — tokens, voice rules, and do/don't pairs — then apply it consistently to any artifact. Use when asked to apply brand guidelines to a document/deck/page, to extract a brand kit from existing materials or a website, to keep AI-produced artifacts on-brand, or to write lightweight brand guidelines for a startup. Produces a compact brand kit (visual tokens + voice rules + application examples) and/or an artifact restyled to it. For a creator's personal voice use creator-brand-kit; for building new UI systems use frontend-design.
日本語の概要は準備中です。原文の説明を表示しています。
Nominates and assesses CRISPR off-target sites genome-wide. Enumerates candidate sites by mismatch and bulge tolerance with Cas-OFFinder/CRISPRitz, ranks them with the published CFD score (SpCas9-only, relative ranker) or MIT/CRISTA/energy models, runs variant-aware screening against gnomAD/individual genomes (CRISPRme), and frames the empirical genome-wide discovery assays (GUIDE-seq, CIRCLE-seq, CHANGE-seq, DISCOVER-seq, Digenome-seq) and high-fidelity nuclease choice (HiFi Cas9, Sniper-Cas9, eSpCas9, SpCas9-HF1). Use when assessing guide RNA specificity, choosing among candidate guides, screening a therapeutic guide against population variation, or planning empirical off-target validation. Distinguishes predicted vs detected vs validated. On-target activity scoring and deaminase (Cas-independent) base/prime-editor off-targets are separate skills.
日本語の概要は準備中です。原文の説明を表示しています。
Create a comprehensive brand standards document — covering logo usage, color, typography, voice, messaging, and application rules. Use when the user says "brand guidelines", "brand standards", "brand book", "style guide", "brand guide", "brand manual", "brand rules", "brand documentation", "brand toolkit", "onboarding designers or copywriters", "need a document for the team", "brand consistency across teams", or wants to codify all brand decisions into a reusable reference document.
日本語の概要は準備中です。原文の説明を表示しています。
Define a brand's verbal identity — tone, voice, writing style, vocabulary, and messaging rules. Use when the user says "brand voice", "tone of voice", "how should we write", "writing guidelines", "copy style guide", "brand language", "verbal identity", "how should the brand sound", "tone guide", "our copy doesn't sound right", "copywriter guidelines", "voice and tone", or when onboarding a copywriter or content team. Also use when the user has a brand strategy and wants to define how the brand communicates.
日本語の概要は準備中です。原文の説明を表示しています。
Guides creation of organisational privacy policy hierarchy aligned to GDPR chapters including top-level policy, supporting procedures, operational guidelines, and training materials. Activate when building or updating policy frameworks. Keywords: policy framework, privacy policy, procedures, guidelines, policy hierarchy.
日本語の概要は準備中です。原文の説明を表示しています。
This skill applies brand guidelines to content creation. It should be used when the user asks to "write an email", "draft a proposal", "create a pitch deck", "write a LinkedIn post", "draft a presentation", "write a Slack message", "draft sales content", or any content creation request where brand voice should be applied. Also triggers on "on-brand", "brand voice", "enforce voice", "apply brand guidelines", "brand-aligned content", "write in our voice", "use our brand tone", "make this sound like us", "rewrite this in our tone", or "this doesn't sound on-brand". Not for generating guidelines from scratch (use guideline-generation) or discovering brand materials (use discover-brand).
日本語の概要は準備中です。原文の説明を表示しています。
The craft of creating and maintaining cohesive brand identity systems. Branding translates brand strategy into tangible visual and verbal identity—logos, color systems, typography, imagery, and voice guidelines that work together to make a brand recognizable and memorable. This skill covers logo design, visual identity systems, brand guidelines, naming, verbal identity, and brand application across touchpoints. Great branding is invisible when done right—it feels inevitable, as if the brand couldn't have looked any other way. Use when "logo, branding, brand identity, brand guidelines, visual identity, color palette, typography, brand book, naming, rebrand, brand refresh, brand system, branding, identity, logo, visual-design, guidelines, naming, typography, color" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a website against the Forter Agentic Readiness Guide. Loads the 25 weighted rubrics in `audit/`, probes the target site (and optional source code), scores each guideline Pass/Partial/Fail/N/A with sub-check granularity, and produces a prioritized fix report. Use when a user asks "score my site against the agentic readiness guide", "audit https://… for agent readiness", or "what do I need to fix to be agent-ready".
日本語の概要は準備中です。原文の説明を表示しています。
Apple Human Interface Guidelines (HIG) に準拠した iOS アプリの UI を、 単一 HTML ファイルの「実際に動くインタラクティブプロトタイプ」として生成するスキル。 iPhone 15 Pro 相当のデバイスフレーム、ステータスバー、ナビゲーションバー、タブバー、 Inset Grouped リスト、モーダル/シート、アラートを iOS 純正の見た目で再現し、 タップ・スワイプ・入力・画面遷移がすべて動作する状態で出力する。 Claude Design / Artifact でそのまま開ける形式。 Use when: iOS アプリの UI を作りたい、アプリのモック画面が欲しい、 HIG 準拠のデザインを作りたい、iPhone 風のプロトタイプを作りたい、 アプリのデザイン案を可視化したい、App Store 提出用アプリの画面イメージを作りたい。 Triggers: "iOS アプリ UI", "iOS デザイン", "HIG", "Human Interface Guidelines", "iPhone モック", "アプリのモック", "iOS プロトタイプ", "アプリ画面を作って", "iOS UI プロトタイプ", "Claude Design", "ネイティブアプリ風", "アプリのデザイン"
[Documentation] Use when you need to generate a step-by-step demo guide (demo script / walkthrough) covering all main user stories and their test cases — scope from a named feature, else the current working context, else confirm with the user — explaining for each case how the domain data is stored/changed and how the domain solves the feature. Triggers: demo guide, generate demo guide, demo script, demo walkthrough, how to demo, prepare demo, sprint demo, user story demo.
日本語の概要は準備中です。原文の説明を表示しています。
業務システムの操作手順書を構造化して作成するスキル。STEPフォーマット （Specific/Target/Expected/Proceed）による手順記述、ANSI Z535準拠の 注意・警告分類、トラブルシューティングガイドを含む包括的な操作マニュアルを 生成する。Use when creating operations manuals, standard operating procedures (SOP), user guides, or system operation guides. Triggers: "operations manual", "操作マニュアル", "手順書作成", "SOP", "操作手順", "standard operating procedure", "ユーザーガイド", "作業手順書", "運用マニュアル"
Knowledge base from the DoD Test & Evaluation Enterprise Guidebook (August 2022 edition 8.02) with DOT&E-facing enterprise emphasis. Use for T&E enterprise roles (DOT&E vs USD(R&E)), DT&E/OT&E/LFT&E, cybersecurity T&E, MOSA/automation/digital enablers, suitability/reliability growth, and TEMP/Strategy/STE planning. Distinct routing from dod-te-guidebook (same guidebook family, pathway-deep pack). Guidance only—defer to DoDI 5000.89 and Title 10 for binding requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the GAO Schedule Assessment Guide (GAO-16-89G, 2015). Use for building, assessing, or auditing a program's integrated master schedule (IMS): the ten best practices of a reliable schedule (capture, sequence, resource, duration, traceability, valid critical path, reasonable total float, schedule risk analysis, updating, baseline), the four characteristics (comprehensive, well-constructed, credible, controlled), critical path method arithmetic (forward/backward pass, total float), schedule risk analysis (Monte Carlo, contingency), statusing and baseline control, and the Appendix II audit triad. Scheduling/time-management oriented: it is the authority on schedule reliability, but it is NOT a cost-estimating guide, a full SE process model, an agile guide, or a risk-management framework — see sibling packs (gao-cost, dau-se-guidebook, nasa-schedule, nasa-risk) for those.
日本語の概要は準備中です。原文の説明を表示しています。
Comparison of the four guideline-approved psychotherapy approaches in Germany: Cognitive Behavioral Therapy, Psychodynamic Therapy, Psychoanalysis, Systemic Therapy — Orientation guide.
日本語の概要は準備中です。原文の説明を表示しています。
Nominates and assesses CRISPR off-target sites genome-wide. Enumerates candidate sites by mismatch and bulge tolerance with Cas-OFFinder/CRISPRitz, ranks them with the published CFD score (SpCas9-only, relative ranker) or MIT/CRISTA/energy models, runs variant-aware screening against gnomAD/individual genomes (CRISPRme), and frames the empirical genome-wide discovery assays (GUIDE-seq, CIRCLE-seq, CHANGE-seq, DISCOVER-seq, Digenome-seq) and high-fidelity nuclease choice (HiFi Cas9, Sniper-Cas9, eSpCas9, SpCas9-HF1). Use when assessing guide RNA specificity, choosing among candidate guides, screening a therapeutic guide against population variation, or planning empirical off-target validation. Distinguishes predicted vs detected vs validated. On-target activity scoring and deaminase (Cas-independent) base/prime-editor off-targets are separate skills.
日本語の概要は準備中です。原文の説明を表示しています。
OpenClawのリリース候補を人が試すために、隔離コピーなどの検証環境を準備し、テストの進行とフィードバック整理を支援します。公開前の報告確認も扱います。
メモや調査資料をもとに、ブログ記事、ガイド、ニュースレターなどの長文を作成し、既存の文体やブランドの方針に合わせて構成と根拠を整えるスキル。
記事やガイド、ニュースレターを、提供された文例やブランドの文体に合わせて執筆します。メモや調査資料の文章化から、既存原稿の構成・根拠の見直しまで扱います。
This skill orchestrates autonomous discovery of brand materials across enterprise platforms (Notion, Confluence, Google Drive, Box, SharePoint, Figma, Gong, Granola, Slack). It should be used when the user asks to "discover brand materials", "find brand documents", "search for brand guidelines", "audit brand content", "what brand materials do we have", "find our style guide", "where are our brand docs", "do we have a style guide", "discover brand voice", "brand content audit", or "find brand assets".
日本語の概要は準備中です。原文の説明を表示しています。
How to build desktop applications with GPUI Kit, the Rust framework published as the gpui-kit crate (GPUI plus gpui_kit::component, gpui_kit::base, gpui_kit::assets). Use when setting up a gpui-kit app, choosing or using a component (Button, Input, Select, Dialog, Sheet, Tabs, Sidebar, List, DataTable, Tree, Chart, etc.), handling component state, theming, or window overlays, and for GPUI mechanics: actions and keybindings, async tasks, contexts, custom elements, entities, events, focus, global state, layout and styling, ElementId, and tests including UI integration testing. Holds the normative Coding Guides: read them before any architecture, state-ownership, public API, naming, or testing decision. Pairs with the gpui-kit-design-guides skill for the Design Guides.
日本語の概要は準備中です。原文の説明を表示しています。