「root」の検索結果

Think and work like an expert Instrumentation Engineer. Use when a task calls for Instrumentation Engineer judgment. Reasons from the process variable, its transduction chain, 4-20 mA loop integrity, and traceable calibration through ISA-5.1 P&IDs, NAMUR NE43 fault bands, ISO 5167 orifice sizing, and GUM uncertainty budgets while treating plugged impulse lines, double-applied square-root, ground-loop noise, and unrevalidated SIS bypasses as first-class failure modes.

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

Internal — for Boundless team members only. Cross-reference Boundless indexer API data, broker telemetry, and service logs to investigate production and staging operational issues. Use when the user wants to understand why slashings happened on prod/staging, diagnose prover or service failures in deployed environments, correlate market events with broker behavior, investigate fulfillment rate drops, look at prover/service logs, or perform any analysis that requires combining on-chain indexer data with off-chain broker telemetry and CloudWatch logs. Also use when the user asks to "investigate", "diagnose", or "find root cause" for prover, service, or market issues on live networks. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.

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

Analyze escaped defects and test suite health through blameless postmortems. Covers bug pattern analysis, test suite health reviews, 5 Whys root cause analysis, process improvement cycles, and postmortem/retro meeting templates with action item tracking. Use when: "QA retro," "escaped bugs," "postmortem," "quality incident," "defect analysis," "improvement cycle." Not for: live release go/no-go decisions — use release-readiness. Not for ongoing metric dashboards — use qa-metrics. Not for reviewing existing test code quality — use ai-qa-review. Related: qa-metrics, test-reliability, test-strategy.

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

Root cause based one-shot bug fix. debugger diagnosis → requirements.md generation → /execute. /bugfix "error description" Full investigation pipeline: debugger + gap-analyzer + standard verify. QA suggestion after successful fix.

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

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.

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

Analyze application error logs and monitoring platform exports (Sentry, Datadog, Rollbar) to identify error patterns, duplicates, and severity. Use when someone asks to "audit errors", "analyze exceptions", "find noisy alerts", "deduplicate error groups", or "triage production errors". Parses JSON/CSV error exports and produces categorized reports with root cause analysis.

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

Use DESIGN.md files to give AI agents a complete design system in plain text. Drop a DESIGN.md into your project root and any AI coding agent generates consistent, pixel-perfect UI matching that design. Use when: building UI with AI agents, maintaining design consistency across AI-generated components, recreating the look of existing websites.

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

Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent memory file. Use after feedback, a non-trivial bug fix, a failed attempt, or the third repetition of a pattern.

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

Refuses "flaky" as a diagnosis. Turns an intermittent failure into a reproduction by isolating it from the environment, naming the variable that controls it, forcing that variable, and measuring before and after with enough runs to count. Separates real defects from environment contention with evidence, and never retries to green or widens a threshold. Use when a test, performance check, or deploy step fails intermittently or passes on rerun.

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

