560 件 ・ 関連度順
概要と使いどころ
Detect technical debt — duplicated code, dead code, TODOs, and oversized functions across the codebase. Use at the end of a session or when auditing code hygiene. Trigger on "find tech debt", "any dead code", "duplicated code", "code hygiene", "techdebt".
日本語の概要は準備中です。原文の説明を表示しています。
Genereert uit een (semi-)gevalideerd regelrecht-corpus een geloofwaardige service-PoC (burger- + behandelaar-portaal, of een headless beslis-service) en zet die in als validatie-instrument met uitvoeringsexperts — om tastbaar te maken wat nodig is om een wet rechtvaardig in de praktijk te brengen, gezien vanuit de betrokkene. Gebruik dit als workshop-fase ná de logica-/scenariovalidatie (audit-products) om de dienstverlening-kant te valideren: welke service impliceert de wet, waar zit menselijk oordeel, welke last ligt bij de burger, welke termijnen, waar is de wet hard of onduidelijk. Dossier-agnostisch; de regelrecht-methode (hooks, legal_character, untranslatables, source/implements, type_spec, receipts) is de vaste taal. Voor de logica-/scenariovalidatie zelf: zie de zusterskill regelrecht-audit-products.
日本語の概要は準備中です。原文の説明を表示しています。
Maakt regelrecht-scenario's vindbaar en hun norm-ketens leesbaar/geassert. Aan de invoerkant — vertaal een platte lijst leaf-parameters naar benoemde casus-assen + een herbruikbare persona-bibliotheek, met een reverse-lookup casus-matrix. Aan de uitvoerkant — maak de norm-keten zichtbaar via keten-checkpoints (assert elke knoop op het kritieke pad, niet alleen de endpoint) en golden-trace-snapshots + branch-coverage. Gebruik dit bij het schrijven of opschonen van scenario-/feature-files, het terugvinden of ontwerpen van een specifieke casus in een grote variabelenlijst, het reviewen van engine-traces, of het regressie-bestendig maken van cross-law-ketens zodat een ketenfout niet stil achter een correcte endpoint verdwijnt. Dossier-agnostisch; de regelrecht-methode is de vaste taal. Haakt aan op regelrecht-stelselanalyse (engine-tests / meta-check) en regelrecht-audit-products (testcase-scenario's).
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an EMT (Basic Life Support tier) — deciding whether a chest-pain patient gets aspirin under protocol, dosing an epinephrine auto-injector for anaphylaxis and knowing when to repeat it, applying spinal-motion-restriction criteria instead of routine backboarding, recognizing the moment a call exceeds BLS scope and requesting ALS intercept, or working a patient refusal (AMA) to a legally defensible conclusion.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Postsecondary Art, Drama, or Music Professor — diagnosing a jury/crit score that contradicts a semester of formative work, building a studio-art or performance tenure dossier around exhibitions and productions instead of publications, staffing applied one-on-one lessons or crit sections between adjuncts and full-time faculty, running a structured critique, or deciding whether a failed barrier jury means a change of major.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a tenure-track or tenured Agricultural Sciences faculty member at a land-grant university — deciding whether to submit a grant this cycle versus wait, allocating time across the teaching/research/extension appointment split, diagnosing a stalled graduate student or field trial, or drafting a tenure-and-promotion dossier narrative.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Acute Care Nurse — tracking early warning score trends across a higher patient ratio than ICU to catch silent deterioration before crisis, distinguishing expected post-operative recovery variation from a true complication requiring escalation, triaging competing needs across multiple simultaneous patients, balancing analgesia against oversedation risk by real-time response rather than fixed dosing, and verifying genuine discharge readiness rather than checking a form.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a postsecondary Anthropology or Archaeology professor — designing a gen-ed or major-track course, building a tenure or promotion dossier, defending a department against an enrollment-driven program review, mentoring a graduate student's fieldwork grant application, or writing an IRB/NAGPRA-compliant fieldwork plan.
日本語の概要は準備中です。原文の説明を表示しています。
Run a focused tech debt reduction sprint — inventories all technical debt (TODOs, outdated deps, missing tests, god objects), fixes code smells, removes dead code, then hardens with a review pass. Use when a codebase feels sluggish, before a major feature push, or on a regular maintenance cadence.
日本語の概要は準備中です。原文の説明を表示しています。
Full-stack app pipeline — build, test, review, and deploy across one or ALL repos. Scans CLAUDE.md, MEMORY.md, TODOs, open PRs, and issues for shippable work. Supports 'ship all' for multi-repo. Use when: 'build and ship', 'ship it', 'ship all', 'deploy everything', 'full pipeline', 'what needs shipping', 'end to end'.
日本語の概要は準備中です。原文の説明を表示しています。
Deep codebase cleanup — kills dead code, fixes all lint/format warnings, removes orphaned files, cleans stale TODOs, strips security hazards, tightens TypeScript strict mode, and organizes imports. Triggers: clean up, dead code, unused imports, lint, technical debt cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find everything about, research and file, go research, build a wiki on.
日本語の概要は準備中です。原文の説明を表示しています。
Author, validate, test, and deploy YARA-L 2.0 detection rules and evaluate end-to-end detection coverage gaps in Google SecOps. Use when writing new detection rules, tuning existing rules, validating syntax, testing logic against historical telemetry, or evaluating detection coverage against threat intelligence blogs, CVE disclosures, and Threat Detection Opportunities (TDOs) using synthetic UDM events and long-running coverage analysis. Don't use for alert triage (use secops-triage), deep forensic event reconstruction on infected hosts (use secops-investigate), or case management operations (use secops-cases).
日本語の概要は準備中です。原文の説明を表示しています。
Automates the end-to-end detection engineering workflow in Google SecOps using MCP tools. Use when fetching threat intelligence from blogs, generating Threat Detection Opportunities (TDOs), simulating attacker behavior with synthetic UDM events, evaluating rule coverage, generating new YARA-L 2.0 rules to close coverage gaps, and with user approval, deploy them to SecOps. Don't use when asked to perform threat hunting actions, and SOC investigative actions.
日本語の概要は準備中です。原文の説明を表示しています。
Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file"
日本語の概要は準備中です。原文の説明を表示しています。
ผู้ช่วยสัตวแพทย์ — species-specific reference (สุนัข/แมว/exotic) + DDx + drug dosing weight-based + clinical pearl สำหรับสัตวแพทย์ที่มีใบประกอบวิชาชีพเท่านั้น
日本語の概要は準備中です。原文の説明を表示しています。
ผู้ช่วยเภสัชกร — drug dictionary (Thai/Generic), interaction matrix, pediatric/geriatric/renal dosing, counseling script สำหรับเภสัชกรที่มีใบประกอบวิชาชีพเท่านั้น
日本語の概要は準備中です。原文の説明を表示しています。
Clinical Decision Support System (CDSS) development patterns. Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classification, and integration into EMR workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Remediation only — repair web accessibility (a11y) violations against WCAG 2.2 with a baseline, edit, and verify loop. Takes a target (URL, files, directory) or a findings worklist from `accessibility-scan`/`accessibility-inspect`/`accessibility-audit`, applies mechanical fixes as given, leaves TODOs for visual or contextual judgment, and verifies by re-running the baseline check. It only fixes. To find issues use `accessibility-scan` (one page, automated), `accessibility-inspect` (one page, manual), or `accessibility-audit` (whole site, WCAG-EM); to check for regressions use `accessibility-diff`. Use it for 'fix the a11y issues in X', 'make this accessible', 'add missing alt text and labels', 'apply these accessibility fixes', 'remediate these violations'.
日本語の概要は準備中です。原文の説明を表示しています。
Guardiao de contexto que preserva dados criticos antes da compactacao automatica. Snapshots, verificacao de integridade e zero perda de informacao.
日本語の概要は準備中です。原文の説明を表示しています。
Cycle 30 min du secrétaire vérificateur myia-po-2026:CoursIA-3. Atteste en tiers, du plus ancien au plus récent, les PRs ouvertes sans dossier valide (chaque READY, une fois lu et approuvé par ai-01, est mergé sans attendre son cycle), et fait circuler l'information sur workspace-CoursIA-3.
日本語の概要は準備中です。原文の説明を表示しています。
6-lens diagnostic slop audit — unused imports, dead private fns, duplicate signatures, abandoned TODOs, lint bypass markers, stale refs.
日本語の概要は準備中です。原文の説明を表示しています。
Define la identidad visual de un producto — propone dos o tres direcciones de color y tipografía justificadas por lo que el producto es, las escribe en design/tokens.css y las deja listas para verlas aplicadas en preview.html antes de decidir. Úsalo tras definir el producto y ANTES de prototipar (p. ej. "define la identidad", "qué paleta usamos", "elige los colores del producto"). No construye vistas.
日本語の概要は準備中です。原文の説明を表示しています。
Revisa o produce textos visibles para la persona usuaria (texto de UI, encabezados, botones, mensajes de error, marketing) con la voz y el tono del proyecto. Úsalo cuando la persona pida escribir/mejorar textos, corregir la redacción, revisar el tono o redactar microcopy (p. ej. "escribe el texto del estado vacío", "haz este mensaje de error más amable", "revisa el titular de la landing").
日本語の概要は準備中です。原文の説明を表示しています。