mcorbett51090/RavenClaude - 2페이지

map-memory-surface

Name the storage surface a write actually lands on — who holds the bytes, who executes the write, and what trust model comes with it. Reach for this before writing any memory design down.

원문 언어: 영어

memory-poisoning-review

Audit an agent's durable memory for poisoning risk and harden it against OWASP ASI06 — enumerate write paths reachable from untrusted input, classify read-only vs read-write, verify audit and rollback. Reach for this when a diff touches a memory store.

원문 언어: 영어

managed-solution-import

Hardened pac solution import plus explicit baseline-aware cloud-flow reactivation for SPN-driven CI/CD — preflight, baseline, import, reactivate, verify. Managed imports leave flows Draft when the importing identity lacks connection permission; this…

원문 언어: 영어

record-screen

Record a Chrome browser tab to video via CLI. Use when the user wants to capture a screen recording of a browser tab. Supports list, start, stop, caption, and status subcommands. No debug mode required — uses a Chrome extension.

원문 언어: 영어

frame-a-deal-thesis

State the deal thesis — why this target, why now, how value is created — in one sentence before any model is built. Reach for this at the very start of any acquisition, before valuation.

원문 언어: 영어

plan-post-merger-integration

Turn synergies into an owner/date/cost-to-achieve register and a 100-day plan, and price integration cost back into the valuation — so the deal isn't underwritten on flawless integration. Reach for this before signing, not after close.

원문 언어: 영어

run-a-diligence-plan

Build a confirm-or-kill diligence plan where every workstream tests a named thesis assumption and every finding is mapped to thesis or price impact — not a data-room checklist. Reach for this once a thesis exists and a deal is live.

원문 언어: 영어

triangulate-a-valuation

Cross DCF, trading comparables, and precedent transactions into a valuation range where the divergence between methods is itself the finding. Reach for this whenever a price needs defending — one method is an opinion.

원문 언어: 영어

design-medallion-lakehouse

