「fid」の検索結果

Active credit card transfer bonuses from Amex, Chase, Capital One, Citi, Bilt, and Rove. Weekly-refreshed data with confidence markers. Use when pricing an award booking that involves a points transfer or deciding whether to wait for a better bonus.

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

Use when working on inclusion, i18n/localization, global name/address forms, low-end devices, slow/metered networks, affordability, or first-time/low-confidence users; not WCAG/screen readers (see accessibility).

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

Use when briefing or managing an EXTERNAL agency, freelancer, or production vendor — scope of work, deliverable specs, revision rounds, approval process, USD payment milestones, IP assignment and confidentiality terms, communication rules, and a post-project vendor scorecard. Trigger on 'brief an agency', 'hire a freelancer', 'scope of work', 'the agency is not delivering', 'onboard a new vendor', 'we keep paying for work we have to redo'. Also use when the user is about to sign a supplier with nothing written down. Not for — briefing an internal team member, see `64-team-brief-global`; the campaign brief itself, see `02-campaign-brief-global`; the asset list the vendor produces, see `41-campaign-asset-list-global`.

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

Review a pull request or a set of code changes for bugs, logic errors, and project-convention violations using a confidence-filtered, multi-agent process. Use this skill when the user asks to review a PR, audit pending changes, or inspect a diff for problems before merging.

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

Review code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter. Use this skill when reviewing a small set of changes locally (such as unstaged diff), when dispatched as a sub-task during feature-dev quality review, or when the user wants a critique of a specific file or function.

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

Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging. This is NOT a general code review.

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

Autonomous skill lifecycle manager. Reviews skill-compounder drafts, promotes high-confidence patterns, merges duplicates, archives low-quality drafts. Zero manual review required - runs on every session start.

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

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

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

Commit mesajlarina yapilandirilmis karar trailer'lari ekle. Constraint, Rejected, Confidence, Scope-risk, Not-tested trailer'lari ile karar baglamini koru.

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

Strategic guidance for choosing and implementing testing approaches across the test pyramid. Use when building comprehensive test suites that balance unit, integration, E2E, and contract testing for optimal speed and confidence. Covers multi-language patterns (TypeScript, Python, Go, Rust) and modern best practices including property-based testing, test data management, and CI/CD integration.

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

Analyze assertion quality, depth, variety, and false confidence in existing tests. ALWAYS USE when asked about weak, shallow, trivial, always-true, self-referential, assertion-free, presence/truthiness-only, or insufficiently diverse assertions, including MSTest, Jest, pytest, and Go. DO NOT USE for direct fixes: writing-mstest-tests owns supplied MSTest assertions; code-testing owns new cases. Use test-gap-analysis when asked whether tests would catch a production change, and test-anti-patterns for general severity-ranked audits.

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

Analyze user-provided reference images and reverse-engineer high-fidelity AI image-generation prompts. Use when the user asks to recreate, imitate, reverse-engineer, or extract prompts from photographs, illustrations, 3D renders, products, characters, landscapes, typography, logos, posters, or other visual references. Do not use for requests that only require OCR or an ordinary image description.

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

Invoke when the user asks to review, check, audit, or look over Qt6 QML code -- or suggest before committing. Runs deterministic linting (47+ rules) then six parallel deep- analysis agents covering bindings, layout, loaders, delegates, states, and performance. Optionally invokes system qmllint for type-level checks. Reports only high-confidence issues (>80/100) with structured mitigations. Read-only -- never modifies code.

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

Invoke when the user asks to review, check, audit, or look over Qt6 C++ code — or suggest before committing. Runs deterministic linting (60+ rules) then six parallel deep- analysis agents covering model contracts, ownership, threading, API correctness, error handling, and performance. Reports only high-confidence issues (>80/100) with structured mitigations. Read-only — never modifies code.

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

