「without」の検索結果

Use when asked to optimize code, make a path faster, make this as fast as possible, reduce allocations, repair a regression, profile a target, grill every inefficiency, or run a subsystem or repo-wide performance campaign against a measured floor; when a performance requirement, slowness report, Core Web Vitals miss, or profiling evidence identifies a bottleneck; or for an "extremely optimize" performance campaign, optimizing suspected hot paths without waiting for benchmarks, or estimating hot and complexity-neutral cold paths while refusing complexity theater. Not for remote, credential, publish, deploy, or irreversible changes.

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

Use when bloated code needs clean re-derivation, or the user says "this module is bloated" or "break it and rebuild". Not for untracked data or changes without VCS rollback.

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

Use when asked to remove old code, migrate consumers, or decide whether to maintain or sunset a system. Not for untracked data or changes without VCS rollback.

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

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.

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

Assess one bounded Proto UI Adapter question without changing repository or external state. Use for new-Adapter research, target compatibility, catalog readiness, reviewed Module support or omission evidence, Host Capability fidelity, lifecycle translation, dependency risk, or implementation readiness. Do not catalog, implement, repair, or approve the Adapter slice.

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

Select at most one eligible Proto UI work item and return a read-only proposal without changing GitHub or repository state. Use after pui-orient when requested contribution work is not yet bounded, or when a user asks what ready task fits the current capability and permission envelope. Do not post a claim, assign anyone, decide readiness, or invent work.

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

Independently review one Proto UI autonomous-maintenance remediation in a fresh read-only context. Use after pui-remediate produces a packet and actual diff. Classify technical-completion eligibility without making product or integration decisions.

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

Run a standalone read-only rules compliance gate against changed files or a git ref. Use when you need a dedicated project-rules check without a full review or verify pass.

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

Diagnose React + Three.js (or any browser canvas) frame stutter by capturing a CDP CPU profile via Playwright instead of guessing from `[perf]` console logs. Use when: (1) frame time is bad but `[perf]` instrumentation doesn't pinpoint the offender, (2) you've spent more than ~30 minutes "fixing" suspects without measuring, (3) hot paths involve animation systems, allocation bursts, or invisible scene-graph traversal, (4) you need self-time per function with line numbers, not aggregate "render slow". The `console.warn` pattern is good for monitoring; CDP is needed for diagnosis. Covers script template, sourcemap setup so minified function names are decoded, and interactive variant where the user drives the interaction and signals stop via `touch /tmp/<flag>`.

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

Speed up Rust development iteration when `cargo build --release` takes 10+ minutes even for one-line edits. Use when: (1) every release rebuild takes minutes despite tiny edits, (2) Cargo.toml has `lto = "fat"` and/or `codegen-units = 1` in `[profile.release]`, (3) you want a production- shaped build for testing without paying the LTO cost on every iteration, (4) you suspect cargo is re-linking the whole binary instead of doing incremental work, (5) developing rfdb/grafema-orchestrator/large Rust binaries where full LTO is enabled for shipped builds. Adds a `fast` profile that inherits release but disables LTO, raises codegen-units, enables incremental compilation — first build still slow because it populates a fresh `target/fast/` dep cache, but every subsequent rebuild drops from ~13 min to ~13 s (≈60×).

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

Continuous self-reflection routine combining Schön (reflection-in-action / reflection-on-action) and Mezirow (content / process / premise) levels, anchored on KAMI values (val-002 глубина, val-007 честность перед собой, принцип 1 правда, принцип 2 нулевая толерантность к бреду). Triggers FIRE DURING THE TURN, not at end. Use when: (1) about to make a 2nd+ patch attempt at the same problem, (2) user pushes back with "стоп / нет / опять / так, ещё раз / не то / пиздёж", (3) noticing self drifting into "I think that..." without evidence, (4) about to report "готово", (5) copying a pattern from one place to another, (6) task took >2× expected time. Embeds scientific method (explicit hypotheses + falsifiability + prediction-first + alternatives) as substrate for premise-level reflection, not as ceremony.

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

Compute a unified outer hull around a group of hex tiles that includes multiple disconnected sub-clusters separated by 1-tile gaps. Use when: (1) rendering nested hierarchy hulls (e.g. "package" hull wrapping multiple "sub-region" hex islands), (2) the naive boundary trace outlines each island separately instead of as one bag, (3) flood-fill from outside walks THROUGH the 1-hex gaps and marks them exterior, (4) heuristic "non-adjacent same-group neighbours" over-fills L-shape concavities, (5) axial-only opposite-pair filling misses non-axial bridges between islands. Solution: morphological close (dilate + erode) on the hex grid — fills exactly the interior 1-hex gaps without affecting exterior corners, then trace boundary on the closed shape.

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