加密链上交易 (加密 / 链上交易 (Crypto & On-chain Trading) — 以加密资产为标的、强调链上活动的主动交易认知操作系统：从「看叙事/选赛道 → 找标的 → 链上尽调与风控 → 选场所(DEX/CEX/链上合约) → 建仓与仓位管理 → 监控链上流向与情绪 → 退出与复盘」的完整决策链。覆盖 (a) 第一性张力 — **链上 on-chain (DEX 现货/AMM、钱包追踪 wallet tracking、资金流向 flow、MEV、memecoin、链上衍生品 Hyperliquid/GMX、自托管 self-custody, 'not your keys not your coins') ⇄ 链下 CEX (中心化交易所现货/合约 Binance/OKX/Bybit、订单簿、托管、出入金法币)**; **合约/杠杆/衍生品 (perps 永续、资金费率 funding、清算 liquidation、爆仓、做多做空、高频/择时) ⇄ 现货/价值/长持 (spot、HODL、定投 DCA、基本面/估值、'time in market > timing the market')**; **价值/基本面派 (协议收入、TVL、代币经济学 tokenomics、真实使用、估值模型) ⇄ meme/叙事/情绪派 (memecoin、narrative rotation 叙事轮动、attention is the asset、纯博弈/PvP、Ponzinomics)**; **链上数据/量化/客观 (on-chain analytics, Nansen/Arkham/Dune、聪明钱 smart money、链上指标、系统化/机械化) ⇄ 直觉/盘感/叙事阅读 (narrative、KOL alpha、社群情绪、tape reading)**; **自托管/去中心化/抗审查 (DeFi、自托管钱包、抗审查、'be your own bank') ⇄ 便利/合规/中心化 (CEX、合规出入金、KYC、托管、ETF)**; **主动交易/择时/高换手 (trading、波段、合约、撸毛/空投 airdrop farming、套利 arbitrage) ⇄ 被动配置/低换手 (配置 BTC/ETH、ETF、长期叙事 beta)**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量 + CLI 化) — 通用链: 叙事/赛道判断 (宏观周期/减半/流动性/板块轮动) → 标的发现 (链上扫链/聪明钱跟单/新币/叙事映射) → 尽调 due diligence (代币经济学/解锁 unlock/团队/合约审计/honeypot 检测/流动性与持仓分布) → 风控前置 (仓位 sizing/最大回撤/止损/相关性) → 场所与执行 (CEX vs DEX、滑点/MEV/gas、限价 vs 市价、TWAP) → 持仓监控 (链上流向/巨鲸/资金费率/解锁日历/情绪指标) → 退出与复盘 (止盈分批/再平衡/记录交易日志); 子流派 SOP: 链上 degen 打新与 memecoin 流程、合约交易者的资金费率与清算地图、空投/撸毛 farming、套利与 MEV、被动配置与定投; (c) 工具栈 — 链上分析 (Nansen 聪明钱/Arkham 实体标注/Dune 自建仪表盘/Dexscreener & DEX Screener 新币/GMGN & Photon & BullX memecoin 终端/Etherscan & Solscan 区块浏览器/DeBank 钱包总览/Token Terminal 协议基本面/DefiLlama TVL/Glassnode & CryptoQuant 链上指标)、交易场所 (CEX: Binance/OKX/Bybit/Coinbase; 链上现货 DEX: Uniswap/Jupiter/Raydium/Aerodrome; 链上衍生品: Hyperliquid/GMX/dYdX)、钱包与安全 (MetaMask/Rabby/Phantom 热钱包、Ledger/Trezor 硬件冷钱包、Revoke.cash 授权管理、honeypot/合约扫描)、行情与图表 (TradingView、CoinGecko/CoinMarketCap)、信息与聚合 (Twitter/X、Telegram、DeFiLlama、RootData/ICO 日历、解锁日历 Token Unlocks)、自动化 (交易机器人、链上 bot/sniper、Telegram trading bot); (d) 知识正典 — 注意加密交易 canon 偏少且新: 通用交易/风控经典 (Edwin Lefèvre 'Reminiscences of a Stock Operator'、Van Tharp 'Trade Your Way to Financial Freedom' 仓位管理、Mark Douglas 'Trading in the Zone' 交易心理、Michael Mauboussin、Nassim Taleb 'Fooled by Randomness/Antifragile')、加密原生 (Bitcoin whitepaper 中本聪、'The Bitcoin Standard' Saifedean、Vitalik 博客与 Ethereum whitepaper、'DeFi and the Future of Finance'、Lyn Alden 宏观、a16z crypto 文章、Messari/Delphi/Bankless 研报)、链上分析方法 (Glassnode/CryptoQuant 教程、Nansen/Arkham/Dune 文档、Dune Analytics SQL)、交易方法论散见于 podcast/Substack/Twitter thread 而非书; (e) figures/流派 — 价值/基本面派 (Vitalik Buterin 以太坊、Hasu/Su Zhu(争议)、Arthur Hayes BitMEX 创始人/宏观+衍生品、Raoul Pal、Lyn Alden 宏观、Cobie/Jordan Fish UpOnly podcast、DeFi 研究 Bankless Ryan Adams/David Hoffman); 链上分析派 (Nansen Alex Svanevik、Arkham、Adam Cochran、Ansem(blknoiz06) 链上交易、Murad memecoin supercycle、链上侦探 ZachXBT 反诈); 合约/衍生品派 (Arthur Hayes、GCR(GiganticRebirth) 传奇合约、Pentoshi、CryptoCred 技术分析、Tyler Durden); meme/叙事派 (Ansem、Murad、Cobie、各 Solana memecoin KOL); 宏观/周期派 (Raoul Pal、Lyn Alden、PlanB stock-to-flow(争议)、Benjamin Cowen 数据/周期); 量化/系统化 (各匿名量化、Hyperliquid 生态); 中文圈 (链上分析/合约 KOL、币圈大 V、播客如 '无人之境'/'Web3 佛学院'、研究机构如 Foresight/PANews/律动 BlockBeats); 反诈/安全 (ZachXBT、SlowMist 慢雾、go+ 安全); (f) 行业话术/黑话 — 现货 spot / 合约 perps 永续 / 杠杆 leverage / 多空 long-short / 爆仓 liquidation 清算 / 资金费率 funding rate / 开多开空 / 止损 SL 止盈 TP / 仓位 position sizing / 满仓梭哈 ape in / 梭 / FOMO / FUD / 钻石手 diamond hands / 纸手 paper hands / 韭菜 / 镰刀 / 庄 / 出货 / 拉盘砸盘 / 插针 wick / 针 / 上车下车 / 埋伏 / 潜伏 / 链上 on-chain / 钱包 wallet / 地址 / 聪明钱 smart money / 巨鲸 whale / 跟单 copy-trade / 老鼠仓 / 貔貅盘 honeypot / 貔貅 / rug 跑路 rug-pull / 归零 / 土狗 (memecoin/小币) / 金狗 (暴涨百倍) / meme 币 / 叙事 narrative / 赛道 / 板块轮动 / 撸毛 撸空投 airdrop / 女巫 sybil / 交互 / 解锁 unlock / 砸盘解锁 / 代币经济学 tomomics / TVL / APY APR / 无常损失 IL / 滑点 slippage / MEV / 三明治 sandwich / gas / 抢跑 frontrun / 貔貅检测 / 授权 approve / 撤销授权 revoke / 私钥 助记词 seed phrase / 冷钱包 热钱包 / 自托管 / 减半 halving / 牛熊 / 山寨季 altseason / 比特币市占率 BTC.D / 山寨 alt / 主流币 / DeFi 暑期 / GM / WAGMI / NGMI / 归零归零 / PvP / Ponzi 庞氏; (g) 争议/批

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

