「eal」の検索結果

Phase 2: Generate and discover tests, validate against real library. Only invoke when explicitly requested by the user or by the yoink orchestrator.

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

Scaffold project: clone repo, install real library. Only invoke when explicitly requested by the user or by the yoink orchestrator.

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

Render a deterministic 15-second vertical promo video from real Simulator screenshots with a three-beat viewer challenge and no Remotion initialization. Use in a twelve-minute parallel launch lane, as a reliable fallback to a richer Claude Design animation, or whenever ffmpeg and ImageMagick are available.

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

Capture reproducible screenshots from the currently booted iOS Simulator and turn them into three App Store marketing cards with validated dimensions and concise copy. Use after a successful Simulator build, during the two-minute proof lane, or when replacing prototype images with real app captures.

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

Assemble cases from context, induce the widest sound rule. Use when a real case shows a class no rule yet decides, or a rule decides only the cases it came from.

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

Use when initializing EAL, configuring PMD drivers and huge pages, using mbuf pools and rte_ring, setting up RSS, or validating a port with testpmd. Not for AF_XDP sockets: use af-xdp.

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

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 asks for onboarding, orientation, a repository tour, or where to start. Produces an evidence-backed seven-section map, deep-reads real files, and asks for the next move.

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

Use when a user asks to audit what recall fed agents. Not for source or remote-system changes.

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

Use when a human asks to compare one closed or stale tracker issue with current reality and mark it done or update it. Don't use for bulk issue reconciliation or multi-issue sweeps.

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

Use when asked to build or modify production-quality components, layouts, state, and pages with WCAG 2.1 AA and real content. Not for token-system design: use frontend-design-deslop.

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

Use when the user invokes /ios-visual-review to audit an iOS app's visuals on a real device. Not for remote, credential, publish, deploy, or irreversible 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.

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

Transfer reusable prevention lessons from another AI Factory project into the current project's skill-context through $aif-evolve. Use when building a similar project and you want to avoid problems already captured in another project's patches without copying or revealing that project's identity, paths, or identifiers.

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

Inspect one bounded Proto UI pull-request slice, produce canonical review input, and route each eligible exact head toward review and integration. Use for review queues, linked work, evidence gaps, merge conflicts, stale revisions, or portfolio health. This evidence leaf is read-only; authorized review and integration continue in their registered leaves.

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

Audit one bounded Proto UI deployment or publication evidence slice against an exact revision and delivery surface. Use to verify revision identity, environment result, artifacts, and observable health. Do not deploy, promote, roll back, publish, release, or change environment protection.

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

Inspect one bounded Proto UI Issue queue slice and route ready governed work toward claim and implementation. Use for intake health, readiness, ownership, claim conflicts, stale state, or a candidate task search. This evidence leaf is read-only; authorized claim and implementation continue in their registered leaves.

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

Implement one governed Proto UI Adapter-profile realization slice. Use when target and runtime range, supported or omitted Module role, Host Capability fidelity, lifecycle translation, failure behavior, compatibility boundary, and evidence scope are fixed by current authority. Use pui-adapter-assess for research or readiness assessment and pui-regression first for a governed failing behavior.

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

Implement or revise one governed Proto UI Host Capability connecting a semantic Module to a bounded host responsibility. Use when capability identity, portable need, public shape, availability, failure, replacement, cleanup, fidelity, Adapter realization, and evidence are fixed by current authority.

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

Add a real achievement, measurement, skill, or project update to the master resume. Use when the user wants to record new factual experience.

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

Design guide + benchmarked pitfalls for building Monte-Carlo / Simulated Annealing refinement layers on top of greedy hex-grid layouts for code visualization (packages/gui/src/store/hexLayout.ts, sandbox/hex-sandbox, future Rust ports). Use when: (1) planning to add MC/SA on top of an existing hex-grid pack, (2) deciding whether a simpler SA would match a hierarchical MC with force-directed + chain drag, (3) budgeting wall-clock for million-node cold-start, (4) debugging "blob turns Swiss-cheese" or "folders stop nucleating" during MC refinement, (5) choosing between folder cohesion and raw Σ-link-length as cost function. Contains four hard-won, quantified lessons and anti-patterns that would take a full day of experiments to rediscover.

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

Recover from stale RFDB nodes that survive `commit_batch` cleanup despite having their `file` field listed in `changed_files`. Use when: (1) re-running an enricher/orchestrator step but old data with the same file field stays in the graph, (2) `commit_batch(changed_files=[X], ...)` reports success but a query later still returns nodes with `file = X`, (3) you re-pointed structural nodes (e.g., DIRECTORY/FILE) from a synthetic file path to real file paths and the old synthetic-path nodes won't go away, (4) graph-stream / find_by_type returns a mix of "stale" and "new" nodes for the same logical entity. Root cause: `handle_commit_batch` calls `engine.find_by_attr({file: X})` to enumerate nodes-to-delete, but that query path returns only a PARTIAL set after compaction (L1 segments and the file→nodes index can desync). Workaround: enumerate stale nodes via the TS rfdb client `queryNodes({file: X})` (different code path that finds all of them) and call `deleteNode(id)` per node, then re-commit the intended state. Related: rfdb-manifest-l1-carryforward (same L1 family).

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

Connects the user with a LegalZoom attorney for legal consultation. Use when a user asks about attorneys, lawyers, or legal help, or when contract review reveals high risks or low-confidence findings.

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

Design and build reactive, type-safe, production-grade backends on Convex. Covers schema, queries/mutations/actions, indexes, auth, file storage, scheduling, real-time multiplayer, mobile backends, and LLM/agent workflows on Convex's one-platform stack.

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