1,104 件 ・ 関連度順
概要と使いどころ
Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.
日本語の概要は準備中です。原文の説明を表示しています。
Every shot carries its own timecode and shows one visible change on a body. The dread comes from the chain — a look, veins, a bite, the next person — and the ending seals a door without settling anything. Use when the user wants a Seedance 2.5 / 2.0 video prompt for this kind of clip (Horror and suspense; 中文触发词: 恐怖悬疑短片, 恐怖, 悬疑, 惊悚), or asks how published cases of this type were prompted. Read references/cases.md before drafting.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating US stocks through Serenity / @aleabitoreddit's AI and semiconductor supply-chain lens: upstream chokepoints, photonics/CPO bottlenecks, hyperscaler capex, institutional rotation, dilution risk, and thesis validation.
日本語の概要は準備中です。原文の説明を表示しています。
Profile code performance and identify bottlenecks
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when computing 3D step-response performance metrics for point-to-point drone flight — rise time, settling time, percent overshoot, and steady-state error based on Euclidean distance to the final target. Use instead of 1D stepinfo for any flight where all three position axes move simultaneously.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when calculating control system performance metrics such as rise time, overshoot percentage, steady-state error, or settling time for evaluating simulation results.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when implementing PID control loops for adaptive cruise control, vehicle speed regulation, throttle/brake management, or any feedback control system requiring proportional-integral-derivative control.
日本語の概要は準備中です。原文の説明を表示しています。
Reference for paired-reversal handling on GL batch tapes: an RV row whose ref-trace points at an earlier row cancels BOTH legs (the RV and the row it references) — but ONLY when the two value-dates fall within the shop's reversal settlement window; an RV that references a too-old posting is NOT a cancellation and posts one-sided. Useful when the posting tape carries a reference-trace column alongside reversal codes and the running balance is off by twice the reversal magnitude, or by a whole leg on stale references.
日本語の概要は準備中です。原文の説明を表示しています。
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.
日本語の概要は準備中です。原文の説明を表示しています。
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
日本語の概要は準備中です。原文の説明を表示しています。
Gestaltet Darlehens- und Finanzierungsbedingungen mit Prüfung von Bearbeitungsentgelten, Pflichtangaben, Zinsänderung und vorzeitiger Rückzahlung. Trennt Kreditgeber, Händler und Vermittler sowie B2B und Verbraucherkredit.
日本語の概要は準備中です。原文の説明を表示しています。
Episode and season structure for TV series (剧集单集与季的结构) — teasers and cold opens, broadcast four/five/six-act grids with page anchors, three tests for finding the invisible acts in streaming scripts, act-out and cliffhanger taxonomies, Oberg's four information tools, A/B/C/runner weaving and scene-count ratios, the Calvisi pilot beat sheet, five-part scene structure, and season shape (tentpoles, bottle and container episodes, two-parters, finales). Merged from Calvisi, Douglas, Oberg, Landau, Goldberg & Rabkin, Miller, Rabkin and Blum, plus act lengths measured from published West Wing, Succession, Sopranos, Downton and Fleabag scripts. Use when breaking an episode into acts, deciding how many acts a script needs, placing act outs and cliffhangers, designing a teaser, weaving A/B/C stories and runners, beating out a one-hour pilot, auditing an episode that has no shape, reverse-engineering a show's structure, or planning a season's episode order (分幕、出幕、悬念结局、季弧、瓶子集).
日本語の概要は準備中です。原文の説明を表示しています。
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 某一集是怎么写的 / 这部剧的结构表.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.
日本語の概要は準備中です。原文の説明を表示しています。
Find and fix game performance problems methodically — measure with the engine profiler first, reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix: object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets. Engine- neutral method that pairs with each engine's profiler. Use when the user mentions performance, optimize, low/dropping FPS, frame drops, stutter, lag, profiler, frame budget, draw calls, batching, garbage collection/GC spikes, object pooling, or "the game runs slow".
日本語の概要は準備中です。原文の説明を表示しています。
Attribute GPU time in one sglang-omni stage to specific lines of `sglang_omni/` python source. Drives the `llm-torch-profiler-analysis` backend with a mapping/formal trace pair plus steady-state gates, and carries the rules for reading its three tables on an omni stage. Use when a stage is slower than expected and the question is which python code is the bottleneck, not which kernel is hot.
日本語の概要は準備中です。原文の説明を表示しています。
Designs and audits macOS launchd watchdogs. Use for LaunchAgent/LaunchDaemon setup, plist changes, scheduled self-healing, repeated notifications, apps reopening after quit, crash or repair loops hammering the Mac, or a watchdog alert shown as Script Editor. Covers stop/disable/restart, cooldown/backoff, notification throttling and alert decisions. 中文：launchd 守护进程、常驻任务、开机自启、后台监控、定时自愈、通知来源排查。
日本語の概要は準備中です。原文の説明を表示しています。
Generates several distinct, clickable HTML interaction prototypes for one product surface into a Design Board and collects selection/remix feedback before implementation. Use for multiple UI versions, interaction alternatives, progressive-disclosure options, or when styling is fine but hierarchy/workflow/interaction feels off. Not for static visual-style calibration (use design-style-picker) or a settled CSS tweak.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-monitor.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 医保怎么报销, 异地就医怎么备案, 住院能报多少, 门诊报销比例, 手工报销要什么材料, 惠民保值不值得买, or work out what China's basic medical insurance (医保) will pay for a treatment. Produces the person's scheme (职工医保 or 居民医保), how a claim works for this case (direct settlement or manual reimbursement), an out-of-pocket estimate built from the city's own deductible, rate and cap, the cross-region registration (异地就医备案) steps, and the documents to keep.
日本語の概要は準備中です。原文の説明を表示しています。
Help a student and family plan university applications after the 高考 (gaokao): use the student's provincial rank rather than raw score, build a 冲 / 稳 / 保 (reach, match, safe) list from official historical admission data, check subject requirements under the new gaokao, and weigh major against university. Use when asked 帮我填高考志愿, 志愿怎么填, 冲稳保怎么排, 这个分数能上什么学校, or plan gaokao applications. Produces a structured application list with the reasoning for each choice, a risk check of the whole list, and the questions to settle as a family. Never guarantees admission.
日本語の概要は準備中です。原文の説明を表示しています。
Help users identify whether supply or demand is their primary growth bottleneck and apply tactical levers to achieve marketplace liquidity and long-term health.
日本語の概要は準備中です。原文の説明を表示しています。
Help users build functional product prototypes from natural language or visual mocks using AI coding tools. This skill enables product leaders to bypass engineering bottlenecks and validate ideas through hands-on building.
日本語の概要は準備中です。原文の説明を表示しています。