「every」の検索結果

Load this skill for every project containing interactive UI elements — buttons, links, modals, dropdowns, sliders, tabs, carousels, or any custom widget. Under no circumstances create an interactive component that cannot be fully operated by keyboard alone. Absolutely always ensure visible focus indicators, logical tab order, and no keyboard traps. Apply these rules to every interactive element without exception.

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

Write minimal, accessible web UI without over-engineering, adapting to whatever stack the project uses — React, Vue, Svelte, Angular, web components, or plain HTML. Use this skill on every project and every task that writes or reviews markup or components, builds forms, adds interactive elements like buttons, dialogs, accordions, or tabs, or audits code for accessibility — even when the user never mentions accessibility, and even inside a framework, CMS, or design system. It's non-negotiable regardless of project type, stack, or deadline. About to reach for ARIA attributes, a dialog library, a focus-trap package, or a headless UI component? Use this skill first.

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

[Code Quality] Use to validate a spec artifact's decisions with the user across three contexts — a freshly-authored Feature Spec (idea-to-spec), an existing canonical spec before PBI decomposition (spec-to-pbi), or a refined idea + §8 test-specs (idea-to-pbi deep mode). Detects the context, walks every applicable validation category, and runs an exhaustive but budget-bounded blocking clarification gate so every non-obvious or conflicting decision is confirmed before the artifact drives downstream work.

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

Phase 4 Turn 2 of disease-market-sizing-orchestration (A6' upgrade). Audits compose output via Cite-or-Block strict — every anchor must reverse-resolve to an actual file in sources/, every fact claim must have an anchor. Returns verdict (ok/blocked) + violations list. Use AFTER cite-bound-content-generator (Turn 1), BEFORE report-bundle-builder (phase 5).

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

Multi-angle deep-research workflow over Ahmad's OpenMark knowledge graph (13k+ bookmarks). Use whenever Ahmad asks anything that requires more than one search to answer well — "what's the landscape of X in my saves", "do a deep dive on Y", "research X across my bookmarks", "compare what I saved about X vs Y", "give me everything on X". Also use when fast-search returned thin results and Ahmad pushed back ("dig deeper", "more results", "actually research it"). Pairs Neo4j graph search with WebFetch on top picks to bring back fresh page content. Triggers on "deep research", "dig deeper", "research", "landscape", "everything on", "thorough", "comprehensive".

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

Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).

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

Builds a DRAFT stakeholder map for one project from the charter, organisation chart, RACI, governance terms, steering minutes, meeting notes and messages the user provides: a stakeholder register, interest and influence ratings each with its stated basis, stance as evidenced by a verbatim fragment with source and date, gaps, and a proposed engagement plan per stakeholder, every line traced to a source and every missing fact marked UNKNOWN. Use when the user asks to "build the stakeholder map", "who are the stakeholders on this project", "map interest and influence", "where does each stakeholder stand", "draft the stakeholder engagement plan" or "refresh the stakeholder register". Do not use for a customer account's stakeholders, use account-plan-builder instead; for a one-page brief before one meeting, use meeting-prep-onepager; for logging decisions and risks against the project, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.

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

Drafts one weekly status update or team status email (done, in progress, blocked, next, asks) from the notes, task lists, tracker exports and messages the user attaches, pastes or makes reachable, every bullet traced to a source and every gap marked UNKNOWN, returned in the chat as Markdown for the user to review and send. Use when the user asks to "write my weekly status update", "draft the team status email", "turn my notes into a status report", "what did we get done this week", "summarise this week for my manager" or "prepare Friday's update". Do not use for maintaining a project's living logs or a project-level report built from them, use project-status-tracker instead. Drafts for human review; never approves, authorises or signs off.

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

