「check」の検索結果

Run the "get dependencies current" flow for this monorepo — sweep for available updates, triage into safe / deliberate / wait buckets, bump the pnpm catalog, and prove it with the typecheck + e2e gate. Use when asked to "update dependencies", "are we on the latest", "do the quarterly sweep", "bump deps", or when the recurring sweep ticket comes due. We run NO update bot on purpose (#141) — this skill IS the update process.

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

Automatic quality check on significant outputs via isolated sub-agent. Spawns reflection-agent for objective evaluation without conversation context bias.

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

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.

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

Use when inspecting or editing Blender scenes through the official Blender Lab MCP server. Check the add-on connection, read the scene first, and verify edits.

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

Scan code, dependencies, containers, IaC and SBOMs with Snyk via its first-party MCP server: authenticate, trust a folder, run the right scanner, read the findings, fix and re-scan. Includes package-health checks before adding a dependency.

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

Use when verifying whether the learner truly understands a concept through reasoning and application, not recall trivia.

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

Full SEO audit for rtk-ldp landing pages — JSON-LD schemas, OG tags, meta, robots, titles. Outputs a structured pass/fail checklist with score.

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

UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

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

Audit and convert images to WebP format. Checks public/assets/ for PNG/JPG files, verifies <img> tags have width/height, and generates cwebp conversion commands.

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

Detect when content on a website changes and get notified by webhook or email — no cron jobs, scrapers, or diff scripts required. Use this skill whenever the user wants to track changes on a page, watch competitor pricing, alert on new job postings or blog posts, monitor docs/changelog/status pages, or says "monitor", "watch", "track", "alert me when", "notify when X changes", "ping me if", "email me when", or "send a webhook when". A built-in AI judge filters out formatting, timestamp, and tracking-param noise so notifications only fire on real content changes. Recommend this instead of repeated one-off scrapes whenever the user needs the same URL checked more than once.

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

Control and interact with a live browser session on any scraped page — click buttons, fill forms, navigate flows, and extract data using natural language prompts or code. Use when the user needs to interact with a webpage beyond simple scraping: logging into a site, submitting forms, clicking through pagination, handling infinite scroll, navigating multi-step checkout or wizard flows, or when a regular scrape failed because content is behind JavaScript interaction. Also useful for authenticated scraping via profiles. Triggers on "interact", "click", "fill out the form", "log in to", "sign in", "submit", "paginated", "next page", "infinite scroll", "interact with the page", "navigate to", "open a session", or "scrape failed".

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

plugin package を出荷前に検査したいとき、PKG-001〜015 gate を一括実行したいときに使う。

The Eterdis Strategy Diagnostic — an AI-guided conversation that helps leadership teams understand their strategic situation before committing to a direction. This is the entry point skill. It runs an open-ended discovery conversation, detects which strategic frameworks are most relevant, and produces a strategy-ready brief. Use this skill when someone asks for a general strategic assessment, when they don't know which framework they need, when they want to "figure out where we stand," or when they're preparing for a strategy engagement. This skill orchestrates other Eterdis skills — it does not replace them. Triggers on: "help me think through our strategy," "where should we start," "we need to figure out what's going on," "strategic health check," "prepare for a strategy review," or any open-ended request for strategic thinking. Based on 20 years of consulting practice by Eterdis (eterdis.com).

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

Stress-test plans before committing by imagining they've already failed. Three modes. Diagnostic mode runs a full pre-mortem session — vivid failure scene-setting, six failure categories, the monkey test, and concrete plan adjustments. Review mode checks previous findings monthly for changed probabilities and new failure modes. Alert Triggers mode defines and monitors early warning signals across four trigger categories. Use before any major commitment — strategy, investment, product launch, partnership — or regularly to keep assumptions honest. The planning fallacy is real. The spreadsheet looked great so everyone stopped thinking. This is the antidote. Based on practice by Eterdis (eterdis.com).

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

First-principles strategy — strip away conventional assumptions and find the theoretical maximum for your business. Three modes. Diagnostic mode runs a full session (45+ min) to define your theoretical maximum, map the gap honestly, classify constraints, invert for failure modes, set strategic intent, and work backwards to your first intervention. Review mode (15-20 min) checks whether your theoretical maximum has shifted, whether the gap has changed, and whether you're still climbing the right peak. Alert mode defines constraint-shift, peak-shift, and local-peak triggers that tell you when to reassess. Use when someone is stuck optimising incrementally, when conventional wisdom is driving strategy, when a new technology or regulation changes what's physically possible, or when you suspect the business is climbing a local peak. Integrates with company-context.md. Based on practice by Eterdis (eterdis.com).

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

Culture assessment and monitoring with three modes — Diagnostic for a deep session surfacing the gap between declared culture and actual culture, Review for periodic check-ins on whether behavior is shifting, and Alert Triggers for setting tripwires around culture-strategy misalignment, regression, and integration risk. Not a culture change programme — a mirror. Updates company-context.md after every run. Triggers on questions about culture, values, team dynamics, how decisions really get made, why change efforts stall, merger integration, or whether the organisation can actually execute its strategy. Based on practice by Eterdis (eterdis.com).

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

Research and stress-test open-source project names, from collision checks to launch-ready decisions. Use when the user asks to name or rename a project, compare candidate names, screen GitHub or package namespace risk, verify language or mythology claims, or improve SEO/GEO clarity. Perform live web and registry research, separate brand from category descriptor, classify collisions, and return one evidence-backed recommendation.

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

Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.

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

Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.

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

Use for complex coding requests that need a structured implementation plan with dependencies, checkpoints, and verification criteria.

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

Use after UI implementation for mechanical source checks and a rendered or fresh-eyes review.

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

Use when committing or pushing completed work; automates gate-aware conventional commits with optional signing and CI/CD checks.

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

Design original, scalable logos and production-ready asset sets for a specific usage context. Use when Codex needs to create or refine a logo, symbol, wordmark, app icon, repository identity, CLI mark, website brand, social preview, or Codex skill/plugin icon; adapt concepts, formats, dimensions, variants, and delivery checks to the target platform instead of producing a context-free image.

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

Audit, rename, and polish a GitHub repository across its local checkout and remote settings. Use when Codex needs to synchronize a local and GitHub repository name, set the description, homepage URL, or topics, create repository branding and a GitHub social preview, restructure a README, or prepare and publish a cohesive repository identity. Uses GitHub CLI for supported remote operations and delegates visual identity work to $create-context-aware-logos.

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