Fix silent incorrect results in RFDB Datalog queries that share a variable between two edge atoms on opposite ends (e.g. self-join patterns like `edge(M, C, "T1"), edge(C, M, "T2")`). Use when: (1) a Datalog rule returns rows that look structurally wrong (e.g. a self-loop rule reports hits but pinning M to each reported id refutes the edge existence), (2) Cypher `MATCH (m)-[:R1]->(c)-[:R2]->(m)` returns the same bogus rows (engine-level bug, not Datalog-specific), (3) results change when you bind one variable explicitly vs. leave it free. Root cause: hash- join fast path in `eval_edge_hash_join` / `eval_incoming_hash_join` unconditionally rebinds the non-key Term::Var without checking whether the variable is already bound in the current row.

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

Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, Google Cloud migration, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate agentic workloads to AWS, move AI workloads to AWS, migrate my AI app to AWS. Runs a 6-phase process: discover GCP resources from Terraform files, app code, or billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. Clarify must finish before Design, Estimate, or Generate. Includes AI provider migration guidance (for example, OpenAI to Amazon Bedrock) by selecting closest-fit Bedrock model families for required modality, latency/quality targets, context windows, and cost constraints. Model mapping is compatibility-guided, not 1:1 parity; validate prompts, tool-calling behavior, and eval metrics before cutover. Do not use for: Azure or on-premises migrations to AWS, AWS-to-GCP reverse migration, general AWS architecture advice without migration intent, GCP-to-GCP refactoring, or multi-cloud deployments that do not involve migrating off GCP.

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

Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.

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

Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.

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

Use when the user wants to run SQL - especially analytical SQL - on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake) without setting up a server. Provides chDB - embedded ClickHouse SQL in Python with 1000+ functions, Session for stateful multi-step pipelines, parametrized queries, and cross-source joins via `s3()`, `mysql()`, `postgresql()`, `iceberg()`, `deltaLake()`, `remoteSecure()` table functions. TRIGGER when: user wants SQL on parquet/csv/files or across remote analytical sources; uses ClickHouse SQL features (window functions, windowFunnel, geoToH3, JSON path ops, Session, parametrized queries); imports `chdb` or calls `chdb.query()`. SKIP this skill for pandas-style DataFrame method-chaining (use chdb-datastore instead) or ClickHouse server administration.

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

ES — Critica a fondo una idea, plan, pitch o proyecto entero sin validar ni adular: asume que va a fracasar y lo demuestra por ocho ángulos (premisas, mercado, competencia, viabilidad, números, ejecución, pre-mortem y punto ciego), investiga fracasos reales cuando hay herramientas, y entrega un veredicto franco con la lista priorizada de qué arreglar. Activar con /abogado-del-diablo, "hazme pedazos esto", "critica mi idea sin filtros", "dime por qué va a fallar", "destruye este plan", "segunda opinión brutal", "pre-mortem". EN — Harshly critiques an idea, plan, pitch, or whole project without validating; assumes it will fail and proves it across eight angles, then returns a blunt verdict with a prioritized fix list. Trigger on "devil's advocate", "red team this", "tear this apart", "why will this fail", "brutal second opinion", "pre-mortem".

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

Run a standalone read-only rules compliance gate against changed files or a git ref. Use when you need a dedicated project-rules check without a full review or verify pass.

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

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause.

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

最强经理之争——把四位风格迥异的中国权益基金经理（易方达郑希、易方达张坤、易方达武阳、财通金梓才）放进同一个擂台， 用他们各自的全部公开观点原文 + 全部在管基金真实数据（季度持仓/净值/回撤/规模），做可溯源的对比与应用。能做： (1) 经理之争擂台——同口径比收益/最大回撤/回撤恢复/波动/Calmar/换手/规模，给"分场景谁更强、各自长短板"； (2) 行业/个股透视——给一个行业或股票，看四人谁持有/谁加减/谁更早布局，再用各自框架给"四个镜头"的综合看法； (3) 持仓/调仓追踪——逐季还原谁加仓、减仓、新进、清仓（季度颗粒度，公开数据能到的最细）； (4) 多视角参考——用四人的方法和真实操作，多角度帮你理解一只基金/一个行业、校准自己的判断（只呈现不同视角，不替你做决定、不构成建议）； (5) 溯源问答/方法讲解/风格化点评——引用某位经理本人原话答其观点，讲其投资框架，或用其口吻点评； (6) 言行对照——用真实持仓核对某位经理"说的"和"买的"。 (7) 进阶玩法——风格雷达+人设卡、本季调仓快报(共识/分歧)、言行一致性打分、观点时间机器(谁最早看到)、四人会诊(四种视角点评)、自定义擂台(把任意基金/经理拉进来比)。 When the user mentions 最强经理之争 / 经理对比 / 谁更强 / 回撤谁控得好 / 张坤/郑希/武阳/金梓才 / 景气轮动 vs 买入持有 / 风格雷达 / 人设 / 谁最早布局 / 言行一致 / 四人会诊 / 把某基金加进来比， asks who holds a sector or stock, wants 调仓追踪/调仓快报, a 风格化点评, words-vs-holdings, a style radar/persona, an opinion timeline, or to apply their methods to a fund/sector ——use this skill, even without the word "skill", even if the topic isn't in a corpus (fall back to that manager's method). 引用忠于原文、不杜撰；原话/推演/需核实分清；季度颗粒度非逐笔；研究学习辅助，非投资建议。

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

Drive the machine itself, mouse, keyboard and screen, without needing vision

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

Extract text from a PDF or a scanned document, with or without OCR.

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

Write an actionable markdown implementation plan, without executing it.

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