protosphinx/sphinxstack - 20페이지

recover-from-a-work-mistake

Contain, disclose, repair, and learn from a workplace mistake without hiding facts or overclaiming resolution. Use when an error has affected people, data, money, service, or trust.

원문 언어: 영어

recruit-research-participants

Recruit research participants through an approved, fair, privacy-preserving process with transparent burden, compensation, and consent boundaries. Use when enrolling people into an ethics-approved study.

원문 언어: 영어

redesign-a-clinical-workflow-interface

Redesign a clinical workflow interface through observed care practice, hazard analysis, human-factors validation, controlled migration, and rehearsed downtime recovery. Use when interface changes can affect diagnosis, medication, treatment, documentation, or…

원문 언어: 영어

redesign-a-critical-checkout-flow

Redesign a critical checkout while preserving financial, inventory, accessibility, legal, fraud, and customer-recovery invariants through controlled migration. Use when a high-volume purchase flow cannot tolerate duplicate orders, lost payments, or…

원문 언어: 영어

redesign-a-global-billing-process

Redesign global billing through explicit financial state, contract and tax controls, migration reconciliation, customer protection, and reversible cutover. Use when replacing or consolidating billing across products, entities, currencies, regions, or business…

원문 언어: 영어

redesign-a-high-risk-account-recovery-flow

Redesign high-risk account recovery through threat modeling, proportionate identity proof, anti-coercion controls, accessible alternatives, session and asset protection, and monitored rollout. Use when recovering access could expose money, health, identity,…

원문 언어: 영어

redesign-a-multitenant-authorization-system

Redesign multitenant authorization through identity, tenant and resource boundaries, policy semantics, migration, revocation, audit, abuse testing, rollback, and verified isolation. Use when existing access rules are inconsistent, unsafe, or unable to support…

원문 언어: 영어

redesign-a-safety-critical-control-interface

Redesign a safety-critical control interface through task and hazard analysis, state visibility, authority, alarm, confirmation, accessibility, degraded operation, validation, rollout, and recovery. Use when interface error can harm people, environment,…

원문 언어: 영어

redesign-an-operational-dashboard

Redesign an operational dashboard around decisions, trusted metrics, state, thresholds, uncertainty, accessibility, drill-down, and incident use. Use when dense monitoring views fail to support timely action.

원문 언어: 영어

reduce-observability-cost

Reduce observability cost through measured signal value, cardinality, volume, retention, tiering, and query efficiency. Use when telemetry spend is rising without proportional operational benefit.

원문 언어: 영어

refactor-without-changing-behavior

Improve an existing codebase's structure while preserving its observable behavior, compatibility, and operational characteristics. Use when someone asks to refactor, simplify, extract, reorganize, or reduce duplication without changing what users or callers…

원문 언어: 영어

references-list

Build the references document employers expect. Who to ask, permission obtained, one clean page. Use when they say "I need references", an application asks for them, or they are about to list someone without asking first.

원문 언어: 영어

remove-dead-code

Produce a removal report and delete unused code, configuration, flags, assets, or dependencies while preserving observable behavior and recovery evidence. Use when maintenance work identifies code believed to be unreachable or obsolete.

원문 언어: 영어

reproduce-a-bug

Build a minimal, repeatable reproduction of a software defect while controlling environment, inputs, and state. Use when a bug report is inconsistent, complex, or not yet proven outside the original system.

원문 언어: 영어

reproduce-a-cli-error

Reproduce a CLI error with exact arguments, input, environment, version, exit status, streams, and minimal conditions. Use when a command fails inconsistently or only for another user or system.

원문 언어: 영어

reproduce-a-research-result

Reproduce a research result by reconstructing its data, code, environment, decisions, and reported outputs with a transparent discrepancy record. Use when checking computational or analytical reproducibility.

원문 언어: 영어

request-an-academic-reference

Prepare a respectful academic-reference request with enough evidence, context, and time for an informed response. Use when asking an instructor, adviser, or research supervisor for a recommendation.

원문 언어: 영어

request-an-informational-interview

Ask for a bounded career conversation with specific context and an easy way to decline. Use when someone wants to learn from another person's experience without disguising a job or referral request.

원문 언어: 영어

research-a-company

Build a dated, source-backed company and role brief for an application, interview, networking conversation, or offer decision. Use when someone asks what to know about an employer, wants company research before an interview, or needs to assess a role without…

원문 언어: 영어

research-a-sales-account

Build a dated, source-backed brief for one prospective customer account without inventing personalization. Use when preparing outreach, discovery, account planning, or qualification that depends on current organizational context.

원문 언어: 영어

research-an-interviewer

Research an interviewer from relevant public professional sources without inferring private traits or manipulating rapport. Use when preparing respectful role-relevant questions.

