「consul」の検索結果

Think out loud about a problem, decision, or approach — Socratic friction to help you find clarity, not sympathy

日本語の概要は準備中です。原文の説明を表示しています。

Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.

日本語の概要は準備中です。原文の説明を表示しています。

Pressure-test an assumption, decision, or inherited constraint — Socratic cross-examination that forces you to defend or abandon your position

日本語の概要は準備中です。原文の説明を表示しています。

Socratic code review and refactoring session — whether it's your own code, a teammate's PR, or something you inherited. Leads you to see the issues through questions, names smells and moves precisely, then closes with a concrete plan.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing, implementing, reviewing, or improving web and mobile UI/UX. Consults searchable design data for product patterns, styles, palettes, typography, accessibility, charts, icons, and common frontend stacks.

日本語の概要は準備中です。原文の説明を表示しています。

Inspect or exercise the paused gaia curate orchestration scaffold for one source URL. The command currently persists an INITIALIZED run ledger and reports status; its 25 named workflow states and transition methods are a design skeleton, not an implemented automated curation or merge pipeline. Use only for scaffold development, status inspection, or dry-run contract work. For live curation, use gaia-full-pipeline or gaia-consult. Trigger phrases: "/gaia-quick-curate", "inspect gaia curate", "curate scaffold", "quick curate status". For batch/multi-page runs use gaia-curate-dynamic; for crawler branches use gaia-bot-curate; for pending intake proposals use gaia-draft-curate.

日本語の概要は準備中です。原文の説明を表示しています。

