'adr' 검색 결과

Records an architecture decision as a Nygard/MADR-shaped ADR under decisions/ — capturing the context that forced the choice, the options weighed, the decision itself, and its consequences in both directions, plus the supersedes chain that keeps a decision log honest. Read when asked to record an architecture decision, write an ADR, log the decision we made, document why we chose X over Y, capture this decision for the record, or supersede an old decision with a new one. Do NOT read to frame a proposal or explore an idea not yet decided (frame-a-proposal), to write a spec or implementation plan (write-a-spec), to write an incident postmortem (write-a-postmortem), or to judge whether a design is sound (review-a-design). This skill records a decision already made; it does not make one.

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

Read every ADR markdown file in the project's docs/adr/ folder so you have full context on past decisions. Use only when the user explicitly calls it.

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

Authoring skill for Architecture Decision Records (ADRs) supporting capture, from-planner-handoff, and adopt-template entry modes with selectable Y-Statement or MADR v4.0.0 output templates, supersession lineage, and ASR trigger evaluation.

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

Create an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs.

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

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, mid-build deviations from the plan need capturing, or a finished change needs buy-in or verified understanding before merge. Pairs with [write-spec](../write-spec/SKILL.md) — walk the quadrants to burn off fog before slicing, and feed the finished map into the spec.

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

RoadRunner asset path lookup tables for map format conversions in MATLAB. Maps lane markings, signs, signals, barriers, objects, and lane types to RoadRunner asset paths. Use when converting map formats to RRHD, resolving asset paths, or assigning visual assets to HD Map objects.

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

Convert Lanelet2 maps (.osm) to RoadRunner HD Map (.rrhd) format using MATLAB. Use when converting Lanelet2 maps into RoadRunner Scene Builder, building driving scenes from open-source map data, or transforming road network definitions for simulation.

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

Creates new Architecture Decision Record (ADR) documents for significant architectural changes using a consistent template and repository-aware naming and storage guidance. Use when a user or agent decides on an architectural change, needs to document technical rationale, or wants to add a new ADR to the project history.

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

AdRoll integration. Manage data, records, and automate workflows. Use when the user wants to interact with AdRoll data.

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

Provider-independent dialogue editing and ADR direction for AI agents producing generated videos, films, ads, avatar clips, explainers, localization/dubbing, podcasts, recuts, and social content. Use for dialogue prep, repair, room tone, take comping, sync, ADR cueing, dubbing direction, pronunciation, de-essing, plosives, mouth clicks, voice continuity, synthetic voice consent boundaries, captions/transcripts handoff, mix handoff, loudness, intelligibility, accessibility, and QA.

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

