protosphinx/sphinxstack - 9ページ

design-a-remote-recording-workflow

Design a remote recording workflow with verified participants, consent, local-quality capture, monitoring, backup, transfer, and recovery. Use when contributors record from different locations over a network.

原文の言語: 英語

design-a-research-method

Design a research method that aligns the question, evidence, sampling, measurement, analysis, feasibility, and limitations. Use when turning a research question into an empirical or analytical study.

原文の言語: 英語

design-a-responsive-layout

Design a resilient layout across content sizes, viewports, input modes, and zoom. Use when an interface must preserve hierarchy, reading, controls, and tasks beyond a few fixed mockup widths.

原文の言語: 英語

design-a-revenue-recognition-checklist

Design a revenue-recognition checklist that connects contract facts, accounting policy, calculations, approvals, and ledger evidence. Use when reviewing new, modified, unusual, or recurring customer arrangements before recording revenue.

原文の言語: 英語

design-a-schema-evolution-process

Design schema evolution with compatibility rules, ownership, versioning, staged rollout, backfill, validation, rollback, and retirement. Use when stored or exchanged data changes across independently deployed producers and consumers.

原文の言語: 英語

design-a-search-interface

Design a search interface around user intent, query construction, result comprehension, and recovery. Use when people must find items across a substantial or changing collection.

原文の言語: 英語

design-a-service-health-check

Design service health checks that distinguish process life, traffic readiness, dependency degradation, and user outcome. Use when orchestrators and operators need safe automated decisions.

原文の言語: 英語

design-a-service-transition

Design a service transition from project or incumbent operation into accountable support, monitoring, continuity, knowledge, access, supplier, and improvement ownership. Use when a new or changed service must enter steady operation safely.

原文の言語: 英語

design-a-session-timeout-experience

Design a session-timeout experience that balances security with warning, accessible renewal, work preservation, reauthentication, and multi-tab consistency. Use when web sessions expire because of inactivity, absolute lifetime, risk, or policy.

原文の言語: 英語

design-a-settings-page

Design settings with clear scope, defaults, dependencies, permissions, save behavior, reversibility, and recovery. Use when users need to inspect or change persistent product, account, workspace, privacy, or notification preferences.

原文の言語: 英語

design-a-telemetry-pipeline

Design a production telemetry pipeline with explicit coverage, loss, overload, governance, tenancy, and recovery guarantees. Use when logs, metrics, traces, or events must cross shared collection and storage infrastructure reliably.

原文の言語: 英語

design-a-user-flow

Map a user task from entry to outcome across choices, system states, errors, permissions, and recovery, then turn it into an implementation-ready flow. Use when a feature feels confusing, screens are being designed without a complete journey, or a team needs…

原文の言語: 英語

design-a-video-caption-workflow

Design a caption workflow for accurate text, timing, speaker identity, sound cues, localization, review, and delivery. Use when video needs accessible captions at repeatable production quality.

原文の言語: 英語

design-a-web-access-control-review

Design a web access control review across identities, sessions, roles, objects, actions, tenants, APIs, caches, jobs, exports, and revocation. Use when authorization coverage must be proven across a web product.

原文の言語: 英語

design-a-web-performance-budget

Design a web performance budget tied to user journeys, device and network conditions, Core Web Vitals, resource limits, and release enforcement. Use when preventing performance regressions across pages, components, and third-party code.

原文の言語: 英語

design-a-web-rate-limit-strategy

Design web rate limits from abuse threats, resource cost, user identity, endpoint semantics, fairness, client guidance, and degraded operation. Use when protecting APIs or web actions without locking out legitimate users.

原文の言語: 英語

design-a-webhook-retry-policy

Design a webhook retry policy with durable delivery identity, bounded backoff, receiver protection, observability, replay, and terminal handling. Use when outbound events must survive timeouts, failures, duplicates, and delayed recovery.

原文の言語: 英語

design-a-websocket-reconnection-strategy

Design WebSocket reconnection with state identity, backoff, resume tokens, replay, deduplication, ordering, authentication, and user feedback. Use when transient disconnects must not lose or duplicate live state.

原文の言語: 英語

design-an-academic-survey

Design an academic survey with construct definitions, sampling, valid questions, accessible delivery, privacy, pilot evidence, and an analysis plan. Use when self-reported data is appropriate to a research question.

原文の言語: 英語

design-an-access-review

Design a repeatable review of user, service, and privileged access. Use when entitlement sprawl, role changes, audit needs, or sensitive systems require owners to verify continuing need and remove excess access.

