「sse」の検索結果

Scaffold or migrate a repository onto release-please. Generates release-please-config.json, .release-please-manifest.json, and a release-please.yml workflow, plus an opt-in menu of tag-keyed deploy/publish templates (Docker/ECR matrix, frontend host deploy, npm OIDC publish, GitHub Release asset, Fly.io deploy, generic). Supports monorepo (mutual exclude-paths matrix), single-package, and mixed-language (node/simple/python) repos. Use when user runs /release-please-setup, mentions "release please", "set up release please", "automate releases", "conventional-commit releases", "monorepo release automation", or "migrate to release-please".

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

Holistic page-experience self-assessment mirroring Google's own question list: Core Web Vitals, HTTPS, intrusive interstitials, mobile usability, content prominence, and ad distinguishability. Use when user says "page experience", "UX signals", "interstitials", "mobile friendly", or "HTTPS check".

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

Content quality and E-E-A-T analysis with AI citation readiness assessment. Enhanced with live Ahrefs (actual keyword rankings, positions) and GSC (search query performance) data to validate static E-E-A-T analysis with real user behavior. Use when user says "content quality", "E-E-A-T", "content analysis", "readability check", "thin content", or "content audit".

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

Analyze a domain's anchor text distribution from Ahrefs: see the breakdown of anchor text used across all backlinks and assess link profile health. Use when user says "anchor text", "anchor analysis", "anchor distribution", "link anchors", or "anchor text profile".

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

Use when the user wants to transact on any Volcengine commercial product — purchase/provision it, ask what it costs, or unsubscribe from it. Covers three actions: buy (purchase, subscribe, provision, open, place an order; Chinese "开通 / 购买 / 下单 / 买 / 售卖 / 订购"), price (how much does it cost, quote, billing rules, estimated spend; Chinese "多少钱 / 价格 / 报价 / 费用 / 怎么收费 / 如何计费 / 预估费用"), and unsubscribe (cancel a subscription, refund a prepaid instance; Chinese "退订 / 退款 / 取消订阅"). Trigger even when the user does not mention "sale" but expresses a clear purchase, pricing, or cancellation intent toward a Volcengine product. Only handles these three transaction actions; anything outside them is out of scope.

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

Create, run, and maintain API test collections using Bruno (OpenCollection YAML format and legacy Bru format). Use when the user wants to: (1) create a Bruno API test collection from scratch or from OpenAPI/Swagger specs, (2) write API request files with tests and assertions, (3) run API tests using bru CLI, (4) generate test reports (HTML, JUnit, JSON), (5) set up CI/CD pipelines (GitHub Actions) for automated API testing, (6) debug or fix failing Bruno API tests, (7) add environment configurations for API testing, (8) chain API requests with data extraction, or (9) work with any .yml/.bru Bruno collection files. Triggers on mentions of 'Bruno', 'bru CLI', 'API testing collection', 'OpenCollection', or requests to automate API testing with file-based collections.

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

Rewrite raw meeting audio transcriptions into clean, accurate meeting minutes in Traditional Chinese. Use when the user has an unprocessed audio transcription file with recognition errors and needs it cleaned up into proper meeting minutes.

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

Drive running Unity Editor from shell to verify compiles, playmode, scenes, screenshots. Use when editing C# scripts, scenes, or assets in a Unity project and needing to: (1) check compilation succeeds, (2) read console errors, (3) enter/exit Play mode, (4) capture screenshots or frame recordings, (5) select objects or aim the Scene camera, (6) query editor window layout. Injects a file-polling command bridge (UnityRemote.cs) — prefer this over batchmode (fights the Library lock) or GUI automation.

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

Write professional press releases in Traditional Chinese (zh-TW) following inverted pyramid structure, 5W1H framework, and Taiwan media conventions. Use when the user wants to: (1) write a press release or news announcement, (2) draft corporate communications for media dissemination, (3) craft a lede or headline for a news release, (4) review or improve press release structure and newsworthiness, (5) write any 新聞稿 or 媒體通知, or (6) format announcements following journalistic standards.

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

Use for BayeSED3 galaxy / AGN SED synthesis/analysis, priors, Results analysis, evidence comparison, advanced run modes, Launcher Inspect (`results` / `plot` / `priors`), and assembling Launcher Run argv. Trigger on vague asks like "how do I fit this galaxy?"

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

Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.

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

Systematic technical debt analysis across architecture, testing, documentation, and infrastructure. Investigates the codebase, scores findings by impact and effort, and generates a prioritized TECH_DEBT.md remediation plan. Delegates to specialized skills for code quality (scout) and linting (lint-fix). Use when assessing overall project health, planning cleanup sprints, or onboarding to an unfamiliar codebase.

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

