2,986 件 ・ 関連度順
概要と使いどころ
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.
日本語の概要は準備中です。原文の説明を表示しています。
Provides monitoring schedule for transgender males on testosterone therapy, detailing timing of clinical visits, laboratory tests, and assessment for virilization and adverse reactions. It is triggered when a clinician manages a transgender male patient on gender‑affirming hormone therapy and needs to schedule appropriate follow‑up.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends discontinuing glucocorticoid when the response to HPA axis recovery tests (morning cortisol, ACTH stimulation, or insulin-induced hypoglycemia) is normal, indicating adequate adrenal function recovery. Use in postoperative Cushing’s syndrome patients with at least one intact adrenal gland when test results are available.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends follow-up morning cortisol and/or ACTH stimulation tests or insulin-induced hypoglycemia to assess HPA axis recovery in postoperative Cushing's syndrome patients with at least one intact adrenal gland. Triggers include postoperative remission (morning cortisol <5 µg/dL or UFC <28–56 nmol/d) and the need to evaluate HPA recovery before glucocorticoid discontinuation.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends re-evaluating the need for treatment of other pituitary hormone deficiencies in the postoperative period following surgical intervention for Cushing's syndrome. It is triggered when assessing a post-op CS patient for ongoing pituitary function, evaluating for hypopituitarism, or checking HPA axis recovery with morning cortisol/ACTH stimulation tests and pituitary MRI within 1–3 months.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends lifelong follow-up tests for cardiac myxoma and associated disease (testicular tumors, acromegaly, thyroid lesions) in patients with Carney complex. Use when managing a Cushing’s syndrome patient with a confirmed or suspected Carney complex diagnosis (e.g., spotty skin lentigines, cardiac myxoma, endocrine tumors).
日本語の概要は準備中です。原文の説明を表示しています。
Work up Malignancy-Associated Hypercalcemia (MAH) — distinguish humoral hypercalcemia of malignancy (HHM, PTHrP-driven), local osteolytic hypercalcemia, 1,25(OH)2D-mediated lymphoma hypercalcemia, ectopic PTH secretion, and multiple myeloma — and pick the right confirmatory tests and therapy direction. Trigger when a clinician asks "is this hypercalcemia from cancer", "PTHrP positive what now", "hypercalcemia in lung cancer / breast cancer / lymphoma / myeloma", "humoral hypercalcemia of malignancy", "MAH workup", or any hypercalcemia case with suppressed PTH and a known or suspected malignancy.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends antihypertensive therapy including mineralocorticoid receptor antagonists (MRAs) for patients with a positive primary aldosteronism (PA) screening test who decline confirmatory testing. Triggers include when a patient has positive screening but refuses additional tests and asks "What should I treat with?" or initiates empiric therapy, with preference for MRAs in typical PA presentations (e.g., spontaneous hypokalemia, resistant hypertension, adrenal tumor on CT).
日本語の概要は準備中です。原文の説明を表示しています。
Write the production code that makes a pre-decided set of failing tests pass, within an explicit write_set, following an explicit behavior contract. Used by `/tdd` Step 3 and by `/swarm-dispatch` workers. The caller has already decided architecture, naming, file layout, and abstraction boundaries — this skill executes that recipe with code-structure discipline and a 5-iteration RALPH loop. No scope expansion, no design decisions, no test edits.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a Workflow Phase 4 technical spec from an intake (and optionally a BRD + scout + research memo). The spec defines how the system will change: design (C4 + UML + dependency graph in PlantUML), data, APIs, tests, rollout, rollback. Output lives at `docs/specs/<slug>.md`. Never self-approves — approval happens via `/approve-direction`.
日本語の概要は準備中です。原文の説明を表示しています。
Dev-only check that a drafted spec for THIS baseline repo won't ship dev-tree references to consumer installs. Catches three failure modes — shipped SKILL.md prose that references paths under `src/`, `tests/`, `scripts/`, `obj/` as runtime invocations (in ```bash fences``` OR `inline backticks`, plus shipped `.mjs`/`.js`/`.sh`/`.py` helper-file imports); new Python helpers added under `.claude/skills/<slug>/` (shipped helpers must be `.sh` or `.mjs`/`.js` going forward); and imports of modules that aren't in `obj/template/.claude/manifest.json` (consumer won't have the file). The aggregate scanner (`scan-shipped-skills.mjs`) walks only baseline-owned skill dirs (via `owner: baseline` frontmatter) at top level — `references/` and other subdirs are documentation, not runtime. BLOCKER findings hard-block implementation entry; ADVISORY surfaces but doesn't block. Read-only — surfaces a punch list; maintainer edits the spec and re-runs until CLEAN.
日本語の概要は準備中です。原文の説明を表示しています。
Decompose an MVP vision into a sprint manifest — a prioritized feature list where every feature carries explicit done-criteria (a done-record reference, named edge tests, and a wiring test). Produces the sprint manifest that `sprint-oracle` checks for completeness. Use when planning a sprint of parallel work (Slice A of the sprint-mode epic). Not a workflow phase; the manifest it writes is the completeness contract a sprint is held to.
日本語の概要は準備中です。原文の説明を表示しています。
The sprint completeness oracle — a mechanical, exit-code-driven check that every feature in a sprint manifest is provably complete across three dimensions (a done-record reference, resolvable edge tests, and a resolvable wiring test). Fails loud with a per-feature gap list naming the missing dimension. Read-only. Use to gate a sprint before it is called done (Slice A of the sprint-mode epic), or any time you want a completeness reading.
日本語の概要は準備中です。原文の説明を表示しています。
Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open ideation or single-option reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
日本語の概要は準備中です。原文の説明を表示しています。
TDD: enforce RED-GREEN-REFACTOR, tests before code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
日本語の概要は準備中です。原文の説明を表示しています。
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
日本語の概要は準備中です。原文の説明を表示しています。
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
日本語の概要は準備中です。原文の説明を表示しています。
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.
日本語の概要は準備中です。原文の説明を表示しています。
Marc Andreessen-mode decision and productivity skill. A blunt, market-first operator that pressure-tests ideas, ventures, features, and career bets through Andreessen's actual frameworks — market dominates team and product; the only milestone that matters is product/market fit; bias to build over deliberate. Use when the user says 'andreessen', 'pmarca mode', 'should I build this', 'is there a market', 'are we at product/market fit', 'pmf check', 'pressure-test this idea', 'be brutal about this venture', 'market-first take', or wants a no-disclaimers, no-hedging, confidence-leveled verdict on whether something is worth pursuing. Also provides the 3x5-card + Anti-Todo personal productivity routine. Runs on a fixed anti-sycophancy operating prompt: leads with the strongest counterargument, never validates premises, uses explicit confidence levels, never apologizes for disagreeing. Not for polite brainstorming — this skill exists to tell you the market is dead when it is.
日本語の概要は準備中です。原文の説明を表示しています。
Verify every claim from multiple independent angles -- code, docs, tests, git history. Use when you need high confidence that something is correct before acting on it.
日本語の概要は準備中です。原文の説明を表示しています。