2,179 件 ・ 関連度順
概要と使いどころ
Autonomous GAS development skill — code, deploy, test, and fix in a self-driving loop. Uses clasp for code management, Web App + gas-run.sh for auto-deploy/execution, and gws for spreadsheet read/write. Triggers on "GAS", "Apps Script", "spreadsheet automation", "clasp", "gws sheets".
日本語の概要は準備中です。原文の説明を表示しています。
ローカルの変更差分（git diff）を3つのサブエージェントで並列レビューし、結果を統合して修正を適用する。PR作成前やタスク完了前のローカル品質チェックに使用する。ai-code-reviewと同一の6観点・重大度基準を適用する。
Generate self-contained HTML/CSS benchmark and comparison charts in an ego-inspired Browser-Native Editorial style. Use for blue-white product metrics, model benchmarks, A/B comparisons, efficiency reports, difficulty breakdowns, and compact technical data panels.
日本語の概要は準備中です。原文の説明を表示しています。
Export Codex rollout/session JSONL as a self-contained HTML report that can be opened offline. Use when a user provides a complete session file path or Codex session ID, or asks to export a Codex session to HTML, generate a session report, or convert a rollout to HTML. Supports exact full-ID lookup in the CODEX_HOME sessions and archived_sessions directories.
日本語の概要は準備中です。原文の説明を表示しています。
Get literature into a research run when the plugin fetches nothing — fetch the source yourself with web_fetch / web_search or take a file the person already has, READ it with the pdf_* tools or ocr, then ingest record and text together with rs_cite, bind locators, and cite with [@key]. Use when a run needs sources, when a library export has to come in, when a citation key is unknown, or when a claim cannot be checked against a source.
日本語の概要は準備中です。原文の説明を表示しています。
Hand a research run over as a file — read `rs_open action=capabilities` for the formats this build writes, choose between `md`, `docx`, a self-contained `html`, the `ris`/`bib`/`enw` library exports and `tex`, pick `draft=watermark` while working or `draft=clean` to hand it over, and read `build/build.json` for what was built from which bytes. Use when a document is finished enough to leave the run, when a citation style or an export has to be chosen, or when a build refuses.
日本語の概要は準備中です。原文の説明を表示しています。
Work the prototyping lab itself — where runs live, what a run is, how to promote a run into the checked example library, and how to add a new runtime (Processing in Rust, Cinder) in one module. Use when asked to add a language or framework to the lab, to turn a prototype into a reusable example, to find or tidy what is in the lab, or when the lab's folder or catalog needs explaining.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user starts a non-trivial coding/building task in Claude Code (e.g. "帮我做个 X", "help me build Y", "add feature Z", "搭一个 Z"). Layers an AI-native pedagogical coat over normal coding work — surfaces implicit assumptions in user intent, annotates non-trivial design decisions inline with brief concept-scaffolding for terms the user may not know, and replaces "should I run it?" handoffs with rigorous AI self-verification plus a clean list of what only the user can verify. Skip for pure Q&A, single-line edits, read-only investigation, or refactoring along an existing pattern.
日本語の概要は準備中です。原文の説明を表示しています。
하나의 긴 메서드를 grouping(Reorder/Chunk)·comment로 정돈해 책임을 드러낸 뒤 Arlo Belshee 6단계 네이밍(완전정직 이름 → Extract Method → Intent Revealing → Domain Abstraction)을 하나의 연속 흐름으로 관통하는 self-contained 워크플로우. "이 긴 메서드 이름이 하는 일을 안 드러낸다", "메서드 이름부터 정직하게 만들어서 쪼개줘", "이름 주도로 이 메서드 리팩토링" 요청 시 사용. 단, 여러 파일에 흩어진 개별 이름 스멜의 배치 교체는 /naming-process, 클래스 분리·도메인 이동 같은 대규모 구조 변경은 /system-wide-refactoring이 적합. /intent-revealing-names로 호출.
日本語の概要は準備中です。原文の説明を表示しています。
Build a rich, self-contained HTML explanation of a code change — diff, branch, commit range, MR/PR — with background, intuition, a code walkthrough, diagrams, and a glossary, then quiz the reader interactively in chat. Use when the user asks to explain a change, understand a PR/MR, walk through a diff, onboard onto a branch, or says "explain this PR", "what does this branch do", "teach me this change", or "/explain-diff".
日本語の概要は準備中です。原文の説明を表示しています。
Load when evaluating an Islamic software feature, provider policy, AI behavior, moderation, monetization, privacy, defaults, ranking, self-hosting, or deployment model for provider responsibility and Islamic value-sensitive design; not for generic fiqh rulings or ordinary technical implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Load when the user asks for CTO advice on feature strategy, architecture direction, build-vs-buy, infrastructure, market positioning, roadmap, self-hosting, cost, or organizational tradeoffs; not for reviewing an existing implementation-plan workstream.
日本語の概要は準備中です。原文の説明を表示しています。
Load for pre-PR self-review or pull-request review that must verify the matched intent, allowed scope, required tests/docs, forbidden actions, architecture gates, and merge readiness; not for a general code-quality diff review alone.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor CI/CD checks until green or failure with auto-diagnosis, failure classification (related vs flaky vs external), self-healing fix attempts, and smart retriggers for flaky E2E tests. Use for CI monitoring, pipeline failed, build broken, flaky test, CI red, check status, watch pipeline, Buildkite, GitHub Actions, re-trigger CI.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Systems Modeling Handbook for Systems Engineering (NASA-HDBK-1009A Rev A, 2025). Use for model-based systems engineering (MBSE) wired into NASA's NPR 7123.1 SE processes: the three aspects of MBSE (language / methodology / framework), the NASA SE Engine and its two OOSEM-derived steps (Model Planning, Setting Up the Model), the Modeling Plan as a SEMP subset, the tool-agnostic NASA SE metamodel of elements and relationships across the four SysML pillars (structure / behavior / requirements / parametrics), worked SysML diagrams and tables for stakeholders, requirements, structure and V&V, generating SE work products (ConOps, MOE, MOP, TPM, V&V), the MBSE Grid framework, alternative modeling approaches (PBR, Scenario, System Specification, Verification), and the ConOps model-content template. Scope is bounded to four common technical processes (Stakeholder Expectation Definition, Technical Requirements Definition, Product Verification, Product Validation). Does NOT teach SysML itself, mandate a tool, define NPR 7123.1 processes, cover technical-management processes 10-17, or reproduce the OMG SysML specification.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from NASA Human Systems Integration (HSI) Practitioner's Guide (NASA/SP-2015-3709). Use for HSI process implementation, lifecycle phase activities, function allocation, ConOps development, HSI Plan writing, HSI metrics (MOE/MOP/TPM/KPP), HITL testing strategy, HSI team organisation, scaling/tailoring for program size, and V&V planning. Does not cover the specific human engineering design standards (NASA-STD-3001 content) or detailed HFE methods beyond what the guide itself provides.
日本語の概要は準備中です。原文の説明を表示しています。
Психообразование по теме травмы: определение травмы, нормальные реакции, окно толерантности, управление триггерами и забота о себе.
日本語の概要は準備中です。原文の説明を表示しています。
Psicoeducación sobre el trauma: definición de trauma, reacciones normales, ventana de tolerancia, manejo de desencadenantes y autocuidado.
日本語の概要は準備中です。原文の説明を表示しています。
创伤心理教育：创伤定义、正常应激反应、容受窗、触发因素管理及自我关怀。
日本語の概要は準備中です。原文の説明を表示しています。
トラウマ心理教育：トラウマの定義、正常な反応、ウインドウ・オブ・トレランス（忍容の度）、トリガー管理、セルフケア。
Erzeugt aus einem Bestand offener und gefallener Entscheidungen einen strukturierten ASCII-Abhängigkeitsgraphen (maximal 100 Spalten) für das Terminal. Bewertet Knoten nach fünf festen Kriterien: sinnvoll, empfohlen, usertypisch (Richtung und decision-avatar-Konfidenz getrennt), zusammenpassend und widersprechend; Kanten tragen Beziehungstyp und Belegstatus. Deckt Blocker, Freischaltungen, Reihenfolgen und widersprüchliche Empfehlungen gnadenlos auf. Nutze diesen Skill bei "welche Entscheidungen hängen voneinander ab", "Abhängigkeitsgraph der Entscheidungen", "Entscheidungspfad visualisieren", "Widersprüche zwischen Entscheidungen prüfen", "Reihenfolge der Beschlüsse", /decision-path. NICHT nutzen, um Entscheidungen erst zu inventarisieren -- das macht decision-briefing; NICHT nutzen, um das empfohlene Gesamtkonzept zur Abnahme zu bündeln -- das macht decision-draw; NICHT für kompakte Fünfteiler- Einzelblöcke mit Optionen und Pro/Contra -- das macht decision-shot; NICHT für die Einzelfall-Erwägung mit Frameworks -- das macht decide.
日本語の概要は準備中です。原文の説明を表示しています。
Verdichtet gebündelte offene Entscheidungen zu EINEM zusammenhängenden, prosa-basierten Gesamtkonzept auf Basis aller empfohlenen Varianten. Zeigt, wie die Teilsysteme nach der Umsetzung konkret ineinandergreifen, statt den Nutzer durch Dutzende isolierte Einzelfragen zu zwingen. Der Nutzer nimmt das Bild als Ganzes ab oder gibt zielgerichtete Korrekturen, die automatisch in Einzelentscheidungen übersetzt und über decision-briefing Phase 4 ins Register zurückgeschrieben werden. Nutze diesen Skill bei "wie sieht das Ganze aus wenn wir allem zustimmen", "zeichne mir das Gesamtbild", "Gesamtkonzept der Entscheidungen", "decision draw", /decision-draw, "wie greifen die Systeme zusammen". NICHT nutzen, wenn Alternativen pro Einzelpunkt diskutiert werden sollen -- das macht decision-briefing; NICHT für den Abhängigkeitsgraphen -- das macht decision-path; NICHT für strukturierte Einzelblöcke mit Optionen und Pro/Contra (auch bei eng zusammengehörigen Gruppen) -- das macht decision-shot; NICHT zur Herleitung einer einzelnen Entscheidung -- das macht decide.
日本語の概要は準備中です。原文の説明を表示しています。
Universeller Skill für LLM-Navigation, Orientierung und Ausfallsicherheit. Stellt aktives Wayfinding, Selbstorientierung und Wiederherstellungsheuristiken bereit, wenn Agenten mit Kontextdrift, fehlschlagenden Werkzeugen, Schleifen oder Sackgassen konfrontiert sind. Enthält die synonymen Strategien survival-routing, dead-reckoning, pathfinder-routing und celestial-routing.
日本語の概要は準備中です。原文の説明を表示しています。
Selbstjustierende Takt-Regelschleife für wiederkehrende Agenten-Scans. Nutzen, wenn ein geplanter Scan sein Intervall bei Aktivität schärfen und bei Stille abkühlen soll, ohne Operator-Eingriff.
日本語の概要は準備中です。原文の説明を表示しています。