2,445 件 ・ 関連度順
概要と使いどころ
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate end-to-end deployments across Stripe, Supabase, and Vercel using the Composio CLI. Update pricing, apply database migrations, deploy frontend, verify changes, and announce releases from a single script.
日本語の概要は準備中です。原文の説明を表示しています。
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.
日本語の概要は準備中です。原文の説明を表示しています。
Get started with Xpoz — set up authentication, verify your account, configure tracking, and discover available skills. Use when asked to "set up Xpoz", "connect to Xpoz", "get started with Xpoz", "what can Xpoz do", "new to Xpoz", "install Xpoz", or "my Xpoz account".
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous goal loop — give it ONE goal plus how to verify it, the agent runs check→fix→check itself and comes back only with the finished result (code with audit, research with fact-check, content with critique, audit/backtest). Self-verification instead of constant supervision, with hard safety guards. Vary the loop with a verification rubric designed before it runs. Triggers — "work autonomously to the result", "don't come back until it's done", "run the loop yourself", "drive it to done".
日本語の概要は準備中です。原文の説明を表示しています。
Deliberate system-improvement loop — audit your own Claude Code setup (rules / memory / skills / MCP / agents / registry), evaluate incoming tools via /vet, adopt the worthwhile ones with discipline (backup → verify), and record every decision. Use when bringing in a tool/idea/collection to improve the setup, or when doing a tooling-improvement pass. Triggers — "upgrade the workflow", "audit our setup", "let's improve the tooling", "evaluate this for us", when handed a post/repo/reel with a tool.
日本語の概要は準備中です。原文の説明を表示しています。
Prove — or honestly fail to prove — a specific technical claim: "the fix works", "it's deployed", "the service is running", "the site is done", "there are no vulnerabilities". Atomizes the claim, picks the shortest decisive signal on the evidence ladder, and returns a verdict from a fixed vocabulary (pass / partial / fail / skip) with an explicit coverage boundary. NOT code review, NOT a fix, NOT orchestration — only "what is proven, and what we merely hope". Triggers — "prove it works", "is it really done?", "are you sure?", "we deployed — is it live?", "verify that", "did we actually check?".
日本語の概要は準備中です。原文の説明を表示しています。
OWASP ASVS v5.0 security verification skill with Drupal 11 mappings. Use when performing security code reviews, implementing security requirements, or verifying security compliance in Drupal projects.
日本語の概要は準備中です。原文の説明を表示しています。
How to fetch the latest github/gh-aw release binary — either as the gh CLI extension (gh aw ...) or as a raw platform binary downloaded from GitHub Releases — including how to resolve the latest tag, pick the right asset, and verify its checksum.
日本語の概要は準備中です。原文の説明を表示しています。
Publish and verify a released GEODE version across GitHub Release and PyPI/uv. Use for uv/uvx distribution, stable promotions, release repair runs, and public installation-channel audits.
日本語の概要は準備中です。原文の説明を表示しています。
Trigger when: (1) the user mentions "manim", "scene", "video", "EN/KO render", "GEODE_HERO_LANG", "1080p60", or (2) editing files under `scripts/visualizations/` ending in `.py`, or (3) the user asks to render, re-render, or extend any of the four validated scenes (`geode_hero.py`, `autoresearch_filewalk.py`, `autoresearch_compare.py`, `critical_floor.py`). GEODE Manim Scene authoring standard. Locks the patterns the four validated scenes already share — Anthropic-style palette, Helvetica Neue + Pretendard font pairing with weight=NORMAL, EN/KO multilingual lang via `GEODE_HERO_LANG` env, `_dashed_arrow_with_head` stage-coupled tinting, `verify_hero_layout.py` ratchet — so the next scene does not re-discover the kerning / padding / transition regressions catalogued in [[viz-frame-audit]].
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and repair a failed GEODE smoke workflow within the requested acceptance criteria. Preserve failed evidence, verify the shared root cause, and apply merge, rebuild, or live rerun stages only when authorized.
日本語の概要は準備中です。原文の説明を表示しています。
Use an available Codex MCP integration as a read-only second-opinion verifier for GEODE code reviews, GAP audits, and contract checks. Use only when the user requests Codex cross-checking and the current tool inventory exposes the required MCP tools.
日本語の概要は準備中です。原文の説明を表示しています。
VitePress documentation workflow for Software Metrics Machine docs under docs/vitepress. Use when creating, updating, reviewing, or restyling SMM documentation pages, especially feature docs that must keep CLI terminal examples and dashboard views/screenshots in sync. Covers Markdown style, VitePress tabs, command examples, dashboard screenshots, sidebar links, and docs validation. USE FOR: docs/vitepress, VitePress docs, documentation style, CLI docs, dashboard docs, screenshots, feature pages. DO NOT USE FOR: application code changes unless needed to verify documented behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Used by the Reviewer agent during Phase 9 (DesignVerify) and Phase 11 (Quality) to evaluate frontend code. Assesses visual hierarchy, spacing consistency, accessibility, and detects formulaic 'AI slop' design patterns, providing actionable feedback to the Developer.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging methodology. Reproduce → Isolate → Hypothesize → Verify → Fix → Confirm.
日本語の概要は準備中です。原文の説明を表示しています。
Calculates pre-petition interest for bankruptcy proofs of claim and produces a filing-ready worksheet. Covers rate source hierarchy, day-count conventions, simple interest formulas, post-petition rules under 11 U.S.C. § 506(b), and fee inclusion standards. Use when preparing interest components of a proof of claim, calculating creditor claim amounts, or verifying interest calculations.
日本語の概要は準備中です。原文の説明を表示しています。
Citation format and verification protocol for legal documents that draw on Bates-stamped source records. Defines the bracket citation format, multi-source citation rules, quotation handling, the verification pass that runs before output, and the [UNVERIFIED] flag protocol. Use this skill any time another skill produces a legal work product that cites Bates-stamped pages, including medical chronologies, deposition summaries, demand letters, case briefs, and discovery responses. Also use any time the user asks how to format a citation or verify that a claim is supported by the source.
日本語の概要は準備中です。原文の説明を表示しています。
Validates and summarizes the four required authorization forms in a personal injury matter (retainer, HIPAA release, insurance authorization, employment record release). Confirms signatures, dates, scope, and completeness to determine readiness for the investigation phase. Use when reviewing client onboarding packets, verifying authorization forms before discovery, or checking HIPAA and record-release compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically QA-tests a web app and fixes bugs: test, then iteratively fix, re-verify, commit each fix. Tiers: Quick, Standard, Exhaustive. Produces before/after health scores and fix evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Unified verification: build → lint → test → type-check → coverage. Use for 'is it green' / 'run all checks'; auto-called by mk:cook. NOT for lint only (mk:lint-and-validate).
日本語の概要は準備中です。原文の説明を表示しています。
Autonomously improve one measurable metric via bounded, git-tracked iterations: one scoped change, verify, keep or revert. NOT for cleanup (mk:cook), known-cause bugs (mk:fix), or shipping (mk:ship).
日本語の概要は準備中です。原文の説明を表示しています。
Linting and static analysis after code edits. Triggers on lint, format, check, validate, types. NOT for full build verification (mk:verify) or test coverage (mk:testing).
日本語の概要は準備中です。原文の説明を表示しています。
Build error triage: detect language, load fix patterns, auto-retry. Chains into mk:verify. NOT for runtime errors (mk:fix); NOT for architecture debugging (mk:investigate).
日本語の概要は準備中です。原文の説明を表示しています。