「flow」の検索結果

Reißverschluss-Verfahren (englisch: zipper merge) für sehr konfliktreiche Merges: Wenn zwei divergente Branches oder ein PR und sein Zielbranch BEIDE wertvolle, unvereinbar erscheinende Änderungen tragen, wird nicht pauschal eine Seite gewählt, sondern Abschnitt für Abschnitt verglichen, per Entscheidungstabelle (Nimm/Warum) die jeweils bessere Version übernommen, abschnittsweise committet und erst am Ende gepusht. Letzte Eskalationsstufe: Rebuild statt Merge — nur die Absicht/Funktionalität des Branches übernehmen und auf dem aktuellen Stand neu bauen. Nutzen bei: "Merge-Konflikt", "divergente Branches", "main vs. master", "konfliktreicher PR", "zipper merge", "Reißverschluss", "beide Seiten haben Recht", "PR ist zu alt zum Mergen".

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

8-phase development cycle: Feature requests, current state, functional planning, frontend, backend planning, backend code, tests, use cases. Iterative framework for systematic software development.

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

Hosting-Muster, um eine lokal gebaute Anwendung (eigene Datenbank, eigener API-Key, In-Process-State) sicher hostbar zu machen, ohne Nutzerverwaltung zu bauen. Kernzug — der Host speichert nichts, der Browser des Besuchers speichert alles — sodass Pro-Besucher-Accounts, Zugriffsprüfungen und Löschfristen gegenstandslos werden, statt gelöst werden zu müssen. Nutzen, wenn eine lokal gebaute App für mehrere Besucher gehostet werden soll, bei "mach das ohne Login hostbar", "keine Nutzerkonten bauen", "Datenschutzerklärung für ein gehostetes Tool verkleinern", "wer ist verantwortlich, wenn wir nichts speichern" oder beim Wählen/Implementieren eines Server-Modus (`local`, `huckepack-gift`, `huckepack-only-host`, `pay-membership`). Liefert eine Data-Flow-Plan-Vorlage, eine Datenschutz-Vorlage und eine rechtliche Ersteinschätzung (DSGVO/TDDDG/UWG, deutsch) als Referenzen.

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

Use when the user wants to send the same prompt to several LLMs and compare the answers - sequentially (stopwatch, clean per-lane timing) or in parallel (true race), with optional repetitions per model, judged by the starting model across quality, correctness, completeness, instruction fidelity and latency (time is only one dimension). Triggers on /compare-race, 'model race', 'vergleiche modelle', 'gleicher prompt an mehrere modelle'.

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

Systematic bug sweep with a codebase-scaled target value, doubling escalation, area tracking, and final verification. Use on /bugsweep or whenever the user requests a systematic bug pass.

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

Reads a cash forecast (spreadsheet, model export, pasted table or the narrative that accompanies it) and returns a DRAFT assumptions sheet: every assumption the forecast rests on, stated or implied by the figures, with its value as read, its location in the model, the cash lines it drives, its stated source or "not stated", the evidence that would test it, an owner, and one neutral challenge question, so a reviewer can work through the assumptions one by one. Use when the user asks to "list the assumptions behind this cash forecast", "what is this cash flow forecast assuming", "prepare the challenge questions for the treasury review", "pull out the drivers of the 13-week cash forecast" or "build an assumptions register for the liquidity plan". Do not use for actuals against budget by line, use budget-variance-explainer instead; do not use for the case behind a capital request, use capex-request-pack instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck, plan or contract summary in character as a General Counsel archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage or clause, legal risks, what would change the verdict and five interrogation questions. Meeting preparation, not legal advice. Use when the user asks to "run a general counsel review", "what would legal say about this", "pressure-test the legal exposure in this deal" or "prepare me for the deal committee". Do not use for price, term, renewal or vendor leverage, use procurement-reviewer instead; for lawful basis and data flows, use cdo-reviewer; for security controls, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reads a process flow diagram (image, PDF or native export) with its job header and returns a provenance-tagged extraction register: equipment, streams, tags, connectivity, instruments already shown, notes and legends, connectivity findings and an explicit UNKNOWN list, then holds at gate G1. Extracts and records only; never enriches, tags or proposes. Use when the user asks to "start a PFD to P&ID job", "read in the attached PFD", "extract the equipment and streams from this PFD" or "read this PFD into a register". Do not use for checking the model, use process-model-check instead; do not use to propose lines, instruments or tags, use piping-enrichment or instrumentation-and-control-enrichment after gate G2. Drafts for human review; never approves, authorises or signs off.

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