Design a Databricks lakehouse from the query and freshness SLO backward: the medallion layering (what earns bronze/silver/gold), the Delta table & partitioning strategy per layer (low-cardinality partition vs liquid clustering, OPTIMIZE/Z-ORDER/VACUUM…

원문 언어: 영어

tune-spark-and-costs

Diagnose a slow or failing Databricks/Spark job from the EVIDENCE (the Spark UI stages/task-skew/shuffle-spill/GC and the query plan) rather than guessing, then apply the fix the evidence points to — AQE skew-join or key salting for a hot key, broadcast for a…

원문 언어: 영어

component-api-and-library-build

Design and build an accessible, composable library component with a contract-grade public API — deciding composition vs configuration and controlled vs uncontrolled, baking in roles/focus/keyboard from v1, and shipping a story and usage docs. Traverses the…

원문 언어: 영어

design-system-versioning-and-adoption

Version a component library like the public contract it is (semver + changesets), ship breaking changes with codemods and loud deprecation, and drive adoption with metrics. Traverses the versioning branch of the design-systems decision tree: semver mapping →…

원문 언어: 영어

design-token-architecture

Structure design tokens across the primitive → semantic → component tiers, with theming/dark-mode and multi-brand solved as a semantic-tier value swap, then emit the platform outputs consumers use. Traverses the token branch of the design-systems decision…

원문 언어: 영어

build-budget-and-reserve-plan

Build an annual operating + reserve budget, set the assessment (dues) level, and set the reserve-funding policy by traversing the community-association decision tree (association authority & governing docs → operating budget → reserve study & percent-funded…

원문 언어: 영어

manage-board-and-vendor-operations

Run board/annual meetings, official records, vendor coordination, and common-area maintenance by traversing the community-association decision tree (meeting notice per the bylaws → agenda & board packet → quorum/proxy → minutes (motions/votes/decisions) →…

원문 언어: 영어

run-covenant-and-collections-workflow

Process a covenant violation, an architectural-review request, or a delinquent-assessment account by traversing the community-association decision tree (find the governing-document authority → for a violation: notice → cure period → hearing → fine/remedy,…

원문 언어: 영어

build-scheduling-and-evv-workflow

Build the visit schedule and the EVV workflow by traversing the home-health decision tree (plan of care + authorization → staffing match & caregiver continuity → visit schedule to ordered frequency/units → EVV capture: check-in/out via GPS/telephony/device…

원문 언어: 영어

plan-intake-and-eligibility

Take a home-health / home-care referral through intake by traversing the home-health decision tree (referral → service-line class: skilled home health vs non-medical home care → eligibility & benefit verification: Medicare homebound + skilled need /…

원문 언어: 영어

run-billing-and-survey-readiness

Turn home-health documentation into paid, survey-proof claims by traversing the home-health decision tree (documentation completeness: OASIS / plan of care / visit notes → PDGM 30-day period billing: NOA + final claim, LUPA watch, comorbidity →…

원문 언어: 영어

build-a-partner-tiering-model

Design partner tiers that trade concrete obligations (certs, pipeline, capacity) for concrete benefits (margin, MDF, leads) — not a logo wall. Reach for this when standing up or fixing a partner program.

원문 언어: 영어

design-an-mdf-program

Design market-development funds as a measured investment tied to a plan and an ROI floor — not a channel rebate nobody tracks. Reach for this when standing up or fixing MDF/co-op funds.

원문 언어: 영어

size-partner-sourced-pipeline

Size partner-sourced vs partner-influenced pipeline with a defined attribution rule, so the program number is one finance trusts and nothing is double-counted with direct. Reach for this before any partner-revenue claim.

원문 언어: 영어

structure-a-co-sell-motion

Build a co-sell motion around a named rep-to-rep play — mapped account overlap, a joint value proposition, and a shared incentive — not a 'we'll co-sell' press release. Reach for this when activating an alliance.

원문 언어: 영어

choose-recsys-approach

Choose the recommendation approach — popularity/heuristic baseline, collaborative filtering, content-based, hybrid, two-tower/embedding retrieval, or sequential — from data volume, sparsity, cold-start severity, latency, and interpretability. Use when…

원문 언어: 영어

evaluate-recommenders

Evaluate recommenders correctly — a temporal train/test split, per-stage offline metrics (recall@k, precision@k, nDCG, MAP, coverage, diversity, novelty) against a popularity baseline, AND the online A/B that is the real verdict. Use to build an eval harness…

원문 언어: 영어

handle-cold-start-and-serving

Handle cold-start (new users and new items) and serve recommendations within a latency budget — content/popularity fallbacks, onboarding & exploration, ANN retrieval, precompute/caching, online feature fetch, and popularity-on-timeout fallback. Use when new…

원문 언어: 영어

design-shopify-build

Design a Shopify build from who-uses-it and does-it-ship-to-the-App-Store backward: the app type (custom vs public vs theme/extension), the integration surface (Admin GraphQL API, webhooks, App Bridge/Polaris embedded UI, extensions), the current-generation…

원문 언어: 영어

ship-app-store-ready

Make a Shopify build correct, secure, and App-Store-review-ready: HMAC-verify every webhook + process idempotently + fast-200-async, implement the mandatory GDPR/data webhooks (customers/redact, shop/redact, customers/data_request), authenticate embedded…

원문 언어: 영어

design-dunning-and-recovery

Design and automate failed-payment recovery (dunning) — retry schedule, smart/adaptive retries, grace period, customer comms sequence, and entitlement-downgrade policy — trading recovered revenue against churn of good customers. Use for involuntary-churn…

원문 언어: 영어

implement-metered-billing

Implement usage-based / metered billing correctly — idempotent usage recording, aggregation & rating to billable quantities, on-time usage reporting before invoice close, and counted-vs-billed reconciliation. Use when billing on API calls, seats used, GB,…

원문 언어: 영어

model-plans-and-pricing

Model the plan / price / entitlement structure for a recurring-billing system — choose flat vs tiered vs per-seat vs usage/metered vs hybrid, define entitlements, and set proration/trial/coupon rules. Use when starting a billing build or re-pricing an…

원문 언어: 영어

handle-notices-and-planning

Respond to an IRS/state notice and run the planning calc by traversing the practice decision tree (identify the notice type & deadline → reconcile the agency figures vs the return → agree/partial/disagree response + substantiation → representation posture:…

원문 언어: 영어

plan-engagement-and-capacity

Plan the client mix, open the engagement, and size busy-season capacity by traversing the practice decision tree (engagement accept/decline & risk screen → client-mix/niche → engagement letter + organizer scope → busy-season volume × preparer-hours vs…

원문 언어: 영어

run-return-preparation-workflow

Run a return from organizer through e-file by traversing the practice decision tree (organizer & completeness check → entity→form routing: 1040 / 1120 / 1120-S / 1065 → preparation & schedules → self-review vs a separate-reviewer gate → e-file &…

원문 언어: 영어

crawl-scheduling-and-pipeline

Design the crawl schedule, change-detection, and the extraction-to-storage pipeline — a re-crawl cadence matched to data volatility, incremental crawls via conditional GET / ETag / sitemap lastmod, a polite rate-limit/backoff budget, and storage with…

원문 언어: 영어

legal-ethical-and-fetch-strategy

Run the legality/ethics gate BEFORE any code (robots.txt, ToS, public-vs-authenticated, rate, PII/copyright), prefer an API/feed/export over scraping, then choose the fetch strategy (HTTP + parser vs headless, JSON-endpoint-first). Traverses the top of the…

원문 언어: 영어

resilient-extraction-and-parsing

Extract web data defensively — prefer structured data (JSON-LD / microdata / __NEXT_DATA__ / JSON API) over brittle CSS/XPath selectors, anchor selectors on stable attributes with fallbacks, and validate every record to a schema so breakage is DETECTED not…

원문 언어: 영어

power-apps-code-apps

Use when building, scaffolding, debugging, or deploying Microsoft Power Apps Code Apps using React, Vue, or TypeScript in VS Code. Handles project initialization via pac CLI, Dataverse and connector data access via the @microsoft/power-apps SDK,…

원문 언어: 영어

wireframe

Invoked by /wireframe. Turn a plain-language description of anything — a web page, an app/software screen, a dashboard, or a flow/diagram — into a validated wireframe MODEL, then a high-fidelity self-contained HTML Artifact (authored via artifact-design) and,…

원문 언어: 영어

design-agent-tools-and-context

Design the tools/functions an agent calls and the context/memory strategy that keeps it coherent — unambiguous tool names, typed parameters, examples-in-description, errors that teach recovery, a small-enough tool count, plus a context plan (what stays…

원문 언어: 영어