「engineering」の検索結果

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

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

Reverse engineer and security-test Telegram bots — API analysis, callback interception, exploit discovery, and vulnerability documentation

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

Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

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

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

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

Implement and finalize one ready rolling-wave slice in one invocation while preserving the lifecycle boundary between implementation and independent review. Use when the user wants a slice delivered end to end without manually invoking implement-slice and finalize-slice, wants main-local implementation by default with workers only when delegation pays, followed by mandatory fresh-context finalization, or says deliver, implement and finalize, or take the slice through review.

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

Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.

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

Finalize an implemented rolling-wave slice for user review. Use when the user wants Codex to review the current branch state against a ready-for-review or in-review slice contract, confirm and fix required findings, repeat review and verification until no required findings remain, ask before accepting findings that materially change project shape or contradict project assumptions, record review state, and leave the clean slice in review for complete-slice.

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

Draft a pull request description from the current branch diff plus rolling-wave project context. Use when the user wants PR body text, changes, potential risks, or reviewer notes for a branch, especially after completing a rolling-wave slice. Defaults to the Git Town parent branch when no base branch is named.

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

Review local git changes before opening a PR or merging. First review all local tracked and untracked files; if none exist, review the current branch against a requested base branch or the Git Town parent branch. Use zero to three review subagents only when risk, diff size, language specificity, or uncertainty justifies the token cost, then report high-confidence bugs, regressions, risky assumptions, and missing tests. Use when the user asks for code review, local review, branch sanity check, pre-PR review, or review of work-in-progress changes.

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

Produce a short executive summary for the current rolling-wave project. Use when the user wants a concise status update, investor/team-friendly summary, leadership summary, project progress snapshot, or TL;DR of completed slices, the current slice plan, and upcoming slices.

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

Implement a ready rolling-wave slice without locking it down with broad tests yet. Use when the user explicitly wants to code the current docs/rolling-wave/{project}/slices/NNN-slug.md slice, mark it in progress while working, implement small or cohesive work in the main context by default, use one to three gpt-5.6-terra workers only for genuine parallel chunks or large discovery/mechanical work where delegation pays for its handoff cost, pause or hand off chunks marked human-fit when appropriate, record implementation notes and final-test backlog, preserve the original slice contract, and mark completed implementation ready for review.

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

Prepare and risk-check the next rolling-wave slice for implementation. Use when the user wants to continue a rolling-wave project, draft one bounded slice in the main context by default, use a fresh planning author only when context or discovery cost warrants it, use a fresh preparation reviewer when semantic risk or uncertainty warrants independent pressure-testing, decompose parallel implementation chunks where appropriate, identify agent, human, either, or hybrid execution fit, write or update docs/rolling-wave/{project}/slices/NNN-slug.md, and mark that slice ready even when other slices are active.

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

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.

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

Pressure-test an existing plan or design artifact until it is coherent enough for the next workflow step or plainly blocked. Use when the user wants to be grilled on a plan, design doc, PRD, ADR, rollout plan, migration runbook, rolling-wave project shape, or slice contract; when they say "grill me"; or when Codex should interrogate a source-of-truth artifact, inspect code and adjacent docs before asking, auto-answer evidence-backed questions, ask only about conflicts or low-confidence recommendations, edit the original file in place, preserve the artifact's existing format, and keep conclusions, blockers, readiness, and deferred work synchronized in the document.

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

Mark a rolling-wave slice done on explicit user authority, regardless of its current lifecycle status or missing implementation, finalization, review, verification, or child-project state. Use when the user says a slice is done, complete, finished, accepted, or should be marked done; capture available material learnings, update project state, and output roadmap progress without requiring earlier workflow steps.

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

FiveM RP server engineering for QBCore, ESX.

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

This skill should be used when the user asks.

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

Expert-level separation processes covering distillation, absorption, extraction, crystallization, membrane separations, and adsorption for chemical engineering applications.

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

Expert-level engineering thermodynamics covering laws of thermodynamics, thermodynamic cycles, steam power plants, refrigeration, gas dynamics, and combustion.

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

Expert-level metals engineering covering crystal structure, phase diagrams, strengthening mechanisms, steel metallurgy, aluminum alloys, and failure analysis.

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

Expert-level spacecraft design covering mission analysis, subsystem design, power and thermal management, attitude control, communications, and systems engineering.

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

Expert-level chemical process safety covering HAZOP, LOPA, relief system design, consequence modeling, inherently safer design, and process safety management.

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

Expert-level polymer science covering polymer structure, thermoplastics and thermosets, mechanical behavior, processing methods, and polymer selection for engineering applications.

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

Expert-level air quality engineering covering pollutant sources, atmospheric dispersion, air quality standards, emission controls, and air quality modeling.

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