「claim」の検索結果

Evidence rules for completion claims. Use before ticking an acceptance criterion, ending an implementation run, or writing anything that says something works, passes or is fixed.

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

Use only after explicit Codex `$superloopy:superloopy-research` or Claude Code `/superloopy:superloopy-research` invocation, a research task started with a leading `loopy` or `루피` (such as `loopy research`), or an active Superloopy loop explicitly routing a research deliverable here. Evidence-backed Superloopy research orchestration with automatic advisory usage targets, parallel read-only lanes, per-retrieval verdicts, graded and dated sources, empirical verification, a priced claim ledger, cited synthesis, and optional reports. Do not activate from research, investigate, look-up, summarize, deep-dive, report, or similar vocabulary alone, in any language; ordinary questions, debugging, and implementation context-gathering stay with their primary workflows.

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

Produce a short motion-graphics video ad — a 15s Facebook/Instagram/TikTok spot — as a rendered MP4. Researches the destination landing page so every on-screen claim matches it, pulls real product imagery off the live site, animates one paused GSAP timeline in a single HTML page, and renders it frame-accurately through Playwright and ffmpeg. Use this whenever the user wants a video ad, promo video, animated ad, "an ad for my product", Meta/TikTok/Reels creative in video form, a 9:16 or 1:1 cut of an existing spot, or a re-render of an earlier ad with a different hook, hero or CTA — including when they never say the words "motion graphics". Not for animating UI inside an app, not for static image ads, and not for long-form or voiceover-led video.

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

Silent quality check after every feature. Fix issues before telling user. Never claim tests passed without running them.

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

How the Strategist works with the user to turn their own trading idea into explicit rules, backtest it honestly on Hyperliquid candle and funding history, and paper-trade it on testnet through the desk lifecycle. Method only - the desk ships no strategies and makes no return claims. Use when the user wants to design, test, compare or paper-trade an idea.

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

Use when auditing self-media videos, scripts, covers, subtitles, voiceover, product links, account copy, comments, articles, or publishing packages for platform violation risk; especially before final delivery or publishing after video production or clipping. Covers e-commerce product consistency, Qianchuan material quality, regulated qualifications, efficacy claims, prices, gifts, activities, and pre-selection risk across WeChat, Douyin, Kuaishou, Bilibili, Xiaohongshu, TikTok, and related platforms.

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

Designs, builds, or refactors user-facing web or application interfaces with deliberate visual direction, typography, color and spacing tokens, content hierarchy, responsive behavior, accessible interaction states, and real rendered-surface verification. Use for pages, components, dashboards, landing pages, design systems, and frontend polish. Not for backend logic, API-only work, or visual claims that cannot be rendered or inspected.

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

Prepares a focused code review request for a branch, commit, pull request, or substantial working-tree diff by defining the review boundary, contract, risk areas, evidence, and questions for an independent reviewer. Use before merge or when another agent needs to review an implementation. Not for processing feedback already received or for claiming runtime correctness.

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

Verifies a completion, fix, passing, compatibility, release, or readiness claim with fresh task-specific evidence mapped to the actual requirements. Use before saying a change is done, before merge, after review fixes, and at release gates. Not a substitute for diagnosing the cause of a failing check.

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

Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.

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

Tests whether data supports a claim: A/B significance, peeking, sample size, eval error bars, multiple comparisons. Use when deciding if results are significant.

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

Designs consensus, quorums, leases, idempotency, and CRDTs. Use when facing split brain, fencing tokens, exactly-once claims, duplicate retries, stale reads, or leader flapping.

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

This skill should be used when a session's job is POST-MERGE VERIFICATION — taking merged PRs and establishing whether the change actually does what it claimed, then recording the result against its `pr_verifications` obligation. "validate the merged PRs", "work the verification backlog", "did that PR actually work", "run the post-merge E2E". It owns the obligation ledger the repo-pulse worker fills. Do NOT load it for building a change and opening its PR (that is `genesis-development`), or for driving open PRs to merge (that is `closing-session`).

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

Query patent bibliographic (catalog) information from the Nexscope patent database by patent ID or publication number. Triggered when users mention patent bibliographic info queries, patent catalog information, patent applicant queries, patent inventor queries, patent classification codes, patent abstract retrieval, patent citation analysis, patent priority claims, patent application citations, patent examiner information, patent bibliographic data, inventor lookup, applicant lookup, patent classification, patent metadata, Nexscope, or patent citations. Even if the user does not explicitly mention "bibliographic info," this skill should be triggered whenever their need involves querying detailed metadata for a specific patent by patent ID or publication number.

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

Design a source evaluation protocol using lateral reading and credibility checks for digital information. Use when students need to evaluate websites, online sources, or social media claims.

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

Map a complex topic by placing factors on hexagonal tiles where adjacency signals a claimed relationship. Use when students need to surface hidden connections in a system before analysis or action.

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

Design a Funhouse Mirror activity where students use their own domain expertise to detect AI distortions, omissions, and overconfidence. Use when students know a subject well enough to evaluate AI claims about it.

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

Check an educational practice or task for cultural bias, WEIRD assumptions, and cross-cultural validity. Use when adapting resources for diverse contexts or questioning universal claims.

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

Design a fact-checking protocol for AI-generated text, extending SIFT with AI-specific adaptations for hallucination detection. Use when students need to verify AI claims and citations.

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

Generate argument structure scaffolds using Toulmin, PEEL, or CER frameworks for a specific claim or question. Use when teaching argumentative or analytical writing across any subject.

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

Verify mini-program implementations and fixes with risk-calibrated evidence across static checks, unit tests, integration tests, state matrices, simulators, real devices, cloud environments, and release artifacts. Use when users ask to test, validate, accept, regression-check, quality-check, confirm readiness, or determine whether a mini-program feature is actually complete. Binds results to a source and build fingerprint, records commands and observable evidence, separates passed, failed, blocked, and not-run layers, prioritizes the next highest-information check, and never converts local success into device, cloud, release, or formal acceptance claims.

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

Analyze WeChat Mini Program platform constraints and evidence layers for an idea or existing repository, including source configuration, build output, WeChat DevTools loading, device behavior, permissions, privacy declarations, cloud or backend linkage, upload, trial, review, and production status. Use when users ask about WeChat-specific configuration, project roots, compile paths, capability permissions, privacy compliance, official platform rules, upload or release readiness, or why source and platform behavior differ. Performs read-only evidence classification by default, verifies time-sensitive or high-risk claims against current official WeChat sources, redacts identifiers and secrets, and never upgrades one evidence layer into another.

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

Design, preview, implement, and assess mini-program interfaces against an approved prototype, screenshot, visual reference, design system, or bounded UI request while preserving product semantics and existing accepted behavior. Use when users ask to reproduce a mini-program screen, refine visual hierarchy, adapt layouts across device sizes, handle safe areas or keyboards, inspect touch targets, scrolling, media, or gesture conflicts, compare an implementation with a reference, or prepare a device-verification matrix. Separates proposed visual previews, user approval, source integration, local checks, and real-device evidence; never invents product functionality for visual completeness or claims device validation without device-specific proof.

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

Perform a read-only, evidence-first intake of an existing mini-program repository before planning or modifying code. Use when users ask to take over, understand, audit, resume, scope, or continue a WeChat or other mini-program project; when project facts may conflict with historical documents; or when an agent needs the framework, rules, Git state, build path, risks, unknowns, protected behavior, and change boundary. Produces a project fact map and handoff without changing code, installing dependencies, building artifacts, or claiming runtime, device, cloud, upload, acceptance, or release status.

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