3,154 件 ・ 関連度順
概要と使いどころ
Use when debugging shared library load failures, setting RPATH or RUNPATH, applying soname versioning, writing dlopen plugins, or intercepting with LD_PRELOAD. Not for static archives: use binutils.
日本語の概要は準備中です。原文の説明を表示しています。
Use when configuring MCU sleep/stop/standby, WFI, STM32 PWR, nRF sleep, clock gating, wake-up EXTI sources, or measuring current draw. Not for the wake ISR: use interrupts-and-exceptions-baremetal.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a C++ template error needs decoding, a template needs a concept or requires-clause instead of SFINAE, or template instantiation is slowing compilation. Not for C++20 modules: use cpp-modules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to explain or teach a subsystem, module, pattern, or change in progressive layers from purpose to code depth. Not for design rationale: use why. Not for source or remote-system changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the learner is ready to apply cleared concepts in a real project. Not for exercises or quizzes: use drill.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a course, a learning workspace, or ongoing teaching across sessions, with cited lessons and retention-gated advancement. Not for one-off explanations: use explain-concept.
日本語の概要は準備中です。原文の説明を表示しています。
Use when addressing review feedback in analyze or reception mode, or handling GitHub PR feedback in autonomous, interactive, or summary mode for a named PR target. Classifies, applies, replies, or summarizes comments.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a current decision needs pressure-testing until the rationale is clear to a skeptic. Not for tasks requiring source or remote-system changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when thumbnail concepts need real-size, accuracy-first scoring without misleading claims. Not for generating thumbnails or declaring winners that fail the accuracy rubric.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an answer is wanted from one named seat only: breaking, business, career, codebase, human, impact, innovation, moat, rent-seeking, skeptic, or stability. Not for multi-lens synthesis: use prism. Not for rebuilding from primitives: use from-first-principle.
日本語の概要は準備中です。原文の説明を表示しています。
Apply one independently reviewable numeric Proto UI package-budget increase for an already accepted capability, using canonical cost evidence and existing development authorization. Use for standalone ceiling transactions, not feature implementation, measurement-policy changes, spending limits, publication or release.
日本語の概要は準備中です。原文の説明を表示しています。
Run Proto UI's dynamic comprehension assessment and derive an unsigned local task-fit result. Use when an Agent needs review calibration or a fresh autonomous task and review ceiling. Do not use a self-result as identity, permission, or acceptance evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Integrate one exact-head Proto UI pull request through either the ordinary independent-review path or a separately explicit current-user connected-operation decision. Preserve source, DCO, live platform enforcement and all deferred criteria; never manufacture approval or acceptance.
日本語の概要は準備中です。原文の説明を表示しています。
Measure the active Agent model with pinned offline ModelTrace sampling and return an unsigned closed-set attribution record. Use before Agent-originated commits, Issue/PR creation or material updates, comments, reviews, and current collaboration writes in either execution mode. Do not treat a fingerprint, declared model label, or record reference as authenticated identity, permission, independent review, or acceptance.
日本語の概要は準備中です。原文の説明を表示しています。
Independently review a Proto UI change against current authority, bounded scope, executable evidence, projections, provenance, and integration conditions. Use for pull-request review, acceptance review, pre-merge audit, or fresh-context verification. Do not use to approve one's own work.
日本語の概要は準備中です。原文の説明を表示しています。
Route one eligible transition in Proto UI's governed autonomous-maintenance protocol. Use for maintenance missions, drift discovery, finding verification, accepted remediation, independent maintenance review, run-ledger closure, or residual-risk planning. Do not use for ordinary user-directed development.
日本語の概要は準備中です。原文の説明を表示しています。
Apply one governed bounded Proto UI dependency update after pui-deps establishes the exact manifest, lockfile, consumers, compatibility evidence, and rollback boundary. Use for ordinary package or toolchain updates whose intended compatibility is already fixed. Route unresolved public compatibility, security disclosure, publication, release, or provenance exceptions to their dedicated decision path.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a readable Proto UI legacy-contract projection for explanation or an explicitly accepted uncataloged gap. Use for internal contract prose, migration banners, rationale, or synchronized readable projections. Do not use when an applicable spec entity already owns the rule or when semantics are unsettled.
日本語の概要は準備中です。原文の説明を表示しています。
Review a tailored application as a skeptical recruiter and an ATS parser. Use when the user wants strict feedback on an existing resume and cover letter.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Playwright automation failures against code-server (VS Code in browser). Use when: (1) trust dialog blocks all clicks — "monaco-dialog-modal-block intercepts pointer events", (2) button:has-text() finds wrong buttons behind modal dialog, (3) keyboard shortcuts don't work — Meta vs Control inconsistency, (4) VS Code extension activity bar icon not found by aria-label, (5) panels show placeholder text despite extension being "Connected". Covers trust dialog dismissal, keyboard shortcut hybrid mode, extension panel selectors, and database connection verification for Grafema extension.
日本語の概要は準備中です。原文の説明を表示しています。
Run the Codex Optimized Development, Evaluation, and Remediation (CODER) Loop with an orchestration-only coordinator, non-overlapping task-family owners, fresh independent reviewers, evidence-scoped remediation, and final coordinator acceptance. Discover and compose optional MSW, Timebox, MSL, and Codex Voice Optimizer companions as the Slopware Dev Stack without making them dependencies. Use in Codex when the user invokes the CODER Loop, asks to divide a complex change into bounded implementation families with independent reviewers, requests multi-agent implementation without overlapping ownership, requires review and repair until every blocking gap is independently rechecked, asks for the CODER tutorial or Slopware Dev Stack, or wants CODER to install or use its companions. Do not trigger for an ordinary single-agent change, a review-only request, or a non-Codex host.
日本語の概要は準備中です。原文の説明を表示しています。
Transform academic papers into in-depth technical articles with multiple writing style options. Use the MinerU Cloud API for high-precision PDF parsing, automatically extracting images, tables, and formulas. Optional formula explanations and GitHub code analysis, generating Markdown and HTML formats.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain governance artifacts without implementation work. Use when: (1) Accepting or refining ADRs, (2) Clarifying or amending RFCs without code changes, (3) Governance-only docs/check/render updates
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing, executing, or running Plans.md tasks — single task, parallel workers, or full team/breezing run. Accepts specific task numbers or ranges. Do NOT load for: planning, review, release, or setup.
日本語の概要は準備中です。原文の説明を表示しています。