2,927 件 ・ 関連度順
概要と使いどころ
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate specialized code, security, architecture, and performance reviewers and consolidate their results. Use when a codebase needs parallel review across multiple disciplines.
日本語の概要は準備中です。原文の説明を表示しています。
Master Julia 1.10+ with modern features, performance optimization, multiple dispatch, and production-ready practices. Expert in the Julia ecosystem including package management, scientific computing, and high-performance numerical code. Use PROACTIVELY for Julia development, optimization, or advanced Julia patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate specialized code, security, architecture, and performance reviewers and consolidate their results. Use when a codebase needs parallel review across multiple disciplines.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
How episodic television actually gets made by a group (编剧室与制作现实) — merged from Goldberg & Rabkin (pitch as audition, leave-behind, cracking the story, beat sheet, notes discipline, production rewrites), Pamela Douglas (John Wells's room, staff-from-hell mistakes, the seven-rung ladder, step deal, the 14-day draft), Neil Landau's showrunner interviews (Lindelof, Mazzara, Katims, Bays), Evan Smith on sitcom staffing and roundtables, Richard Blum (dated), Kam Miller, and first-hand accounts by David Chase, Jesse Armstrong, Lucy Prebble, Aaron Sorkin, Julian Fellowes and Phoebe Waller-Bridge. Use when joining or running a writers' room, breaking an episode with a group, writing a leave-behind, beat sheet or outline on deadline, pitching episode ideas to an existing series, writing a spec episode, taking or giving notes, rewriting because of money, actors or locations, choosing between a staffed room and a single-author process, or asking 什么是 showrunner／编剧室怎么运作／怎么接 note.
日本語の概要は準備中です。原文の説明を表示しています。
Genre anatomy from John Truby's The Anatomy of Genres (类型解剖 / 类型节拍 / 混合类型 / 超越类型) — genres as beat systems with a life philosophy underneath; three rules (hit every beat of your genre, mix three or four genres, transcend the primary genre), the ladder and families of twelve genres (Horror 恐怖, Action 动作, Myth 神话, Memoir and Coming-of-Age 回忆录与成长, Science Fiction 科幻, Crime 犯罪, Comedy 喜剧, Western 西部, Gangster 黑帮, Fantasy 奇幻, Detective and Thriller 侦探与惊悚, Love 爱情), each with its hero/opponent/world/plot-shape template, beat list, hard rules with failure conditions, subgenres and transcendent paths, plus a genre-mixing worksheet and a diagnostic. Kept beside sw-truby-anatomy and the Field/Snyder page maps. Use when choosing or confirming a script's genre, when a genre story feels generic or misses the beats its audience expects, when mixing genres, when a horror lacks pressure, an action lacks plot, a love story lacks opposition or a detective story lacks reveals.
日本語の概要は準備中です。原文の説明を表示しています。
Research-brief + claim-record discipline for delegated or AI-assisted research work. Use when starting any substantive research task or long autonomous run (write the brief first), and when reporting results that will support a claim in a paper or decision (produce the claim record). Keeps faster execution from being confused with credible evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Assemble a submission-ready replication package to the AEA Data and Code Availability Standard (DCAS) / openICPSR / Social Science Reproduction Platform expectations — standard replication README, dataset manifest, computational-requirements capture, a Table/Figure → script:line map, and a confidential-data deposit plan. Use when user says "build the replication package", "prepare the openICPSR deposit", "make the AEA data and code package", "DCAS compliance", "assemble the deposit for the journal", or after a paper is accepted and the journal's data editor needs the package. NOT a numeric verifier — it calls /audit-reproducibility to confirm claims reproduce before packaging.
日本語の概要は準備中です。原文の説明を表示しています。
Root-cause a failing or wrong empirical result with a disciplined reproduce → minimise → hypothesise → instrument → fix loop, instead of guessing-and-poking. Use when the user says "why is my regression wrong", "this number changed", "my script errors out", "the result won't reproduce", "debug this", "this estimate looks wrong", or "it worked yesterday". Tuned for research code (R/Stata/Python): type coercion, NA/merge blow-ups, factor levels, clustering/SE choices, weighting, collinearity/convergence, seeds, package-version drift. Use `--no-fix` to localize the root cause without editing shared or load-bearing files.
日本語の概要は準備中です。原文の説明を表示しています。
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision. Use whenever the user asks to draw, diagram, sketch or visualize a system on AWS, Azure or Google Cloud, or one built from their services (Lambda, DynamoDB, S3, EC2, EKS, RDS, API Gateway, Azure Functions, App Service, AKS, Cosmos DB, Cloud Run, GKE, BigQuery and the like), even if they never say 'cloud', 'diagram' or a tool name; also for a diagram of Terraform code. Prefer it over Mermaid, PlantUML, hand-written SVG or ASCII, which cannot use the official icons or VPC/subnet grouping. Not for diagrams that are not cloud infrastructure: sequence diagrams, flowcharts, class or ER diagrams, code or module structure, org charts, on-premises-only networks; use Mermaid or similar for those. Works with or without Terraform: with Terraform code the diagram comes from terraform plan; without it, write a small JSON graph and render it.
日本語の概要は準備中です。原文の説明を表示しています。
When a symptom has several plausible causes, rank falsifiable hypotheses and run the cheapest discriminating observation first; prefer least-assumptive survivors only after evidence fit.
日本語の概要は準備中です。原文の説明を表示しています。
Design and build the visual layer of a long-form talking-head video as one persistent world the camera moves through, instead of a sequence of separate graphics. Use when asked to edit a video, add motion graphics, design the visuals for a script, plan an edit, or fix an edit judged confusing, text-heavy, hard to follow, or "clearly made by an AI". Covers the persistent world, camera grammar, the spotlight rule, spatial open loops, ornament and token discipline, transcript timing, and the verification gates.
日本語の概要は準備中です。原文の説明を表示しています。
Generate and render Mermaid diagrams for architecture docs, READMEs, PRs, terminals, chats, and CI as themed SVG, PNG, or ASCII/Unicode art. Use this skill whenever the user provides Mermaid code or .mmd files; asks for a flowchart, sequence/state/class diagram, ERD, XY chart, or architecture/workflow/data-model visualization; or wants to beautify, theme, batch-convert, or make a diagram terminal-friendly. Runs locally without a browser or DOM, with 15 built-in themes and custom colors.
日本語の概要は準備中です。原文の説明を表示しています。
DataOps and DS/MLOps testing reference for data tiering, Bronze-to-Silver validation placement, pipeline invariants, pytest categories, and validation-versus-drift. Use when designing, reviewing, or generating data pipelines, transformation code, data validation, or data-science test suites.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture diagram authoring for cloud infrastructure and declared data catalogs. Use when rendering Azure IaC or DS_CATALOG_V1 relationships as caller-selected ASCII or Mermaid diagrams.
日本語の概要は準備中です。原文の説明を表示しています。
Experiment design reference for problem-class framing, Minimum Viable Experiment coaching, hypothesis formation, vetting and red flags, and experiment readiness. Use when translating a stated business outcome into candidate data-science problem classes, or when framing, vetting, scoping, or evaluating an experiment of any kind, including data feasibility, architecture, LLM, performance, use-case, UX, prototyping, and hardware experiments.
日本語の概要は準備中です。原文の説明を表示しています。
Design Thinking method coaching knowledge across all nine methods including per-method techniques, deep expertise, and industry context (energy, financial services, healthcare, manufacturing, nonprofit and social impact, pharmaceuticals and life sciences, professional services, public sector, retail and CPG)
日本語の概要は準備中です。原文の説明を表示しています。
Design and build the visual layer of a long-form talking-head video as one persistent world the camera moves through, instead of a sequence of separate graphics. Use when asked to edit a video, add motion graphics, design the visuals for a script, plan an edit, or fix an edit judged confusing, text-heavy, hard to follow, or "clearly made by an AI". Covers the persistent world, camera grammar, the spotlight rule, spatial open loops, ornament and token discipline, transcript timing, and the verification gates.
日本語の概要は準備中です。原文の説明を表示しています。
Land the winning experiment from an evo run as a clean, mergeable change -- open a PR when the repo has a remote, otherwise merge into the working branch. Distills the best-scoring experiment down to the minimal diff that reproduces its behaviour, shaped for the qualities a maintainer merges on (scope discipline, test integrity, style adherence), then attaches an advisory mergeability report. Use when the user invokes /evo:ship, asks to land/merge/ship the best result, or wants to turn a finished optimization into a pull request.
日本語の概要は準備中です。原文の説明を表示しています。
数据可视化的判断层 SSOT——画任何图表、dashboard、看板之前先加载它，不是画完之后。管"该不该这么画"：这张图想让读者得出什么结论、用均值还是中位数、能不能聚合、堆叠还是折线、能不能上双轴、配色与颜色数量、同一实体跨图是否同色同位、表格该留几列。介质无关：HTML 报告页、React/Vue dashboard、PPT 原生图表、matplotlib/plotly/ECharts/D3、渲染成 PNG 的图，一律适用。Use when 动手画图之前，或评审既有图表（"这几张图有什么问题"、"图例为什么不一致"）。Not for 报告页的排版/组件/交互（用 report-with-html:report-with-html）或 PPT 原生图表的实现与渲染陷阱（用 deck-creator:deck-creator）。
日本語の概要は準備中です。原文の説明を表示しています。
Produces the reader-facing HTML artifact — report, dashboard, architecture view, data browser, or review workbench — evidence-backed, browser-verified. Use when the deliverable IS a visual HTML report, or the user asks for an HTML/web presentation. Load data-visualization-discipline for chart judgment. Not for chat status or Markdown prose unless asked to become a report; not for PowerPoint (deck-creator Route C).
日本語の概要は準備中です。原文の説明を表示しています。
Run a fast, honest competitive scan — the dimension table built from public evidence (sites, docs, pricing pages, changelogs, reviews), the claims-vs-observed discipline, and the so-what synthesis that ends in moves, not a landscape mural. Use when asked what are competitors doing, quick scan of these three rivals, how does our pricing/feature set compare, or prep the competitive slide honestly. Produces the evidence-based comparison table, the marketing-vs-reality flags, the so-what synthesis, and the staleness date.
日本語の概要は準備中です。原文の説明を表示しています。
Fix a team's chat sprawl — the channel map with one purpose per channel, the naming scheme that makes purpose findable, the archive pass for the dead and duplicated, and the posting norms (threads, @-discipline, urgency signals) that keep signal findable. Use when asked clean up our Slack/Teams, we have 90 channels and nothing is findable, set channel norms, or where should things get posted. Produces the channel audit and map, the naming scheme, the norms card, and the archive pass.
日本語の概要は準備中です。原文の説明を表示しています。