6.2천건 · 관련도순
Validates code fixes by running the code, checking compilation, verifying runtime behavior, and confirming fixes resolve the reported issue. Use when verifying that bug fixes actually work at runtime.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate Japanese PDFs using reportlab or fpdf2 with CJK font embedding, vertical text, business document templates, and inkan image placement. Triggers on requests to create 日本語PDF, 請求書PDF, 領収書PDF, PDF帳票, 縦書きPDF.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep, iterative internet research for current facts, source triangulation, contradiction checks, due diligence, competitive analysis, claim verification, "latest" lookups, and cited reports. Use when the user asks to browse, search, research the web, verify claims, compare sources, gather primary sources, investigate companies, people, products, technical topics, news, events, markets, or create AKBP-ready durable research evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Report project state and route the next stage. Use when the user says "where is my project", "what is next", or "run the pipeline".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure the studio, brand, and generation tools. Use on a missing-config report, or when the user says "set up manticore", "change my tools", or "update my studio".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
日次レポートを生成してSlackに投稿する。コミット・PR・Issue・進捗を集計して可視化する
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Integrates Sentry error tracking and performance monitoring into Flutter apps using `sentry_flutter`. Use when setting up crash reporting in Flutter, calling `SentryFlutter.init`, adding `SentryNavigatorObserver` to GoRouter, tracing HTTP requests with `sentry_dio`, capturing handled exceptions via `Sentry.captureException`, adding breadcrumbs, configuring session replay (`replay.onErrorSampleRate`), tuning `tracesSampleRate` or `profilesSampleRate`, controlling PII with `sendDefaultPii`, or setting user context after login and logout.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a user interface under real-world conditions across responsiveness, hostile content, interaction states, accessibility, network failure, interruption, and complete user journeys, reporting observable user harm with evidence rather than aesthetic opinion. Use whenever the user wants to stress-test a UI, verify responsive and edge-case behaviour, inspect loading/error/empty/recovery states, review a flow for friction, or find where an interface fails under reality. Part of the audit suite; inherits the shared constitution while its own job is proving observable user harm.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reproduce, isolate, and diagnose a specific software failure before changing production behaviour, then propose the smallest safe fix with regression protection. Use whenever the user reports a bug, crash, error, stack trace, flaky test, incorrect output, "works on my machine," intermittent failure, regression after a deploy, or any behaviour that diverges from expectation and the cause is not obvious. Prefer this over jumping straight to a fix. Part of the audit suite; inherits the shared constitution, while its own job is proving causality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to author one new tdmcp MCP tool the house way — the file shape (XImpl + registerX), the Python-bridge pattern (buildPayloadScript/parsePythonReport over executePythonScript), the result helpers (errorResult/guardTd/jsonResult/structuredResult), fail-forward error handling, ESM/.js + Biome style, and the offline msw unit test that proves it. Load this whenever building, extending, reviewing, or testing a tdmcp tool file under src/tools/** (and its test under tests/unit/**). Use it for every Phase-13 / v0.5.0 feature-build tool and any re-run after a gate failure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Experimental workflow for finding interrupted coding runs and reporting resume candidates. Use after an agent host restart or an interrupted automation; resuming anything needs the user's literal GO.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or drafting proposed host automations for report-only review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to see what learned instincts exist, their confidence scores and how current they are — reads the local instincts file under ~/.aos/instincts/ and reports it. Read-only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Nauthilus validation, guardrails, dependency patch refreshes, vendoring, generated-output checks, `make release-guardrails`, govulncheck-sensitive publishing, structured commits, branch/tag choreography, website-doc side effects, and final clean-state reporting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Govern FriendlyBet agent values, professional standards, anti-hallucination behavior, truthfulness, risk reporting, AI resource discipline, feedback loops, skill improvement, performance reviews, decision-rights hygiene, and team quality. Use when creating, reviewing, promoting, correcting, or retiring agents; reducing hallucinations or mistakes; reviewing AI/tool usage; handling agent incidents; or aligning work with Eyal's philanthropic user-first approach.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Act as FriendlyBet's CEO and primary front door for every FriendlyBet request through automatic company preflight. Own end-to-end routing, planning, execution coordination, department orchestration, decision-rights enforcement, quality gates, board-style reporting, and escalation only for strategic, legal, brand, cost, risk, or taste decisions. Use by default in FriendlyBet threads, with full department planning for broad, ambiguous, strategic, cross-functional, or outcome-driven requests such as SEO, new features, multi-sport expansion, product direction, release execution, company operations, or agent coordination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate phase validation across code-quality and production-readiness gates with mandatory reporting and verdicting
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Document templates for all pipeline output documents — specs, indexes, reports, and strategy docs. Use when any workflow needs to produce a structured document.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pre-scan decision types, collect downstream references, classify contradictions, and write propagation scan report
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute production-readiness gates with applicability control, consolidate validation report, and issue final readiness verdict
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run operational infrastructure verification gates for workspace/infrastructure/auth checkpoints and emit pass/fail audit report
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.