Results for “star”

Monitors euthyroid adults with growth hormone deficiency (GHD) who are initiating GH replacement therapy for the development of central hypothyroidism (CH). Initiates levothyroxine (L-T4) if free thyroxine (fT4) falls below the laboratory reference range; triggers include GHD patient starting GH replacement.

issue-start 가 증거와 리포트를 게시하고 사람이 승인한 작업을 마무리합니다. 기존 증거의 완결성과 게시 상태를 확인하고, 부족하거나 바뀐 경우에만 보강·재게시한 뒤 PR 을 만듭니다. merge 는 하지 않고 issue-merge 로 넘깁니다. `$issue-end`, "이슈 마무리", "작업 종료", "승인한 작업 PR" 요청에 사용합니다.

Econometrics skill for creating publication-quality LaTeX regression and summary tables. Activates when the user asks about: "regression table", "LaTeX table", "esttab", "stargazer", "modelsummary", "publication table", "format results", "multi-panel table", "journal table", "export regression results", "table formatting", "回归表格", "LaTeX表格", "结果导出", "论文表格", "回归结果格式化", "多模型表格"

Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions.

Use to build Cell's data and code deposition plan and the Data and Code Availability statement that lives inside STAR Methods Resource Availability — approved repositories, accessions/DOIs at submission, and Cell's three-bullet availability format with Mendeley Data as Elsevier's default.

Use when the user wants to install, authenticate, or configure Google Gemini CLI on their system. Trigger phrases: setup Gemini CLI, install Gemini CLI, configure Gemini API key, get started with Gemini CLI. For specific tasks see gemini-cli-copywriting or gemini-cli-seo.

Generate and send a daily briefing to your owner covering today's meetings, urgent emails, open tasks, and anything that needs attention. Use when: it's the start of the owner's day, when asked for a summary, or on a scheduled cron job.

Suggests testing HPA axis functionality before and after starting GH replacement in patients not receiving glucocorticoid replacement with apparently normal pituitary-adrenal function. Triggers include initiating GH replacement in a GHD patient who is not on glucocorticoids and has normal adrenal function.

Use when a Claude-Design export already exists and you must adapt it into a production page before render-verify — real data, honest empty states, existing tokens/components (never ship mock numbers). Prefer this over claude-design when generation is done and adaptation starts.

Search engine optimization for startups. Covers technical SEO, content strategy, and link building. Focus on sustainable approaches that compound over time rather than tricks that get penalized. Use when "seo, search engine optimization, organic traffic, google ranking, keyword research, backlinks, content strategy, search visibility, " mentioned.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Use when starting a new research project, exploring a research idea, deciding whether a question is viable, or before touching code or data for a new paper. Runs a research-focused brainstorm that clarifies research question, identification strategy, data feasibility, and contribution before any implementation.

Govern Power Automate flows and Power Apps at scale by classifying business impact, detecting orphaned resources, auditing connectors, enforcing compliance, and computing archive scores — all without Dataverse or the CoE Starter Kit.

Guides dose escalation for obesity pharmacotherapy based on efficacy and tolerability while staying within approved upper dose limits. Triggers include clinician questions like "How should I titrate naltrexone/bupropion if the starting dose is tolerated?" or "What is the maximum liraglutide dose I can use?"

Use after solving a non-trivial bug or making a non-obvious decision, to capture it as durable, searchable documentation so the next session doesn't re-derive it from scratch - and use at the start of related work to check whether that documentation already exists.

Write end-user documentation including tutorials, how-to guides, walkthroughs, onboarding flows, and feature documentation. Use when creating documentation for non-technical or semi-technical end users. Also trigger for 'user guide', 'tutorial', 'how-to', 'walkthrough', 'onboarding docs', 'help article', 'user manual', or 'getting started guide'.

Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.

Understand GitHub well enough to run a GTM context repo, no CS degree required. The mental model (repo, commit, branch, push, pull, clone), the operator's GUI-first workflow (GitHub Desktop, or let Claude Code handle the git), how to organize the repo, and the hard rules on what to never commit (CRM data, API keys, transcripts, pricing). The prerequisite to building a context repo. Fire on "what is a repo", "how does GitHub work", "learn git", "GitHub for GTM", "do I need to know GitHub", "clone the starter kit", "commit and push", "how do I organize my repo", or the start of building a GTM context repo.

Manage memory in long projects and summarize the current state to prevent agent context loss. Use when starting a new session on a long-running project, resuming work after a break, switching contexts between tasks, or when context window is approaching limits. Ensures continuity and consistency across sessions.

Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.

Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.

