4,632 件 ・ 関連度順
概要と使いどころ
Use tmux from the command line to run, drive, and monitor terminal programs as a coding agent (detached sessions, send-keys input injection, capture-pane output polling, formats, completion detection, and control mode). Use when a task needs long-running or interactive processes (builds, tests, servers, REPLs, watch modes, TUI apps) kept alive across turns or inspected live; skip when plain `cmd > log 2>&1 &` is enough.
日本語の概要は準備中です。原文の説明を表示しています。
Detects when a stated outcome names a specific instance — a mechanism-as-means or a single named product — where a category was meant, and returns a neutral fork for the lead to show the user, or nothing. Invoked by launch commands at outcome capture, in place of the verbatim echo.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic backlink building for indie founders. Covers 5 channel types ranked by GEO + SEO ROI: Wikipedia (entities), authoritative media (PR), industry reviews (G2/Capterra/Product Hunt), Reddit/Quora discussions, and HARO/Featured.com expert quotes. Designed for 0→1 sites where domain authority is the bottleneck. Aligns with 2026 Google/Bing GEO guidance: backlinks are the strongest brand-authority signal AI search engines use to decide citations. Defaults to dev/B2B link sources; for 2C products (education, consumer apps) authority links differ — see gingiris-seo-geo/references/2c-adaptation.md.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews tokio async runtime usage for task management, sync primitives, channel patterns, and runtime configuration. Covers Rust 2024 edition changes including async fn in traits, RPIT lifetime capture, LazyLock, and if-let temporary scoping. Use when reviewing Rust code that uses tokio, async/await patterns, spawn, channels, or async synchronization. Also covers tokio-util, tower, and hyper integration patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Register and implement PydanticAI tools with proper context handling, type annotations, and docstrings. Use when adding tool capabilities to agents, implementing function calling, or creating agent actions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an implementation against its plan with a hostile peer agent, debate findings to consensus, and drive fix waves until the auditor runs dry. Use when a done-claim needs verification the implementer cannot game ("hostile review", "adversarial audit", "is this PR faithful", "find the escape hatches") — the loop that beats the laziness bias with its own game theory.
日本語の概要は準備中です。原文の説明を表示しています。
Produce visual PR evidence — a screenshot or video — whenever a change has on-screen impact. Tests are never a substitute; a change can be backend by cause and visible by effect. Capture via the project's e2e harness on a pu box, or by driving a live kolu with the chrome-devtools MCP; host on a GitHub release and post a `## Evidence` comment. Triggers on "post evidence", "screenshot the change", "record a video of this", "show it working", "prove it", or finishing any change whose effect is visible on screen.
日本語の概要は準備中です。原文の説明を表示しています。
Launch the kolu dev server on two RANDOM free ports so it never collides with the running production `kolu.service`, remember the ports for the rest of the session, and tear down only the dev instance. Load before running the app locally — for evidence capture, driving a live kolu with the chrome-devtools MCP, or any `just dev` you'd otherwise run by hand. Triggers on "run kolu locally", "launch the dev server", "boot kolu", "drive a live kolu", "start the app to screenshot it", or before pointing chrome-devtools at a local kolu.
日本語の概要は準備中です。原文の説明を表示しています。
Tax optimization strategies analyzer. Identifies high-impact tax savings across tax-loss harvesting, tax-advantaged accounts (401k, IRA, HSA), Roth conversions, backdoor and mega backdoor Roth, charitable giving, business deductions, capital gains harvesting, state tax minimization, and estate tax planning. Produces FINANCE-TAXES.md with prioritized strategies and estimated annual tax savings.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging method: 5-step root-cause analysis (capture, isolate, hypothesize, investigate, fix & verify) plus common bug-pattern reference. Use when errors, exceptions, test failures, or unexpected behavior appear. Loaded automatically by the debugger agent.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
日本語の概要は準備中です。原文の説明を表示しています。
Operate the Ryuumonbuchi MCP server for headless Ghidra reverse engineering. Use when driving decompilation, disassembly, patching, type and symbol recovery, memory edits, transactions, and Ghidra project analysis through a Ryuumonbuchi server (stdio or streamable HTTP). Covers the safe read-only-first workflow, session and address discipline, mutation and transaction rules, headless.run, task and error recovery, raw ghidra.call/ghidra.eval/ghidra.script escape hatches, and a sleep/timing-gate bypass recipe.
日本語の概要は準備中です。原文の説明を表示しています。
保险方案顾问。险种推荐、产品对比、保费计算、理赔指南、定期寿险、健康险方案。Insurance advisor with recommendation, comparison, premium calculation, claim guide, term life, health insurance. Use when you need insurance advisor capabilities. Triggers on: insurance advisor.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a structured initial contact summary memorandum from a potential client's first interaction with the firm. Captures case facts, liability indicators, damages, insurance details, and screening criteria. Use during client intake to support conflict checks, case evaluation, and engagement decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Financial services advisory skill for consulting engagements. Use when preparing research briefs on banking, insurance, capital markets, or wealth management, building performance benchmarking frameworks, regulatory impact assessments, or stakeholder materials for CFOs, CROs, and technology leaders.
日本語の概要は準備中です。原文の説明を表示しています。
Subsidiaries, cap table, D&O insurance tracking
日本語の概要は準備中です。原文の説明を表示しています。
Quantify cyber risk using FAIR methodology with Monte Carlo simulation, assess control effectiveness against NIST CSF/CIS/ISO 27001 frameworks, evaluate risk appetite alignment, and analyze cyber insurance coverage adequacy. Covers threat landscape mapping, asset valuation, loss event frequency and magnitude estimation, annualized loss expectancy calculation, control gap analysis with ROI ranking, residual risk assessment, and insurance policy gap modeling at 90th/95th/99th percentile loss scenarios. Use when building risk registers, preparing board-level risk dashboards, evaluating security investment priorities, assessing cyber insurance coverage, or auditing any organization's risk quantification maturity per NIST RMF, ISO 27005, or FAIR standards.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a U.S. Consulting Services Agreement covering scope, compensation (hourly, fixed, retainer, hybrid), independent contractor classification, IP ownership, confidentiality, indemnification, liability caps, insurance, and dispute resolution. Use when drafting consulting contracts, professional services agreements, or independent contractor agreements.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses physical and transition climate risk for CRE properties and portfolios. Translates hazard exposure (flood, wind, wildfire, extreme heat, sea level rise) and regulatory/market shifts into financial impacts on NOI, cap rates, insurance costs, and tenant demand. Produces dollar-denominated risk, not abstract hazard scores.
日本語の概要は準備中です。原文の説明を表示しています。
Activates Warren Buffett's complete investment thinking system. The following scenarios must trigger it: analyzing any stock or company, evaluating investment opportunities, interpreting financial reports/annual reports/shareholder letters, assessing business moats or competitive advantages, evaluating management quality and integrity, making buy/hold/sell decisions, understanding core value investing concepts (compounding/intrinsic value/margin of safety/circle of competence/Mr. Market), analyzing any industry (insurance/banking/consumer/media/energy/railroads/technology), handling capital allocation/buybacks/dividends questions, assessing market sentiment and macro risks, exploring when to sell, analyzing institutional imperative or management behavior. Even if the user does not mention "Buffett," proactively trigger whenever the topic involves investment analysis, business quality assessment, or investment decision-making.
日本語の概要は準備中です。原文の説明を表示しています。
Structures insurance company financial analysis with combined ratio, reserve adequacy, and capital metrics. Use when analyzing insurance financials, evaluating combined ratios, or assessing reserve strength.
日本語の概要は準備中です。原文の説明を表示しています。
Adaptive conversion of LaTeX, PDF, or Markdown sources into a complete Word .docx that follows a user-supplied .docx template. Use when pandoc --reference-doc alone is not enough — for thesis, dissertation, report, or institutional Word formatting that needs cover pages, declarations, TOC, heading numbering, captions, three-line tables, equations, citations, and visual verification.
日本語の概要は準備中です。原文の説明を表示しています。
Guide a researcher step by step into an unfamiliar research field, or decode a paper, abstract, figure caption, or referee comment they cannot parse. Builds understanding in rungs (motivation, vocabulary, core framework, methods, frontier), anchored to what the user already knows, with a checkpoint before each advance. Use when the user says they are new to a field, asks what a research area or method is, says an explanation was too technical, asks to be walked through something step by step, asks for a reading path, or supplies dense research text. Trigger even when the user only names an unfamiliar field or pastes an abstract without asking to be taught. Do not trigger for a one-line summary, a short overview request, or a direct factual answer; do not use it for translation, editing, search, debugging, or specialist questions inside the user's own field. Also trigger in other languages, including Chinese such as 入门, 一步一步讲, 看不懂, 这篇论文讲什么, 帮我理解这个领域.
日本語の概要は準備中です。原文の説明を表示しています。