322 件 ・ 関連度順
概要と使いどころ
Active Directory ACL abuse playbook. Use when exploiting misconfigured AD permissions including GenericAll, WriteDACL, DCSync rights, shadow credentials, LAPS reading, GPO abuse, and BloodHound-guided attack paths.
日本語の概要は準備中です。原文の説明を表示しています。
Set up your personal OS from scratch with guided questions
日本語の概要は準備中です。原文の説明を表示しています。
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
日本語の概要は準備中です。原文の説明を表示しています。
Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a complete architecture blueprint before any code is written. Engine-version-aware: flags knowledge gaps and validates decisions against the pinned engine version.
日本語の概要は準備中です。原文の説明を表示しています。
Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
日本語の概要は準備中です。原文の説明を表示しています。
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or any GDD authoring begins.
日本語の概要は準備中です。原文の説明を表示しています。
Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates 6-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) for guided feature development. Use when user runs /core:develop command, requests spec-driven development, wants to create implementation plans with architecture decisions, or mentions "SDLC", "spec-driven", "plan feature", "development pipeline". Supports plan persistence, wave-based resume, autonomous mode, and architecture/implementation verification.
日本語の概要は準備中です。原文の説明を表示しています。
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
日本語の概要は準備中です。原文の説明を表示しています。
Run the explicit, human-in-the-loop Circuit Weaver questionnaire from requirements through a validated design and KiCad handoff. Use only when the user asks for the design-wizard skill, the offline interactive wizard, or a slow step-by-step guided questionnaire. Do not trigger for ordinary new-design requests; use circuit-weaver for automatic end-to-end orchestration.
日本語の概要は準備中です。原文の説明を表示しています。
Generate, score, and shortlist brand names through a guided interview. Use when the user says "name my brand", "help me name", "come up with a name", "naming ideas", "what should I call this", "brand name", "product name", "company name", "rename", "rebrand", or is stuck choosing between names. Self-contained and brand-agnostic: it does not read knowledge/, so it works for naming a brand-new venture, product, service, feature, or rebrand from scratch, before any brand context exists. Runs on Alexandra Watkins' SMILE and SCRATCH tests to generate and filter, Marty Neumeier's 7 criteria to score, and the Lexicon Branding method for sound symbolism and strategy. Asks the user questions before generating. For the positioning the name has to carry, see positioning-doc. For the message architecture built on top of it, see messaging-framework.
日本語の概要は準備中です。原文の説明を表示しています。
Build custom AI prompts from scratch using guided workflows and patterns from a 2,500+ prompt database. Supports image, video, and text prompts for Midjourney, Flux, Leonardo AI, DALL-E, Sora, and 12 more models. Use when user says "build a prompt", "create a prompt", "write a prompt", "make me a prompt", "new prompt", or "prompt from scratch".
日本語の概要は準備中です。原文の説明を表示しています。
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection. Use for research storytelling, contribution framing, paper comparison, figure planning, or research retrospectives. Not an acceptance predictor or a routine grammar/citation formatter.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to self-hosted inference on GKE, or asks follow-up questions during such a migration (hardware sizing, model staging, manifest generation, validation, traffic cutover). DO NOT use for brand new GKE inference deployments with no existing workload to migrate (use gke-inference instead). DO NOT use if the user intends to automate the migration via the Gemini Cloud Assist MCP server.
日本語の概要は準備中です。原文の説明を表示しています。
Guides a developer's first steps on Google Cloud, covering account creation, billing setup, project management, and deploying a first resource. Use when a new developer wants to initialize their first Google Cloud project, configure billing, and verify deployment. Don't use for enterprise organization setup (use Google Cloud Setup guided flow for that instead). Don't use for complex multi-project architectures.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or customizing industry-specific guided processes in Salesforce Industries clouds: insurance claims lifecycle (FNOL through closure), telecom order management decomposition, and utility service request workflows. Trigger keywords: FNOL process design, claims OmniScript customization, Industries order decomposition workflow, utility service order design, insurance claim lifecycle stages, telecom commercial-to-technical order flow. NOT for the Industries object model — use architect/industries-data-model. NOT for Insurance Cloud licensing and policy architecture — use architect/insurance-cloud-architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Guided setup for sharing moflo's durable learnings through a git-tracked JSONL artifact — for a whole TEAM on one repo, OR for one person across several MACHINES (a team of one). Use when the user says "share learnings with my team", "commit our moflo memory", "sync memory across my laptop and desktop", "set up memory.team_artifact", or "auto-export learnings on every PR". Installs a pre-commit hook so the artifact rides along in every commit. For many worktrees on ONE machine, use /memory-worktree instead.
日本語の概要は準備中です。原文の説明を表示しています。
โค้ชสมาธิ + mindfulness — guided meditation script (5/15/30 min) + breathing technique (box, 4-7-8) + theme practice (focus, anxiety, sleep, loving-kindness)
日本語の概要は準備中です。原文の説明を表示しています。
Apple FoundationModels framework for on-device LLM — text generation, guided generation with @Generable, tool calling, and snapshot streaming in iOS 26+.
日本語の概要は準備中です。原文の説明を表示しています。
Queries PharmGKB / CPIC / DPWG for drug-gene interactions; calls CYP2D6/CYP2C9/CYP2C19/DPYD/TPMT/NUDT15/UGT1A1/SLCO1B1 star alleles and phenotype with PharmCAT, Cyrius (CYP2D6 structural variants), Aldy, Stargazer; applies Caudle 2020 activity-score translation. Use when implementing pharmacogenomic-guided prescribing, applying CPIC vs DPWG guidance, screening HLA risk alleles for ICI / antiepileptics / abacavir, or interpreting compound TPMT+NUDT15 thiopurine risk.
日本語の概要は準備中です。原文の説明を表示しています。
A guided agent security review of amux, its CI/CD, and repo.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
日本語の概要は準備中です。原文の説明を表示しています。
Pure API reference for reddapi.dev - authentication, all endpoints (vector search, semantic search, trends, subreddit lookup), request parameters, response schemas, and error codes, with no research-workflow framing. Use when the user wants raw endpoint documentation, is debugging a reddapi.dev integration, needs exact request/response field names, or asks for 'reddapi API reference', 'reddapi.dev endpoints', or 'reddapi error codes'. For guided research workflows and query playbooks, see reddit-research. For B2B lead scoring, see reddit-leads.
日本語の概要は準備中です。原文の説明を表示しています。
Generate guided Chinese software copyright application materials from a real project. Use this skill when the user asks for 软件著作权, 软著申请资料, 软著代码材料, 操作手册, 申请表信息, or wants Word/TXT materials for software copyright registration. The workflow analyzes the imported project, extracts real source code, creates Markdown drafts for user confirmation, then uses bundled DOCX tooling to produce final Word documents and TXT.
日本語の概要は準備中です。原文の説明を表示しています。