「setup」の検索結果

One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write `.absolute.config.json` (project, committed) and `~/.absolute/config.json` (user defaults + per-project overrides). Every other absolute-* command reads it instead of re-detecting; non-blocking — commands proceed without it and soft-recommend it. Triggers on "absolute init", "set up absolute", "initialize absolute", "configure absolute", "first-time setup", "remember my conventions for this repo".

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

Trade execution using price action setups, major trend reversal trading top and bottom, MTR failure continuation, strong bull and bear breakout trading, strong and weak channel trading strategies, trading range strategies, opening range swings, integration with gold.technical_setups for setup matching and execution planning

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

First-time setup for protein design tools. Use this skill when: (1) User is new and hasn't run any tools yet, (2) Commands fail with "file not found" or "modal: command not found", (3) Modal authentication errors occur, (4) User asks how to get started or set up the environment, (5) biomodals directory is missing or tools aren't working.

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

A/B Test Setup workflow skill. Use this skill when the user needs Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Email triage system that handles both one-time setup and recurring triage in a single skill. Auto-detects state: if no knowledge base exists at ${WORKSPACE}/Email/, runs an 8-section onboarding interview (grill-me discipline, one question at a time) to build a 7-file personalized KB, then offers to run triage immediately. If the KB already exists, skips setup and goes straight to triage — searches recent emails, classifies them via the user's taxonomy, researches new senders, generates TAKE IT/WORTH/PASS/FLAG recommendations, drafts replies (NEVER sends), delivers a report, and updates the KB. Use with 'update' argument to refresh preferences. Setup triggers: 'set up my inbox', 'configure inbox triage', 'set up my email system', 'configure email triage', 'build my email knowledge base', 'initialize email management'. Triage triggers: 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage'.

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

Discoverability shim for the Retail-Agentic-Commerce setup Codex skill. Use when the user asks to setup, install, start, launch, or run the project stack.

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

Obtain or reuse a Prisma Postgres database and connect an application. Use for "set up Prisma Postgres", "connect my app to Prisma Postgres", or Prisma Postgres setup in v0 and Vercel Marketplace. Hands Prisma ORM configuration to prisma-orm-setup; honors an explicit driver, alternative ORM, or database-only choice.

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

Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity"

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

Automatic init the first time Claude acts in an incident or alerts channel — one named like #inc-…, #incident-…, #sev0-…/#sev1-…, or whose recent messages are pages or alerts from PagerDuty, Opsgenie, incident.io, Datadog, Sentry or Grafana, or relayed by people (talk about being paged is not an alert) — that isn't already a team's oncall / monitoring channel. Run once per channel, on first contact (just invited, first @-mention, channel just created), before doing what was asked: load the oncall memory oncall setup wrote to shared workspace memory, pick the owning team's section, work out which monitoring / paging / code tools Claude can reach and which are missing, post one short zero-context message, note findings in this channel's memory, then hand off to `incident-investigate` if something was asked — or immediately, unasked, when the channel was plainly opened for a live outage. Works with no oncall memory (offers setup once). Also on "load the oncall setup here" / "init this incident".

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

Analytics and attribution setup — tracking plan, UTM conventions, dashboard design, and attribution model selection. Use when "analytics setup", "attribution", "tracking plan", "UTM", "marketing analytics", "dashboard setup", "measurement strategy", "how do I track", "which metrics", or any request to set up or improve marketing measurement and attribution.

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

First-run guided setup for a fresh gAIOS clone. Interviews the user (identity, role, priorities, voice, connections, team, pain, guardrails) and fills the templates — CLAUDE.md, context/, references/voice.md, connections.md — then introduces the WAT / wiki / workflows / experiments features. Trigger on "/setup", "set me up", "get started", "onboard me", or a fresh clone where CLAUDE.md still has {{placeholders}}.

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

Check Telegram bot configuration and guide setup if anything is missing.

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

Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment", "set up branches", or when a freshly cloned repo has no sibling worktrees.

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

Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.

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

Set up the local iOS dev/build toolchain for NowStack Mobile: Xcode, Simulator, CocoaPods, Watchman, mobile deps, and first `expo run:ios`. Use for `/ns setup-ios`, simulator preview, `expo run:ios` failures, or before local TestFlight builds. macOS only; signing is `/ns ios setup`.

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

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.

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

Run the NowStack Mobile setup checker as a strict read-only contract. Use for `/ns check`, configuration readiness, external account status, production preflight, or machine-readable setup evidence.

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

A 15-minute guided setup that teaches Cowork who you are, how you work, and what tools you use — so every result feels tailored instead of generic. Use when setting up Cowork for the first time, for personalizing your workspace preferences, during onboarding after your first session, when configuring your tools and context, or when the user says "set up cowork", "configure cowork", "why is cowork giving me generic results", "cowork setup", "personalize cowork", "make cowork know me", "cowork feels like chatgpt", or "how do I get better results from cowork".

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

Audits your Cowork setup across five categories, scores each one, and gives you a prioritized improvement plan. For reviewing how well you are using Cowork, when optimizing your workspace configuration, or during a quarterly productivity review. Use when the user says "health check", "am I using cowork right", "optimize my setup", "cowork audit", "what am I missing", "is my setup good", or "how do I get more out of cowork".

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

Use this skill when the user wants to update their project's CLAUDE.md or AGENTS.md, verify their Claude Code setup, or check for improvements to their project configuration. Triggers on requests like: "update my project docs", "verify my claude setup", "check my project configuration", "audit my .claude directory", "improve my CLAUDE.md", "is my setup correct", "/update-project", "/verify-project", or "/check".

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

Dependency checker and installer for agent-canvas, agent-eyes, and canvas-edit skills. Use BEFORE running any canvas skill for the first time, or when canvas skills fail with import/browser errors. Triggers on "setup agent canvas", "install canvas dependencies", "canvas not working", "playwright not found", or any setup/installation request for canvas skills.

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

Full project initialization wizard from ProjectConfig, including folders, packages, Git, and MCP setup. Use when setting up a new Unity project from scratch, creating the folder structure, or bootstrapping infrastructure. Triggers on requests like "set up a new project", "create folder structure", "initialize the project", or "/uw-cmd-setup-project". Reads ProjectConfig.yaml for all decisions.

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

Expert setup assistant for the Stably Playwright SDK. Use this skill when installing Stably SDK in a new project, migrating from @playwright/test, or configuring Stably reporter for CI/CD. Triggers on tasks like "setup stably", "install stably sdk", or "configure playwright with stably".

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

Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when user asks to "audit tooling", "recommend tools", "quality stack", "what tools am I missing", "setup eslint", "setup detekt", "add coverage", "add ruff", "configure CI quality pipeline", "scan project tools", "tooling audit", "android tooling", "android quality", "compose testing", "kmp testing", or "screenshot testing".

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