'adr' 검색 결과

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

개발 스킬의 첫 사용에 앞서 작업 관리 위치, 분류 라벨, 용어집과 설계 결정 기록의 위치를 확인합니다. 사용자 검토를 거쳐 저장소 공통 설정 문서를 정리합니다.

• 개발 스킬의 초기 설정
• 작업 관리 위치와 분류 라벨 정리
• 용어집과 설계 결정 기록의 위치 결정

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

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

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

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

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

Coordinate feature development from product direction through architecture, planning, validation, and implementation. Run the whole workflow or start at a selected stage, with saved decisions, review checkpoints, and a final pull request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Take a feature idea through planning and implementation
• Review architecture before writing an implementation plan
• Validate an existing plan before execution

Refine a plan or design through an ongoing interview while creating documentation. The skill combines grilling and domain-modeling to produce architectural decision records, which capture design decisions, and a glossary of relevant terms.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Refine a plan through follow-up questions
• Explore a design through an interview
• Record design decisions during discussion