Prepares a DRAFT data incident impact brief from the incident notes and data inventory the user provides: the timeline as stated, systems involved matched to the inventory, data categories held and evidenced as involved, people and record counts potentially affected with the source and method behind every figure, third parties, notification questions for legal and the data protection officer, and every UNKNOWN with the evidence that would settle it. No legal determination: it never states whether the incident is a reportable breach, whether notice is due, to whom or by when. Use when the user asks to "prepare the impact brief for this incident", "what data was involved", "how many people are affected", "map the incident to our data inventory" or "pull together what legal needs on the incident". Do not use for the blameless postmortem or root-cause timeline, use incident-postmortem-drafter instead. Drafts for human review; never approves, authorises or signs off.

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

Summarises one sprint from the board export, sprint report and review or stand-up notes the user provides into a one-page DRAFT sprint review summary: the sprint goal as written, items delivered, items not delivered with the reasons the sources state, carry-over, impediments, metrics exactly as given, and numbered questions for the retrospective, every row referenced to a work item or note fragment and every missing fact marked UNKNOWN. Use when the user asks to "summarise the sprint", "write the sprint review", "what did we deliver this sprint", "list the carry-over and blockers" or "draft the sprint recap". Do not use for the retrospective write-up or themed lessons across several sprints, use lessons-learned-synthesis instead; for a weekly project status report, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.

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

Turns one meeting transcript, recording recap or set of raw notes into concise DRAFT minutes returned in the chat as a single Markdown document: header metadata, attendance and apologies, agenda items each with a short neutral summary and outcome, numbered decisions with an owner, numbered action items with owner and due date, open questions, carried-over actions and the next-meeting line, every entry backed by a short verbatim source fragment and every missing fact marked UNKNOWN. Use when the user asks to "write the minutes", "draft minutes from this transcript", "turn these notes into meeting minutes", "produce the minutes of meeting for today's call", "tidy my rough minutes into the standard format" or "prepare the minutes for circulation". Do not use for extracting action items, task lists or per-owner follow-up emails alone, use transcript-to-actions instead. Drafts for human review; never approves, authorises or signs off.

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

Applies a change-safety review to any requested file, mail or calendar change: lists every create, modify, move, rename, archive or delete before proposing it, marks destructive items as requiring the user's typed confirmation, proposes versioned file names instead of overwrites, declines to draft bulk destructive operations, and drafts a change journal entry for the user to keep. Use when the user asks to "clean up this folder", "delete the old versions", "reorganise these files", "archive everything older than a year", "rename and move these documents" or "make sure nothing gets overwritten while we work", or when any task is about to create or modify files, emails or calendar items. Do not use for backing up, journalling or restoring a skills folder, use skills-backup-keeper instead. Drafts for human review; never approves, authorises or signs off.

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

Turns one long support ticket thread (helpdesk history, email chain, chat transcript, call notes) into a one-page DRAFT escalation summary: the customer's ask in their own words, account context as stated, a dated history, what was tried and the stated result of each attempt, the current state, and what is needed from whom by when, every line referenced to a message and every missing fact marked UNKNOWN. Use when the user asks to "escalate this ticket", "summarise this thread for tier two", "write the hand-over for this case", "what has been tried so far", "brief engineering on this customer issue" or "prepare the escalation note". Do not use for a batch of tickets, use ticket-triage-pack instead; for the review after an outage, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

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

Read a media file's real structure with ffprobe through media_run - the JSON invocation and how to read it, what every family of field means, how to count frames, sample without decoding everything, detect HDR and interlacing, and diagnose a missing duration, a stream with no frames or a container that lies. Covers when media_probe's own report is already enough.

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

Reimagine an everyday photograph as a cinematic live-action film still using motivated lighting, source-aware framing and restrained color, with optional original subtitles. Use for 电影剧照, 日常电影画面, cinematic photo scenes, or a film-like moment from a supplied photograph.

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

Run an investor-outreach wave end to end: assemble the batch of targets, personalize pitches from real templates, send from the designated account, and log every touch in the CRM. Walks the exact checklist with rate limits and dedup against everyone already contacted. Triggers: "/notpeople-wave", "next outreach batch".

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

