4천건 · 관련도순
Performs claim-evidence verification for agent outputs, recording supported, contradicted, or insufficient-evidence results alongside source accessibility. 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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validates agent outputs against expected schemas and quality criteria. Reports structural and content checks within the declared evidence scope. Activate on 'validate output', 'output validation', 'schema validation', 'check output', 'output quality'. NOT for confidence scoring (use dag-confidence-scorer) or hallucination detection (use dag-hallucination-detector).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement WCAG 2.2 AA/AAA compliance with automated testing, keyboard navigation, screen reader support, and focus management. Activate on: accessibility audit, WCAG compliance, keyboard navigation, screen reader, aria attributes, axe-core, focus trap. NOT for: design-level accessibility review (use design-accessibility-auditor), color contrast only (use css-in-js-architect).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit an existing Coval evaluation setup for coverage, misleading scores, missing evidence, judge validation and execution risk. Read-only; use when inheriting an eval or deciding whether its results support a release decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a Coval adversarial / red-team testing report and turn it into an agent-hardening plan. Use when a user provides a Coval report URL, report export, run IDs, screenshots, or a per-scenario scorecard from an adversarial sweep and wants evidence-backed next steps such as prompt/guardrail changes, refusal hardening, verification fixes, escalation routing, or expanded attack coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to up to 15 specialists (8 always + 7 conditional), generates health score. Use when user says audit, full SEO check, analyze my site, or website health check.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when modifying anything under features/files/, app/(core)/files/, app/(public)/share/, or any caller that uploads, downloads, lists, moves, renames, shares, or previews user files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reimagine UI posture — bold from-scratch reinvention of a screen. Use when asked to rethink or reinvent a UI, merge screens, change its core interaction model, break the frame rather than polish, or generate surprising new concepts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recipe for THE DOOR LAW (every record the UI names opens; every detected problem ships its fix) and THE INVENTORY LAW. Use before building or fixing a surface that names a record or flags a problem (cell, row, dialog, badge, warning, id, count), or on 'no link to X', 'why can't I click this', 'dead end', EntityRef, peek. NOT for page chrome (use core-route-headers).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Startup rules for the app shell, layouts, and global providers. Use when editing app/Providers.tsx, app/DeferredSingletonWrapper.tsx / DeferredSingletonCore.tsx, a layout.tsx, StoreProvider, or a global provider; adding startup fetches or mount-time useEffects high in the tree; or reading auth state (isAdmin, isGuest, fingerprintId) client-side.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the current agent's thin semantic consistency review after shared Keel Core gates and before task completion, sync, archive, or meaningful handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writes and cleans up messages and docs for their channel and reader (email, Slack, a text, release notes, store pages, READMEs, Claude Docs) in a plain voice that never moves a fact. Trigger to write, rewrite, shorten, line-edit, retell or change the tone of any message, even a two-line text; to strip dashes or AI tells; to fix UI wording (a dialog, button or error); to score text without rewriting; to plan release comms; to write a store page, launch post or listing title, blurb and tags; to write in a voice or learn one; or say commscribe (draft, reshape, humanize, audit, retell, formats, cadence, voice, docs). It never sends. A skill's own files (SKILL.md, references) are skillwright's; brand voice and layout brandscribe's; sourced write-ups researchscribe's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds, audits and packages Agent Skills, with their evals. Trigger to build, audit (security too), score or package a skill or SKILL.md; to design or integrate a pack; whether a skill beats incumbents; for trigger evals, test cases or assertion suites (skill, prompt card, agent spec); to slim a skill; when a skill did not fire or a run cost too much; for a prose pass on a skill's own files; to port or sanitize a skill set; to build or contract-test the MCP tools a plugin or mod ships; or say skillwright (evals, slim, diagnose, mcp, refresh, port, pack, integrate, upkeep). Prompt tuning is promptwright's; running a suite, claude plugin eval's; config slims, rigwright's; other docs, commscribe's; brands, brandscribe's; runtime grants, gatewarden's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Vets third-party skills, plugins, MCP servers, GitHub Actions and model weights before install, with a verdict (PASS, CONDITIONAL, HOLD, FAIL) and install terms. Trigger on any should-I-install question, even with its files or hooks pasted in or a scan already clean; is this skill safe, vet this MCP server, check this GitHub Action, is this checkpoint safe or commercially usable, what does this installer write, a licence check before a fold-in, what changed in a plugin update; or say trustwarden (vet, revet, terms, refresh). Uses skillspector, zizmor, pinact and Scorecard when present; lists files no scanner read. Runtime permissions are gatewarden's; secrets shieldwarden's; your own skills skillwright's; sandboxing a download hypervrunner's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs image, video and audio generation on a local ComfyUI server and guards the GPU before long renders. Trigger to generate an image, video, audio or music locally; to run, test or check a ComfyUI workflow before a long or queued render; when a video render crashed the machine, ran out of memory or hung in VAE decode; to render while LM Studio holds the GPU; to run a pixelsmith brief locally; or say comfyrunner (audit, check, test, run, status). Refuses an untiled video decode and scores resolution times frames. Briefs and judging art are pixelsmith's; sound briefs soundsmith's; freeing LM Studio lmstudiorunner's; schedules agentwright's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Directs screens and proves they fit — game menus and HUD, web dashboards, single-page artifacts, store-page layouts and plugin panes. Writes the design brief (layout, hierarchy, spacing and type scales, every state, focus and hit size, a check against generic-looking output) and probes the rendered page at phone-to-desktop widths in every theme. Trigger to design or lay out a menu, HUD, dashboard, settings screen or panel, or review its mockup before the build; when a page scrolls sideways on a phone, text is clipped or a dark theme breaks; to check that a page or pane fits from 320 to 1440 px in light and dark; for UI direction before a build, even when nobody says design; or say uismith (direct, probe, fit-first audit). The probe needs optional Playwright. A critique, scored review or brand pass of a built page, palettes and type are brandscribe's; sprites and icons pixelsmith's; Godot scene proof godotsmith's; words commscribe's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run convex-doctor static analysis, interpret findings, and fix issues across security, performance, correctness, schema, and architecture categories. Use when running convex-doctor, fixing convex-doctor warnings or errors, improving the convex-doctor score, or when asked about Convex code quality, static analysis, or linting Convex functions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write JavaScript code in the style of Dan Abramov, co-creator of Redux and React core team member. Emphasizes predictable state management, composition over inheritance, and developer experience. Use when building React applications or managing complex state.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[62] VALIDATE. Final self-check before delivery. Verify goal alignment, completeness, correctness, and identify residual risks. Produces quality score (0-100) and delivery status. Use when completing any significant work, before handoff, or when you need confidence that work is ready.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[30] ANALYZE. Understand how changes impact the system — what's the core, what's affected, what depends on what. Use when planning changes, analyzing systems, debugging issues, or anytime you need to see the full picture of cause and effect. Triggers on "what's affected", "impact analysis", "dependencies", "scope mapping", or when you need to understand ripple effects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.