Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
日本語の概要は準備中です。原文の説明を表示しています。
3,071 件 ・ 関連度順
概要と使いどころ
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
日本語の概要は準備中です。原文の説明を表示しています。
Generate systematic refinement steps from high-level specifications to concrete implementations in Isabelle/HOL or Coq, preserving correctness obligations at each step. Use when working with formal verification, program refinement, proof development, or when translating abstract specifications into executable code while maintaining formal guarantees. Supports data refinement (abstract types → concrete structures), algorithmic refinement (specifications → algorithms), and stepwise refinement with proof obligations.
日本語の概要は準備中です。原文の説明を表示しています。
Locate root causes of failing regression tests by analyzing code changes, error messages, and test dependencies. Use when regression tests start failing after code changes, investigating test failures in CI/CD, debugging flaky tests, or understanding why previously passing tests now fail. Analyzes git diffs, stack traces, test output, and dependency changes to produce structured markdown reports ranking likely causes. Triggers when users ask to find why tests are failing, debug regression failures, investigate test breakage, or analyze failing test suites.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate or fix a GitHub issue by number or URL. Keep investigation-only requests read-only.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate, reproduce, and safely fix a bug with regression protection. Composes context, diagnosis, architecture, code quality, and testing guardrails into a reproduce-first repair workflow. Use when the user says 'fix this bug', 'debug this', 'investigate this failure', 'patch this regression', 'repair this issue', or 'why is this broken'.
日本語の概要は準備中です。原文の説明を表示しています。
Infer cell-cell communication networks from scRNA-seq data using CellChat, NicheNet, and LIANA for ligand-receptor interaction analysis. Use when inferring ligand-receptor interactions between cell types.
日本語の概要は準備中です。原文の説明を表示しています。
Boltz-1 / Boltz-2 structure prediction for proteins, complexes, and ligand-aware validation. Use this skill when: (1) Predicting protein complex structures, (2) Validating designed binders, (3) Need open-source alternative to AF2, (4) Predicting protein-ligand complexes, (5) Using local GPU resources. For QC thresholds, use protein-design-qc. For AlphaFold2 prediction, use alphafold2-multimer. For Chai prediction, use chai1-structure-prediction.
日本語の概要は準備中です。原文の説明を表示しています。
Design protein sequences using ProteinMPNN inverse folding. Use this skill when: (1) Designing sequences for RFdiffusion backbones, (2) Redesigning existing protein sequences, (3) Fixing specific residues while designing others, (4) Optimizing sequences for expression or stability, (5) Multi-state or negative design. For backbone generation, use rfdiffusion or bindcraft. For ligand-aware design, use ligandmpnn. For solubility optimization, use solublempnn.
日本語の概要は準備中です。原文の説明を表示しています。
Solubility-optimized protein sequence design using SolubleMPNN. Use this skill when: (1) Designing for E. coli expression, (2) Optimizing solubility of designed proteins, (3) Reducing aggregation propensity, (4) Need high-yield expression, (5) Avoiding inclusion body formation. For standard design, use proteinmpnn. For ligand-aware design, use ligandmpnn.
日本語の概要は準備中です。原文の説明を表示しています。
Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't explicitly ask for a slideshow, confirm before authoring. Unclear → /hyperframes.
日本語の概要は準備中です。原文の説明を表示しています。
Provisional sector-specific Plain Language standard for document design (based on ISO/WD 24495-5, under development). Applied when structuring complex documents so readers can find and navigate content through layout, visual hierarchy, and navigation aids.
日本語の概要は準備中です。原文の説明を表示しています。
Internal — for Boundless team members only. Query AWS CloudWatch logs for Boundless services (provers, slasher, distributor, order stream, order generator, indexer, signal) on prod/staging environments. Use when the user asks to look at service logs, debug service behavior from log output, search logs for a request ID, or investigate errors using CloudWatch. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the bundled self-contained Godot WeChat Mini Game adapter kit to an official Godot checkout. Use when the user wants to port official Godot to WeChat Mini Game, refresh a nearby 4.6-based port, or inspect the shipped patch/source bundle for WXMEMFS, `wx.request`, audio cleanup, display/input, WXGLX dual-path rendering, `.wasm.br`, and `wx.exitMiniProgram`. This skill is version-locked to the bundled upstream base and must not be described as a generic “Godot 4.x” patch dump.
日本語の概要は準備中です。原文の説明を表示しています。
Test for WCAG 2.2 AA compliance with axe-core + Playwright, keyboard navigation audits, screen reader testing, ARIA pattern validation, and legal compliance mapping (ADA, EAA, Section 508). Automated tools catch 30-40% of issues — this skill covers automated and manual testing together. Use when: "accessibility," "a11y," "WCAG," "screen reader," "axe," "keyboard navigation," "ARIA," "ADA compliance." Not for: cookie-consent/GDPR compliance — use compliance-testing; pixel-diff visual regression — use visual-testing. Related: playwright-automation, compliance-testing, visual-testing, ci-cd-integration.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging methodology - scientific method, hypothesis testing, and root cause analysis that works across all technologiesUse when "bug, debugging, not working, broken, investigate, root cause, why is this happening, figure out, troubleshoot, doesn't work, unexpected behavior, debugging, root-cause, hypothesis, scientific-method, troubleshooting, bug-hunting, investigation, problem-solving" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Accessibility isn't a feature - it's a fundamental quality of good software. 1 in 4 adults has a disability. Many more have temporary impairments or situational limitations. Your users include people who can't see, can't hear, can't use a mouse, or can't process information the way you do. This skill covers WCAG guidelines, ARIA patterns, keyboard navigation, screen reader compatibility, and automated testing. Key insight: accessible code is better code. The constraints of accessibility lead to simpler, more semantic, more maintainable implementations. 2025 lesson: Accessibility lawsuits are at an all-time high. "We'll add it later" is both ethically wrong and legally risky. Start accessible, stay accessible. Use when "accessibility, a11y, wcag, aria, screen reader, keyboard navigation, focus trap, alt text, color contrast, skip link, accessible, accessibility, a11y, wcag, aria, screen-reader, keyboard, inclusive, semantic-html" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic research methodology for building comprehensive, current knowledge on any topic. Requires web_search tool. Use when questions require thorough investigation, recent developments post-cutoff, synthesis across multiple sources, or when Claude's knowledge may be outdated or incomplete. Triggered by "Research", "Investigate", "What's current on", "Latest info on", complex queries needing validation, or technical topics with recent changes.
日本語の概要は準備中です。原文の説明を表示しています。
The test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches commit-gate until all six are green.
日本語の概要は準備中です。原文の説明を表示しています。
Select and design navigation patterns that match product structure, user tasks, and platform conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomously navigate websites and extract structured data across pages. Use when the task requires navigation or no suitable ready-made workflow or data provider covers it.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate a monitoring alert end-to-end. Pulls metrics, logs, traces, and recent code changes to identify root cause. Works with any monitoring MCP.
日本語の概要は準備中です。原文の説明を表示しています。
用户在选择投资标的或商业模式时,纠结于"便宜买差企业"还是"合理价买好企业"。 语言信号:"这个便宜能不能捡"/"估值低是不是就值得买"/"贵的好公司值不值得买"/"便宜货有什么问题" 不适用于:已有明确投资方法论且不需要在两种风格间做选择的场景。
日本語の概要は準備中です。原文の説明を表示しています。
NavigationAgent2D使用、AStarGrid2D算法、自定义A*实现、流式寻路及性能优化。用于2D/3D导航系统、动态障碍物避让、游戏AI导航等场景。
日本語の概要は準備中です。原文の説明を表示しています。
Autonomously navigate websites and extract structured data across pages. Use when the task requires navigation or no suitable ready-made workflow or data provider covers it.
日本語の概要は準備中です。原文の説明を表示しています。