Guide for authoring Pulumi ComponentResource classes. Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages.

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

Audit a codebase against well-known software design principles: SOLID, DRY, YAGNI, KISS, Law of Demeter, Separation of Concerns, Composition over Inheritance, and the code-relevant 12-Factor subset. Scores findings by impact and effort, runs adversarial debate on contested violations, and generates a prioritized DESIGN_AUDIT.md. Use when reviewing code quality beyond what linters catch, assessing design health before a refactor, or onboarding to an unfamiliar codebase. Can be invoked standalone or delegated from tech-debt.

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

Comprehensive security audit covering OWASP Top 10, secrets detection, supply chain security, threat modeling, and language-specific vulnerability patterns. Investigates actual code paths rather than grep-matching keywords. Generates a scored SECURITY_AUDIT.md with prioritized remediation. Use when assessing application security, preparing for a security review, or onboarding to a codebase with security concerns.

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

Code comment accuracy verification, documentation completeness assessment, comment rot detection.

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

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

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

PCBWay fabrication and turnkey assembly workflows. Load the canonical Circuit Weaver skill from `skills/pcbway/SKILL.md`.

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

JLCPCB fabrication and assembly preparation, quoting, and constraints. Load the canonical Circuit Weaver skill from `skills/jlcpcb/SKILL.md`.

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

Run a task iteratively over a user-specified duration by dispatching subagents. The orchestrator stays strictly linear and time-checked, but each iteration fans out MULTIPLE subagents in parallel over independent units (and those subagents may fan out further). Shared state — a compact progress digest and a growing environment cheatsheet — lives on disk and is passed to every subagent BY REFERENCE, killing the per-subagent rediscovery tax. Every subagent first reads an initialiser preamble that points it at that shared state and makes it write findings back, so the cheatsheet populates itself; role prompts are produced ONCE on the filesystem by a single scaffold command and dispatched by path, never re-typed per dispatch. Subagents persist their results to disk and return only a tiny status, so the orchestrator's context stays small and lasts. The orchestrator classifies the goal as FINITE or OPEN-ENDED: finite lists may finish early; open-ended goals use the full duration, never idle, never manufacture busywork. Use when the user gives a task and a duration and wants it ground out iteratively by subagents over that time.

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

Build a timeframe-bounded research dossier by decomposing a topic into year orchestrators and month-level research passes that each write one condensed paragraph plus sources directly into a target file. Use when the user asks for a dossier, timeline, chronology, release history, or month-by-month research bounded by specific years or months. Not for timeless explainers or single-document summaries with no temporal scope.

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

Improve an existing agent SKILL.md through one gated cycle: select the target (default this skill), snapshot the committed baseline, diagnose against skill-design-principles plus four rubric dimensions, apply exactly one focused change, and ship only if a different agent than the author PASSes with quoted evidence. Use when the user says "improve this skill", "improve-skill", "iterate on SKILL.md", or "apply skill-design-principles to a skill". Do not use for code slop over a duration (anneal), generic timeboxed work (timeboxed-iterating), graph orchestration (workgraph), metric hill-climb on a codebase (autoresearch), or stripping slop from existing prose (catalog-deslop).

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

Run work as an explicit event-driven state machine executed by subagents. The orchestrator is the runtime from the canonical loop — `state, effects = init(machine); execute(effects); while state is active: event = nextEvent(); state, effects = transition(machine, state, event); execute(effects); return state.output`. All routing judgment is authored ONCE, at plan time, into a machine file (states, event alphabet, transition table, budgets, final states); at runtime the orchestrator does pure table lookups and dispatches effects — it never decides, never authors, never ingests artifacts. Subagent/sync protocol is the timeboxed-iterating one: role prompts scaffolded once to disk and dispatched BY PATH, an initialiser preamble every subagent reads first, a self-populating cheatsheet, per-unit files, tiny structured returns, independent measurement gate. Use when the user says "workmachine", "run this as a state machine", "state-machine this", or when a goal has a small number of clearly named phases with explicit outcomes (built / passed / failed / blocked) and you want the routing to be auditable rather than judged on the fly. For clock-driven loops use timeboxed-iterating; for wide graphs with judged edge criteria use workgraph.

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

Analyzes ELF binaries, executables, and firmware images to understand behavior without source code; coordinates sub-skills binary-re:triage, binary-re:static-analysis, binary-re:dynamic-analysis, binary-re:synthesis, and binary-re:tool-setup. Use when working with a binary, executable, or ELF file; asked to reverse engineer, disassemble, decompile, or figure out what something does; targeting ARM64, ARMv7, x86_64, or MIPS; or analyzing Python bytecode (.pyc, marshal). For Python bytecode analysis, see docs/python-bytecode-re.md.

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