Provides strategic product leadership guidance for CPOs and product leaders, covering vision, portfolio management, product-market fit, org design, and metrics. Includes diagnostic questions, frameworks, and scripts for scoring PMF and analyzing portfolios.

Create a committed per-feature spec under `docs/specs/YYYY-MM-DD-<slug>/{spec,tasks}.md` with frontmatter (status, created, owner, pr, tags). Promotes an ephemeral `.claude/plans/<name>.md` into a persistent, searchable artifact. Use when starting a feature that's larger than a one-shot PR.

Use for designing, creating, reviewing, or debugging Model Context Protocol server configuration for GitHub Copilot in Visual Studio Code, including .vscode/mcp.json, transports, inputs, trust, sandboxing, and tool scope. Do not use for implementing an MCP server, ordinary HTTP clients, or silently installing or starting external software.

Interact with GitHub via the `gh` CLI. Use for issues (read, comment, file), pull requests (view, comment, check CI status), workflow runs, and `gh api` for queries the subcommands don't cover. Authentication is via the bot's GITHUB_TOKEN (already wired through `gh auth setup-git` at container start).

Create a globe-like 3D particle visualization with a dense luminous spherical core and thinner orbital ring or flattened disc. Use when a design needs a premium planetary, orbital, synthesized data-globe effect rendered with real WebGL/Three.js particles, not generic starfields or full page layout changes.

Brainstorm and develop game concepts, exploring genres, themes, target audiences, and unique selling points. Use when starting a new game project from scratch or pivoting an existing idea. Also trigger for "game idea", "what kind of game", "I want to make a game", "game pitch", or "explore game concepts".

Skeptical pushback on the outline before drafting starts. Asks whether the outline is MECE, BLUF, problem-agitate-solution; whether it covers the topic better than the SERP top-5; whether sections duplicate; whether each section earns its visual. One revision pass on FAIL (BLOG_AGENT_OUTLINE_REVISION_BUDGET, default 1).

Wizard de configuracao do plugin civel ao perfil do escritorio. Cria a pasta civel/ com identidade (nome, OAB, escritorio, cidade), areas de atuacao civel, tribunais-alvo (para IRDR/jurisprudencia local), tom e modo de fluxo. Use quando o operador disser configurar civel, instalar civel, primeira vez, /start-civel, onboarding civel.

Router for Google Stitch design-to-code in this pack. Use when starting any Stitch workflow, choosing Stitch vs Aura vs Figma vs Claude Design, or before calling generate/edit MCP tools. Enforces ~400 Stitch credits/day. Points to phased pack skills: enhance-prompt → generate-design → extract → build → loop.

Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.

Integrate services or agent harnesses with the 33GOD Bloodbank event bus. Covers schemas in Bloodbank schemas/ and docs/event-naming.md, producing events (NATS preferred; Dapr, HTTP /publish, hookd_bridge alternatives), consuming events (NATS, Dapr, FastStream, event-toaster), and agent hook wiring through the canonical services/agent-hooks publisher. Use for event publish/consume, authoring schemas, integrating harnesses (Claude Code, Copilot CLI, OpenCode, Cursor, Aider, Codex CLI, Hermes), or debugging missing envelopes. Triggers: bloodbank, event bus, publish, subscribe, NATS subject, holyfields legacy, CloudEvents, event-toaster, ntfy.delo.sh/bloodbank, bloodbank.v1.agent.session.started, bloodbank.v1.agent.tool.completed, bloodbank.cmd.v1.agent.invocation.start. Skip for generic brokers, n8n, hindsight memory, or non-event-bus 33GOD.

Build a task-aware context bundle (relevant code + applicable standards + related past decisions) via the local RAG index, capped at a token budget. Use at the start of any implementation/refactor/debug task instead of reading files blindly. Replaces "read whole file" with "retrieve the function + callers + rules + prior ADR."

Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and platform-specific Kubernetes work for EKS, GKE, AKS, OpenShift, GitOps controllers, or observability stacks.

Operate a self-managed Redpanda broker process and node from the CLI using the `rpk redpanda` command family and `rpk iotune`: node lifecycle (start/stop), production vs. development mode, kernel autotuning, node configuration (redpanda.yaml), and per-node Admin API operations including broker.

Practical codebase onboarding for Nick's workflow. Use when opening a stale project, picking up a new repo, rebuilding context after time away, or generating fast markdown docs that explain how to start working on a codebase right now. Focus on setup, key files, flows, commands, risks, and what to touch first.