「orm」の検索結果

Calculates the lowest effective glucocorticoid dose (dexamethasone or prednisone) to normalize blood pressure and serum potassium in glucocorticoid-remediable aldosteronism (GRA/FH-I) by titrating to biochemical and clinical targets. Indicated when initiating medical treatment for confirmed GRA, triggered by findings such as early-onset hypertension, family history of stroke before age 40, spontaneous hypokalemia, or suppressed plasma renin activity with elevated aldosterone.

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

Suggests that pregnant patients with primary adrenal insufficiency be monitored for clinical signs of glucocorticoid over- or under-replacement such as normal weight or gain, fatigue, postural hypotension or hypertension, and hyperglycemia, with at least one review each trimester. Use when managing a pregnant patient with PAI to assess glucocorticoid dosing adequacy.

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

Screen a child with obesity for red flags suggesting monogenic, syndromic, or secondary endocrine causes — distinguishing atypical from typical exogenous obesity. Trigger when a clinician asks whether obesity could be genetic or hormonal, suspects Prader-Willi syndrome, Cushing disease, hypothyroidism, ROHHAD, Bardet-Biedl syndrome, leptin deficiency, or craniopharyngioma, or when a child has early-onset severe obesity, short stature with obesity, hyperphagia, hypotonia, dysmorphic features, or developmental delay with weight gain.

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

Recommends measurement of plasma ACTH to establish primary adrenal insufficiency (PAI) diagnosis in patients with confirmed cortisol deficiency; a plasma ACTH concentration ≥2-fold the upper limit of the reference range supports PAI. Use when evaluating plasma ACTH in a patient with low morning cortisol or abnormal corticotropin stimulation test.

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

The Endocrine Society guideline recommends against routine hormonal monitoring of glucocorticoid replacement in primary adrenal insufficiency and advises adjusting therapy solely based on clinical response. Use when evaluating glucocorticoid dose adequacy, such as when patients report fatigue, weight loss, hypotension, or signs of Cushingoid over-replacement.

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

Suggests using hydrocortisone 15–25 mg or cortisone acetate 20–35 mg daily in two or three divided oral doses for adult primary adrenal insufficiency (PAI) patients initiating glucocorticoid replacement. The highest dose is given upon awakening, with the second dose either early afternoon (≈2 h after lunch) or split into lunch and afternoon doses; consider total daily dose calculation based on chosen formulation and frequency.

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

Recommends performing biochemical testing for HPA axis at least 18-24 hours after last hydrocortisone dose or longer for synthetic glucocorticoids. Use when scheduling HPA axis testing in glucocorticoid-treated patient needing assessment of adrenal reserve.

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

Performs corticotropin stimulation test to diagnose adrenal insufficiency when morning cortisol is indeterminate (3-15 µg/dL). Triggers include morning cortisol 3-15 µg/dL requiring further AI testing.

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

This skill guides annual evaluation of patients with primary adrenal insufficiency (PAI) for symptoms and signs of glucocorticoid and mineralocorticoid over- or under-replacement. Use during annual follow-up when assessing for weight changes, blood pressure abnormalities, edema, or symptoms such as fatigue, insomnia, or salt craving.

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

Read-only release + backlog recap. Reports the last release, commits-since-tag classified by conventional-commit type with the semver bump they trigger and pushed-vs-origin state, the backlog bucketed (open/picked-up/dropped with epic parent→child nesting), the roadmap epics with their per-task tallies, and condensed open questions — then recommends the next pickup. One `cli.mjs recap` call returns all six recap keys. Invoke any time (on demand) to plan a release or choose the next thing to build; a compact form is also surfaced at session start. Not a workflow phase; never writes CHANGELOG; never starts or commits work.

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

Contract document for the binding test verdict file at .claude/state/last_test_result. Format spec for callers (integrate, simplify, chore, the verify-tick worker) that inline the four mechanical operations. Not Skill-tool-invocable.

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

Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.

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

Run an org-team workflow — a flat pod of up to four peer Claude Code sessions claims lane-tagged slices of an approved spec over the baseline MCP channel and implements them concurrently, each in its own git worktree. Each peer DECIDES its own in-lane implementation choices in its own main context (Article X); only un-decidable or cross-lane forks escalate peer→lead→human (yield_fork for task-bound forks, ask_lead for free-form queries). Opt-in and OFF by default (velocity.org_mode.enabled). Graduates the retired sprint-dispatch prototype into the constitutionally-sanctioned org-team model (Article X — Multi-session coordinated workflows). Requires git.

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

Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

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

Cycle-end retrospective converting recurring judgment failures into durable enforcement. Reviews the cycle's friction — repeated user corrections, guard trips, RCA themes, integrate failures — and turns each recurring one into a landmines.md entry, then proposes graduation candidates up the enforcement funnel (landmine → advisory hook → hard gate). Pairs with standup: standup says what shipped and what's next; retrospective says what kept going wrong and how to stop it structurally. Writes only memory entries and a report — graduation proposals are advisory and require the normal seed.md amendment path to become enforcement. Invoke at the end of a release cycle, an epic, or any stretch of work with repeated friction.

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

Workflow Phase 7 — Mechanical cleanup pass over the branch diff, followed by a `code-structure` review pass and a `verify` re-stamp. Shadows the global `simplify` skill at project scope; the cleanup pass is performed inline rather than via Skill self-call.

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

Phase 10.6 — sync the project's execution roadmap (project.json → roadmap.path, default docs/roadmap-execution-plan.md) to the just-landed work. Flips the tasks named in workflow.json → roadmap_tasks[] from ⬜ to ✅ and promotes their epic headings ⬜→🟡→✅, preserving the standup parser format contract. On the epic track it appends instead — the epic's heading plus one row per slice — and stamps roadmap_epic back into the epic state. Also hosts the ad-hoc backfill that puts every epic already on disk onto the roadmap. Fail-open: never throws, no-ops when roadmap.path is unset/absent or no task matches, and never blocks a commit. Runs after /archive and before /memory-sync on every committing track.

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

Draft a Business Requirements Document (BRD) for cross-functional or stakeholder-heavy work that needs more structure than an intake. Use after `/intake` when the request spans multiple systems/teams, carries regulatory weight, or needs formal sign-off. Output lives at `docs/brd/<slug>.md`.

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

Use when female Chinese web novel writing or 女频小说写作 needs Fanqie female-rank market radar, 言情, 古言, 现言, 快穿, 团宠, 权谋, 情绪流, 女性向人设, 人物关系, 评论区, 短视频文案, or platform voice references for AI-assisted fiction writing.

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

Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.

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

Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization.

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

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

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

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.

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

Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

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