「hr」の検索結果

End-to-end pipeline for extracting heart rate (HR) and breathing rate (BR) from raw short-range radar I/Q captures — both continuous-wave (CW, 24 GHz clinical boards) and FMCW mmWave (60/77 GHz, TI IWR/AWR). Use when Claude needs to parse interleaved I/Q binary, do a Range FFT on FMCW chirps, remove static clutter, pick a subject range bin, extract phase with unwrapping, design HR/BR bandpass filters, pick a peak frequency via PSD, reject the HR second harmonic that often dominates the fundamental, or handle respiration-harmonic leakage on slow breathers. Not for pulse/UWB range gating, MIMO beamforming, Doppler-only gesture radar, arrhythmia detection, or multi-subject source separation.

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

Download flood stage thresholds from NWS (National Weather Service). Use when determining flood levels for USGS stations, accessing action/minor/moderate/major flood stages, or matching stations to their flood thresholds.

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

Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture reviews, threat identification, and secure-by-design planning.

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

Für Chronologie: Compliance-Dokumentation und Aktenvermerk: ordnet Akte, Belege und Lücken; Ergebnis: Chronologie mit Beleg- und Widerspruchsmatrix.

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

Für Anklageschrift zerlegen: erstellt Entwurf mit Antrag, Beweis und Anlagen; Ergebnis: Schriftsatz mit Begründungs- und Anlagenlogik.

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

Für Aktenvorblatt: Schriftsatz-, Brief- und Memo-Bausteine: erstellt Entwurf mit Antrag, Beweis und Anlagen; Ergebnis: Schriftsatz mit Begründungs- und Anlagenlogik.

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

Für Unternehmerverkehr Schnellcheck: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

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

Für Schriftform Textform: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

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

Für Mehrsprachige AGB Check: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

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

Für Gesetzliches Leitbild Abweichung 307: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesetzliches-leitbild-gewahrleistung.

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

Für Gewährleistung Ausschluss: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

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

Für Compliance Sanktionen: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: haftung-sanktionen-grobe-fahrlaessigkeit.

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

Writing plays and screenplays in the Chekhovian mode (契诃夫戏剧法) — distilled from the complete plays (没有父亲的人/普拉东诺夫, 伊凡诺夫, 林妖→万尼亚舅舅, 海鸥, 三姊妹, 樱桃园, nine one-acts) plus Chekhov's own letters, Stanislavsky's and Nemirovich-Danchenko's rehearsal notes and 焦菊隐/童道明 criticism. Covers the four-act mood-based structure without central climax, off-stage events, "correct answer stated in Act 1 and refused", the announced event that never happens, three-layer endings (hope monologue + nihilist line + household action), no-villain conflict with environment, every character's object and catchphrase, one-way love chains, half-step-off dialogue, philosophy cut by thirst, the shortest words for the deepest pain, stage-direction and sound discipline, and how Chekhov revised The Wood Demon into Uncle Vanya. Use when the user wants an ensemble drama, a "nothing happens" play, subtext-heavy dialogue, a family estate / provincial story, an anti-climactic structure, or asks how to "Chekhov-ize" a script.

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

Japanese (and other non-Hollywood) screenwriting methods (日本编剧方法/原创剧本实战) — distilled from ten Japanese directors and writers in ゼロからの脚本術; Kosawa Ryota (three acts as 起承转合, speed by jumping), Uchida Kenji (beautiful structure, time-axis tricks), Miki Satoshi (small-material notebook, theme emerges later), Sono Sion, Omiya Ellie (dialogue from inner monologue), Kakei Masaya ("if + moreover"), Fukuda Yuichi (character = actor + flaw, audience as tsukkomi), Yokohama Satoko, Takahashi Izumi ("pain"), Yukisada Isao (situation-born originals); plus Arai Haruhiko (IP adaptation, "write what you're ashamed of"). Neighbours; sw-korean-french-screenwriting, ozu-screenplay-style. Use when writing an original Japanese-style script or TV drama, working from small material and fragments, choosing between structure-first and character-first methods, building a Japanese 企画書, designing comedy tsukkomi systems, or when Hollywood models feel wrong for a quiet, daily-life, non-goal-driven story.

Project orchestrator for the screenwriting skill set (剧本项目主线调度 / 状态存档 / story bible) — a meta-skill that adds no new craft knowledge but routes a screenplay or stage-play project through stages (premise → structure → character → scenes → draft → revision → submission) and a TV / streaming series project (电视剧 / 剧集 / pilot / 一季) through a separate series stage table (engine → character network & season arc → documents/bible → pilot structure → break story & outline → draft → submission), names which sw-* skill to invoke at each stage, defines each stage's deliverable and advisory exit check, and keeps all project state in a story-bible.md file so work can resume across sessions. Use when starting a new script project, resuming one ("continue my screenplay", "where were we"), when the user asks "what should I do next" on a script, when converting a vague idea into a full development pipeline, or when the other sw-* skills are firing individually and the overall process needs sequencing.

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

