Results for “adr”

Real-time quotes, K-line charts, order book, trade ticks, intraday capital flow, market sentiment temperature, trading session schedule, security lists, exchange rates, and IPO calendar for HK/US/A-share/SG via Longbridge. Also covers ADR premium and FX carry frameworks. Triggers: "股价", "行情", "K线", "走势", "盘口", "资金流", "市场温度", "汇率", "IPO", "打新", "隔夜股", "ADR溢价", "外汇套息", "K線", "盤口", "資金流", "市場溫度", "匯率", "ADR溢價", "外匯套息", "现在多少钱", "多少钱", "stock price", "quote", "kline", "chart", "depth", "orderbook", "capital flow", "market sentiment", "exchange rate", "IPO calendar", "security list", "ADR premium", "fx carry", "market open", "trading hours", "开市", "溢价", "NVDA.US", "700.HK", "600519.SH", "股價", "走勢", "開盤", "今天開市"

The English summary is being prepared. Showing the original description.

Create or update an ADR under `docs/ADR/` for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts. Use when the user asks to write, update, or document an ADR, record a design decision, capture architecture trade-offs, or justify a repo-wide technical policy.

The English summary is being prepared. Showing the original description.

Presentation/Core/Engine split control plane — the canonical entry point for any work decomposing the Yuzu server into three binaries (presentation · core · engine) per ADR-0031-presentation-core-engine-decomposition / ADR-0032 (the admission interlock) / ADR-0033 (access-control spine). Use when the user says "/split", "/pce-split", "/decomposition", asks to plan or implement a split workstream (WS-A*, WS-B*, WS-X*), asks "what's our gap to the presentation/core split" or "is it safe to extract presentation/the engine yet", asks to audit split readiness, or starts work touching the seam (handlers calling stores directly, the INV-31-4 contract test, the Drogon port, `server/presentation` or `server/engine`, the `uce` DB grants, component service identity, or the ADR-0032 admission/grant/audit substrate — `use_case_run_id`, the release log, the capability-declaration registry).

The English summary is being prepared. Showing the original description.

This skill suggests follow-up tests for specific comorbidities associated with Cushing's syndrome in patients with adrenal adenoma when CT density is less than 10 Hounsfield units. Use when managing a post-adrenalectomy Cushing's syndrome patient with confirmed adrenal adenoma pathology and low-density imaging (<10 HU).

The English summary is being prepared. Showing the original description.

Recommends immediate IV hydrocortisone stress dosing for patients with suspected adrenal crisis presenting with severe adrenal insufficiency symptoms such as hypotension, hyponatremia, hyperkalemia, or acute abdominal pain. Use when clinician observes signs of adrenal crisis (e.g., syncope, delirium, marked abdominal tenderness) prior to diagnostic test results.

The English summary is being prepared. Showing the original description.

Administers immediate parenteral injection of 50–100 mg hydrocortisone for suspected adrenal crisis secondary to adrenal insufficiency. Triggers include hypotension, hypoglycemia, or acute illness in a patient with known adrenal insufficiency.

The English summary is being prepared. Showing the original description.

Migrate existing ADRs to YAML frontmatter format. Scans docs/decisions/ for ADRs without frontmatter, infers status from body text, shows dry-run for approval. Trigger: /adr-migrate

The English summary is being prepared. Showing the original description.

Use to promote a pool ADR (ADR-pool.*) into an active, versioned ADR package.

The English summary is being prepared. Showing the original description.

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

アーキテクチャ決定会議。技術選定・設計方針・構成変更を多角的に検討し、ADR(Architecture Decision Record)として出力する。「アーキ会議」「技術選定して」「設計会議」「どっちの構成がいい」「ADR書いて」などのリクエストで使用。

The English summary is being prepared. Showing the original description.

Claude Codeセッション中に行われたアーキテクチャ上の意思決定を構造化されたADRとして記録する。意思決定の瞬間を自動検出し、コンテキスト、検討された代替案、根拠を記録する。将来の開発者がコードベースの形状の理由を理解できるようADRログを維持する。

