「state」の検索結果

Designs session and task state for coding-agent runtimes: resume, checkpoints, compaction, cancellation, background and scheduled runs. Use when persisting agent work.

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

Designing workflows and state machines. Use when state transition design, invalid transition detection, Saga patterns, or approval flow design is needed.

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

Author learning targets for a competency across developmental bands with precise, observable progression language. Use when writing 'I can' statements for competency-based programmes.

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

Convert a vague mini-program idea, feature request, or partially documented product into an evidence-calibrated product specification with target users, core problem, version-one scope, main and exception flows, page responsibilities, state matrices, and testable acceptance criteria. Use when users ask to define an MVP, clarify requirements, organize product flows, specify page behavior, resolve ambiguous product states, or prepare a stable handoff before architecture or implementation. Separates facts, user decisions, assumptions, unknowns, and future ideas; never invents product logic merely to complete a screen or technical plan.

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

Diagnose and fix mini-program failures through reproducible, evidence-driven root-cause analysis across source, state, asynchronous timing, caches, mock data, build versions, platform behavior, devices, cloud calls, and external services. Use when users report white screens, crashes, stale or jumping values, missing data, intermittent behavior, permission failures, performance stalls, device-only defects, API or cloud-function errors, source-versus-build mismatches, or regressions whose cause is not yet established. Freezes the observation environment, ranks competing hypotheses, runs discriminating checks, creates a failing regression test before repair, covers analogous states, and never hides a known failure with longer waits, swallowed errors, forced success, or cosmetic patches.

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

Generate Mermaid diagrams (.mmd) and export to PNG/SVG/PDF using mmdc CLI or Kroki API. USE THIS SKILL when user mentions diagram, flowchart, sequence diagram, class diagram, ER diagram, state machine, architecture, visualize, git graph, 画图, 架构图, 流程图, 时序图, 类图, ER图, 甘特图, 状态机. PROACTIVELY USE when explaining ANY system with 3+ components, API flows, authentication sequences, class hierarchies, database schemas, or state machines. Supports 17+ diagram types with fully automatic layout.

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

Reviews axum web framework code for routing patterns, extractor usage, middleware, state management, and error handling. Use when reviewing Rust code that uses axum, tower, or hyper for HTTP services. Covers axum 0.7+ patterns including State, Path, Query, Json extractors.

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

Reviews SwiftUI code for view composition, state management, performance, and accessibility. Use when reviewing .swift files containing SwiftUI views, property wrappers (@State, @Binding, @Observable), or UI code.

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

Implements stateful agent graphs using LangGraph. Use when building graphs, adding nodes/edges, defining state schemas, implementing checkpointing, handling interrupts, or creating multi-agent systems with LangGraph.

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

Reviews LangGraph code for bugs, anti-patterns, and improvements. Use when reviewing code that uses StateGraph, nodes, edges, checkpointing, or other LangGraph features. Catches common mistakes in state management, graph structure, and async patterns.

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

Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).

Tax optimization strategies analyzer. Identifies high-impact tax savings across tax-loss harvesting, tax-advantaged accounts (401k, IRA, HSA), Roth conversions, backdoor and mega backdoor Roth, charitable giving, business deductions, capital gains harvesting, state tax minimization, and estate tax planning. Produces FINANCE-TAXES.md with prioritized strategies and estimated annual tax savings.

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

Use when identifying cybersecurity-specific regulations and incident reporting obligations. Covers NIS2, DORA, SEC cyber disclosure rules, CISA incident reporting, state breach notification laws, cyber insurance requirements, and security certification frameworks. USE FOR: NIS2, DORA, SEC cybersecurity rules, CISA, breach notification, incident reporting, SOC 2, ISO 27001, cyber insurance, FedRAMP, StateRAMP, CMMC, data breach response DO NOT USE FOR: implementing security controls (use security skills), security testing tools (use security/security-testing), general data privacy (use privacy-data-protection)

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

Drafts U.S. commercial real estate owner-developer agreements covering scope, entitlements, schedule, pricing (fixed, GMP, cost-plus), change orders, payment and retainage, insurance, indemnity, IP, confidentiality, termination, and disputes. Use when user mentions "development agreement", "owner-developer agreement", "project development contract", "real estate development", "GMP", "cost-plus", "milestones", or "change orders".

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

Regulatory compliance guidelines for life insurance policy administration transactions. Use when processing address changes (state-change impacts), beneficiary changes (community property, ERISA, minors), or any transaction that may trigger compliance review. Covers NAIC model regulations, state-specific rules, OFAC screening, and suitability requirements.

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

Manage Allstate insurance with Drivewise and Milewise programs.

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

Use when asked about UX patterns, interaction best practices, form design, navigation patterns, or loading states. Examples: "best practice for form validation", "navigation pattern for dashboard", "loading state UX"

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

Write UX copy for a feature, flow, or component — buttons, errors, empty states, tooltips. Use when asked to "write the copy for this flow", "word this error message", or "write empty state copy".

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

Implement and audit SaaS billing systems, subscription state machines, secure webhooks, and local database synchronization / Implementasi dan audit sistem billing SaaS, state machine langganan, webhook aman, dan sinkronisasi database lokal.

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

Orchestrates Single-Page Application (SPA) architecture, integrating frontend state management with API-driven backends / Mengorkestrasi arsitektur Single-Page Application (SPA), mengintegrasikan state management frontend dengan backend berbasis API.

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

Expert guide for mathematical formal verification, SMT solver constraints (Z3, Dafny, TLA+), invariant theorem proving for FinTech billing state machines, RBAC/ABAC authorization, and zero-violation architecture / Panduan ahli verifikasi formal matematis, SMT solver (Z3, Dafny, TLA+), pembuktian invarian state machine billing FinTech, otorisasi RBAC/ABAC, dan arsitektur zero-violation.

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

Elite frontend design taste for building, reviewing, and polishing web interfaces. Use whenever the user wants to design, redesign, shape, critique, audit, polish, or improve any UI (landing pages, portfolios, dashboards, product UI, components, forms, onboarding, empty states) or asks to make something look better / premium / modern, fix the styling, add or fix animations, or make a design feel less generic ("AI slop"). Covers typography, color, spacing, layout, visual hierarchy, motion, micro-interactions, component states, accessibility, responsive behavior, UX copy, and anti-pattern detection.

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

Spinners, skeletons and staggered reveals that manage wait times. Use when designing loading states, async data or the feel of a slow interface.

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

Rest, hover, active, focus, disabled and loading states, derived from the base colour. Use when designing buttons, links, inputs or any clickable component.

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