Mouse, keyboard, and scroll primitives for cua_click / cua_type / cua_key / cua_scroll. Reference for action shapes, modifier keys, key chord syntax, and screenshot-driven targeting workflows.

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

Interact with GitHub using the `gh` CLI. Use when managing issues, PRs, workflow runs, or advanced API queries via `gh issue`, `gh pr`, `gh run`, and `gh api`.

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

Audit BMAD source files for file-reference convention violations using parallel Haiku subagents. Use when users requests an "audit file references" for a skill, workflow or task.

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

画面遷移図の新規作成・更新を支援する。画面一覧の SCR-* を利用者ごとの Mermaid 図でつなぎ、画面間の遷移を表す D2 成果物。画面一覧の策定後に呼び出す。

Query and mutate Linear issues, projects, cycles, teams, workflow states, and comments via its GraphQL API. Use when the user wants to read or change Linear data programmatically — without the MCP server, and without hand-navigating the Linear UI.

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

Modern C++ project setup: CMake/CMakePresets, vcpkg, Ninja, VS Code/clangd, GoogleTest, clang-format/tidy, Doxygen, CI, macOS/Linux/Windows. Use for bootstrapping or modernizing host-side C++ apps and libraries; prefer embedded-project-setup for MCU firmware and cross-debug flows.

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

Use when explaining or writing TBQ3 language syntax, including Params, Vars, Events, data types, variables, sequence variables, arrays, Map variables, control flow, operators, assignment, functions, and formula execution rules.

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

Transform an ordinary object in a supplied photo into a poetic museum-exhibit poster, preserving its identifying shape while reimagining the display setting. Use for 私人生活博物馆, 日常物件展品, or a collectible still-life poster from food, flowers, toys or personal objects.

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

- Corporate due-diligence workflow — resolve a brand or website to its registered legal entity, map group structure and beneficial ownership, profile officers and directors, enumerate the digital estate, and screen litigation, insolvency,… Use when asked to check out, vet or research a company, verify a supplier or counterparty before signing or paying, or assess whether a business is real

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

- End-to-end workflow to establish where and when a photo or video was captured and whether it is authentic — evidentiary handling, metadata extraction, reverse image search for provenance, visual geolocation, chronolocation from shadows, and manipulation… Use when asked to verify where an image was taken, confirm or refute a claimed location or date, or authenticate media before relying on it

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

Turn a verified correction or repeated workflow into a reusable local learning.

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

Query the user's local and synced-device data via the screenpipe REST API at localhost:3030 — recordings, audio, UI, meetings, connected services, and memory. Use for screen activity, other-device or cross-device history, productivity, media export, connections, durable memory, or discovering and automating saved workflows.

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

Route a new rule, preference or policy edit into every home it belongs in (always-loaded canon, memory, the behavioral codex, a skill, a hook) and leave a trace in the always-loaded layer so parallel sessions pick it up on their own. Flow: dedup recall, classify by form, write to all homes, back up, report. Triggers: "/intake", "record this rule", "route this to its homes".

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

Researches what prompts people ask AI engines (ChatGPT, Gemini, Perplexity, Claude) about a product category and produces a prompts.csv artifact — a prioritized, strictly-schema'd list of the queries where the brand should be cited. Feeds the monitor workflow.

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

Senior engineer CLI expertise for AI agents — workflows, safety guardrails, gotchas, and anti-patterns across cloud, IaC, containers, databases, dev tools, and platforms

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

Capture and develop a reusable skill, tool repair, or behavior improvement noticed while completing a task. Use when instructions are stale, a recurring workflow deserves a skill, or a tool contract fails in practice.

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