The English summary is being prepared. Showing the original description.

Prepare a repository for engineering skills by documenting where issues are tracked, which triage labels organize incoming work, and where glossaries and architecture decision records belong. Review the existing setup and confirm drafts before writing configuration files.

• Prepare a repository before using engineering skills
• Document the issue tracker and triage labels
• Set rules for glossary and architecture decision record locations

Train and evaluate RuView models using Wi-Fi measurements for pose estimation, retrieval, and adaptation to different environments. Follow laptop or GCloud GPU workflows, then package and publish trained models to Hugging Face.

• Train pose estimation without cameras or labels
• Train pose estimation with paired camera and Wi-Fi data
• Adapt models to different rooms and environments

Verify RuView changes with Rust and Python tests, output hashes that detect processing changes, and firmware hash records. Packages test logs and audit evidence into a witness bundle that recipients can check with a single command.

• Verify a RuView build after significant changes
• Check tests and documentation before merging a PR
• Prepare a verification bundle for a recipient

Plan system architecture by comparing technical options, component relationships, and requirements such as performance, security, and growth. Produce architecture diagrams, data flow diagrams, decision records, and technology comparisons that explain the reasoning behind a proposed design.

• Planning the architecture of a new system
• Comparing technology options and trade-offs
• Documenting component relationships and data flows

Compare two JSON records describing agent setups and their scores. Receive an overall similarity score with component details to help assess reuse, compare template candidates, identify overlapping work, or check how much a setup has changed.

• Deciding whether to reuse an existing agent setup
• Ranking template candidates for a target repository
• Finding duplicate work across teams

Experiment with the policies that govern an AI agent, such as planning, memory, and tool use. Test one policy change per variant in a sandbox, an isolated environment, and promote only candidates with measured improvements.

• Finding policy changes that improve low evaluation scores
• Exploring initial agent settings for a new domain
• Comparing manual tuning with an evolved baseline

Create or edit Markdown with each prose paragraph on one source line, letting the viewer wrap the text automatically. Preserve meaningful line breaks in lists, code, and poetry while reducing unnecessary changes in file comparisons.

• Writing READMEs without fixed-width line wrapping
• Joining manually wrapped Markdown paragraphs
• Keeping Markdown changes easier to review

Plan technology investments and engineering team growth using structured assessments. Evaluate technical debt, compare building versus buying, document architecture choices, and define engineering health metrics to produce prioritized plans grounded in costs, risks, and business needs.

• Prioritize technical debt fixes by impact and effort
• Plan engineering hiring, timing, and budget
• Compare building internally with buying a service

Review a completed development task against its acceptance criteria, check differences from design and architecture documents, and prompt code review. After approval, update the task's status and identify the next story to work on.

• Checking acceptance criteria before closing a development task
• Recording differences between implementation and design
• Remembering code review before marking work complete

Review game code for architecture, coding standards, testability, and performance concerns. Get findings tied to specific code, checks against recorded design decisions, and a report separating required fixes from optional improvements.

• Reviewing game code before closing a development task
• Checking implementation against recorded architecture decisions
• Finding testability gaps and performance concerns

Audit an existing project's design documents and supporting files to check whether their formats work with the template's skills. Get a numbered migration plan that prioritizes gaps and required changes, rather than simply listing what exists.

• Checking existing documents before adopting a project template
• Auditing game design documents or architecture decision records
• Prioritizing gaps in project tracking and configuration files

Break a large game development feature into implementation tasks with clear acceptance criteria. Each task carries relevant requirements and design decisions, with test specifications added when the selected review mode includes a QA review.

• Break a game feature into implementation tasks
• Carry requirements and design decisions into task files
• Define acceptance criteria and test specifications

Validate an implementation plan before execution through structural checks and specialist agent reviews. Check dependencies, files, tests, and architectural decisions, then update the plan to resolve findings, requesting human decisions when existing guidance is insufficient.

• Checking an implementation plan for missing sections or dependencies
• Reviewing security or database changes before implementation
• Checking consistency with architectural decisions and project rules