Build or improve a UI testing strategy covering visual regression, interaction testing, and accessibility assertions. Use when the user asks to add tests, set up testing, fix flaky tests, improve test coverage, validate UI behavior, catch visual bugs, or establish confidence in shipping frontend changes.
日本語の概要は準備中です。原文の説明を表示しています。
aladicf/better-web-ui☆ 422026年5月22日 更新
Hreflang and international SEO audit, validation, and generation. Detects common mistakes, validates language/region codes, and generates correct hreflang implementations. Use when user says "hreflang", "i18n SEO", "international SEO", "multi-language", "multi-region", or "language tags".
日本語の概要は準備中です。原文の説明を表示しています。
mits-pl/wove☆ 422026年6月20日 更新
Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".
日本語の概要は準備中です。原文の説明を表示しています。
mits-pl/wove☆ 422026年6月20日 更新
Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says "schema", "structured data", "rich results", "JSON-LD", or "markup".
日本語の概要は準備中です。原文の説明を表示しています。
mits-pl/wove☆ 422026年6月20日 更新
Lint, build, test, verify specs, commit, and push — one micro-commit to remote. Validates the working tree, verifies spec alignment, and creates an atomic save point.
日本語の概要は準備中です。原文の説明を表示しています。
villetakanen/asdlc-io☆ 422026年10月9日 更新
Register an external knowledge base library in the user-scope global registry at ~/.sdlc/global-libraries.json. Validates that the target path exists, contains a _shelf-index.md, and parses its format_version. Optional helper — hand-editing the JSON is also supported.
日本語の概要は準備中です。原文の説明を表示しています。
SteveGJones/ai-first-sdlc-practices☆ 412026年10月5日 更新
Validated commit — runs quick checks before committing. Use when ready to commit changes.
日本語の概要は準備中です。原文の説明を表示しています。
SteveGJones/ai-first-sdlc-practices☆ 412026年10月5日 更新
Run the SDLC validation pipeline using direct tool invocations. No wrapper scripts required. Use when checking code quality before commits or PRs.
日本語の概要は準備中です。原文の説明を表示しています。
SteveGJones/ai-first-sdlc-practices☆ 412026年10月5日 更新
Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.
日本語の概要は準備中です。原文の説明を表示しています。
SteveGJones/ai-first-sdlc-practices☆ 412026年10月5日 更新
Analyze a repository's type system and generate type-safe DAG execution pipelines with GraphSentry-style certificate verification. This skill should be used when building LLM-driven workflows that need deterministic type safety, when composing typed operations into validated execution graphs, or when adding contract-checked pipeline orchestration to any codebase. Supports Python (Pydantic) and TypeScript (Zod).
日本語の概要は準備中です。原文の説明を表示しています。
tdimino/claude-code-minoan☆ 412026年9月28日 更新
Coordinate SEO, LLM-readable site architecture, UX, content, monitoring, security, and external authority work as a task-plan-driven sequence. Use this skill when the user asks to plan, execute, validate, or route multi-skill website growth work; asks what to do next across semantic core, URL structure, internal linking, schema, llms.txt, UX journeys, analytics, citation monitoring, or white-hat link placement; or wants a central architect that preserves evidence, alarms, handoffs, and tests.
日本語の概要は準備中です。原文の説明を表示しています。
sergekostenchuk/seo-llm-skill-cluster☆ 402026年6月12日 更新
Validate SEO and LLM-readability claims against live HTML, local fixtures, and generated artifacts. Use this skill when the user asks to prove whether title, meta description, canonical, hreflang, JSON-LD, NewsArticle.image, OpenGraph, Twitter cards, RSS autodiscovery, robots.txt, llms.txt, sitemap, news-sitemap, crawler access, or performance evidence is actually present, and when subjective audits must become timestamped pass/fail reports.
日本語の概要は準備中です。原文の説明を表示しています。
sergekostenchuk/seo-llm-skill-cluster☆ 402026年6月12日 更新
Validate proposed or existing backlinks for relevance, editorial legitimacy, link attributes, spam/toxicity risk, platform compliance, anchor quality, target-page fit, and monitoring evidence. Use this skill when the user asks whether an external link opportunity or placed backlink is safe and useful, and reject toxic, irrelevant, paid-undisclosed, fake, or spam placements.
日本語の概要は準備中です。原文の説明を表示しています。
sergekostenchuk/seo-llm-skill-cluster☆ 402026年6月12日 更新
Builds, validates, packages, tests, and optimizes deployment-ready Skill files (SKILL.md + references/ + scripts/ + agents/) from design specifications. Three pre-build gates + 9-dimension quality gate (with D9a/b/c empirical evidence tiers) + behavioral iteration loop + automated description optimizer + blind version comparator. Use for building, reviewing, revising, testing, or optimizing Skills. Trigger on: "build this Skill," "review this Skill," "test my Skill," "optimize the description," "compare these Skill versions," "should this be a hook instead," "build a template first." Also: "my Skill doesn't activate," "my description truncates," "my SKILL.md is too long," "my Skill is overtriggering." Do NOT use when designing Skill methodology — that's design work, not packaging. Do NOT use for prompt compilation, project auditing, or prompt scoring (use rootnode-prompt-compilation, rootnode-project-audit, or rootnode-prompt-validation if available).
日本語の概要は準備中です。原文の説明を表示しています。
drayline/rootnode-skills☆ 402026年9月14日 更新
Builds complete, optimized Claude prompts and Project scaffolds from task descriptions. Use when building, designing, creating, or structuring a Claude prompt or system prompt. Trigger on: "build me a prompt," "compile a prompt for," "create a system prompt," "write a Claude prompt," "design a prompt for," "help me write a prompt," "scaffold a Claude Project," "design a Project for." Uses a four-stage methodology (Parse, Select, Construct, Validate) and a tested 5-layer architecture (Identity, Objective, Context, Reasoning, Output + Quality Control). In Project Mode, the Compiler is global-layer-aware — checks User Preferences, installed Skills, and MCP Connectors to avoid redundancy and flag gaps. Do NOT use for auditing existing prompts (use rootnode-prompt-validation if available) or diagnosing existing Projects (use rootnode-project-audit if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.
日本語の概要は準備中です。原文の説明を表示しています。
drayline/rootnode-skills☆ 402026年9月14日 更新
Self-configuring content creation pipeline with geo-lint validation. On first use, scans your project to learn its framework, content schema, categories, and authors, then creates SEO & GEO-optimized content matched to your brand voice. Validates every piece with geo-lint's 92 rules until zero violations. Triggers on: "content-creator", "create content", "write blog", "new post", "content calendar", "brand voice", "content strategy".
日本語の概要は準備中です。原文の説明を表示しています。
IJONIS/geo-lint☆ 402026年3月19日 更新
SEO & GEO content linter — validates Markdown/MDX files for AI search visibility using 92 deterministic rules (35 GEO, 32 SEO, 14 content quality, 8 technical, 3 i18n). Runs an autonomous lint-fix loop: scan content, read structured violations, fix them, re-lint until clean. Use when optimizing content for AI citations, auditing SEO compliance, checking GEO readiness, or running pre-publish content validation. Triggers on: "geo-lint", "lint content", "SEO audit", "GEO", "content optimization", "AI search", "citation readiness".
日本語の概要は準備中です。原文の説明を表示しています。
IJONIS/geo-lint☆ 402026年3月19日 更新
Validate RuField CSI or ultrasonic recording replay and its fusion boundary. Use for captured CSI JSONL, BatVu ultrasonic replay, replay adapter integration, or replay regression diagnosis.
日本語の概要は準備中です。原文の説明を表示しています。
ruvnet/rufield☆ 392026年10月14日 更新
Validate and scientifically interpret completed research runs, including negative, null, boundary, confounded, failed, and inconclusive outcomes. Use after execution to assess evidence and claim impact; not to edit methods or schedule experiments.
日本語の概要は準備中です。原文の説明を表示しています。
cpt13-g/build-research-evidence☆ 392026年9月21日 更新
Phase 2: Generate and discover tests, validate against real library. Only invoke when explicitly requested by the user or by the yoink orchestrator.
日本語の概要は準備中です。原文の説明を表示しています。
theogbrand/yoink☆ 382026年4月5日 更新
Capture reproducible screenshots from the currently booted iOS Simulator and turn them into three App Store marketing cards with validated dimensions and concise copy. Use after a successful Simulator build, during the two-minute proof lane, or when replacing prototype images with real app captures.
日本語の概要は準備中です。原文の説明を表示しています。
sean-sunagaku/claude-code-plugin☆ 382026年7月30日 更新
Perform a Computer Systems Validation (CSV) assessment following GAMP 5 methodology. Covers user requirements, risk assessment, IQ/OQ/PQ planning, traceability matrix creation, and validation summary reporting. Use when a new computerized system is being introduced in a GxP environment, when an existing validated system is undergoing significant change, when periodic revalidation is required, or when a regulatory inspection demands a validation gap analysis.
日本語の概要は準備中です。原文の説明を表示しています。
pjt222/agent-almanac☆ 372026年10月13日 更新
Format citations across academic styles (APA 7, Chicago, Vancouver, IEEE) using CSL processors and R tooling. Convert between citation styles, generate in-text citations and reference lists, and validate formatting against style guides using citeproc, knitcitations, and Quarto's built-in citation engine. Use when rendering a Quarto or R Markdown document with formatted citations, converting a bibliography between citation styles, generating a standalone reference list, or setting up citation infrastructure for a multi-document project.
日本語の概要は準備中です。原文の説明を表示しています。
pjt222/agent-almanac☆ 372026年10月13日 更新
Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.
日本語の概要は準備中です。原文の説明を表示しています。
pjt222/agent-almanac☆ 372026年10月13日 更新