音乐制作 / 混音 (音乐制作 / 混音 (Music Production & Mixing) — 录音棚与卧室工作室里把一首歌从编曲/录音/编程做到混音/母带成品的工程+艺术认知操作系统，面向制作人(producer)、混音师(mixing engineer)、母带工程师(mastering engineer)、beatmaker、唱作人/bedroom producer，以及想入行/服务这行(录音棚、plugin 厂商、sample 公司)的视角。覆盖: (a) 第一性张力 — **服务歌曲/情绪 (serve the song / emotion-first: 技术只为打动人，'if it sounds good it is good'，用耳朵不用眼睛) ⇄ 技术正确/工程纪律 (technical correctness: gain staging 增益结构、headroom 余量、相位 phase、监听校准、LUFS 响度规范)**; **黄金耳朵/直觉混音 (mix by ears, reference-driven, 不看分析仪) ⇄ 看表/分析仪/规则 (mix by metrics: EQ 曲线、频谱仪 spectrum analyzer、相关计 correlation meter)**; **少即是多/减法混音 (subtractive, 'less is more', 录好源头 = 混音成功一半) ⇄ 重度处理/'we'll fix it in the mix' (heavy processing, 后期补救)**; **In-the-box 全数字 (ITB: DAW + 插件，召回方便，bedroom 可达专业) ⇄ 模拟硬件/outboard (analog console + 硬件，'mojo'/谐波染色 vs 召回噩梦)**; **人性化/groove/不完美 (humanize, push/pull, 'the feel') ⇄ 量化/网格/修音 (quantize to grid, pitch-correct, 'in the pocket' 靠编辑)**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量+CLI 化) — 编曲制作 arrangement/production → 录音/编程 tracking/programming → 编辑 editing (comping 选段/quantize/pitch-correct/time-align) → 混音 mixing (gain staging → balance 平衡 → EQ → compression → 空间 reverb/delay → 自动化 automation → 总线/母线处理 bus/mix-bus) → 母带 mastering (响度/EQ/限制 limiting/dither/排序+间隔) → 交付 delivery (DDP/streaming spec/stems); (c) 工具栈 — DAW (Pro Tools 录音棚标准/Ableton Live 电子+现场/Logic Pro Mac 性价比/FL Studio beatmaker/Cubase/Studio One/Reaper); 插件 (EQ: FabFilter Pro-Q/SSL/API; 压缩: 1176/LA-2A/SSL bus comp 及其复刻 Waves/UAD/Plugin Alliance; 混响: Valhalla/Lexicon/Bricasti; 调音: Auto-Tune/Melodyne; 限制器 limiter: Pro-L 2/Ozone); 硬件 (监听音箱 monitors: Yamaha NS-10/Genelec; 声学处理 acoustic treatment; 转换器 converters: Apollo/RME; 话筒 mics: U47/SM7B/57); 采样/音色 (Splice/sample packs/Kontakt/Serum 合成器); (d) 知识正典 — Mixing Secrets for the Small Studio (Mike Senior)、The Mixing Engineer's Handbook / Recording Engineer's Handbook (Bobby Owsinski)、Zen and the Art of Mixing (Mixerman)、The Art of Mixing (David Gibson 可视化)、Modern Recording Techniques、Sound on Sound 杂志、Mix With The Masters 大师课、Pensado's Place; (e) figures/流派 — 混音大师 (Chris Lord-Alge CLA 摇滚/Andrew Scheps 'Stadium' 3-bus/Tony Maserati/Manny Marroquin/Serban Ghenea 流行隐形混音/Michael Brauer multing); 制作人 (Rick Rubin 减法/氛围、Quincy Jones、Dr. Dre 完美主义、Max Martin 流行结构、Jack Antonoff、Finneas bedroom→Grammy、Metro Boomin/trap、Timbaland、Pharrell); 母带 (Bob Katz K-system/响度战争批判、Bob Ludwig、Greg Calbi); 教育者 (Mike Senior、Pensado、Warren Huart Produce Like A Pro、Dan Worrall 技术深挖); (f) 行业话术/黑话 — gain staging/headroom/LUFS/true peak/comping/bouncing/printing/stems/DI/reamp/sidechain/parallel compression 并行压缩/mid-side/bus/aux/send-return/dry-wet/transient/sibilance/de-ess/pumping/mud 浑浊/harsh 刺耳/boxy/muddy/in the pocket/the pocket/quantize/swing/groove/vibe/mojo/reference track/A/B/recall/print/glue 胶水; (g) 争议/批判 — 响度战争 loudness war (Bob Katz/Loudness Penalty/streaming 归一化 LUFS 终结了吗)、修音/Auto-Tune 之争 (artistic vs cheating)、ITB vs 模拟玄学 (硬件 'warmth' 是否安慰剂、null test 盲测)、preset/AI 混音 (iZotope/LANDR/sample-based 是否毁了 craft)、bedroom producer 民主化 vs 录音棚消亡、'loudness'/over-compression、plugin 复刻 vs 真硬件、Spotify normalization 对母带的影响、过度依赖 reference/抄袭; (h) 创意 vs 技术张力是本行业 deep tacit 知识的核心 — 大量隐性 '听感' 知识难以言传，靠 reference/学徒/千小时积累。不含: 现场扩声 live sound/PA、音乐理论/作曲 composition (虽相关但聚焦录音棚后期制作)、配乐/film scoring (虽相关但聚焦歌曲制作)、纯硬件电子工程/合成器 DIY、音乐商业/版权/发行 (虽相关但聚焦制作技艺本身)。) Master OS — automated mastery of 音乐制作 / 混音 (Music Production & Mixing) — 录音棚与卧室工作室里把一首歌从编曲/录音/编程做到混音/母带成品的工程+艺术认知操作系统，面向制作人(producer)、混音师(mixing engineer)、母带工程师(mastering engineer)、beatmaker、唱作人/bedroom producer，以及想入行/服务这行(录音棚、plugin 厂商、sample 公司)的视角。覆盖: (a) 第一性张力 — **服务歌曲/情绪 (serve the song / emotion-first: 技术只为打动人，'if it sounds good it is good'，用耳朵不用眼睛) ⇄ 技术正确/工程纪律 (technical correctness: gain staging 增益结构、headroom 余量、相位 phase、监听校准、LUFS 响度规范)**; **黄金耳朵/直觉混音 (mix by ears, reference-driven, 不看分析仪) ⇄ 看表/分析仪/规则 (mix by metrics: EQ 曲线、频谱仪 spectrum analyzer、相关计 correlation meter)**; **少即是多/减法混音 (subtractive, 'less is more', 录好源头 = 混音成功一半) ⇄ 重度处理/'we'll fix it i

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

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

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

