「state」の検索結果

Carefully curated, modern minimal style with elegant serif typography and understated, sophisticated palettes.

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

Premium pre-launch waitlist page template — dark charcoal canvas with subtle vignette, drifting portrait video-thumbnail cards, fade-up cascades, glass nav, live-updating join counter, single email form with success/error states. Built for creative-tool / AI / niche-SaaS invite-only launches with hushed exclusive tone, not loud growth-marketing.

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

SolidJS reactivity + UI state patterns for Openrind Desktop

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

Skill for direct usage of Reka UI v2 headless primitives (the foundation of shadcn-vue). Use when you need to compose custom components beyond those available in shadcn-vue, understand asChild/as, controlled state, portals, or migrate from Radix Vue.

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

Generate and safely advance the SDD Composy task projection from approved PRD, stories, and TechSpec: import contracts, list/next/show, and guarded start/block/transition/verify. Use when work must be decomposed or a task's state inspected or moved — 'quebrar a spec em tarefas', 'listar as tarefas', 'qual a próxima task', 'mark TASK-003 blocked'. Do NOT use to implement a task (sdd- execute), reconcile Markdown and JSON (sdd-sync), or for a status overview (sdd- status).

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

Reconcile SDD Composy task Markdown and the JSON projection: read-only inspect and plan, then apply only with an explicit authority and the CONFIRM-SDD-SYNC token. Use when task contracts and operational state diverged — 'sincronizar as tarefas', 'o JSON das tasks está desatualizado', 'markdown and json disagree'. Do NOT use to list or advance tasks (sdd-tasks), for a status overview (sdd-status), or to simulate approval.

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

Read-only consolidated snapshot of an SDD Composy workspace: lifecycle stage, task contracts, trace integrity, loops, fleets, and the next action, without changing any file. Use for 'em que pé está o SDD', 'status do fluxo', 'qual a próxima ação', 'where are we in the workflow'. Do NOT use for git, CI, infrastructure, or other plugins' status, or to change state.

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

Implement exactly one SDD Composy task in the ready state with dependency preflight, TDD RED evidence, allowed paths, real verification commands, and the guarded transition to qa_required. Use when a ready task should be executed — 'executar a TASK-003', 'implementar a próxima tarefa', 'run task 4'. Do NOT use for changes without an approved task (sdd-quick), for autonomous multi-stage correction (sdd-loop), or for QA, review, or verification.

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

Initialize or inspect project-local PWDEV QA context without overwriting existing state or installing tools.

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

Define auditable QA metrics with explicit numerators, denominators, populations, windows, and treatment of every result state.

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

Record a reproducible defect, independent triage, immutable attempts, and evidence-backed retest state.

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

Use when the user asks which PRDs exist — 'listar PRDs', 'quais PRDs temos', 'list PRDs' — with status, version, roadmap state and GitHub Project. Read-only.

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

Review requirements, coverage, results, evidence, and findings without changing the product or recorded state.

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

Use when the user wants a UI-only action plan — components, pages, composables/hooks, state, forms and their E2E coverage — 'plano de frontend para a tela X', 'plan the settings page'. Writes .planning/feat/features/{slug}/plan.md with E2E scenarios and playwright-cli checks. Do NOT use for API/database work (feat-backend), full features (feat-feature), writing code (feat-exec) or UI review (feat-review).

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

Use when the user asks for the state of pwdev-feat plans — 'status do feat', 'quais planos estão pendentes', 'show feature status' — listing pending, complete, with-caveats, failed and resumable plans plus codebase-context health. Read-only. Do NOT use to execute (feat-exec) or query the audit trail (feat-audit).

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

Escreve microcopy de interface — mensagens de erro, estados vazios, tooltips, rótulos de botão, onboarding e notificações. Use quando o usuário disser "UX writing", "microcopy", "mensagem de erro", "empty state", "texto do botão", "texto da interface", "onboarding do sistema".

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

Add search to a GNOME app — header-bar search button toggling a GtkSearchBar with SearchEntry, live filtering, Ctrl+F, and empty "no results" state. Use when adding search or filtering to lists or content views.

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

Build reusable, composable, and maintainable React/Vue/Angular components following established design patterns like compound components, render props, custom hooks, and HOCs. Use when creating component libraries, implementing component composition, building reusable UI elements, designing prop APIs, managing component state patterns, implementing controlled vs uncontrolled components, creating compound components, using render props or children as functions, building custom hooks, or establishing component architecture standards.

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

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.

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

Restore working context saved earlier by /context-save. Loads the most recent saved state (across all branches by default) so you can pick up where you left off — even across Conductor workspace handoffs. Use when asked to "resume", "restore context", "where was I", or "pick up where I left off". Pair with /context-save. Formerly /checkpoint resume — renamed because Claude Code treats /checkpoint as a native rewind alias in current environments. (gstack)

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

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

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

Guides concurrency and async decisions in Rust. Use when encountering Send/Sync errors (E0277), choosing between threads vs async, designing shared state, or debugging deadlocks.

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

Babysit a GitHub pull request during a user-approved monitoring window by polling review comments, CI checks/workflow runs, and mergeability state. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and report fresh review feedback. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

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

Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.

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