「fact」の検索結果

Senior {{engine_name}}/{{engine_code_language}} developer that performs direct, ad-hoc code tasks without a formal plan — and the code-execution engine other unikit skills and agents delegate to. Use it whenever the user asks to do something in code right now, e.g. "add this method to this class", "refactor this function", "write a script that does X", "change this code", "optimize this class". Phrases like "without a plan", "no plan", "just do it", or "directly" are strong signals to use this skill rather than planning. Covers writing, refactoring, optimizing, and discussing {{engine_code_language}} code and patterns (DI, ECS, MVC, state machines, event systems). For a larger multi-step feature, plan it with /unikit-plan and build it with /unikit-implement — this skill is for direct, unplanned code work.

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

Autonomous iterative refactoring workflow. Scans for tactical code quality improvements (DRY, dead code, naming, complexity), implements through SMEs, verifies with QA, commits atomically, and loops until no improvements remain.

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

Use when a Coworld player needs to checkpoint or upload a debug artifact.

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

Manage Spec Kit presets via `specify preset`. USE FOR: listing installed presets as text or JSON, installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling presets, setting resolution priority, or managing preset catalogs. DO NOT USE FOR: full artifact composition stacks (use speckit-artifact), extensions (use speckit-extension), bundles (use speckit-bundle), or workflows (use speckit-workflow).

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

Manage Spec Kit extensions via `specify extension`. USE FOR: listing installed extensions as text or JSON, installing/removing/updating extensions, searching the extension catalog, showing extension info, enabling/disabling extensions, setting resolution priority, or managing extension catalogs. DO NOT USE FOR: artifact composition stacks (use speckit-artifact), presets (use speckit-preset), bundles (use speckit-bundle), or workflows (use speckit-workflow).

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

Universal platform artifact cleaner: Replit, StackBlitz, CodeSandbox, Glitch

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

Proactive monitoring of Aave V3 borrow positions with liquidation alerts. Queries user collateral, debt, and health factor across chains (Ethereum, Polygon, Arbitrum, etc.). Sends urgent alerts to Telegram/Discord/Slack when health factor drops below configurable thresholds (critical at 1.05, warning at 1.2). Use when you need continuous monitoring of Aave positions, want alerts before liquidation risk occurs, or need periodic summaries of your borrowing health.

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

Test-driven development with a red-green-clean loop, running mix credo on the whole project at the end of every vertical slice so standards violations are fixed in the slice that introduced them instead of piling into a refactor at the end. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

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

Produce a UGC-style talking-head video ad end to end on the MaxFusion MCP — research the product with user-supplied competitor leads, tear down 5 competitor Meta ads and 5 organic TikToks, write a pain-driven script that sounds like a person talking (never like an ad), reverse-prompt a rights-clean photoreal actor from a user-supplied reference photo, generate two chained 10-second Gemini Omni clips that play as one continuous take, and ship a single seamless 9:16 MP4. Use whenever the user wants a UGC ad, a talking-head ad, an ad for an app or product, mentions Omni or Gemini Omni Flash, drops an actor photo and asks for a video ad, or says anything like "make me some UGC", "let's make ads for X", or "another variation". Built for Claude Code (local ffmpeg); degrades to Claude app with documented fallbacks.

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

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

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

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

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

ALWAYS invoke this skill before writing, editing, generating, or refactoring ANY code. Do not write or modify code directly without first loading and following these Clean Code guidelines. Use when writing new functions/classes, refactoring existing code, reviewing code, fixing bugs, or any task that produces code output.

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

Scope, preregister, execute, audit, normalize, and publish GEODE evaluations with research-question, reproduction, attempt-lineage, trajectory, verifier-receipt, and immutable artifact contracts. Use for benchmark runs or comparisons, eval-artifact and cache-accounting audits, GPT or subscription result normalization, research question or hypothesis framing, retry diagnosis, trajectory publication, DPO or reward-data readiness reviews, and requests involving MCPMark, tau2, BFCL, Agent-World, HAL, Terminal-Bench, or Toolathlon.

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

Codebase audit + refactoring workflow. Dead code detection, God Object splitting, duplicate function removal, design flaw identification, frontier comparison verification. Triggered by "audit" ("감사"), "dead code" ("데드코드"), "refactor" ("리팩토링"), "god object", "duplication" ("중복"), "design flaw" ("설계 결함") keywords.

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

Code review from the Kent Beck Simple Design 4 Rules perspective. God Object splitting, SRP, duplication removal, naming, cyclomatic complexity. Triggered by "kent beck", "simple design", "simplify", "refactoring" ("리팩토링"), "refactor", "god object", "SRP" keywords.

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

Deletes files and directories through a wrapper that avoids the usual per- command permission prompt. Use only when content must genuinely be deleted, such as clearing build artifacts or dropping obsolete files during a refactor. Moves, renames, and relocations that preserve content use mv instead.

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

Refactor code units whose size or mixed responsibilities impede understanding, testing, or change. Use when recent work makes a function, class, or module materially harder to reason about.

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

Generates a structured attorney work product memorandum from an initial client consultation for commercial litigation. Extracts verifiable facts from uploaded documents, builds a chronological narrative, identifies parties and contracts, flags preliminary legal claims and defenses, and produces a prioritized action plan. Triggers at matter intake when a business client needs a foundational case evaluation document for a pre-filing commercial dispute.

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

Star schema, snowflake schema, SCD types, and Kimball methodology for analytical data modeling. Activate on: dimensional model, star schema, snowflake schema, SCD, fact table, dimension table, Kimball, grain, surrogate key. NOT for: dbt implementation (use dbt-analytics-engineer), warehouse tuning (use data-warehouse-optimizer).

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

Detects fabricated content, false citations, and unverifiable claims in agent outputs. Uses source verification and consistency checking. Activate on 'detect hallucination', 'fact check', 'verify claims', 'check accuracy', 'find fabrications'. NOT for validation (use dag-output-validator) or confidence scoring (use dag-confidence-scorer).

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

Verifies build output integrity after code changes. Runs builds, validates artifact structure, checks for regressions in bundle size, asset references, and static export completeness. The last line of defense before a bad deploy ships.

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

Use when a plan directory (plan.md + phase-*.md) needs a visual review. By DEFAULT this drives the STRUCTURED visual-plan artifact (visual-plan/plan.json) via the mewkit visual-plan CLI — generate if absent, validate, open the local studio (view/edit), and export plan.html from the approved artifact. Pass --static for the legacy prompt-only single-file plan.html template render. Triggers on "render this plan", "visualize the plan", "open the plan studio", "make a shareable plan page", "plan.html". This is the canonical owner of plan-as-visual-review. NOT for plan critique or scope review (see mk:plan-ceo-review / mk:validate-plan), NOT for generic code/diagram/diff visuals (see mk:preview), NOT for live media generation (see mk:multimodal).

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

Create a self-contained, visually polished HTML showcase page for a topic or set of artifacts. Supply a mission (topic summary) and optional artifact paths explicitly — the skill never auto-scans the repo. Writes output to assets/showcase/<mission>/. Screenshots are optional (requires Puppeteer). Publishing is local-only by default; publish requests without a configured path fail clearly.

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

Use when surfacing architectural friction and proposing deepening refactors (shallow modules → deep modules) for testability and AI-navigability. Triggers on "improve architecture", "find deepening opportunities", "where is this codebase shallow", "architecture review". Emits structured candidates + precise patches; delegates ALL rendering to mk:preview. NOT for diagram/HTML rendering (see mk:preview); NOT for trade-off deliberation (see mk:party); NOT for plan critique (see mk:plan-ceo-review).

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