Creates, supersedes and validates decision records (ADRs) against the convention a collection already follows, instead of imposing a published one. Use when the user wants to record a decision, write an ADR, supersede an existing decision, audit or lint a decisions folder, check that an ADR index is in sync, or asks "why did we decide X". Deduces the filename scheme, section set and status vocabulary from the records already there; ships a validator with an exit code, so the audit is a check and not an opinion.

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

Create and manage Architecture Decision Records (ADRs). Use when making architectural changes (refactoring, API versioning, new domain layers, schema changes), when reviewing recent commits for documentation needs, or when the user mentions ADR, architecture decisions, or documenting technical decisions.

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

Trademark filing procedures covering EUIPO (EU), USPTO (US), and WIPO Madrid Protocol (international). Walks through pre-filing conflict checks, Nice classification, descriptiveness assessment, mark type decisions, filing basis strategy, office-specific e-filing procedures, Madrid Protocol extension, post- filing monitoring, and open-source trademark policy drafting. Use after running screen-trademark to confirm the mark is clear, when ready to secure trademark rights in one or more jurisdictions.

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

Write effective Architecture Decision Records. Use when: (1) Creating a new ADR, (2) Recording a design decision, (3) User mentions ADR, decision, trade-off, or alternatives

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

Super Base Context — project doc loader & synchronizer. Triggers even without explicit "load docs"/"sync docs." READ MODE — load architecture/modules/coding/decision docs when work references project state: code work (write/modify/remove); design (features/APIs/schemas/architecture); review (modules, past solutions); tech selection; ADR research; migration/refactor planning; performance/security analysis; tests; code reviews; any spec/plan/design/ADR referencing project. WRITE MODE — NET DELTA vs. last doc sync: additions/modifications/REMOVALS/deprecations of previously-synced code or decisions (docs revert: delete BCU file/ADR), AND rollbacks. User signals: sync docs/done/ready to commit/pre-commit/record decision. Auto-fires before final task-completion reply. WRITE MODE does NOT fire on: brainstorming, generic/read-only Q&A, in-session try-and-undo with no net change, already-synced.

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

Identifies young patients with classic primary aldosteronism features who may proceed directly to unilateral adrenalectomy without adrenal venous sampling based on high probability of unilateral disease. Triggered when a clinician sees a patient <35 years with hypokalemia, unilateral adrenal tumor on CT, and high plasma aldosterone concentration and asks whether AVS can be bypassed.

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

Selects spironolactone as first-line mineralocorticoid receptor antagonist for bilateral primary aldosteronism, with eplerenone as an alternative when spironolactone–related adverse effects are problematic. Trigger phrases include 'confirmed bilateral PA on AVS', 'idiopathic adrenal hyperplasia', 'bilateral adrenal hyperplasia', 'glucocorticoid-remediable aldosteronism', and 'initiating medical therapy for bilateral adrenal disease'.

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

This skill outlines the emergency management of suspected adrenal crisis, recommending immediate parenteral hydrocortisone (100 mg adult, 50 mg/m² pediatric) plus fluid resuscitation, then 200 mg/24 h (50–100 mg/m²/24 h pediatric) hydrocortisone. Trigger when patient presents with hypotension, hyponatremia, hyperkalemia, or unexplained shock suggestive of adrenal insufficiency.

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

Recommends measuring serum cortisol levels at 8–9 AM as the first-line test for diagnosing central adrenal insufficiency. Use when starting diagnostic workup for suspected adrenal insufficiency; triggers include suspected adrenal insufficiency requiring initial cortisol testing.

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

Applies serum cortisol cutoffs (<3 μg/dL indicates central adrenal insufficiency; >15 μg/dL likely excludes it) when evaluating morning cortisol for suspected adrenal insufficiency. Triggers include morning cortisol measurement in suspected AI and use when interpreting morning cortisol levels for adrenal insufficiency workup.

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

Recommends against using fludrocortisone for mineralocorticoid replacement in patients with secondary adrenal insufficiency. Trigger phrases include: considering mineralocorticoid replacement for secondary adrenal insufficiency and secondary adrenal insufficiency patient needing mineralocorticoid replacement.

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

Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.

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