2,996 件 ・ 関連度順
概要と使いどころ
Run the end-to-end viewer smoke test (`tests/viewer_smoke.sh`). Spawns `rezolus view` in upload-only, file, A/B, and proxy modes, exercises the API endpoints, and verifies experiment attach/detach. Use after any change touching `src/viewer/` or before opening a viewer-related PR.
日本語の概要は準備中です。原文の説明を表示しています。
CRITICAL: Never modify files in content-addressable storage systems where the filename IS the content hash (SHA256, IPFS CID, etc.). Use when: (1) Working with Blossom protocol, IPFS, or any CAS system, (2) Considering "optimizing" stored files (faststart, compression), (3) Implementing transcoding or processing pipelines for hash-identified content, (4) Building on top of ProofMode or any cryptographic verification system. Modifying files in place breaks hash verification and content integrity.
日本語の概要は準備中です。原文の説明を表示しています。
Select, build, and validate Blender deformation and motion-control systems including Simple Deform, Curve, Lattice, Mesh Deform, Shrinkwrap, Surface Deform, Armature, shape keys, hooks, constraints, and drivers. Use when an object must bend, twist, taper, follow a path, conform to a surface, deform smoothly, articulate, or move through controlled mechanical relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Build, inspect, audit, and refactor Blender Geometry Nodes systems for procedural models, instancing, modular effects, curves, scattering, flocks, data visualization, fields, simulation zones, and node-graph cleanup. Use whenever a Blender task specifically calls for Geometry Nodes, reusable procedural node graphs, node connections/layout, or a scalable procedural asset.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate production-grade Blender work by probing the installed Blender version, retrieving relevant official Blender documentation, assigning visual design intent, classifying shape grammar and geometry/deformation/procedural/physics/shading needs, comparing direct Blender components with node systems, creating staged artifacts, and routing to specialist skills. Use for every non-trivial Blender creation, reconstruction, simulation, animation, environment, or scene-modification request, especially when the user does not know whether to use topology, Boolean, Array, curves, snapping, Displace, simulation, Geometry Nodes, or shading.
日本語の概要は準備中です。原文の説明を表示しています。
Scan repositories for newly disclosed CVEs in dependencies after a specific cutoff date. Takes a repository path, cutoff date (YYYY-MM-DD), and optional parameters for transitive dependencies. Parses dependency manifests (package.json, pom.xml, requirements.txt, go.mod, Cargo.toml) and lockfiles to extract exact versions. Queries vulnerability databases (OSV.dev, NVD, GitHub Advisory) to identify CVEs disclosed strictly after the cutoff date. Distinguishes between newly disclosed CVEs and previously known CVEs. Use when: (1) Performing security audits to find new vulnerabilities since last review, (2) Checking if new CVEs affect a historical codebase version, (3) Generating compliance reports showing vulnerability status at specific dates, (4) Tracking security posture changes over time. Supports npm, Maven, pip, Go modules, Cargo, and other major ecosystems.
日本語の概要は準備中です。原文の説明を表示しています。
Establish explicit traceability between formal specifications (preconditions, postconditions, invariants) and verified code components with their correctness proofs. Produce structured Markdown mapping reports showing verification coverage and proof evidence. Use when auditing formal verification, documenting verified systems, establishing traceability for certification, or when the user asks to map specifications to code, generate verification reports, or analyze verification coverage in Coq, Dafny, Isabelle, or other proof assistants.
日本語の概要は準備中です。原文の説明を表示しています。
Generate executable code together with formal proofs certifying safety and correctness properties in Isabelle/HOL or Coq. Use when building verified software, safety-critical systems, or when formal guarantees are required. Produces code with accompanying proofs for memory safety, bounds checking, functional correctness, invariant preservation, and termination. Supports extraction to OCaml/Haskell/SML and integration with existing codebases.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically extract abstract finite-state models in SMV/NuSMV format from source code (C/C++, Java, Python) for formal model checking. Use when users need to: (1) Generate SMV models from program code for verification, (2) Extract state-transition models from protocol implementations, (3) Analyze control flow and data flow to construct formal models, (4) Create models for checking safety and liveness properties, (5) Convert imperative code to declarative state machines. Particularly effective for protocol implementations, concurrent systems, and control logic with clear state transitions.
日本語の概要は準備中です。原文の説明を表示しています。
Generate integration tests for multiple interacting components in Python. Use when testing interactions between: (1) Multiple services or APIs (REST/GraphQL endpoints, microservices), (2) Database operations with repositories/ORMs (SQLAlchemy, Django ORM), (3) External services (payment gateways, email services, third-party APIs), (4) Message queues and event-driven systems, (5) Full stack workflows (API + database + business logic). Provides test structure templates, fixtures, test data builders, and patterns for pytest-based integration testing.
日本語の概要は準備中です。原文の説明を表示しています。
Produces comprehensive summaries and insights about legacy codebases to help understand unfamiliar code. Use when onboarding to a new project, planning refactoring efforts, assessing code for acquisition/migration, or generating documentation for undocumented systems. Analyzes architecture, dependencies, code quality issues, and test coverage. Creates high-level overviews with architecture diagrams, key components, entry points, and actionable insights for understanding and improving legacy code.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically repair code violations of temporal properties using model-checking counterexamples as guidance. Use when working with formal verification results, temporal logic property violations (LTL, CTL), model checking counterexamples, or when asked to repair property violations, fix counterexamples, repair temporal properties, fix model checking violations, or repair code based on counterexamples. Applicable to concurrent systems, state machines, synchronization issues, safety/liveness properties, and resource management violations.
日本語の概要は準備中です。原文の説明を表示しています。
Identify the precise location of bugs in source code, modules, and systems. Use this skill when debugging applications, investigating test failures, analyzing error reports, tracing runtime issues, or performing root cause analysis. Analyzes stack traces, error messages, failing tests, and code patterns to pinpoint buggy functions, classes, files, or modules with confidence rankings and supporting evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies boundaries between modules or components in software systems through static code analysis and dependency detection. Use when Claude needs to analyze software architecture, identify module boundaries, detect boundary violations, find circular dependencies, or assess component coupling. Supports Python (packages and imports) and Java (packages and dependencies). Trigger when users ask to "identify boundaries", "find component boundaries", "detect boundary violations", "analyze module structure", "check architecture", or "find circular dependencies".
日本語の概要は準備中です。原文の説明を表示しています。
Automatically migrates build systems and CI/CD configurations to target platforms. Use when modernizing build infrastructure, switching CI/CD providers, or standardizing across projects. Supports common migration paths including Maven↔Gradle, npm↔Yarn, Travis CI→GitHub Actions, CircleCI→GitHub Actions, Jenkins→GitLab CI, and GitLab CI→GitHub Actions. Analyzes existing configuration, generates equivalent target configuration, maps dependencies and commands, and provides validation and migration documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects. Use when creating or updating CI workflows for npm packages, Python packages, Go modules, Rust crates, or other library projects that need automated build and test pipelines. Includes templates for common package ecosystems with best practices for dependency caching, matrix testing, and artifact publishing.
日本語の概要は準備中です。原文の説明を表示しています。
Uses abstract interpretation to automatically infer loop invariants, function preconditions, and postconditions for formal verification. Generates invariants that capture program behavior and support correctness proofs in Dafny, Isabelle, Coq, and other verification systems. Use when adding formal specifications to code, generating verification conditions, inferring contracts for functions, or discovering loop invariants for proofs.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze customer churn patterns, identify at-risk accounts, create retention playbooks, and build early warning systems
日本語の概要は準備中です。原文の説明を表示しています。
Use when Code implementation and refactoring, architecturing or designing systems, process and workflow improvements, error handling and validation. Provide tehniquest to avoid over-engineering and apply iterative improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
TRIGGER THIS when building DEI strategy, creating diversity goals, designing inclusive programs, building equity analyses, developing training, addressing inclusion issues, or tracking DEI metrics. Develops comprehensive diversity, equity, and inclusion strategies aligned to business goals with measurable outcomes, training programs, metrics frameworks, and accountability systems.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute organizational or technical changes. Trigger with "we're changing", "rolling out", "migration plan", "how do we communicate this change", "change management plan", or when the user is planning a change that affects people, processes, or systems.
日本語の概要は準備中です。原文の説明を表示しています。
ACTIVATE when building executive dashboards, tracking business metrics, creating executive scorecards, monitoring organizational KPIs, setting up health metrics, building dashboards for real-time monitoring, or establishing systems to track and measure business performance. Critical for any executive who needs to monitor company health, make data-driven decisions, or track progress toward strategic goals.
日本語の概要は準備中です。原文の説明を表示しています。
Design scale-adaptive game architecture with engine systems and networking. Use when the user says "game architecture" or "design architecture"
日本語の概要は準備中です。原文の説明を表示しています。