「engineering」の検索結果

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".

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

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.

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

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.

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

Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".

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

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.

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

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.

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

Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports. Use when asked to "write an ADR", "map the architecture", "document this decision", "onboarding docs", or "what changed".

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

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".

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

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.

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

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.

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

Expert guide for Vercel AI SDK (Core, UI, RSC), streaming structured data, multi-provider model switching, tool calling loops, and React 19/Next.js 15 AI engineering / Panduan ahli Vercel AI SDK, streaming data terstruktur, dan integrasi AI pada React 19/Next.js 15.

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

Expert guide for error handling patterns, resilience engineering, retry strategies, circuit breakers, and graceful degradation across React, Next.js, and Node.js / Panduan ahli pola penanganan error, rekayasa ketahanan, strategi retry, circuit breaker, dan degradasi anggun di React, Next.js, dan Node.js.

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

Expert guide for deterministic prompt prefix engineering, KV-cache locking for Gemini 4 Pro / Claude 5.5 / GPT Astra 6, canonical tool sorting, and achieving 90%+ prompt cache hit rates / Panduan ahli rekayasa prefix prompt deterministik, penguncian KV-cache untuk Gemini 4 Pro / Claude 5.5 / GPT Astra 6, pengurutan kanonikal tool, dan pencapaian 90%+ cache hit rate.

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

Expert guide for reverse-engineering UI/UX interactions from screen-recordings and spatial video, extracting animation spring curves, and generating pixel-perfect Tailwind CSS v4 and Framer Motion code / Panduan ahli rekayasa balik interaksi UI/UX dari rekaman layar dan video spasial, ekstraksi kurva pegas animasi, dan pembuatan kode presisi Tailwind CSS v4 serta Framer Motion.

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

Expert guide for Data Pipelines, ETL/ELT, and Analytics Engineering. Covers dbt, Apache Airflow, Dagster, BigQuery, ClickHouse, and DuckDB / Panduan ahli untuk Data Pipelines, ETL/ELT. Mencakup dbt, Airflow, Dagster, BigQuery, ClickHouse, dan DuckDB.

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

Expert guide for engineering and optimizing ultra-large context windows (2M+ tokens) across Gemini 4 Pro, Claude 5.5, and GPT Astra 6 — context partitioning, retrieval-augmented context injection, sliding window strategies, and cost-aware token budgeting / Panduan ahli rekayasa dan optimasi context window ultra-besar (2M+ token) di Gemini 4 Pro, Claude 5.5, dan GPT Astra 6 — partisi konteks, injeksi konteks berbasis retrieval, strategi sliding window, dan penganggaran token sadar-biaya.

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

Sovereign Anti-AI Slop Directive & Enforcement Engine (2026 Unified Edition). Absolute zero-tolerance standard for lazy placeholders, conversational fluff, syntax narration, speculative over-engineering, hallucinated code, generic UI clichés, and 38 mandatory rules (R-01 to R-38) with Liveliness Dials (ENERGY/RHYTHM/MOTION), Two Usage Modes (During vs Audit After), and Delivery Gate verification / Doktrin dan mesin penegakan anti-AI slop mutlak v5.0.

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

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'.

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

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.

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

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.

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

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.

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

Software design principles, patterns, and architecture from SOLID through distributed systems. Covers the five SOLID principles with violations and fixes, DRY/KISS/YAGNI heuristics, separation of concerns, 12 GoF design patterns organized by intent (creational, structural, behavioral), architectural patterns (MVC, MVP, MVVM, layered, hexagonal, microservices, event-driven), coupling and cohesion metrics, dependency injection, and the design decision framework for choosing between competing approaches. Use when making design decisions, reviewing architecture, refactoring code, or teaching software engineering principles.

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

NASA Systems Engineering methodology mapped to cloud operations. Use when planning, executing, verifying, or documenting OpenStack cloud infrastructure following NASA SP-6105 and NPR 7123.1 processes. Provides phase gate criteria, document templates, and cross-references for all 7 SE lifecycle phases applied to cloud deployment and operations.

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