「fix」の検索結果

Pick the right LLM for CONTRACT REVIEW — reviewing an existing agreement for risk, deviations from standard, missing protections, and internal contradictions, and proposing redlines. Vendor-neutral routing grounded in mid-2026 legal benchmarks. Contract review is a COMPOSITE skill (extraction + reasoning + redlining + conflict-detection), so this routes by the dominant sub-task. Asks up to 4 quick questions (cost, speed, accuracy/stakes, privacy/jurisdiction/ language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model to review this contract / NDA / MSA", "best AI to redline", "route this contract review", or is about to review an agreement without a fixed model.

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

Verification-first methodology for the Special Court for Sierra Leone and its Residual Special Court. Citations are verified against rscsl.org and legal-tools.org. Covers Taylor, the AFRC/CDF/RUF cases, the child-soldier and forced-marriage holdings, the head-of-State immunity decision, and the fixed-term (no life) penalty regime. Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

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

A drafting-and-review copilot for a founders' / co-founders' agreement — the terms fixing equity, vesting, IP, roles, control, deadlock, and departure between cofounders. Jurisdiction-agnostic, anchored on the Delaware C-corp default. Two modes: DRAFT (intake → equity & vesting → clauses → blocker triage → pre-signature check) and REVIEW (audit an existing agreement against an 18-clause checklist and red-flag scan). It handles the highest-dispute terms first-class: the equity split as documented reasoning (not a fake calculator), reverse vesting and the 83(b) clock, present-tense IP assignment (the Stanford v. Roche trap), leaver buyback and dead equity, and the deadlock clause most tools omit. It drafts for the venture, never one founder against another. Not legal advice.

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

Adversarially stress-tests a legal text — a contract, statute, regulation, or judicial opinion — for interpretive ambiguity: it finds the seams where the people governed by it will later disagree about what it means and turns each into a concrete dispute scenario with both sides' arguments, the likely outcome, and a fix. Use it whenever someone wants to pressure-test, red-team, audit, or find weak spots, loopholes, gaps, ambiguities, or drafting problems in a legal document; whenever a drafter wants to tighten a contract, statute, regulation, or opinion before it issues; whenever a litigator wants to mine an opinion or contract for arguments; or whenever someone hands over a legal text and asks where it will be fought over or for issue-spotting. Trigger it for contract review, statutory-ambiguity analysis, judicial-opinion scope analysis, and drafting QA — even if the user never says "stress-test" or "ambiguity."

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

Produces detailed law-school case briefs of United States judicial opinions in a fixed nine-section structure: memory jogger, facts, procedural history, judicial votes, holding, opinion-by-opinion analysis, five future-application hypotheticals, critique, and verified key quotations. Also builds vote tables, cross-case consistency tables, perspective-based critiques, and LaTeX in article, Beamer and casebook-chapter formats. Use whenever someone asks to brief a case, analyse or explain an opinion, summarise a decision for students, generate hypotheticals from a holding, critique a judgment, tabulate how justices voted, or convert case analysis to LaTeX. Triggers on "brief this case", "case brief", "explain the holding", "what did the court hold", "hypotheticals based on", "critique this opinion", "vote table", "Beamer presentation", "chapter brief", and on any reference to a judicial opinion or Supreme Court decision in a teaching context. Requires web search to verify quotations, votes and holdings.

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

When you want to create, adapt, or update an Agent Skill (Claude Code, Codex, Cursor, and other hosts) in one of your repos (listed in ~/.config/makerskills/skillify/repos.yaml; defaults to makerskills). Modes — CREATE (from chat, video, dump, or scratch) turns a workflow into a new skill. ADAPT ports an external skill with keep/adapt/add classification, license check, and attribution. UPDATE improves existing skills from learnings with cross-skill propagation, memory-vs-skill triage, and semver. Checks new skills for host portability. Triggers on "/skillify," "create a skill," "make this a skill," "skill from this chat," "adapt this skill," "port this skill," "fork this skill," "update X skill," "apply this to the relevant skills," "propagate this learning," "improve [skill]," "fix [skill]." Part of the -ify trifecta (skillify / toolify / loopify).

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

When you want to set up an agent loop, cron-scheduled task, or recurring workflow that runs autonomously. Judgment layer on top of Claude Code's ScheduleWakeup, CronCreate, and /loop — or, on other hosts, cron/GitHub Actions plus a headless agent CLI. Picks dynamic pacing, fixed cron, or a one-shot loop; designs idempotent loop bodies; sets bail-out conditions so loops don't run forever. Examples — weekly review pulse, daily brief, hourly metric monitor, periodic vault compile, upstream-check for an adapted skill. Triggers on "/loopify," "set up a loop," "schedule this task," "run this daily," "run this weekly," "cron this," "make this recurring," "automate this on a schedule," "keep this running until X." Part of the -ify trifecta (skillify / toolify / loopify). NOT for authoring a new skill — that's skillify. NOT for adding a tool/integration — that's toolify.

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

Expert blueprint for idle/clicker games including big number handling (mantissa + exponent system), exponential growth curves (cost_growth_factor 1.15x), generator systems (auto-producers), offline progress calculation, prestige systems (reset for permanent multipliers), number formatting (K/M/B suffixes, scientific notation). Use for incremental games, idle games, or cookie clicker derivatives. Trigger keywords: idle_game, big_number, exponential_growth, generator_system, offline_progress, prestige_system, number_formatting.

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

Bevy genre router for tower defense. Use when placing towers, marching creeps along waypoints, and spending gold on a fixed timestep. Keywords: Bevy, tower defense, creep, waypoint, gold, ECS.

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

Route a Bevy 0.20 race. Use when lap and gate index live on the racer, the race clock is one resource, and gate checks run after the clock step in one chain. Keywords: Bevy, Racing, Racer, RaceClock, FixedUpdate, chain, genre.

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

Route a Bevy 0.20 simulation. Use when hunger and jobs are components, the sim hour is one resource, and needs run after the clock step in one chain. Keywords: Bevy, Simulation, SimClock, Hunger, Job, FixedUpdate, chain, genre.

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

Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified", "is this actually done", "maker checker", "second pair of eyes on this change". Not for prose, docs or typo edits.

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

Expert blueprint for idle/clicker games including big number handling (mantissa + exponent system), exponential growth curves (cost_growth_factor 1.15x), generator systems (auto-producers), offline progress calculation, prestige systems (reset for permanent multipliers), number formatting (K/M/B suffixes, scientific notation). Use for incremental games, idle games, or cookie clicker derivatives. Trigger keywords: idle_game, big_number, exponential_growth, generator_system, offline_progress, prestige_system, number_formatting.

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

Bevy ECS skill for character movement. Keywords: Bevy, movement, ECS, fixed timestep.

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

Use when a new Godot system or feature has open design decisions — interrogates them in batched rounds, scope first, each question with a recommended answer, and records the answers before any design or code. Triggers on "grill me", "ask me first", "question me on the design", "what do I need to decide before building". Not for choosing between nodes or APIs, and not for bug fixes.

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

Use when debugging Godot projects — remote debugger, print techniques, signal tracing, common error patterns and fixes

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

Triage improvement work and run or resume accepted measured loops in a local project. Architecture, documentation, UX, product study, open research, taste, and one-shot fixes stay direct unless the user explicitly requests repeated measurement with a complete experiment contract.

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

Lay out and organize a ComfyUI workflow cleanly on the live panel canvas. Dependency-layered node placement with no overlaps, subgraphs, colored group boxes, and subgraph rail alignment. Use when asked to tidy / clean up / organize / arrange a workflow, add groups or subgraphs, fix overlapping nodes, or build a workflow that should look good from the start.

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

Common ComfyUI errors and fixes. OOM, missing nodes, dtype mismatches, black images, and debugging strategies

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

Issue reporting is disabled during limited maintenance of comfyui-mcp and the local Agent Panel. When the user hits a defect, explain that no report will be filed and continue helping with the task. Do not call report_issue to file, draft a report, collect reporting information, or submit through another tool. Triggers on "report this", "fix this bug", or errors in our software.

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

Debug a WRONG or imperfect render (not a hard error) by inspecting inputs and intermediate steps with run-to-node. Render one branch up to an output, preview-tap latents/masks/preprocessor maps, localize the first bad stage, then fix. Use when a final image/video completes but looks wrong, such as artifacts, wrong subject/pose/composition/color, blur, a ControlNet/IPAdapter/mask/LoRA not taking, or a two-stage refiner or upscale degrading the result. For errors/OOM/missing nodes use the troubleshooting skill.

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

Design and implement a new feature or component from a GitHub issue. Use for net-new functionality, not bug fixes.

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

Turn a photo of handwriting into a real installable font (TTF/WOFF/WOFF2). Use when the user shares a photo of handwritten letters and wants a font, asks to "make my font", "handwriting font", "turn my handwriting into a font", "font from this photo/image", asks for a handwriting font template, or wants to refine a font made earlier (smoother, thicker, fix a letter). Not for choosing, recommending, or identifying existing fonts - only for creating a font from the user's own handwriting.

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

End-to-end implementation workflow. Use when user wants to implement a feature, fix a bug, or make changes and have everything validated and committed.

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