A strict code reviewer, pair programmer, debugger, and mentor for Python, Bash, Google Apps Script, JavaScript, and Swift/Apple platforms. Use when writing, reviewing, debugging, planning, or securing code, or for senior-level rigor, a security review, or mentoring. Mode triggers — REVIEW: (critique + refactor), EXPLAIN: (teach), MVP:/PROTOTYPE: (lean-but-safe), DEBUG: (root-cause), AUDIT: (report-first); default is pair-programming. Drives a spec→plan→TDD→verify loop with a deterministic-first, verify-before-asserting (anti-hallucination) discipline. Enforces a security floor (secrets, injection, input validation, isolation, least privilege, authn) and a backup/continuity floor on a phase-aware rigor ladder (Prototype→MVP→Production) — cheap ≠ insecure. Covers testing & fuzzing, SAST/secret-scan/type-check/supply-chain gates, multi-tenant data protection, resilience & DR, scalability, CI/CD, cloud/containers/DBs, and accessible UI — deep references read on demand.

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

Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six Sigma, root cause analysis, strategic decisions, process improvement, or asks for philosophers/ancients (Socratic, Aristotelian, Stoic method experts).

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

Diagnose an AWF (Agentic Workflow Firewall) failure from an error, workflow run URL, or symptom. Covers auth (api-proxy, enterprise/BYOK Copilot, OIDC, mcpg), ARC/DinD and self-hosted runners, alternative runtimes (gVisor/Kata/chroot), Squid/DNS/egress denials, CI and gh-aw safe-output failures, and suspected security regressions. Routes to the canonical diagnosis registry in docs/diagnostics.

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

