「state」の検索結果

Drafts an architecture or design decision record (ADR) from the discussion notes, design review minutes, chat threads and diagram descriptions the user provides: context, decision drivers, options considered with arguments as stated, the decision as the group worded it, consequences and a review date, with every factual claim tagged evidenced, asserted or UNKNOWN so unsupported claims are marked for the author to substantiate. Use when the user asks to "write an ADR", "document the architecture decision", "record why we chose this design", "turn these design review notes into a decision record" or "draft the design decision log entry". Do not use for a business or governance decision with no technical design, use decision-memo-builder instead; for the change ticket that implements the decision, use change-request-pack. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT board paper skeleton from the sponsor's inputs: purpose, recommendation as the sponsor states it, options including do nothing, risks, financials exactly as provided, authority to decide and the decision sought, with every claim tagged evidenced, asserted or UNKNOWN so the sponsor sees what still needs support. Use when the user asks to "draft a board paper", "structure the committee paper", "prepare the decision paper for the investment committee", "skeleton the board memo" or "what goes in the paper for the audit committee". Do not use for a pre-read or briefing pack with no resolution sought, use executive-briefing-pack instead; to record a decision already taken in a discussion, use decision-memo-builder. Drafts for human review; never approves, authorises or signs off.

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

Assembles a DRAFT capital expenditure request pack from the requester's inputs: business need, options including do nothing, costs exactly as provided, benefits as stated, risks, assumptions, budget status and the approvals route read from the organisation's own delegation of authority, with UNKNOWN for every missing figure, date or name. Use when the user asks to "prepare a capex request", "draft the business case for this equipment", "fill in the capital request form", "structure this investment proposal" or "what approvals does this spend need". Do not use for a board or committee decision paper, use board-paper-skeleton instead; for an IT change approval, use change-request-pack; to pressure-test a finished business case, use cfo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Work with SuperCollider projects as files - the shape of a .scd piece, how to read and write one with sc_project, how to send the file that is on disk into the live session with sc_load, what state belongs in the session and what belongs in the file, and how to package a piece the SuperCollider way (a folder with its .scd, its SynthDefs, and a Quark-style layout) instead of inventing a format.

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

Recall past work across Claude Code and Codex sessions. Finds decisions, research, fixes, and conversations by intent; with only a project and no question, orients on that project's recent state.

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

Strategic session-end preservation. Captures decisions, discoveries, and state that the automatic hooks miss.

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

Query and mutate Linear issues, projects, cycles, teams, workflow states, and comments via its GraphQL API. Use when the user wants to read or change Linear data programmatically — without the MCP server, and without hand-navigating the Linear UI.

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

FastAPI service setup: app/main.py, API routers, pydantic-settings, lifespan/app.state services, middleware, health checks, pytest/TestClient, Uvicorn, Gunicorn/uvicorn-worker, Docker/Compose. Use for scaffolding or modernizing Python API services; skip for Flask/Django-only, frontend-only, non-Python APIs, or Supabase-specific work.

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

Use when reviewing, debugging, or improving TBQ3/TB language code for trading correctness, Bar strategy behavior, order direction, position state, sizing, costs, backtest realism, event timing, multi-symbol logic, or function documentation consistency.

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

- Corporate due-diligence workflow — resolve a brand or website to its registered legal entity, map group structure and beneficial ownership, profile officers and directors, enumerate the digital estate, and screen litigation, insolvency,… Use when asked to check out, vet or research a company, verify a supplier or counterparty before signing or paying, or assess whether a business is real

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

- Research companies, directors, shareholders and ultimate beneficial ownership in official corporate registries, filings and offshore datasets — OpenCorporates, UK Companies House and the PSC register, SEC EDGAR, US Secretary of State registries, EU business registers, GLEIF LEI… Use when asked who owns or controls a company, to find a person's other directorships, or to unpick a group structure

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

Delegate work over a shared task chat: a task is assigned by a short code phrase, and the assignee's agent expands it into a full seed and starts immediately, with state tracking so no delegated task dies silently. Triggers: "/task", "task <ID>", "my delegated tasks", "delegate <task> to <person>".

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

Pick up and continue a serialized build-in-public book: read the current state (which days are written in which languages, what is uncommitted, where the gaps are), then keep writing through the established pipeline. Triggers: "/journey", "the book", "continue the journey".

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

Run the vault data-safety runbook: 3-2-1 backup, the never-deleted originals archive, the schedulers that keep it running, and the restore or new-machine migration procedure. Verifies by reading state rather than trusting exit codes. Triggers: "make a backup", "verify the backup", "the backup looks broken", "restore the vault".

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

Keep serialized build-in-public content continuous: read one canon file of season, arcs, beats and loops and say which narrative beat to advance next, so episodes chain into a series. Pairs with the episode adapter, which does the writing. Triggers: "/reality-show", "season state", "what arcs are open".

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

Reboot a fleet node safely by one protocol: pre-flight (save state, finish syncing, warn peers, verify autostart is armed), then a full restart rather than a fast-startup hybrid, then a post-reboot check through the crash-recovery skill. Triggers: "/reboot", "restart this machine".

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

Drive the current task to a verified result instead of stopping at a plausible report. Use when the user says /continue, keep going, not done yet, push further, or is unhappy with the result. Rebuilds requirements from the conversation, re-checks real state, fixes root causes, verifies from the consumer side, offloads side quests.

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

Recover a session after a hard crash (app died, machine rebooted, context lost mid-work): replay the turn-state ledger for the last requests, files and decisions, run a green/red health ping over the system map, file sync and MCP connectors, then rebuild the previous session history for pickup. Triggers: "/1", "resume after crash", "wake".

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

Open the alpha review screen to mark judge keepers as gold or miss, read per-miner precision, and print the eval state. Use when tuning a miner's accuracy. Thin launcher over the existing harvest engine and local review server. Triggers: "/alpha-review", "alpha screen", "open the review screen".

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

Implement Feature-First architecture with Riverpod state management and Flutter Hooks in Flutter applications

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

Map repository structure, likely tests, git state, and write scope before edits. Use when asked for repo mapping, blast radius, file inventory, or change planning.

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

Use when designing interface states, feedback, hover/focus/press, gestures, direct manipulation, navigation transitions, loading/error/empty behavior, or deciding where interaction should carry the design concept.

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

Use when a website needs rendered screenshot review, Playwright visual regression, multi-viewport checks, horizontal overflow detection, console-error checks, focus/state inspection, or a repeatable visual QA evidence set.

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

Use when turning an art direction into reusable design tokens, typography, spacing, layout, surface, component, state, motion, responsive, or content rules before or during implementation.

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