「engineer」の検索結果

Design a game day — simulated failure scenario, runbook, and post-event review. Use when asked to "run a game day", "plan a failure drill", or "simulate an outage".

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

Evaluate model performance — check for accuracy drops, data drift, and error patterns. Use when asked about "model accuracy dropped", "evaluate the model", "check for drift", or "model performance".

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

Build an ML pipeline — from data to trained model to serving endpoint. Use when asked to "build ML model", "train a model", "prediction pipeline", "classification", or "regression".

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

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

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

Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".

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

System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

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

Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".

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

Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".

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

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

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

Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".

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

Spawn-count analytics for the tonone roster — which agents this project actually uses, from local session transcripts. Use when "which agents do we actually use", "show tonone stats", "prune the roster", or before running apex-profile.

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

Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.

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

Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".

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

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

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

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

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

Reach ANY tonone specialist on demand, even ones not installed in this session's roster — no restart needed. Use when asked "which agent handles this", "reach a specialist we didn't install", "route this to the right agent", or whenever a scoped apex-profile roster is missing the right hat for the job.

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

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

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

Evidence-first expert knowledge handoff skill. Use when a founder, senior engineer, salesperson, support lead, consultant, or other domain expert is leaving, changing roles, or needs their judgment made reusable. It turns consented documents, chat, meeting notes, interviews, and explicit facts into a traceable handoff package. Trigger on requests such as: "capture this expert's judgment", "prepare a departure handoff", "make an onboarding mentor", "extract the decision rules", or "把专家经验交接下来".

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

The Relic of a retiring engineering lead — judgment, intuition, and the way he taught people, kept after the person left the building. 一位退休技术主管的「专家 Relic」：人离开了公司，判断逻辑、经验直觉和带人的方式留下来。

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

Provides Site Reliability Engineering best practices for SLOs, SLIs, SLAs, error budgets, toil reduction, reliability reviews, and capacity planning. Use when defining service objectives, measuring reliability, reducing toil, planning capacity, or when user mentions 'SRE', 'SLO', 'SLI', 'SLA', 'error budget', 'toil', 'reliability', 'on-call', 'capacity planning'.

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

Use when working with the non-metallic engineering materials — polymers, ceramics, or composites — and you need to reason about structure, processing, or properties. Covers thermoplastics versus thermosets, chain structure, glass transition, and viscoelasticity in polymers; ionic and covalent bonding, sintering, brittleness, and Weibull statistics in ceramics; and fiber-reinforced laminates, matrix and reinforcement roles, the rule of mixtures, and anisotropy in composites. Reach for it to choose a plastic, understand why a ceramic fails, or predict the stiffness of a laminate.

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

Systematic materials selection for engineering design using performance indices, Ashby charts, multi-constraint optimization, and case-based reasoning. Covers the five-step Ashby method — function, objective, constraint, free variable, index — with worked examples for stiffness-limited beams, strength-limited ties, thermally shocked vessels, and minimum-cost components. Use when choosing among metals, polymers, ceramics, and composites under competing objectives.

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

Metallurgy of the major nonferrous structural and engineering alloys — aluminum, copper, titanium, nickel, magnesium, and their strengthening mechanisms. Covers precipitation (age) hardening in Al-Cu and Al-Zn-Mg systems, solid-solution strengthening in brass and bronze, alpha-beta titanium, nickel superalloys with gamma-prime, and the trade-offs in density, strength, corrosion resistance, and cost that decide when to leave steel for a lighter or more specialized metal.

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

Classical control and system dynamics for engineered systems — feedback and closed-loop control, transfer functions and block diagrams, poles/zeros and stability, time-domain response (rise time, overshoot, settling time), PID controllers and tuning, and frequency response (Bode plots, gain and phase margin). Traces feedback control from the flyball governor to modern controllers. Use when analyzing feedback loops, designing or tuning a PID controller, assessing stability from poles or margins, or characterizing transient response of a dynamic system.

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