Investigate an unexplained defect or unexpected behavior without changing application code. Use for root-cause diagnosis and an evidence-backed handoff, including a bounded unresolved result. Not for implementing a known fix, new features, or explanation-only questions.

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

Investigate an unexplained defect or unexpected behavior without changing application code. Use for root-cause diagnosis and an evidence-backed handoff, including a bounded unresolved result. Not for implementing a known fix, new features, or explanation-only questions.

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

Opt this repo into codeArbiter — scaffold the root-level .codearbiter/ state store.

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

MBB-level management consultant with mastery over structured thinking, frameworks, guesstimation, industry analysis, and executive-grade deliverables. Use this skill for: solving business problems, structuring cases, market sizing, profitability analysis, market entry, M&A, pricing, operations, digital transformation, org design, and any consulting deliverable (deck, memo, one-pager). Trigger on: "consulting framework", "MECE", "issue tree", "hypothesis-driven", "80/20", "McKinsey", "Bain", "BCG", "strategy consulting", "management consulting", "problem statement", "root cause", "executive summary", "due diligence", "case study", Porter's Five Forces, 3C's, Ansoff, value chain, or any structured business problem-solving and strategic analysis task.

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

Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".

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

Manage AI agent fleets in Herdr: tile root + sub-agents in one tab, start/prompt/wait/read/monitor via the herdr agent CLI, steer any pane; `help` lists every operation. Use for Herdr fleets. Don't use for tmux, screen, or non-Herdr terminals.

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

Applies the philosophical frameworks of Plato (ancient Greek philosopher, Theory of Forms, founder of the Academy) to structural, ethical, and epistemological problems. Use this skill whenever the user is grappling with organizational design, leadership ethics, defining abstract concepts, aligning incentives, or uncovering the root essence of a problem. Trigger this when discussing justice, governance, the nature of knowledge, structural harmony, or when a user is trapped by superficial metrics (shadows) and needs to find fundamental truths (Forms). Do not wait for the user to name Plato; proactively apply his dialectical reasoning to cut through illusions.

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

This skill channels the strategic and scientific reasoning of Demis Hassabis, CEO and co-founder of Google DeepMind, AlphaGo and AlphaFold, and 2024 Nobel Prize in Chemistry. Use this skill whenever you are evaluating AI for scientific discovery, tackling "root node" problems, designing reinforcement learning systems, or discussing AGI timelines, safety, and global governance. Reach for it when the user faces massive combinatorial search spaces, wants to apply AI to physical/biological sciences (like digital biology), or needs to balance rapid AI scaling with the rigorous scientific method. Apply these mental models to shift the focus from building consumer apps to using AI as the ultimate meta-solution for understanding reality.

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

Applies the frameworks of Aristotle (ancient Greek philosopher, logic, ethics, metaphysics, 384-322 BCE) to decision-making, ethics, and analysis. Use this skill whenever the user is grappling with moral dilemmas, character development, habit formation, finding balance (the Golden Mean), persuasive communication (rhetoric), or understanding the root causes and ultimate purpose (teleology) of a project or system. Reach for this skill even if the user doesn't name Aristotle, especially when discussing career fulfillment, long-term happiness (eudaimonia), balancing extremes, or structuring persuasive arguments.

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

Find and repair unresolved root causes.

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

Suede AI findings-only code review with full context: changed files, callers, contracts, and deploy surface. Covers TypeScript, React, Next.js, database, Swift/iOS, OWASP, accessibility, SEO, observability, commit hygiene, and deploy risk, ranked P0-P3 with file:line evidence and a fix path. Use when asked to review a diff, PR, branch, or commit range, find the bugs before merge, check a change for security or accessibility problems, or judge whether a change is safe to deploy. Emits findings and a ship gate, not a grade. NOT FOR: the A-F letter grade alone (use suede-code-grader); findings plus grade in one pass (use suede-code); making CI enforce the result on every merge (use suede-ci-gate); root-causing a live bug or failing test (a private Suede Labs companion, not in this pack).

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