原文の言語: 英語

design-an-accessible-command-palette

Design an accessible command palette with discoverable entry, search, keyboard and screen-reader behavior, context, confirmation, undo, and alternatives. Use when many actions need fast access without replacing clear navigation.

原文の言語: 英語

design-an-accessible-resume

Design an accessible resume with semantic structure, readable typography, logical order, meaningful links, and tested DOCX and PDF output. Use when a resume must work for screen readers, magnification, printing, and applicant systems.

原文の言語: 英語

design-an-api-contract

Define an API that consumers can integrate with and providers can change safely. Specify resources, errors, compatibility, retries, and contract tests before implementation. Use when multiple systems or teams need a durable interface rather than an informal…

原文の言語: 英語

design-an-approval-workflow

Design an approval workflow with decision scope, evidence, authority, conflicts, sequence, service levels, exceptions, audit, and revocation. Use when an action requires accountable permission before it proceeds.

原文の言語: 英語

design-an-assessment-rubric

Design an assessment rubric with outcome-aligned criteria, observable performance levels, fair weighting, accessibility, calibration, and feedback use. Use when work must be evaluated consistently and transparently.

原文の言語: 英語

design-an-email-nurture-sequence

Design a consent-aware email sequence around useful recipient progress and branching. Use when onboarding, education, evaluation, renewal, event, or re-engagement messages need coordinated timing, content, evidence, and measurement.

原文の言語: 英語

design-an-empty-state

Design an accurate and useful interface when expected content is absent. Use when first use, no results, completed work, filters, permissions, loading failure, or deleted content could otherwise look identical.

原文の言語: 英語

design-an-error-state

Design an accessible product error state that explains what happened, protects user work, offers an appropriate recovery, and produces support evidence. Use when a form, page, transaction, upload, integration, or background task can fail and the current…

原文の言語: 英語

design-an-escalation-path

Design an escalation path with triggers, levels, responders, authority, response times, communication, alternatives, and closure. Use when an issue can outgrow the person or team handling it.

原文の言語: 英語

design-an-event-feedback-survey

Design a focused event survey that measures experience and intended outcomes without coercion or noise. Use when organizers need participant evidence for improvement and accountability.

原文の言語: 英語

design-an-expense-policy

Design an expense policy that balances stewardship, tax and audit needs, equitable access, employee safety, and timely reimbursement. Use when establishing or revising travel, purchasing, card, receipt, approval, and exception rules.

原文の言語: 英語

design-an-on-call-rotation

Design a sustainable incident-response rotation with service scope, authority, readiness, compensation, escalation, and evidence. Use when production support must be reliable without unsafe hidden labor.

原文の言語: 英語

design-an-onboarding-flow

Design onboarding that reaches a meaningful first outcome with clear choice, progressive setup, accessible guidance, and recoverable state. Use when new users, members, or administrators must understand and configure a product.

原文の言語: 英語

design-an-operating-rhythm

Align recurring forums, decisions, planning horizons, signals, and follow-through into a coherent operating cadence. Use when meetings multiply but ownership and execution remain unclear.

原文の言語: 英語

design-application-error-handling

Design application error handling that classifies failures, preserves useful causes, protects users and data, supports recovery, and produces safe observability. Use when defining service or library failure behavior.

原文の言語: 英語

design-basics

Teach visual design by fixing something the person is making. Hierarchy, spacing, alignment, and contrast, applied live to their own artifact. Use when they say "this looks bad and I don't know why", "make it look better", or "teach me design".

原文の言語: 英語

design-critique

Critique something the person designed, then fix it with them. Names what works and what fails, and applies the top three fixes. Use when they say "is this good", "review my site", "why does this look off", or want feedback before sharing.

原文の言語: 英語

design-customer-onboarding

Design a customer onboarding plan that reaches a measurable first-value outcome with clear responsibilities, recovery paths, and instrumentation. Use when creating or repairing a product, service, migration, or implementation onboarding flow.

原文の言語: 英語

design-for-keyboard-navigation

Design predictable keyboard operation, focus, and recovery across an interface. Use when custom controls, overlays, dynamic content, shortcuts, or complex widgets must work without pointer input.

原文の言語: 英語

design-mobile-navigation

Design mobile navigation around priority, context, touch, and constrained space. Use when a product or site must preserve findability and task progress without copying desktop navigation into a hidden drawer.

原文の言語: 英語