「rds」の検索結果

Design, build, refactor, or review terminal interfaces—full-screen TUIs, interactive prompts, and command-line tools. Use for terminal-app layout and UX, CLI behavior, ncurses-style tools, dashboards, REPLs, fzf-like pickers, and libraries such as Bubble Tea, Ratatui, Textual, or Ink, including requests that name a known TUI such as lazygit, k9s, btop, helix, or yazi instead of saying “TUI.” Do not use for browser or web UI, native GUI, editor or font configuration, or backend and shell work that has no terminal interface.

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

Provision and manage cloud infrastructure using Terraform with HCL modules, remote state backends, workspaces, and plan/apply workflow. Implement infrastructure as code patterns with variable management, output values, and state locking for team collaboration. Use when provisioning new cloud infrastructure, migrating from ClickOps or CloudFormation to declarative IaC, managing multi-environment infrastructure, versioning infrastructure changes alongside application code, or enforcing standards through reusable modules.

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

Redact rendered visual artifacts — Mermaid diagrams, SVGs, and HTML dashboards — before public disclosure, using an ordered longest-first mapping table (specific label, then namespace label, then catch-all placeholder) that swaps sensitive identifiers for descriptive stand-ins while preserving structure, node ids, and teaching value. Covers whole-word identifier replacement, node-label-vs-node-id discrimination, re-rendering the derived image from the redacted source, and verifying the result through the redaction gate. Use when a diagram or dashboard built from internal findings must ship to a public mirror without leaking the names behind it.

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

Design and operate a data integrity monitoring programme based on ALCOA+ principles. Covers detective controls, audit trail review schedules, anomaly detection patterns (off-hours activity, sequential modifications, bulk changes), metrics dashboards, investigation triggers, and escalation matrix definition. Use when establishing a data integrity monitoring programme for GxP systems, preparing for inspections where data integrity is a focus area, after a data integrity incident requiring enhanced monitoring, or when implementing MHRA, WHO, or PIC/S guidance.

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

Establish and maintain longitudinal baselines of CLI binary contents across versions. Covers marker selection by category (API / identity / config / telemetry / flag / function), weighted scoring, threshold-based system-presence detection, and per-version baseline records. Use when tracking a feature's lifecycle across releases, when probing for dark-launched or removed capabilities, or when verifying that a scanning tool itself still catches known-good markers on old binaries.

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

Implement electronic signatures compliant with 21 CFR Part 11 Subpart C and EU Annex 11. Covers signature manifestation (signer, date/time, meaning), signature-to-record binding, biometric vs non-biometric controls, policy creation, and user certification requirements. Use when a computerized system requires legally binding electronic signatures for GxP records, when replacing wet-ink signatures in regulated workflows, when implementing batch release or document approval workflows, or when a regulatory gap reveals missing signature controls.

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

Implement audit trail functionality for R projects in regulated environments. Covers logging, provenance tracking, electronic signatures, data integrity checks, and 21 CFR Part 11 compliance. Use when an R analysis requires electronic records compliance (21 CFR Part 11), when you need to track who did what and when in an analysis, when implementing data provenance tracking, or when creating tamper-evident analysis logs for regulatory submissions.

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

Implement policy-as-code enforcement using OPA Gatekeeper or Kyverno to validate and mutate Kubernetes resources according to organizational policies. Covers constraint templates, admission control, audit mode, reporting violations, and integrating with CI/CD pipelines for shift-left policy validation. Use when enforcing resource configuration standards, preventing security misconfigurations such as privileged containers, ensuring compliance before deployment, standardizing naming conventions, or auditing existing cluster resources against policies.

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

Record insect sightings with location, date, habitat, photography, behavior notes, preliminary identification, and citizen science submission. Covers GPS coordinates, weather conditions, microhabitat description, macro photography techniques, behavioral observations, preliminary identification to order using body plan, and submission to citizen science platforms such as iNaturalist. Use when encountering an insect you want to document, contributing to citizen science biodiversity databases, building a personal observation journal, or supporting ecological surveys with georeferenced photographic records.

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

Design serialization schemas using JSON Schema, Protocol Buffer definitions, or Apache Avro. Covers schema versioning, backwards compatibility, validation rules, and evolution strategies for long-lived data formats. Use when defining a new API contract or data interchange format, adding fields to an existing schema without breaking consumers, migrating between schema versions, choosing between schema systems, or documenting data validation rules for automated enforcement.

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

Design Shiny application UIs using bslib for theming, layout_columns for responsive grids, value boxes, cards, and custom CSS/SCSS. Covers page layouts, accessibility, and brand consistency. Use when building a new Shiny app UI from scratch, modernizing an existing app from fluidPage to bslib, applying brand theming, making a Shiny app responsive across screen sizes, or improving accessibility of a Shiny application.

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

Design an A2A Agent Card (.well-known/agent.json) manifest describing agent capabilities, skills, authentication requirements, and supported content types. Use when building an agent that must be discoverable by other A2A-compliant agents, exposing capabilities for multi-agent orchestration, migrating an existing agent to the A2A protocol, defining the public contract for an agent before implementation, or integrating with agent registries that consume Agent Cards.

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

