1,486 件 ・ 関連度順
概要と使いどころ
Automatically organize invoices and receipts for tax preparation by extracting key information, renaming files consistently, and sorting into logical folders. Transform chaotic bookkeeping into tax-ready records.
日本語の概要は準備中です。原文の説明を表示しています。
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
日本語の概要は準備中です。原文の説明を表示しています。
Plan dependency-aware atomic commits for changes that span multiple logical concerns. Use when a refactor, feature, or API change would benefit from reviewable, independently meaningful commit boundaries. To triage an already-dirty working tree and propose commits for existing uncommitted changes, use `planning-commits` instead.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate repeated code and consolidate duplication when a shared abstraction improves correctness or maintenance. Use after introducing similar logic or when repeated changes reveal a missing source of truth.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a structured attorney work product memorandum from an initial client consultation for commercial litigation. Extracts verifiable facts from uploaded documents, builds a chronological narrative, identifies parties and contracts, flags preliminary legal claims and defenses, and produces a prioritized action plan. Triggers at matter intake when a business client needs a foundational case evaluation document for a pre-filing commercial dispute.
日本語の概要は準備中です。原文の説明を表示しています。
一站式法律服务平台 — 专业法律咨询 + 要素式/通用起诉状起草 + 刑事专项材料辅助 + 法条分析与法规检索。flk.npc.gov.cn API实时法条优先，不可用时AI知识库降级兜底；以22类法律领域覆盖矩阵约束路由边界；支持35个起诉状模板、5类刑事专项材料辅助；内置Logic Doctor逻辑自检、诉讼时效追踪及10类异常容错处理（含连续失败熔断）；渐进式意图收敛协议（3轮状态机）；混合意图自动任务拆解（按依赖排序→合并→顺序执行）。非标准案由自动使用通用模板。
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a state-court complaint for breach of a real property purchase agreement. Triggers when the user needs to initiate a lawsuit for breach of a real estate purchase contract, purchase agreement breach, or buyer/seller contract dispute. Covers caption, jurisdiction/venue, party allegations, chronological facts, contract elements, damages, and prayer for relief.
日本語の概要は準備中です。原文の説明を表示しています。
当AI智能体需要处理以下情形时触发本技能： 1. 当前案件/问题在现行法律中没有直接、明确的规定（法律漏洞）； 2. 需要参考已有判例、相似案件或相近法律规范来推导当前问题的处理方案； 3. 用户明确要求"参照""比照""类推适用"某一规范或案例； 4. 在法律论证中需要以"相似案件相似处理"（Like cases should be treated alike）原则支撑结论； 5. 需要评估两个或多个案件/规范之间的相似性与差异性，以判断能否进行类比； 6. 在合同解释、侵权责任认定、行政处罚裁量等场景中，需要借助类似情形的处理经验形成论证。 本技能的核心是：识别相似性基础（tertium comparationis），论证类比的正当性，并在此基础上得出合理的法律结论。
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial code review using attacker mindset — trust boundary, attack surface, business logic, and defense evaluation
日本語の概要は準備中です。原文の説明を表示しています。
YAML-based DAG workflow engine with topological execution and failure strategies
日本語の概要は準備中です。原文の説明を表示しています。
Task-sized forensic analysis of Vivado synthesis and routed timing evidence for processor RTL. Use when Codex must trace a named setup or hold path, audit whole-design timing populations, compare implementation runs, map primitive, LUT, CARRY, BRAM, DSP, MUXF, register, and routed-net stages back to Chisel or generated RTL, distinguish logic from routing pressure, identify missing DCP queries, or write an evidence-backed timing report. This skill is read-only by default and stops at ranked modification directions. Use optimize-chisel-fpga-timing for RTL edits and routed A/B implementation closure.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Decompile a function to C-like pseudocode for human-readable analysis. Use to understand function logic, review control flow, or prepare for code pattern matching.
日本語の概要は準備中です。原文の説明を表示しています。
Generate several distinct UI directions for a screen or flow before committing to one. Produces 2-4 named interface directions with layout logic, component choices, and tradeoffs, optionally with generated mockup images. Use when the user says "ideate the UI", "give me layout options", "design directions for this screen", "explore the interface", or after context/research and before prototyping. Part of the Product Design set.
日本語の概要は準備中です。原文の説明を表示しています。
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
日本語の概要は準備中です。原文の説明を表示しています。
Up-to-date Zig programming language patterns for version 0.17.0-dev (0.16.0 stable APIs plus the 0.17 deltas). Use when writing, reviewing, or debugging Zig code, working with build.zig and build.zig.zon files, or using comptime metaprogramming. Critical for avoiding outdated patterns from training data - especially std.net→std.Io.net (requires Io instance), std.time timestamps removed (use clock_gettime), std.Thread.Mutex/Condition/sleep removed (use pthreads), std.crypto.random removed, build system APIs (root_module, Compile methods→Module methods), I/O APIs (buffered writer pattern), container initialization (.empty/.init), allocator selection (DebugAllocator), ArrayList now unmanaged by default, @typeInfo lowercase fields (.@"struct" not .Struct), and removed language features (async/await, usingnamespace). Also covers 0.17.0-dev deltas: b.args→run_cmd.addPassthruArgs(), std.gpu→std.spirv, @bitCast logical-bit (endian-agnostic) semantics, build configurer/maker split, and the zig-pkg/ package directory. Also covers quality tooling Zig does not ship: coverage with kcov (and why in-file tests wreck the denominator), detecting unused private functions (neither the compiler nor zlint's unused-decls finds them), duplicate detection with jscpd, zlint (NOT the same-named X.509 linter in Homebrew), and the built-in fuzzer whose testOne now takes *std.testing.Smith rather than []const u8.
日本語の概要は準備中です。原文の説明を表示しています。
Representations for hierarchical skill structures including knowledge graphs and ontological decomposition
日本語の概要は準備中です。原文の説明を表示しています。
Design resilient React error handling with Error Boundaries, Sentry integration, recovery UI, retry patterns, and graceful degradation. Activate on: error boundary, crash recovery, Sentry, error fallback UI, retry logic, unhandled exceptions. NOT for: form validation errors (use form-validation-architect), API error codes (use api-architect).
日本語の概要は準備中です。原文の説明を表示しています。
Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-skill that orchestrates the discourse skill suite: routes between steel-man-argument, socratic-questioning, toulmin-argument-analysis, logical-fallacy-detector, bad-faith-rhetoric-detector, discourse-elision-analyzer, forensic-speech-structure, and productive-discourse-facilitator. Use when analyzing conversations, facilitating discourse, or operating as a dialogue copilot. Maintains mode (silent analysis, coaching overlay, active facilitator) and decides which skills to invoke based on conversation dynamics.
日本語の概要は準備中です。原文の説明を表示しています。
Tracks cumulative LLM costs across DAG execution and makes real-time decisions to stay within budget. Downgrades models, skips optional nodes, or stops early when cost exceeds thresholds. Use when managing execution budgets, analyzing cost breakdowns, or optimizing model routing for cost. Activate on "cost budget", "too expensive", "reduce cost", "cost optimization", "model downgrade", "budget exceeded". NOT for LLM model selection logic (use llm-router), pricing comparisons across providers, or billing/invoicing.
日本語の概要は準備中です。原文の説明を表示しています。
Describe patterns that may indicate bad-faith or manipulative communication including gish gallop, whataboutism, tone policing, motte-and-bailey, sealioning, lying by omission, deflection, and strategic evasion. Use when the user suspects manipulation, notices repeated non-engagement, wants to analyze debate tactics, or mentions 'bad faith', 'deflection', 'manipulation', 'dodging the question', 'avoiding the issue', 'gaslighting', 'moving goalposts'. Describes behavioral patterns without making psychological diagnoses.
日本語の概要は準備中です。原文の説明を表示しています。
Build production computer vision pipelines for object detection, tracking, and video analysis. Handles drone footage, wildlife monitoring, and real-time detection. Supports YOLO, Detectron2, TensorFlow, PyTorch. Use for archaeological surveys, conservation, security. Activate on "object detection", "video analysis", "YOLO", "tracking", "drone footage". NOT for simple image filters, photo editing, or face recognition APIs.
日本語の概要は準備中です。原文の説明を表示しています。