「terminal」の検索結果

Scan running terminals for dev server URLs (localhost ports), report them, and optionally open the app in Cursor's built-in browser.

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

Export code, terminal output, diagrams, or UI components to PNG images using headless browser rendering or CLI tools.

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

Pharmacokinetic (PK) analysis of concentration-time data — non-compartmental analysis (NCA) for Cmax, Tmax, AUC (0-t and 0-∞), terminal half-life, clearance (CL), volume of distribution (Vd), MRT, and absolute bioavailability (F). Also one-compartment fitting. Use when you have plasma/serum drug concentrations over time after a dose and need PK parameters, or to compute bioavailability from IV + oral AUCs. NOT for ADMET property prediction from structure (use tooluniverse-admet-prediction).

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

Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

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

Use when the user, inside an Orca terminal, asks Hermes to resolve, dispatch, orchestrate or supervise GitHub issues with Orca workers — 'orquestrar as issues 12, 15 e 18 no Orca', 'despachar as issues com label ready', 'coordenar workers do Orca para estas issues', or to resume such a Run after compaction. Do NOT use for a single unsupervised hand-off to another agent (Orca CLI directly), for working on one issue in this session (pwdev-feat feat-loop), or outside Orca.

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

Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs.

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

Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

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

Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.

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

Connect Claude to external apps via the Composio CLI. Use this skill when the user wants to send emails, create issues, post messages, or take actions across Gmail, Slack, GitHub, Notion, and 1000+ services from the terminal.

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

Connect Codex to any app via the Composio CLI. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services from the terminal.

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

Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

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

Use this skill when a driver needs to move a CMV within a yard, terminal, or property under § 395.8 yard-move provisions. Covers what counts as yard move, ELD configuration, and where yard move ends and on-duty driving begins.

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

Use this skill when a driver needs to extend the 14-hour duty window using the 16-hour exception under § 395.1(o). Covers eligibility, frequency limits (once per 7 days), return-to-terminal requirement, and documentation.

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

Use when a carrier asks about disaster recovery (DR) and business continuity planning (BCP) — cyber incident, natural disaster, terminal loss, key-person departure, financial liquidity event, major customer loss, insurance crisis, or fuel supply disruption. Covers risk assessment, continuity strategy, communication plans, and recovery time objectives.

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

Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.

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

SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.

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

Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.

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

Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.

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

Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

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

Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC/drum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP/MES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.

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

Analyze raw prompts, identify intent and gaps, match ECC components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt. Advisory role only — never executes the task itself. TRIGGER when: user says "optimize prompt", "improve my prompt", "how to write a prompt for", "help me prompt", "rewrite this prompt", or explicitly asks to enhance prompt quality. Also triggers on Chinese equivalents: "优化prompt", "改进prompt", "怎么写prompt", "帮我优化这个指令". DO NOT TRIGGER when: user wants the task executed directly, or says "just do it" / "直接做". DO NOT TRIGGER when user says "优化代码", "优化性能", "optimize performance", "optimize this code" — those are refactoring/performance tasks, not prompt optimization.

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

Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.

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

Modern Perl 5.36+ idioms, best practices, and conventions for building robust, maintainable Perl applications.

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

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.

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