メニュー
このリポジトリの skills
SkillsMP は mcorbett51090/RavenClaude から 924 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
mcorbett51090/RavenClaude収集済み skill 924 件中 40 件を表示しています。
Produce trustworthy artifacts: reproducible/deterministic builds, minimal non-root container images, SemVer + immutable digests, build-time SBOM (CycloneDX/SPDX), and SLSA provenance + signing for verifiable supply-chain integrity.
原文の言語: 英語
Build trustworthy A/B-test plumbing: deterministic sticky assignment, exposure logging (who actually saw the variant), Sample-Ratio-Mismatch checks before reading results, pre-registered metric/MDE/duration, and guardrail metrics — leaving significance to…
原文の言語: 英語
Instrument trustworthy product analytics: a tracking plan first, a consistent typed event/property schema (object_action naming, versioned), identity stitching (anonymous -> known), CDP routing (instrument once), and event-quality validation as code.
原文の言語: 英語
Use feature flags safely: match the flag type to its purpose (release/experiment/ops/permission), give every risky change a kill switch, roll out progressively gated by a health signal, evaluate deterministically and fail-safe, and manage the flag lifecycle…
原文の言語: 英語
Architect money-safe payments: represent money as integer minor units + currency (never floats), keep a double-entry append-only ledger as source of truth (the PSP is an integration you reconcile against), design a money-event model, and reconcile…
原文の言語: 英語
Minimize PCI-DSS scope (engineering posture): use PSP client-side tokenization so the raw PAN never touches your servers (SAQ-A), reduce scope ruthlessly, log money operations for audit without ever logging card data, and route attestation/regulation/verdict…
原文の言語: 英語
Integrate a PSP correctly: idempotency key on every money operation (charge/refund/payout), verify webhook signatures and handle them idempotently + out-of-order, model the charge state machine explicitly, and handle 3DS/SCA and hard-vs-soft declines.
原文の言語: 英語
Build subscription/usage billing: model plans and prorate mid-cycle changes correctly, meter usage idempotently, run a reliable recoverable billing-cycle job, recover failed payments with smart dunning, and emit clean revenue events for finance.
原文の言語: 英語
Make a frontend fast to a budget: analyze and code-split the bundle by route, lazy-load heavy/below-the-fold, optimize images/fonts, minimize hydration (RSC/islands), kill render-blocking and request waterfalls, and tune the Core Web Vitals (LCP/INP/CLS)…
原文の言語: 英語
Architect frontend state: treat server data as a cache (TanStack Query/SWR/RSC), place client state at the narrowest workable scope (local -> context -> store), invalidate deliberately, use optimistic updates with rollback, and derive rather than duplicate.
原文の言語: 英語
Build composable, accessible React components: small components with clear props (composition over a flag-laden mega-component), correct hooks (complete deps, no stale closures, effects only for external sync), controlled validated forms, and accessibility in…
原文の言語: 英語
Choose the rendering strategy per route: SSG/ISR for static content, SSR/RSC for personalized or SEO-critical pages, CSR for behind-login interactive shells; default to server components and hydrate only interactive islands to minimize shipped JavaScript.
原文の言語: 英語
Choose GCP compute by operational burden: Cloud Run (default for stateless containers/HTTP, scale-to-zero), GKE/Autopilot (k8s/portability), Cloud Functions (small event handlers), GCE (legacy); design Pub/Sub integration with idempotency + dead-letter topics.
原文の言語: 英語
Write least-privilege GCP IAM: predefined/custom roles over primitive (Owner/Editor/Viewer), service accounts + Workload Identity Federation instead of exported key files, IAM Conditions, and binding at the correct hierarchy level.
原文の言語: 英語
Design private-by-default GCP networking: Shared VPC for multi-project, default-deny firewall targeted by tag/service-account, Private Google Access + Private Service Connect, and Cloud NAT for controlled egress.
原文の言語: 英語
Design the GCP resource hierarchy: organization -> folders (env/dept) -> projects (app/workload), and set org-policy constraints (allowed regions, disable SA key creation, no external IP, OS Login) high in the tree for inheritance.
原文の言語: 英語
Prevent training-serving skew: compute features once via a feature store or shared transformation so training and serving use identical logic, with point-in-time correctness for temporal features and no leakage of future data.
原文の言語: 英語
Keep production models honest: monitor input/data drift, prediction/concept drift, and performance decay (when labels arrive); define the retraining trigger up front (schedule/threshold/drop); alert on model health; and close the loop to retraining.
原文の言語: 英語
Serve models reliably: choose online vs batch by the use case, deploy a versioned model from the registry, optimize latency to a budget (batching/quantization/distillation/hardware), and roll out safely with shadow -> canary -> full.
原文の言語: 英語
Build reproducible training: a versioned prep->train->evaluate->register pipeline (not a notebook), experiment tracking (params/metrics/code/data/env), a model registry as source of truth, and leakage-free time-aware validation.
原文の言語: 英語
Build native Android the platform way: state-driven Jetpack Compose (state hoisting, remember, list keys), coroutines/Flow with lifecycle-scoped structured concurrency, Keystore/EncryptedSharedPreferences, WorkManager background respecting Doze, and Material…
原文の言語: 英語
Build React Native/Flutter well: maximize shared logic while honoring per-platform conventions, manage the bridge/platform-channel native boundary (and write native modules when needed), avoid framework-specific performance pitfalls, and handle…
原文の言語: 英語
Build native iOS the platform way: state-driven SwiftUI with correct property-wrapper ownership, Swift Concurrency (async/await, actors, @MainActor), Keychain secure storage, lifecycle/background-task handling, and Human Interface Guidelines + accessibility.
原文の言語: 英語
Decide native vs React Native vs Flutter by the app's real needs (platform-specific UX, performance, OS-feature access, team), and set the offline-first sync strategy (local source of truth, write queue, conflict resolution) and lifecycle-survival plan.
原文の言語: 英語
Run an incident and learn from it: declare + classify severity, split IC/comms/ops roles, communicate on a cadence, mitigate before root-causing, and write a blameless postmortem with owned, dated action items.
原文の言語: 英語
Instrument a service with OpenTelemetry: OTLP export, semantic conventions, the key spans and metrics, a sampling strategy (head vs tail), cardinality control, and trace/log correlation via propagated context.
原文の言語: 英語
Design SLIs/SLOs and an error-budget policy: pick user-centric indicators, set targets by user need (not 100%), define the ship-vs-freeze budget rule, and enforce with multi-window multi-burn-rate alerts.
原文の言語: 英語
Run continuous product discovery: weekly JTBD customer interviews, an opportunity-solution tree (outcome -> opportunities -> solutions -> experiments), assumption mapping with riskiest-assumption testing, and problem validation before solutioning.
原文の言語: 英語
Prioritize by evidence, not opinion: use a transparent framework (RICE = reach x impact x confidence / effort, or cost-of-delay, or opportunity scoring) to make trade-offs explicit and arguable, and frame everything around outcomes rather than outputs.
原文の言語: 英語
Measure what matters: define a North Star metric that captures delivered value, decompose it into 3-5 movable input metrics, distinguish vanity (cumulative totals) from actionable (rates/cohorts/retention), set guardrails, and judge outcomes vs a baseline.
原文の言語: 英語
Write deterministic E2E/integration tests: target resilient role/test-id selectors, wait on conditions never fixed sleeps, isolate and clean up test data, and structure with page objects so a UI change updates one locator.
原文の言語: 英語
Build trustworthy test infrastructure: factory-based isolated test data, ephemeral per-run environments + service virtualization, automated flaky-test detection/quarantine, parallel sharding, and coverage+mutation reporting in CI.
原文の言語: 英語
Design a test strategy on the pyramid: map defect classes to the cheapest test level that catches them, prioritize by risk, use coverage as a floor and mutation testing as the quality truth, and decide what not to test.
原文の言語: 英語
Stand up tuned application security scanning in CI: SAST + SCA per-PR, DAST on a deployed build, secret-scanning, and triage by exploitability×blast-radius rather than raw CVSS.
原文の言語: 英語
Manage secrets safely: detect them in code/config/logs, vault them, federate with short-lived credentials, rotate on a schedule, and treat any committed secret as compromised (rotate, don't just delete).
原文の言語: 英語
Secure the software supply chain from the consume side: ingest the SBOM, triage CVEs by reachability, pin dependencies with a deliberate update cadence, verify SLSA provenance, and defend against malicious packages.
原文の言語: 英語
Threat-model a design with STRIDE: draw the data-flow diagram and trust boundaries, walk STRIDE per element, rank threats by likelihood×impact, and map each to a mitigation or a routed accepted-risk.
原文の言語: 英語
Write trustworthy developer reference: drive it from the spec (OpenAPI/AsyncAPI) so it can't drift, make every example runnable, document the unhappy path (errors/limits/auth/pagination), and optimize the quickstart for time-to-first-success.
原文の言語: 英語
Apply the Diataxis framework: identify which of the four documentation kinds you're writing (tutorial/how-to/reference/explanation), keep them separate, and organize the whole docs set around the reader's journey rather than the system's structure.
原文の言語: 英語
Run docs like software: pick the tooling by needs (Docusaurus/Mintlify/MkDocs/Starlight), keep docs in the repo with PR review, build/preview/deploy in CI, version docs to match the product, and gate quality with link-checking + example-testing.
原文の言語: 英語