Produce a high-confidence, CONCISE implementation / architecture / strategy PLAN that follows the OMC plan system end to end. It first runs OMC's real requirements interview (auto-chains the `omc-plan` skill: one question at a time, explore-first, Analyst consult) to produce an initial plan in `.omc/plans/`, then DEEPENS that plan with a 3-round ITERATIVE fusion loop — each round an Opus 4.8 panelist (Agent subagent) and a GPT-5.5 panelist (via codex) critique/improve it IN PARALLEL and BLIND, then Opus 4.8 (the orchestrator) judges and synthesizes one tighter plan that seeds the next round, stopping early on convergence. Writes the final dense plan back to the same `.omc/plans/<slug>.md`, then offers the OMC handoff (`/omc-plan --review` → `/team` or `/ralph`). Use for high-stakes planning, architecture decisions, strategy calls, and hard debugging — especially when the user runs /plan or asks how to approach a non-trivial build. Reuses the `fusion` skill's run_codex.sh + judge rubric. NOT for trivial tasks (single pass is enough).

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

Use with every WinDbg plugin investigation to apply evidence-first reasoning, confidence calibration, contrarian review, structured reporting, and deterministic validation. Not a bug-family-specific triage skill.

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

Routes heterogeneous queries to the appropriate index, tool, or answering engine before retrieval. Use when one endpoint serves multiple handlers, such as summary, vector retrieval, text-to-SQL, or tools, and query types require different paths. Covers LLM, semantic, and rule-based routers, confidence thresholds, fallbacks, and framework mappings. Do not use when one handler serves all queries or branching is fixed.

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

Turns a pile of ideas, requests and goals into a confidence-scored roadmap plus a goals/OKR set the team can actually follow. Use when someone says 'prioritize', 'what should we build next', 'roadmap', 'now next later', 'ICE or RICE', 'write our OKRs', 'quarterly planning', 'too many priorities' or 'sales keeps changing the plan'. Draws on 133 Lenny's Podcast guests including Itamar Gilad, Christina Wodtke and Janna Bastow.

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

Build, run, and improve a Security Operations Center — alert prioritization, runbook authoring, escalation criteria, on-call structure, alert tuning workflow, MTTD / MTTR / fidelity KPIs, analyst tiering, and shift handoffs. Use when the user mentions 'SOC,' 'security operations,' 'SOC analyst,' 'alert triage workflow,' 'runbook,' 'escalation,' 'on-call,' 'SOC tiering,' 'tier 1 / tier 2,' 'MTTD,' 'MTTR,' 'alert fatigue,' 'alert tuning,' 'shift handoff,' 'SOAR,' or wants to design or improve a security operations team.

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

Think before typing. Root cause first, two candidate fixes, pick one, ask if still unclear, then change only the files the request needs. Edit the confidence bar and scope rules to fit the project. Use when a bug report comes in, when a previous fix did not work, or when the request is vague.

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

Diffusion-based molecular docking. Predict protein-ligand binding poses from PDB/SMILES, confidence scores, virtual screening, for structure-based drug design. Not for affinity prediction.

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

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

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

Access AlphaFold's 200M+ AI-predicted protein structures. Retrieve structures by UniProt ID, download PDB/mmCIF files, analyze confidence metrics (pLDDT, PAE), for drug discovery and structural biology.

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

Diagrams and checkable docs from a codebase. Draws ERDs, C4 context/container/component views, API endpoint catalogues, lifecycle/state machines, and service-to-service call maps as a validated JSON spec plus a standalone HTML viewer, with Mermaid export. Imports OpenAPI, GraphQL SDL and Prisma; otherwise reads the code (NestJS, TypeORM, Express) and writes the spec. Use for: database diagram, ERD, data model, table relationships, C4 or architecture diagram, system context, API map, endpoint list, "show me the endpoints", status flow, state machine, allowed transitions, "what happens after X is approved", how services call each other, microservice map, Mermaid diagram. Also writes documentation as a fact graph: each statement carries its source and a computed confidence, and a drift check fails CI when the code moves. Use to document a system, write architecture or onboarding docs, or explain how a system works.

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