Unify metrics, logs, and traces for cohesive debugging. Implement exemplars for log-to-trace linking, build unified dashboards using RED/USE methods, and enable rapid root cause analysis across observability signals. Use when investigating complex incidents spanning multiple systems, reducing mean time to resolution, implementing distributed tracing, or moving from siloed tools to a unified observability platform.

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

Reference Hildegard von Bingen's Physica natural history knowledge. Covers classification of plants, stones, animals, fish, birds, elements, and trees with their medicinal, symbolic, and practical properties. Enables cross- referencing between categories and application guidance. Use when exploring a specific plant, stone, or animal from Hildegard's perspective, researching medieval natural history and cosmology, cross-referencing properties across categories, or integrating Physica knowledge into health, spiritual, or creative practice.

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

Collect and preserve insect specimens following museum-grade standards including legal compliance, collection methods, humane dispatch, dry pinning, wet preservation, labeling, storage, and curation. Covers permit requirements, protected species regulations, sweep nets, beating trays, pitfall traps, light traps, Malaise traps, aspirators, ethyl acetate killing jars, freezing, pin placement by order, wing spreading, ethanol preservation for soft-bodied specimens, specimen labeling with locality and date, storage with pest management, and database entry. Use when building a reference collection for taxonomic study, preserving voucher specimens for ecological research, preparing specimens for identification by specialists, or curating an existing collection.

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

Compute and analyze gematria (Hebrew numerical values) using standard, ordinal, and reduced methods. Covers word-to-number conversion, isopsephy comparisons, and interpretive frameworks. Use when computing the numerical value of a Hebrew word or phrase, comparing two words for shared gematria values, studying a biblical verse or divine name for numerical correspondences, or connecting a numerical result to its position on the Tree of Life.

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

Select an OCR/HTR engine by benchmarking candidates on the same labelled samples — source ground truth from open datasets (e.g. Hugging Face PAGE-XML corpora) or hand-transcription, wrap every engine behind a transcribe(image_path) -> str adapter (vision-LLMs via any OpenAI-compatible endpoint, dedicated HTR REST APIs, cloud OCR), and score with zero-dependency raw CER, lenient CER, WER, and a critical name/date token diff. Use when choosing an engine for handwriting or historical-document transcription, when published accuracy claims need honest verification on your own material, or when a records workflow must surface confident-but-wrong names and dates that a low aggregate CER hides.

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

Create parameterized Quarto or R Markdown reports that can be rendered with different inputs to generate multiple variations. Covers parameter definitions, programmatic rendering, and batch generation. Use when generating the same report for different departments, regions, or time periods; creating client-specific reports from a single template; building dashboards that filter to specific subsets; or automating recurring reports with varying inputs.

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

Capture reproducible screenshots from the currently booted iOS Simulator and turn them into three App Store marketing cards with validated dimensions and concise copy. Use after a successful Simulator build, during the two-minute proof lane, or when replacing prototype images with real app captures.

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

Vue 3 form patterns: native v-model, vee-validate + zod (most common), VueUse helpers, defineModel for custom inputs, controlled vs uncontrolled, field arrays, multi-step wizards. Use this skill to: - Wire vee-validate with a validation schema (zod / yup). - Build custom form components with defineModel (Vue 3.4+). - Implement multi-step forms. - Handle async validation. - Integrate forms with TanStack Query mutations or Pinia actions. Do NOT use this skill for: - General SFC conventions (see vue-conventions). - State management (see vue-state-management). - Routing (see vue-routing). - Testing forms (see vue-testing).

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

Form patterns for React: react-hook-form (most common), Formik (legacy/stable), TanStack Form (newer). Validation via zod / yup / valibot. Controlled vs uncontrolled inputs, field arrays, multi-step wizards. Use this skill to: - Wire react-hook-form with a validation schema. - Pick between controlled and uncontrolled patterns. - Build multi-step forms with state preservation. - Handle async validation (e.g., username availability). - Integrate forms with TanStack Query mutations. Do NOT use this skill for: - General state management (see react-state-management). - Routing (see react-routing). - Component conventions (see react-conventions). - Testing forms (see react-testing).

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

Etsy SEO optimization for existing and new listings. Auto-detects REWRITE (when user pastes a current title + tags + description) or CREATE (when user gives a short product context). Triggers on "rewrite this listing", "optimize my Etsy listing", "fix my title and tags", "create new listing", "make a new Etsy listing". Uses live Etsy autocomplete + competitor SERP scraping for evidence-driven keyword research. Enforces 2026 Etsy rules — tag ≤20 chars, primary keyword in first 40 chars, indexing spread across title/tags/attributes/description/hero alt, NLP-aware writing, trademark stoplist scan. When the user's problem isn't SEO (CTR, conversion, photos, price, saturated niche), it says so directly and routes to concrete next steps. Silently maintains a markdown listing database at ~/etsy-listings/ for cross-session memory on Claude/Cowork. Catches duplicate primary keywords across the user's own listings.

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

Use when explaining branch predictors, mispredict penalties, speculative execution, Spectre or Meltdown mitigations, or branchless code. Not for pipeline stage theory: use cpu-pipelines-and-hazards.

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

Use when a repository decision needs an interview plus durable terminology and decision records. Not for remote, credential, publish, deploy, or irreversible changes.

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