'fuse' 검색 결과

Observe the user's screen via screenpipe, detect repeated research workflows, match them against existing scientific-agent-skills, and draft new skills (or composition recipes that chain existing ones) for the patterns not yet covered. Use when the user asks to analyze their recent work and propose skills based on what they actually do. Requires the screenpipe daemon (https://github.com/screenpipe/screenpipe) running locally on port 3030 — the skill has no other data source and will refuse to run if screenpipe is unreachable. All detection runs locally; only redacted cluster summaries reach the LLM.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the extended Corpo Net range suite across many models on one remote host with parallel isolated range instances, local Langfuse recording, bounded spend, and verified teardown. Use when asked to run, rerun, or scale a Corpo Net campaign; use run-ephemeral-hosts for the host contract and manage-remote-resources for billable resource ownership.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Recommends antihypertensive therapy including mineralocorticoid receptor antagonists (MRAs) for patients with a positive primary aldosteronism (PA) screening test who decline confirmatory testing. Triggers include when a patient has positive screening but refuses additional tests and asks "What should I treat with?" or initiates empiric therapy, with preference for MRAs in typical PA presentations (e.g., spontaneous hypokalemia, resistant hypertension, adrenal tumor on CT).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert-level aircraft structures covering structural design philosophy, wing and fuselage analysis, fatigue and damage tolerance, composite structures, and certification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Rates a project with Jevaluate and keeps the rating private, with the same rubric and checks, a private library that export refuses, and nothing pushed or published. Use when a rating must stay private, such as "/jevaluate-private" followed by a link or folder, "rate this privately", "evaluate my own project", a client's or employer's code, a design doc or a local folder that isn't public, or any rating that must not reach the public ratings or the repo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when governing a worktree across its whole life — scope-lock declaration, merge-readiness status, scoped verification, and safe cleanup that refuses while unique unmerged commits exist.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When scoring whether an agent response defended against an injection — treated untrusted content as data, refused role-takeover, ignored fake boundaries. Inverted axis; never auto-gates.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read a Reddit thread or single tweet the host cannot fetch — 'what does this Reddit thread say', 'top comment on this post', 'what does this tweet say' — when reddit.com is refused or x.com 402s.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When shrinking always-loaded memory files (AGENTS.md, CLAUDE.md, .cursorrules) exceeding ~150 lines or ~4,000 chars — telegraph grammar, refuses sensitive paths, .original.md round-trip.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test, fold or refute hypotheses beside the knowledge record, and reconcile records across branches. Use when open or check say hypotheses wait or an id is CONTESTED, when a write was refused into a hypothesis, before merging a branch whose record changed, and when a pull request's dry run or remeasure is red. Covers consolidate --dry-run, the fold, --refute, --from, same and distinct at the fold, and remeasure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

INTERNAL sub-agent, not a user-facing skill. Performs context-isolated nine-dimension rubric scoring for cheat-score, cheat-predict, and cheat-bump. Accepts only script and rubric-note paths, returns strict JSON, and refuses post-publish evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Work the verification ladder of a research run with rs_verify — read the ladder report before claiming anything is checked, run the two file rungs (r1-record, r2-locate) that need no reader, record the r3-support verdicts and strength verdicts that only a reader can make, tell a miss from an inconclusive, and know what a clean build will still refuse. Use when a document is written and about to be called checked, when a claim's quote does not match its source, or when a gate or build answers with an integrity refusal.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hand a research run over as a file — read `rs_open action=capabilities` for the formats this build writes, choose between `md`, `docx`, a self-contained `html`, the `ris`/`bib`/`enw` library exports and `tex`, pick `draft=watermark` while working or `draft=clean` to hand it over, and read `build/build.json` for what was built from which bytes. Use when a document is finished enough to leave the run, when a citation style or an export has to be chosen, or when a build refuses.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The crouton mental model for someone who has never seen this repo — what "layer" means (two different things), the two-halves rule, the three app.config registries, team-scoped multi-tenancy, manifest-driven field types, the numbered invariants with the incidents behind them, and the known-weak points. Use when orienting in this codebase for the first time, when a question is shaped like "how does crouton work / why is it built this way / where does X live", when deciding whether a change belongs in a package or a generated layer, when confused by an extends chain or by croutonApps/croutonCollections/croutonLayoutBlocks, or before proposing any structural change. Trigger phrases: "what is a crouton layer", "package vs generated layer", "how does multi-tenancy work here", "why is there a stub component", "where do field types come from", "what invariants must hold".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AID methodology phase gate enforcement. Ensures work follows correct 6-phase order (Discovery -> PRD -> Tech Spec -> Impl Plan -> Dev -> QA & Ship). Enforces gates, validates transitions. Use before any work to check the current phase and refuse work belonging to a later phase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prove a Convex feature works — seed, drive as multiple mocked users via convex-test, assert behavior including the negative authz cases (wrong user refused, data-scope enforced).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prove a Convex feature works — seed, drive as multiple mocked users via convex-test, assert behavior including the negative authz cases (wrong user refused, data-scope enforced).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews the instructions text and skills of a declarative agent, with its stated capabilities, knowledge sources and audience, for prompt-injection exposure, data-leakage paths, over-broad permissions and missing refusals, and returns an attack-surface map, a findings table with severity, quoted evidence and attack path, one pasteable fix per finding, a probe pack the owner can run and a refusal-coverage table. Use when the user asks to "red-team this agent", "check these instructions for prompt injection", "could this agent leak data", "review the permissions on my agent" or "what should this agent refuse". Do not use for checking a SKILL.md against the format rules, use skill-file-reviewer instead; do not use for designing the launch test set, use agent-evaluation-plan instead. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Publish a vetted post to an X (Twitter) account through the owner's real logged-in Chrome tab, rate-guarded and draft-first. Counts length the way X does, treating every link as 23 characters, and refuses over-limit text instead of silently truncating. Triggers: "/x-post", "tweet this", "post to X".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Register a custom WooCommerce payment gateway — extend WC_Payment_Gateway, declare $id / $title / $supports, implement process_payment returning array(result, redirect), optionally process_refund when refunds is in supports, register via the woocommerce_payment_gateways filter. The single most-confused thing AI gets wrong is payment_complete vs update_status — payment_complete runs the canonical paid-order state machine (status, transaction id, session flag, woocommerce_payment_complete action), update_status only changes the status string. Includes the always-forgotten WC cart empty_cart call after success. Use when integrating a payment provider, reviewing gateway code, or debugging "payment succeeded but cart didn't clear" / "order stuck in pending". Triggers on WC_Payment_Gateway, woocommerce_payment_gateways, process_payment, process_refund, payment_complete, get_return_url, woocommerce_payment_complete_order_status.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guidelines for deep learning development with PyTorch, Transformers, Diffusers, and Gradio for LLM and diffusion model work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guidance for deep learning, transformers, diffusion models, and LLM development with PyTorch, Transformers, Diffusers, and Gradio.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create Kotlin Compose design tokens from one of three supported sources — Google Stitch (MCP), Figma (MCP or JSON), or Claude Design (kta-design-spec output, Claude HTML/markdown artifacts). Three-layer architecture (Primitive/Semantic/Component) with code generation. Use when user asks to "generate design tokens", "create theme from Figma/Stitch/Claude design", "build Compose tokens from design spec", or "convert design source to tokens". Refuses any other input source and asks user for correct seed data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.