Eat the elephant one bite at a time: turn a large list-shaped job into a finite routine that chews a small batch every night, detects when it is done, switches itself off and reports. Triggers: /elephant, eat the elephant, split into bites, make it a routine, ten a day, backfill everything.

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

Programmatically clear WP Rocket cache from a third-party plugin / theme when data changes — the public rocket_clean_* function family (rocket_clean_post, rocket_clean_files, rocket_clean_term, rocket_clean_user, rocket_clean_home, rocket_clean_minify, rocket_clean_cache_busting, rocket_clean_domain, rocket_clean_cache_dir). Critical detection rule — WP Rocket is a PAID plugin not on Packagist; always feature-detect via function_exists('rocket_clean_post') OR defined('WP_ROCKET_VERSION') before calling, since not every site has it. Never raw-unlink the cache directory or call wp_cache_flush() expecting it to clear WP Rocket — wp_cache_flush is WP object cache, WP Rocket is FILE cache. The before_*_clean_* / after_*_clean_* action lifecycle hooks fire around every clean — useful for audit logging, monitoring, custom invalidation chains. Use when integrating cache invalidation in a companion plugin, WC integration, custom data plugin. Triggers on rocket_clean_, before_rocket_clean, af...

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

Cold start — every GPU, every model size GPU Model ZSE vLLM Speedup NVIDIA T4 (16 GB) Qwen2.

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

Check the latest Claude (Anthropic), OpenAI Codex, and Google Gemini model releases from official primary sources, update model selections in this dotfiles repo, and update the Claude Code, Codex, and Gemini CLIs through their configured managers. Every run checks both the model settings and CLI for the selected provider, then scans the invoking repository for hardcoded model IDs. Use when the user asks to "モデル更新", "モデルを最新に", "最新モデル確認", "Codex/Claude Code/Gemini CLI本体の更新", "model bump", "update models", or "update agent CLIs". Do NOT use for one-off model selection in a single conversation, general model questions, or unrelated package updates.

Produce a single consolidated hardening report for the DSH node. Runs audit.sh, dome-check.sh, and machine-probe.py, parses their outputs, and writes one markdown file listing every passing check, every failure with a specific remediation command, and a top-line verdict (ALL GREEN / N ISSUES). Non-destructive — reads only, no auto-fix.

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

Rory Sutherland's 'psycho-logic' approach to marketing, product, and business problems — solve the human perception, not just the engineering or economic metric. Use when the obvious 'logical' fix is expensive, slow, or already done by every competitor; when the user asks 'how do we make people want X', 'the product/price/funnel is fine but nobody converts', 'how do we stand out', 'is there a cheaper way to fix this', or mentions behavioral economics, nudges, irrational behavior, perception, or 'it doesn't make sense but it works'. This is the ROUTER skill: it diagnoses the problem in human terms, then dispatches to reframing, costly-signaling, counterintuitive-tests, or experience-design. Inspired by Rory Sutherland's book *Alchemy*. 日本語の相談（「商品はいいのに売れない」「値下げしかない？」「競合と差別化できない」）にも使う。中文咨询（“产品很好却卖不动”“只能降价吗？”“无法差异化”）也适用。For a catalogue of individual biases, use marketing-psychology (separate plugin) instead.

Token-slim mode — cut this session's token usage by routing every file read, code search, directory listing, and JSON dump through the token-slim MCP server (or its binary directly). Works in any repository or folder; the server itself is LLM-agnostic (any MCP client). Use when the user types /slim, or asks to save/reduce tokens, "トークン節約", "トークン削減", "コンテキスト節約", "token slim".

Daily per-section review cycle driving a section toward the smallest, clearest form that still does everything it does today. Selects its section live each run (scripted), inventories every file, derives the target shape before any scan, works parallel reading threads into one ranked list and strikes it on a 2-3h budget. One PR per run; each run's report and Needs-Peter queue live in its own docs/health/runs/ file; 'resume' applies Peter's answers later. Use for the morning section-improvement run, 'doctor <section>', or 'run section doctor'.

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