Korean and French screenwriting practice (韩国/法国编剧方法) — from the international masterclass; Oh Seung-uk (Christmas in August, The Shameless; field research in disguise, "write the emotion", first act and last act first, spaces as skeleton, reading to hostile listeners, surviving producers), Choi Seok-hwan (King and the Clown; genre as promise to the audience, "story = deepening crisis + intensifying desire", two reversals and bittersweet endings, the producer/director/writer trio), and Frédéric Auburtin (Paris je t'aime; dialogue last, Italian-style table reads, "12 lines not 13", dignity for characters, originals born from commissions, editing by emotion). Use when working in a Korean-style commercial drama or genre film, a French auteur/commission context, when planning field research, when a producer relationship is the problem, or when you need the Korean "three live together" development model or the French "emotion first, structure second" editing approach.

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

Case studies of television series writing (剧集案例库) from primary texts; Sorkin's six West Wing teleplays (act-page tables, eight act-out types); Chase's five Sopranos scripts (the 35-beat A/B/C/D recipe, what a pilot refuses to explain); Fellowes's annotated Downton Abbey season two (19 storylines, 419 footnotes); Waller-Bridge's Fleabag Scriptures (the six-episode half-hour template); Calvisi's eight minute-by-minute pilot beat sheets (Breaking Bad, Mad Men, Game of Thrones and more); Landau's 47-series structure appendix; Miller's Hannibal and HTGAWM breakdowns; Goldberg & Rabkin's beat sheets; Sakamoto Yuji's We Made a Beautiful Bouquet (a feature) and Noh Hee-kyung's The Most Beautiful Goodbye. Use when you want a worked example of how an episode or pilot is built, need real act lengths, scene counts or storyline grids to imitate, are breaking a multi-thread ensemble episode, designing a bottle episode or a finale, writing a relationship or family drama, or ask 某一集是怎么写的 / 这部剧的结构表.

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

Generate one or more standalone Meta image-ad creatives via ChatGPT Image 2 (gpt-image-2) through the Arcads external API. Locks the model, auto-strips platform chrome, enforces edge-safe layouts and glyph-safety inside body text. Use when the user asks for a "gpt-image-2 ad", "ChatGPT Image ad", "Image 2 ad creative", "make a static image ad with GPT", or anchors on a need for typography-heavy / dense-text / UI-mimicry ad creatives (chat threads, comparison tables, fake search results, iOS dialogs, Slack snapshots, ChatGPT-conversation ads, Apple Notes lists). Does NOT trigger on Nano Banana cues — use nano-banana-image-ad for those.

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

Systematic strategic planning framework for philosophy and interdisciplinary academic papers targeting preprint platforms (PhilArchive, arXiv, PhilSci-Archive). Use when users want to: (1) plan a paper on a specific topic, (2) identify research gaps and assess originality, (3) develop optimized paper outlines, (4) prepare for preprint submission, or (5) understand platform requirements and writing standards. Triggered by phrases like 'plan a paper on,' 'help me design a paper about,' 'identify research gaps in,' 'is this idea original,' or when users need structured research planning. The skill guides through three phases: Platform Analysis (identifying target venue and studying sample papers), Theoretical Framework (AI-driven literature search and gap identification), and Outline Optimization (structured design with reviewer-perspective self-assessment). Each phase includes quality evaluation standards and validation checkpoints. Output: optimized detailed outline ready for systematic writing (use with academic-paper-composer skill).

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

Read and write Plain support: find and upsert customers, list threads, create and reply to support threads. Trigger phrases: plain, support tickets.

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

Minimalist UX/Interaction Audit Expert that deconstructs complex interactions through cognitive load and operational efficiency lenses. Use this skill when you need to perform a UX walkthrough audit on a Figma prototype or web interface, evaluating usability based on principles like fewer clicks, less UI elements, no hidden logic, and self-explanatory design.

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

Use when positioning an American Anthropologist (AA) manuscript against the literature so it reads as a four-field contribution. AA readers span sociocultural, archaeology, biological, and linguistic anthropology, so the paper must engage the conversations they expect and decenter a US/Anglophone-only canon. Stakes the contribution and citational politics; it does not write the lit review.

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

Use when defending the research design of an American Anthropologist (AA) manuscript — fieldwork and participant observation, interview and archival design for ethnographic/qualitative work, material/contextual analysis for archaeology, and appropriate lab/quantitative design for biological anthropology. AA judges each mode on its own terms with reflexivity. Strengthens the design; it does not write code or run fieldwork.

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

Use when starting or navigating any American Anthropologist (AA) manuscript as the entry point. Routes to the right AA sub-skill based on lifecycle stage, subfield (sociocultural, archaeology, biological, linguistic), and section type (Research Article, Vital Topics Forum, World/Public/Multimodal Anthropologies, Review Essay). It dispatches; it does not draft content.

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