「gate」の検索結果

Step 4 of the PaperOrchestra pipeline (arXiv:2604.05018). ONE single multimodal LLM call that drafts the remaining paper sections (Abstract, Methodology, Experiments, Conclusion), extracts numeric values from experimental_log.md into LaTeX booktabs tables, splices the generated figures from Step 2, and merges everything into the template that already contains Intro + Related Work from Step 3. TRIGGER when the orchestrator delegates Step 4 or when the user asks to "write the methodology and experiments sections" or "fill in the rest of the paper".

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

Detect and investigate bulk registration abuse on SaaS platforms. Given access to a user database (or exported CSV/JSON), run a multi-dimensional anomaly analysis — email domain clustering, registration tempo, UA fingerprinting, session structure, usage patterns, and credit consumption — to produce a scored abuse report with actionable recommendations. Use when investigating suspicious sign-up spikes, credit fraud, free-tier abuse, or account farming.

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

Autonomously navigate websites and extract structured data across pages. Use when the task requires navigation or no suitable ready-made workflow or data provider covers it.

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

Weekdays. Takes the one card the standup marked next and turns it into a reviewable change on a branch, never a deployment. It reads the project's own rules and docs first, makes the smallest change the card describes, runs that project's own gate, writes a change brief with the rollback in one line, and pushes the branch for the member to merge. It never merges, never deploys, never applies a migration, and never rotates a key.

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

Weekly. Works dependency and supply chain debt one project at a time, sorting every candidate into patch and lockfile only, minor, and anything major or breaking. It bumps the first class on a branch behind that project's own gate and pushes it for the member to merge. It holds the other two with a reason and a card carrying the evidence, so the member decides rather than being handed a red build.

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

Use the official Sentry CLI to investigate issues, events, traces, and logs for Vibe Remote without committing Sentry credentials into the repository.

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

Deliver Avibe, backend, docs, avault and vault-sandbox PRs through worktrees, Codex review, CI, circuit breaking and gated close-out. Required on every Agent backend.

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

This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".

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

Type-specific validation checklists, six quality characteristics, and quality gate thresholds for documentation assessment

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

Strategic and tactical DDD patterns, bounded context discovery, context mapping, aggregate design rules, and decision frameworks for when to apply DDD

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

Evidence quality validation and decision gate criteria for product discovery reviews

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

Minimizes test count while preserving coverage. Detects byte-identical pairs, parametrize-inflation, language-guarantee tests, AST-shape tests, stale migration nets. Approval gate before any change.

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

Monitoring, observability, operational procedures, CI/CD lessons learned, and quality gate definitions. Load when assessing production readiness or validating operational excellence.

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

DELIVER wave orchestration workflow -- 9 phases from baseline to finalization. Load when user invokes *deliver command. Covers state tracking, smart skip logic, retry, resume, and quality gate enforcement.

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

Tactical DDD — aggregate design rules, entities, value objects, domain events, repositories, domain services, and anti-pattern detection

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

4-phase discovery workflow with decision gates, phase transitions, success metrics, and state tracking

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

Event Modeling facilitation technique — brainstorm events, identify commands and views, define aggregate boundaries, write Given-When-Then specifications

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

Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution

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

Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.

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

Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.

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

Handle SLEAP GitHub support workflow for issues and discussions. Use when the user says "support", provides a GitHub issue/discussion number like "#2512", or asks to investigate a user report from talmolab/sleap. Scaffolds investigation folders, downloads posts with images, analyzes problems, and drafts friendly responses.

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

Thiet ke thu mien phi de doi lay thong tin lien he — ma tran loai lead magnet theo giai doan nhan thuc, danh sach dinh dang hop VN (checklist, bang bao gia mau, mini-guide, quiz, file Google Sheet tinh san, buoi tu van hoac dung thu mien phi), bang quyet dinh co nen gate hay khong, xin thong tin gi, giao qua kenh nao, trang cam on, tin hieu chat luong lead, va thang cham diem 8 yeu to cho cong cu mien phi. Kich hoat khi user nhac 'lead magnet', 'tang gi de lay so dien thoai', 'qua tang mien phi', 'tai lieu mien phi doi thong tin', 'moi mien phi', 'cong cu mien phi lay lead', 'chay lead ads ma khong biet tang gi'. Khong dung cho — lam trang dat lead magnet thi dung skill 12-brief-landing-page; nuoi duong sau khi da co contact thi dung skill 14-email-marketing; thiet ke goi ban tra tien thi dung skill 31-offer-design.

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

Dung khi can brief mot chien dich cu the cho ca team thuc thi — muc tieu, thong diep, deliverable, timeline phan cong theo tuan, gate duyet va ma tran rui ro. Kich hoat khi user nhac 'brief chien dich', 'ke hoach campaign', 'len brief cho team', 'chien dich thang toi', 'phan cong campaign', 'timeline chien dich'. Khong dung cho — ke hoach marketing ca ky thi dung skill 00-ke-hoach-mkt; danh sach asset can thiet ke thi dung skill 41-campaign-asset-list; giao viec cho tung nguoi thi dung skill 64-team-brief.

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

Use when a specific campaign needs a brief the whole team can execute from — context, objective, audience, core message, creative direction, channels, deliverables, week-by-week timeline, approval gates, and risks. Trigger on 'campaign brief', 'creative brief', 'launch brief', 'brief the team on this campaign', 'we are running a promo next month', 'what is the plan for this campaign'. Also use when the user describes a promotion out loud and asks for something the team can actually run. Not for — the whole period plan, see `00-marketing-plan-global`; the list of design files needed, see `41-campaign-asset-list-global`; assigning work to one person, see `64-team-brief-global`; a new product launch sequence, see `59-go-to-market-global`.

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