How to write source comments, doc comments, and test names/tags that have lasting value — and what to never write. Consult before adding or editing comments in core/**, examples/**, tools/**, test/**, docs/**, or any shipped source. Handles "write a comment", "is this comment ok", "comment hygiene", and keeping new code from adding the breadcrumbs the cleanup stream removes.

日本語の概要は準備中です。原文の説明を表示しています。

Before designing, training, or auditing ANY model that replicates human-annotated labels, audit the annotation protocol's INPUT — the exact document/evidence the human labelers consulted — and give the model that same input. Use when: (1) designing a classifier/LLM extractor whose target is a hand-coded label set, (2) a label-replication model shows low recall concentrated in a label subset and the diagnosis on offer is "the label's information is not in the features", (3) reviewers propose construct splits (e.g. "designation vs record-evident"), adjudication sittings, or per-domain stop rules to explain residual disagreement with gold, (4) validating an extraction pipeline against labels transcribed from a source document. Symptom of the underlying failure: elaborate theory accumulates to explain why gold is "partially unpredictable" when the model was simply never shown the document the annotators read.

日本語の概要は準備中です。原文の説明を表示しています。

Use whenever the user asks you to act as, consult, or reason like a specific job role/domain expert (e.g. "review this like a CFO," "what would a UX designer say," "act as a contracts lawyer") and this repo's roles/ directory is available. Finds the best-matching role SKILL.md and adopts it, or honestly reports the gap if none exists.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to analyze, consult, setup, manage, configure, or design a Volcengine Landing Zone, including organization, accounts, finance, identity, cloudtrail, or network infrastructure, or to deploy a solution/blueprint.

日本語の概要は準備中です。原文の説明を表示しています。

Write an executive summary using the Pyramid Principle SCQA structure. Use when a consultant says "write an executive summary", "I need a one-pager for the exec", "how do I open this report", "write me the intro for this deck", "draft the cover memo", "I need to frame the findings", "executive doesn't have time to read the full report", "help me write the storyline", or "write the situation-complication-answer". Also trigger when someone has findings or recommendations and needs to communicate them top-down to a time-constrained audience.

日本語の概要は準備中です。原文の説明を表示しています。

Decompose a business problem MECE using an issue tree, generate hypotheses, and prioritize branches for investigation. Use when a consultant says "help me structure this problem", "I need to break down this issue", "build me an issue tree", "I don't know where to start on this problem", "help me frame the problem", "what are the hypotheses here", "we need to prioritize our analysis", or "the client problem is too broad". Also trigger when describing a complex or ambiguous business problem that needs systematic decomposition before analysis begins, or when an engagement is starting and a workplan needs to be structured from a problem statement.

日本語の概要は準備中です。原文の説明を表示しています。

Locates and loads the right Google product skill on demand from a remote catalog index, instead of preloading every skill. Use at the START of any request touching a Google product, API, or developer platform - including Google Cloud (GKE, Cloud Run, IAM, BigQuery, Vertex AI, Spanner), Google Ads, Google Analytics, Google Workspace (Gmail, Drive, Admin SDK), Chrome and Chrome extensions, Android, Firebase, YouTube, Google Maps, Gemini and the Gemini API, Google Play, and Flutter. Consult the index before answering from memory or searching the web. Don't use for non-Google products.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an ISV or consulting partner is creating, pricing, publishing, or maintaining an AgentExchange listing through the Partner Console — covers the listing plan, the 5-step Listing Builder workflow (Fill in the Basics, Set Pricing, Add Details, Link Your Solution, Grow Your Business), commercialization models (revenue share vs. annual fee vs. freemium), AgentExchange Checkout setup (Stripe connection, pricing plans, fees, geographic eligibility), Private Offers, Security Review gating, and post-publish listing updates. NOT for building the agent or managed package itself (use agentforce/agentforce-agent-creation and devops/second-generation-managed-packages), NOT for LMA/Trialforce licensing internals (use devops/isv-license-management-and-trialforce), and NOT for the customer-side install experience.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when building, reviewing, or refreshing a RACI (Responsible / Accountable / Consulted / Informed) matrix for a Salesforce project so that every Salesforce-specific decision — data model change, automation tier choice, security model, integration boundary, deployment, license/edition — has exactly one accountable owner and a documented escalation path that downstream agents can route to. Trigger keywords: RACI matrix salesforce project, stakeholder authority salesforce, escalation path salesforce decisions, who approves data model change, salesforce decision rights, REFUSAL_NEEDS_HUMAN_REVIEW routing. NOT for the change advisory board operating model itself (use admin/change-management-and-deployment). NOT for end-user training rollout plans (use admin/change-management-and-training). NOT for the technical mechanics of permission set assignment authority (use admin/permission-set-architecture). NOT for pure stakeholder requirements elicitation (use admin/requirements-gathering-for-sf). More trigger keywords: who approves a sandbox refresh, who signs off a data load, release update activation owner, delegated admin authority vs RACI, multi-org decision rights, escalation time-box.

日本語の概要は準備中です。原文の説明を表示しています。

I Ching (易經) expert covering hexagram interpretation, traditional wisdom, and consultation methods

日本語の概要は準備中です。原文の説明を表示しています。

User experience and interface design expert for wireframing, user research, and design systems

日本語の概要は準備中です。原文の説明を表示しています。

Consult the Eldar — audit a project's moflo + Claude Code setup for portable, high-leverage gaps and guide remediation. Default mode is read-only audit with severity-ranked findings; --fix presents an interactive triage menu and walks the user through each chosen fix (healer, missing CLAUDE.md, sparse guidance, hook/MCP wiring, empty memory namespaces, stack→guidance gaps). Use when starting in a new project, when Claude feels lost or inefficient, when guidance/CLAUDE.md is sparse, or as a periodic health check.

日本語の概要は準備中です。原文の説明を表示しています。

Strategic planning consultant that produces decision-complete work plans through Socratic interview, codebase exploration, Metis gap analysis, and optional Momus high-accuracy review. MUST USE when the task has 5+ steps, scope is ambiguous, multiple modules are involved, or the user asks for a plan. Triggers: plan this, create a work plan, interview me, start planning, prometheustic, plan mode, help me plan this, break this down.

日本語の概要は準備中です。原文の説明を表示しています。

ที่ปรึกษาภาษีไทย — ภ.ง.ด.90/91/50, ลดหย่อน, tax planning, VAT, ภาษีนิติบุคคล รองรับบุคคลธรรมดา + บริษัท

日本語の概要は準備中です。原文の説明を表示しています。

ที่ปรึกษาธุรกิจ SME + startup ทำ SWOT, Business Canvas, Porter 5 Forces, pitch deck, และ 3-year forecast

日本語の概要は準備中です。原文の説明を表示しています。

Use for Hono (web framework) development when Codex needs to consult Hono documentation or test Hono apps via the `hono` CLI. Trigger on requests about Hono CLI usage, searching/browsing Hono docs, or testing Hono routes without running a server.

日本語の概要は準備中です。原文の説明を表示しています。

Run internal compliance audits against major frameworks without hiring a consultant.

日本語の概要は準備中です。原文の説明を表示しています。

Your AI compliance officer. Guides startups and scale-ups through SOC 2, ISO 27001, GDPR, HIPAA, and PCI DSS — from zero to audit-ready. No consultants needed.

日本語の概要は準備中です。原文の説明を表示しています。