「decisions」の検索結果

Analyze NFT projects for investment decisions — evaluate fundamentals, identify red flags, assess risk, and provide buy/hold/avoid recommendations

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

Recall project knowledge, past decisions, failures, and preferences when they can help a coding task. Capture changed files before responding.

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

Turns a vague "what should we do about X" into a scored decision - explicit actions, an explicit unknown, an explicit prior, and one utility scale - then picks by maximum expected utility and checks the result for framing effects. Use when facing a choice between options under uncertainty, when a decision has stalled in circular debate, when someone asks "should we do A or B", or before writing any decision record, strategy memo, or roadmap commitment.

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

Save durable decisions, findings, plans, and implementation knowledge from the visible Kimi Code conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.

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

Save durable decisions, findings, plans, and implementation knowledge from the visible pi conversation into a new or existing NeatContext context. Use only when the user explicitly asks to preserve the current conversation as reusable context, or runs /neatcontext-save.

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

Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.

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

Perform a deep architectural analysis or security review requiring extended reasoning. Use for complex architecture decisions, security audits, or when standard analysis is not finding the root cause.

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

Review a written plan or design doc through a designer's lens before implementation - seven passes over information architecture, interaction states, emotional arc, AI-slop risk, design-system alignment, responsive and accessibility coverage, and unresolved decisions. Each dimension is rated 0-10 with an explicit statement of what would make it a 10, then the plan is edited to get there. Use when a plan has a UI surface and you want the design gaps closed before code is written. Not for auditing a live site.

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

Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"

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

Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Stops before extract; run that manually.

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

Run the speckit preparation phases end-to-end — specify, plan, critique, tasks — making all decisions autonomously. Stops before implementation.

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

Creates marketing analytics reports, KPI dashboards, ROI calculations, and performance summaries for SME marketing teams. Handles weekly/monthly reporting, campaign analysis, content performance reviews, and data-driven recommendations. Use when user asks about marketing metrics, reporting, KPIs, dashboards, ROI analysis, performance review, or data-driven marketing decisions.

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

Expert SwiftUI guidance for macOS apps — covers writing and reviewing code with runtime-level understanding of observation, concurrency, performance, and platform integration. Use when user asks to "build a SwiftUI view", "review my SwiftUI code", "fix observation issues", "bridge AppKit", "architect state management", "debug view updates", or works on any macOS SwiftUI project — building features, reviewing existing code, debugging view updates or performance, fixing concurrency issues, architecting state management, bridging AppKit, or making design decisions. Do NOT use for iOS/iPadOS-only SwiftUI, UIKit bridging, or basic Swift language questions. Focuses on non-obvious traps and deep patterns, not basics.

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

Pursue an agreed goal to a working outcome without waiting: decompose it, re-prioritise as evidence arrives, branch, gate, get an independent review (a different model or a fresh reviewer subagent — the writer never approves), merge, prune, and bank the operator's decisions in STATUS.md instead of blocking on them. Trigger on "get it done", "don't wait for me", "proceed autonomously", or when an epic or roadmap objective is handed over. Not a close-out: this work set is expected to grow.

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

Check proposed stack, data flows, cloud choices, and delivery controls against declared enterprise policies, compliance frameworks, and security controls. Trigger at R2/R3 risk classification, before locking architecture decisions, or when the operating profile names a governance pointer.

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

Architecture decisions, trade-off analysis, and ADR authoring. Trigger when a significant technical decision needs to be made, documented, and owned — not when an implementation detail needs a choice.

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

Verify that the current Git branch, upstream state, and dirty working tree match the user's intended task before staging, committing, pushing, or continuing work from another session. Use this to detect stale branch reuse, leftover dirty files from previous sessions, unrelated commits on the current branch, cases where work should be split into a new branch or worktree, and post-publish cleanup decisions after push, PR creation, or PR merge.

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

Use when reasoning about cash runway — burn shape, fundraise triggers, layoff-vs-cut-vs-grow decisions. Triggers on 'how long do we have', 'should we raise', 'cut or grow'.

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

Use when choosing between alternatives with trade-offs — X-or-Y decisions or a weighted decision matrix / gewichtete Entscheidungsmatrix ('score my options'); ADR via `adr-create`.

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

Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.

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

Grounded brand decisions from a curated corpus — archetype, voice, naming, colour psychology, logo-style fit, messaging frameworks, archetype→type mapping. Use to ground brand strategy and identity.

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

All agents have equal voice; decisions made by majority vote.

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

Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.

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

Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the final, optional layer. Prioritize resilience and universal access over cutting-edge features.

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