원문 언어: 영어

research-compensation

Research compensation using comparable scope, location, level, currency, and total-reward evidence with transparent uncertainty. Use when setting expectations, evaluating an offer, or preparing a negotiation.

원문 언어: 영어

research-paper-workshop

Coach a research paper the student writes themselves. Question, sources, outline, and argument feedback; drafts annotated, never written. Use when they say "help me with my paper", "I have an essay due", or "is my argument any good".

원문 언어: 영어

resolve-a-merge-conflict

Resolve a merge conflict by reconstructing both changes, choosing the intended combined behavior, and testing the integrated result. Use when Git cannot combine overlapping edits automatically.

원문 언어: 영어

resolve-conflicting-sources

Diagnose why credible sources disagree and determine what can be concluded without forcing false consensus. Use when research returns incompatible facts, estimates, or recommendations.

원문 언어: 영어

respond-to-a-business-cash-crisis

Respond to an acute business cash crisis through verified liquidity, lawful payment priorities, controlled actions, communications, and recovery monitoring. Use when payroll, tax, critical suppliers, debt, or minimum cash may fail soon.

원문 언어: 영어

respond-to-a-client-side-data-leak

Respond to a client-side data leak by protecting users, preserving browser and third-party evidence, tracing exposed fields and recipients, containing collection, and verifying durable remediation. Use when scripts, tags, URLs, storage, logs, or browser…

원문 언어: 영어

respond-to-a-container-orchestration-control-plane-compromise

Respond to a container orchestration control-plane compromise through independent containment, workload and identity reconstruction, clean-cluster recovery, data protection, trust replacement, and verified return. Use when cluster administration, scheduling,…

원문 언어: 영어

respond-to-a-critical-open-source-maintainer-compromise

Respond to a critical open-source maintainer compromise through human protection, independent project containment, source and release reconstruction, ecosystem notification, governance recovery, and verified trust replacement. Use when a maintainer identity,…

원문 언어: 영어

respond-to-a-data-poisoning-incident

Respond to suspected data poisoning by containing unsafe inputs and decisions, preserving provenance, scoping affected datasets and models, recovering from trusted versions, and verifying recurrence controls. Use when malicious or unauthorized data changes…

원문 언어: 영어

respond-to-a-data-subject-request

Coordinate a verified, scoped, and privacy-safe response to an individual's data rights request. Use when access, correction, deletion, restriction, objection, or portability work crosses systems or processors.

원문 언어: 영어

respond-to-a-failed-database-migration

Respond to a failed production database migration through write protection, evidence preservation, schema and data reconciliation, recovery choice, and controlled restart. Use when a migration leaves database state partial, blocked, or uncertain.

원문 언어: 영어

respond-to-a-frontend-supply-chain-incident

Respond to a compromised frontend dependency, build tool, registry, tag, or hosted script through scoped containment and trusted recovery. Use when untrusted code may have executed in users' browsers or release assets.

원문 언어: 영어

respond-to-a-hiring-process-data-breach

Respond to a hiring-process data breach through candidate protection, evidence preservation, identity and vendor containment, data-scope reconstruction, notification, remediation, and verified reform. Use when applications, interviews, assessments,…

원문 언어: 영어

respond-to-a-job-offer-deadline

Respond to a job-offer deadline by verifying terms, prioritizing open questions, requesting bounded time, and recording accept, decline, or negotiate decisions. Use when an offer expires before diligence is complete.

원문 언어: 영어

respond-to-a-job-rejection

Respond to a job rejection with professional closure, optional bounded feedback, record updates, and a useful search review. Use when an employer ends a candidacy at any stage.

원문 언어: 영어

respond-to-a-live-broadcast-failure

Respond to a live broadcast failure through audience safety, scoped diagnosis, alternate transmission, clear communication, and verified recovery. Use when a real-time program loses signal, content, control, accessibility, or distribution.

원문 언어: 영어

respond-to-a-live-broadcast-integrity-crisis

Respond to a live broadcast integrity crisis with human protection, independent preservation, signal reconstruction, editorial containment, audience correction, clean recovery, and accountability. Use when a live program may be fabricated, hijacked,…

원문 언어: 영어

respond-to-a-major-vendor-failure

Respond to a major vendor failure through safety and customer continuity, evidence and contract control, alternate-service activation, financial and data reconciliation, recovery, and exit. Use when a critical supplier suffers outage, compromise, insolvency,…

원문 언어: 영어

respond-to-a-media-rights-dispute

Respond to a media rights dispute by preserving claims and licenses, mapping actual uses, containing unsupported distribution, and documenting resolution and remediation. Use when ownership, permission, attribution, likeness, music, footage, image, or…

원문 언어: 영어