Prepare, execute and verify authorized Fusion CAD changes using resolved entities, explicit units and state-bound plans. Use for reviewed parameter, sketch, feature, assembly or configuration operations.
日本語の概要は準備中です。原文の説明を表示しています。
1.5万 件 ・ 関連度順
概要と使いどころ
Prepare, execute and verify authorized Fusion CAD changes using resolved entities, explicit units and state-bound plans. Use for reviewed parameter, sketch, feature, assembly or configuration operations.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate reviewed Grafana APM evidence for request rate, error rate, and operational latency. Use when an application is slow, erroring, dropping traffic, regressing against a baseline, or needs a bounded request-rate, error, and p95 latency health assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Guide setup for and verify a reviewed, read-only Grafana Observability profile and its activated capability packs. Use when a user asks to set up Grafana access, verify profile readiness, discover available infrastructure, APM, log, IoT or business KPI packs, or troubleshoot why a Grafana pack cannot run.
日本語の概要は準備中です。原文の説明を表示しています。
Stage and verify Fusion exports, drawing PDFs, flat-pattern DXF, viewport images and local renders. Use for engineering deliverables, not automatic publication or release.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze reviewed Grafana log evidence for event patterns, error-rate changes, and enrolled security markers. Use when a user needs bounded log analytics for an incident window, error-log comparison, anomaly triage, operational debugging, or a cautious check of approved security signals.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect reviewed Grafana infrastructure evidence for host or fleet CPU usage, memory load, disk space, and system load. Use for server-health checks, capacity symptoms, resource saturation, disk pressure, cloud or local host comparisons, and bounded infrastructure triage.
日本語の概要は準備中です。原文の説明を表示しています。
Develop, challenge, and document Chisel processor microarchitecture designs before implementation. Use when discussing or writing design documents for processor pipelines, queues, issue logic, rename, ROB, LSU, caches, MSHRs, forwarding, wakeup, replay, flush, privilege, exceptions, or other cycle-accurate hardware mechanisms; when converting design conversations into stable Markdown specifications; or when reviewing a proposed Chisel CPU design for correctness, timing, area, verification cost, and cross-document consistency.
日本語の概要は準備中です。原文の説明を表示しています。
Document-driven workflow for implementing, reviewing, and verifying Chisel processor and memory-subsystem RTL. Use when Codex must work from maintained Architecture and Design, trace a complete integration surface, reason in synthesized-hardware terms, keep source-adjacent _codex.md summaries current, avoid redundant or overprotective logic, or run focused functional verification.
日本語の概要は準備中です。原文の説明を表示しています。
Generate multiple angles and shot types of a single product for ecommerce-ready image sets. Produces a coherent set (hero 3/4, front, side, back, detail macro, scale, packaging, in-hand) keeping product identity consistent across shots. Use when the user says "different angles", "product shots", "ecommerce image set", "shot list", "PDP gallery", or needs a multi-view set of one product. Part of the Creative Production set.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrator for the Creative Production skill set — turn a brief into reviewable visual assets. Routes to the right sub-skill (explore, moodboard, positioning, offer, ads-explorer, scene, shot, polish) based on where you are in the creative process. Use when the user gives a high-level creative goal like "make campaign assets", "I need visuals for X", "produce ad creative", "design product shots", or isn't sure which creative step they need. Delegates to creative-* skills.
日本語の概要は準備中です。原文の説明を表示しています。
Fallback for general coding work that does not match any specific sextant sub-skill. Use for lightweight tasks: config changes, style fixes, utility functions, one-off scripts, or tasks too small to warrant a dedicated workflow. All dedicated sub-skills take priority over this one — check these first: sextant:fix-bug (broken behavior), sextant:debug (unknown bug location), sextant:add-feature (new functionality), sextant:modify-feature (changing existing behavior), sextant:review-code (evaluating code), sextant:write-tests (test coverage), sextant:refine-requirements (ambiguous scope), sextant:plan (multi-step sequencing), sextant:ship (release prep), sextant:migrate (cross-module upgrade), sextant:security (vulnerability audit). Only use this skill when none of the above match.
日本語の概要は準備中です。原文の説明を表示しています。
Apply or adapt a complete dual-theme UI specification board for product interfaces. Use when Codex should build or restyle dashboard, admin, workspace, settings, or system UI with both light and dark themes, shared semantic tokens, structured component states, and a full preview board covering foundations, controls, navigation, data display, and feedback patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Apply or adapt a dual-theme neo-glow control board for UI kits, design-system previews, settings surfaces, admin panels, control rooms, and dense operational interfaces. Use when Codex should build or restyle interface work with bright white or dark control surfaces, compact neumorphic cards, vertical icon rails, blue/cyan halo accents, glowing active states, luminous toggles, and a board focused on control states, inputs, and specification details.
日本語の概要は準備中です。原文の説明を表示しています。
Apply or adapt a dual-theme liquid glass UI board for premium dashboards, workspace launchers, settings surfaces, design-system previews, and glossy interface concepts. Use when Codex should build or restyle interface work with frosted translucent panels, aurora glow accents, pill controls, circular glass actions, blurred color blooms, and a polished light-plus-dark material system.
日本語の概要は準備中です。原文の説明を表示しています。
Generate JSON wireframe with HTML preview
日本語の概要は準備中です。原文の説明を表示しています。
Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.
日本語の概要は準備中です。原文の説明を表示しています。
Navigate your projects. Get context, paths, status. Use when needing project overview or finding specific work.
日本語の概要は準備中です。原文の説明を表示しています。
The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.
日本語の概要は準備中です。原文の説明を表示しています。
Bridge Codex to web-based AI model products by packaging local task context, scrub-checking it, sending it through an approved browser surface to ChatGPT Pro, Claude, Grok, Gemini, or another web model, waiting for the answer, and returning the model response to the user or Codex. Also guide DevSpace-like MCP Connector Mode when the user wants ChatGPT Pro or another MCP-capable web host to access approved local workspaces without relying on Codex browser automation. Use when the user asks for GPT Pro, ChatGPT Pro, Claude web, Grok, Gemini web, web model bridge, external model consult, ask another model, second opinion, use a web AI model, browserless agent access to GPT Pro, MCP connector, DevSpace-like workflow, or send local repo context to a browser-based model for planning, review, debugging, architecture discussion, or implementation guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Generalize published Spectre and remote microarchitectural research into passive target prerequisites, defensive review, and approval-gated local validation. Use for shared runtimes, JavaScript isolates, edge workers, serverless platforms, browser sandboxes, remote timing, cache side channels, speculative type confusion, or Dynamic Process Isolation analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Authorized testing of LLM applications, agents, chatbots, RAG systems, guardrails, and tool-using model workflows. Use for LLM mode selection, jailbreak and prompt-injection assessment, guardrail bypass review, tool misuse, tool or system prompt disclosure, data exfiltration paths, model refusal/stop detection, bypass hypotheses, and hardening guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Assess package choices and generated dependency names, publisher or release anomalies, incident exposure, and changes in package risk reports. Use before trusting a new dependency, when a release changes unexpectedly, or when investigating a supply-chain alert.
日本語の概要は準備中です。原文の説明を表示しています。
Passive, pattern-calibrated risk discovery for authorized security research over an open-source project, repository URL, dependency, release, or local checkout. Use when the security research agent needs to find highest-risk areas, map attack surface, identify likely bug-hunting targets, prioritize security review, inspect structural/logical/security-critical code, compare vulnerable versus patched versions, reason from broad high-severity vulnerability families, or remember areas of interest for later attack-chain research.
日本語の概要は準備中です。原文の説明を表示しています。
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
日本語の概要は準備中です。原文の説明を表示しています。