2,108 件 ・ 関連度順
概要と使いどころ
AI DevKit · Track dev-lifecycle / structured-debug progress on a durable task with the ai-devkit task CLI. Use to record phase, progress, next step, blockers, and validation evidence.
日本語の概要は準備中です。原文の説明を表示しています。
AI DevKit · Guide structured debugging before code changes by clarifying expected behavior, reproducing issues, identifying likely root causes, and agreeing on a fix plan with validation steps. Use when users ask to debug bugs, investigate regressions, triage incidents, diagnose failing behavior, handle failing tests, analyze production incidents, investigate error spikes, or run root cause analysis (RCA).
日本語の概要は準備中です。原文の説明を表示しています。
Query the local AST-derived code graph (functions, classes, calls, imports) for structural codebase questions — what calls X, what does Y import, where is Z defined, blast radius of a change. The graph rebuilds automatically after each agent turn; use hivemind_graph_search and hivemind_graph_neighborhood tools (no manual build step).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user types /hep-storm, mentions @Hephaestus storm, or asks to force-robustly drive a loop-worthy goal (apps, sites, agents, automations, debugging, multi-step research, data/report generation) to a verified finish. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs a verifier-first loop that does not stall, run away, or claim false success. Trivial questions are answered directly, not stormed.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user types /hep-storm or /agentlas-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.
日本語の概要は準備中です。原文の説明を表示しています。
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or agent; brief a colleague taking over; prepare a shift change summary; or onboard someone mid-task. Produces ready-to-use handoff documents covering current status, next steps, known issues, technical context, and communication templates for both planned and unplanned transfers.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a product walkthrough, bug report video, Loom, or ScreenPal using Minutes transcription plus visual review. Use when the user wants a recorded demo or bug clip turned into a durable brief with transcript, key frames, issues, and next steps.
日本語の概要は準備中です。原文の説明を表示しています。
Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never curated prose.
日本語の概要は準備中です。原文の説明を表示しています。
Sets up and maintains isolated Claude Code CLI profiles to run Kimi, MiniMax, DeepSeek, GLM, StepFun or Anthropic in separate terminal windows. Use for multi-provider setup, switching models, csk/csd/csg aliases, CLAUDE_CONFIG_DIR, or ~/.claude-profiles. Owns profile-drift troubleshooting (missing skills/hooks, symlink drift, settings drift) and context-window setup ([1m] marker vs CLAUDE_CODE_MAX_CONTEXT_TOKENS).
日本語の概要は準備中です。原文の説明を表示しています。
Open a pull request for octane work. Load before creating the branch, commit, changeset, or PR, including when opening a PR is the tail step of a task that was about something else.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a landing page or funnel step and produce a prioritised CRO test plan. Use when asked to improve conversion rate, audit a landing/signup/checkout page, reduce funnel drop-off, or plan A/B tests for a page. Produces a CRO plan — a heuristic conversion audit, the diagnosed friction, prioritised test hypotheses (ICE), test designs with sample-size math, and the measurement guardrails.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 年终奖怎么算, 13薪和年终奖有什么区别, 年终奖怎么交税, 单独计税还是并入综合所得, 年终奖被扣了怎么办, 离职了年终奖还发吗, 怎么问 HR 年终奖, or understand a year-end bonus in mainland China. Produces how the person's bonus is likely calculated from their documents, the 13薪 versus discretionary bonus distinction, the tax options with a worked comparison marked to confirm, questions to ask HR or the manager in writing, and the steps if a bonus is withheld after resignation, all marked to confirm against current rules. Not tax or legal advice.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 帮我写期末评语, 学生评语, 班主任评语, 综合素质评价评语, 素质报告单评语, or write end-of-term comments for a class in China. Produces individual comments in Chinese, warm and specific to each student, in the second person, built from the teacher's notes: a real strength with an example, one growth area framed as a next step, and encouragement, with no labels, no comparison between students and no repeated stock phrases across the class.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 质量追溯体系怎么建, 产品追溯方案, 批次追溯, 一物一码, 客户要求可追溯性, 召回演练, 正向追溯和反向追溯, or plan product and batch traceability in a Chinese factory. Produces a traceability plan in Chinese: the trace unit and coding rule, the data to capture at each process step (material lots, work orders, equipment, people, inspection results), forward and backward trace paths, record retention, a mock recall drill with a target time, gaps against the current system, and a phased rollout, with industry rules (food, medical devices, automotive) marked to confirm.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 等保怎么做, 等保 2.0 定级, 等保备案和测评流程, 等保三级要求, 我们的系统需要过等保吗, or prepare an information system for China's Multi-Level Protection Scheme (MLPS 2.0, 网络安全等级保护). Produces a grading recommendation (定级) with the reasoning for the expert review, the filing (备案) and assessment (测评) steps and their usual timing, a gap checklist across the ten control areas of GB/T 22239-2019, and a remediation plan, marked as preparation for a licensed assessor.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 医保怎么报销, 异地就医怎么备案, 住院能报多少, 门诊报销比例, 手工报销要什么材料, 惠民保值不值得买, or work out what China's basic medical insurance (医保) will pay for a treatment. Produces the person's scheme (职工医保 or 居民医保), how a claim works for this case (direct settlement or manual reimbursement), an out-of-pocket estimate built from the city's own deductible, rate and cap, the cross-region registration (异地就医备案) steps, and the documents to keep.
日本語の概要は準備中です。原文の説明を表示しています。
Capture everything an outgoing club secretary, chair, or organizer carries in their head before they disappear — accounts and logins with owners, the annual rhythm calendar, key relationships and their quirks, the unwritten rules, and the first-90-days guide for the successor. Use when a committee member is stepping down, when someone says 'it all lives in Linda's head', or right after elections. Produces a complete handover pack plus the one-hour handover meeting agenda.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 数据出境要申报吗, 数据出境安全评估还是标准合同, 个人信息出境标准合同怎么备案, 我们把数据传到海外总部合规吗, or decide how to transfer data out of mainland China lawfully. Produces a data map of what leaves China, the route that applies (an exemption, the personal information export standard contract, certification, or a CAC security assessment) with the thresholds to confirm, the filing steps, and the documents to prepare, including the personal information protection impact assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Set a boundary with someone — a friend, family member, coworker, or partner — clearly and kindly, with the actual words and a plan for the pushback. Use when asked how do I set a boundary with, I need to say no to, someone keeps overstepping, or help me set limits with. Produces a read on the boundary you actually need, a warm-but-firm script to state it (without over-explaining or apologizing it away), how to hold it when they push back or guilt-trip, and what to do if they don't respect it — because a boundary you can't state and hold isn't a boundary.
日本語の概要は準備中です。原文の説明を表示しています。
Interview someone about their working life and turn the answers into a master CV inventory: every role, project and achievement with real numbers, before any CV is tailored. Use when asked to build my master CV, get my experience down properly, I don't know what to put on my CV, or as the first step before a tailored CV. Produces a structured inventory of roles, achievements in a fixed shape with evidence and numbers, skills with proof, and a list of gaps to fill. Never invents a number.
日本語の概要は準備中です。原文の説明を表示しています。
Write a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report an issue, or turn 'it's broken' into an actionable ticket. Produces a structured report — a precise title, steps to reproduce, expected vs. actual, environment, severity/priority, and evidence — so a developer can reproduce and fix it without a back-and-forth.
日本語の概要は準備中です。原文の説明を表示しています。
Run a family meeting to make a big care decision together. Use when asked help me run a family meeting about care, we need to decide together about mom's care, my siblings and I disagree about our parent, or facilitate a care decision. Produces an agenda and structure for the meeting, how to prepare (facts, options, everyone's input), ground rules to keep old family dynamics from derailing it, how to include the person being cared for, ways to work through disagreement toward a decision, and clear next steps with owners. Not legal, medical, or financial advice.
日本語の概要は準備中です。原文の説明を表示しています。
Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.
日本語の概要は準備中です。原文の説明を表示しています。
Triage a raw bug report into something a team can act on — clean repro steps, a defensible severity/priority, environment, likely area/owner, and duplicate check. Use when asked to triage this bug, set severity and priority, is this a P1, or clean up this bug report for the backlog. Produces the normalized repro, a severity and priority with the reasoning (impact × frequency × workaround), the environment/metadata, a suspected component and owner queue, and a duplicate/related-issue check — flagging when info is missing rather than guessing.
日本語の概要は準備中です。原文の説明を表示しています。