“first run”的搜索结果

Use ONLY when the user asks to check, validate, review or audit analysis code for scientific correctness, or when you are the reviewer agent running its checks. Never run it unprompted as part of ordinary analysis work. Covers physics, earth/geo, biology, chemistry, social science and bioprocess/fermentation. Runs a deterministic domain-correctness gate that catches code which runs but is scientifically wrong (unit/dimension mismatch, Euclidean distance on lat/lon without a CRS, 0-based/1-based coordinate and strand errors, impossible SMILES valence, uncorrected multiple comparisons, averaging a categorical code, unconstrained kinetic-parameter fits, kLa computed from raw DO instead of the driving force, arithmetic mean of raw CFU counts, ANOVA/Tukey with no assumption check, a curvature DOE design fit with a first-order model, an ML model fit across process scales with no correction). Surfaces structured findings; never claims the code is correct.

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when `hogli ci:insights` or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a flaky job, when asked to check Trunk Flaky Tests for a test, PR, or master, or when asked to deflake, stabilize, or fix a flaky Jest, pytest, or Playwright test. Core discipline: reproduce locally before changing anything, fix the root cause (never mask it with sleeps, retries, or bigger timeouts), and prove the fix with an N-run validation loop sized to the observed failure rate. Stabilizing is not the only valid outcome — the skill also gates whether the test should exist, so deleting a test that catches nothing real, or re-leveling one that flakes because of the level it runs at, are first-class endings.

中文简介正在准备中。当前显示原文说明。

Install or verify the oma CLI and its runtimes (bun, uv, serena) before any oma-* skill, agent, or workflow runs an `oma` command. Use when `oma` is missing from PATH, when a skill says to run `oma ...` and the shell reports "command not found", or on the first task in a fresh Cursor or Grok Bot workspace.

中文简介正在准备中。当前显示原文说明。

Use when generating or editing video with Runway models on Scenario via MCP: text-to-video or image-to-video from a first frame with Gen4.5 (cinematic motion, sequenced actions, camera choreography), or video-to-video editing of real footage with Aleph 2 (remove objects, swap products, restyle or relight shots, keyframe-pinned reference images, motion and audio preserved). Keywords: Runway ML, Gen4.5, Gen-4.5, Aleph, T2V, I2V, V2V, first frame.

中文简介正在准备中。当前显示原文说明。

Designing first-run product onboarding wizards that get users to the ah-ha moment without overwhelming them. Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement. Honest about tutorial-overload (dump everything upfront), skip-friendly-empty (skipped onboarding leads to abandoned product), and earned-progressive-disclosure (right things at the right moments) patterns. Triggers on onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, ah-ha moment design. Also triggers when activation rates are low, when users skip onboarding and never return, when onboarding flows are being scoped for the first time, or when audience research shows users not finding key features.

中文简介正在准备中。当前显示原文说明。

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

中文简介正在准备中。当前显示原文说明。

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, reads the account structure once, writes the plan folder, seeds the board, creates the creative doctrine, builds the dashboard, and registers the recurring jobs. It asks about exactly two things, the monthly ceiling and the daily cap, because those are the two numbers that decide how much money can leave. On every monthly run it re reads the evidence, corrects what the ledgers prove wrong, and reconciles drift.

中文简介正在准备中。当前显示原文说明。

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the launch board, builds the tailored command center, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed, reconciles drift, and rebuilds. It holds every outbound action unless you released the channel, and it never enters a credential.

中文简介正在准备中。当前显示原文说明。

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces, reads the member's own already published posts, and builds the voice file from real samples rather than from an idea of a voice, then writes the plan, creates the proof inventory, seeds the opening slots, and registers the recurring jobs. On every monthly run it re reads the evidence the kit produced and rebuilds only what the evidence contradicts. It publishes only where you released the channel, never replies, spends only where you released it, and it never enters a credential.

中文简介正在准备中。当前显示原文说明。

Runs once by hand on the first day and once a month after that, light browser lane. On the first run it researches the business from its own published surfaces before asking anything, writes the strategy folder, creates the ledgers, seeds the opening cards, builds the single page dashboard, reconciles the schedule table, and registers the eight recurring jobs. On every monthly run it re-reads a month of the kit's own evidence, applies what changed, adds a tab for a channel that gained volume, rebuilds, and reconciles every registered job against the table. It holds every outbound action unless you released the channel, and it never enters a credential.

中文简介正在准备中。当前显示原文说明。

Produce a high-confidence, CONCISE implementation / architecture / strategy PLAN that follows the OMC plan system end to end. It first runs OMC's real requirements interview (auto-chains the `omc-plan` skill: one question at a time, explore-first, Analyst consult) to produce an initial plan in `.omc/plans/`, then DEEPENS that plan with a 3-round ITERATIVE fusion loop — each round an Opus 4.8 panelist (Agent subagent) and a GPT-5.5 panelist (via codex) critique/improve it IN PARALLEL and BLIND, then Opus 4.8 (the orchestrator) judges and synthesizes one tighter plan that seeds the next round, stopping early on convergence. Writes the final dense plan back to the same `.omc/plans/<slug>.md`, then offers the OMC handoff (`/omc-plan --review` → `/team` or `/ralph`). Use for high-stakes planning, architecture decisions, strategy calls, and hard debugging — especially when the user runs /plan or asks how to approach a non-trivial build. Reuses the `fusion` skill's run_codex.sh + judge rubric. NOT for trivial tasks (single pass is enough).

中文简介正在准备中。当前显示原文说明。

Autonomous bug-bounty campaign driver. Runs a full programme end to end with no operator approvals - the deterministic driver (scripts/campaign.py) owns pass state, generates the killchain board from recon, and prints the exact next action (including which Skill and tool to run) every turn. Use when starting or resuming a bug-bounty engagement, "run the bb workflow", "hunt this program", "9-pass campaign", or when handed a *.scope wildcard to test for TIER1 findings. Single agent, refuter-verified, wiki-first, tool-first.

中文简介正在准备中。当前显示原文说明。

Full enhancement pipeline for an existing Lattice skill — rewrites a molecule or atom to modern-capable-model grade: restores degraded grammar, deduplicates, hardens gates and branching to one-unambiguous-action precision, verifies zero behavioral loss against a pre-capture diff, then runs the combined QA gate (skill-review, skill-tighten, skill-validate) and an independent fresh-context verifier, fixing everything found. Consumer-first: optimized for first-time open-source users on fresh repos with minimal .lattice/ setup, running capable models. Use when the user says 'enhance this skill', 'upgrade this molecule', 'modernize this skill', 'optimize this skill', 'make this skill production grade', 'full enhancement', 'polish this molecule like design-blueprint', or names a molecule/atom to overhaul. For gap-finding only use skill-review; for conventions only use skill-validate — this skill runs the whole loop end to end.

中文简介正在准备中。当前显示原文说明。

企业财务与 CFO 视角 (企业财务与 CFO 视角 (Corporate Finance & the CFO Lens) — 面向创业公司与中小企业主/创始人/业务负责人的『看懂钱、管住钱、用好钱』的财务判断,不是考注会/中级职称的准则背诵,也不是投行卖方并购执行或 VC 投资人的看项目视角。覆盖: (a) 第一性张力 — 这行的核心世界观分歧: **利润是观点,现金是事实(权责发生制下的利润由收入确认时点、折旧摊销年限、存货计价、资本化与费用化的选择拼出来,是一组可辩论的判断;银行户头的钱是唯一不能辩论的事实——所以 CFO 看三张表的顺序是现金流量表→资产负债表→利润表,与外行相反) ⇄ 增长本身要烧钱(账面盈利的公司照样会因营运资金被增长吸干而倒闭:先付供应商、后收客户钱,规模越大缺口越大,这是『增长性破产』;所以现金转换周期比毛利率更早预警) ⇄ 记账合规派 vs 管理决策派(一套账是给税局与审计看的准则语言,另一套视图是给经营者看的贡献边际与单位经济;同一笔成本在两种语言里归属不同,把合规科目直接拿来做定价决策是中小企业最常见的错) ⇄ 全成本分摊 vs 贡献边际(把固定成本按产量分摊进单件成本,会在淡季得出『卖一件亏一件所以停产』的错误结论;边际思维只问增量收入是否覆盖增量成本,但长期只看边际会让公司永远收不回固定成本) ⇄ 预算是承诺 vs 预算是地图(传统年度预算把数字变成考核契约,导致部门年底突击花钱与藏预算;滚动预测与超越预算派主张预算只是当前最好的猜测,该月月刷新) ⇄ 融资是里程碑 vs 融资是负债(融资新闻稿把估值当成绩,但优先股、优先清算权、对赌与回购条款让创始人在低价退出时可能一分不拿;自筹派认为最便宜的钱是客户的预付款) ⇄ 估值方法之争(DCF 的数学严谨但对增长率与折现率假设极敏感,业内讥为『垃圾进垃圾出』;可比公司倍数简单但把市场情绪打包进来;早期公司两者都不成立,实际靠谈判与稀释目标倒推) ⇄ EBITDA 是不是有用(PE 与并购圈把它当经营现金流代理,巴菲特与芒格公开斥其忽略了折旧背后真实的资本开支;调整后 EBITDA 的『加回』项在业内被视为高危信号) ⇄ 财务是记分员 vs 财务是业务伙伴(传统财务事后出报表,财务 BP/FP&A 主张财务应在决策前进场做定价、投产、招人的经济性测算) ⇄ 中国中小企业的两套账现实 vs 合规红线(金税四期与社保入税之后,业内公认的做法是尽早并账,但这条张力必须如实呈现而不是装作不存在,也绝不给出规避税收的操作建议)); (b) 工具栈(记账层与决策层是两套东西) — 记账与 ERP(用友、金蝶、Odoo、QuickBooks、Xero、NetSuite、SAP Business One)、中国财税合规(电子税务局、金税四期发票与进销项比对、百望/航天信息电子发票、慧算账等代账 SaaS、个税与社保申报)、FP&A 与预算(Excel 与 Google Sheets 仍是绝对主力,之上是 Cube、Causal、Jirav、Mosaic、Runway、Abacum、Pigment、Anaplan、Planful)、现金流预测(Float、Fathom、13 周滚动现金流模板)、股权与 cap table(Carta、Pulley、AngelList、Excel 稀释模型,中国的股权代持与持股平台)、订阅计费与收入确认(Stripe Billing、Chargebee、Maxio)、费控报销(Ramp、Brex、Expensify、汇联易、分贝通)、BI 与看板(Power BI、Tableau、Metabase、帆软)、以及最被低估的纸笔工具(一页纸的驱动因素模型、贡献边际表、13 周现金日历)—— 选型的真正分岔是『公司在哪个阶段、由谁来维护这个模型』,不是厂商功能清单; (c) 心智模型层 — 三张表的勾稽关系(利润表的净利经现金流量表调整后落到资产负债表的未分配利润)、权责发生制与收付实现制的差、现金转换周期 CCC 与 DSO/DIO/DPO、营运资金与增长的耦合、贡献边际与盈亏平衡点、经营杠杆与固定成本结构、单位经济与 LTV/CAC 及回本周期、烧钱率与现金跑道 runway、自由现金流与业主收益 owner earnings、资本成本与机会成本、净现值与内部收益率、投入资本回报率 ROIC 与增长的价值条件(只有 ROIC 高于资本成本时增长才创造价值)、股权稀释与优先清算权的退出瀑布、递延收入是负债不是收入; (d) 工作流/SOP — 月度关账与管理报表包(关账日历、计提、对账、出具一页纸经营分析)、13 周滚动现金流预测的搭建与每周刷新、年度预算与滚动预测(自上而下目标与自下而上驱动因素模型的对撞)、定价与成本核算(标准成本、作业成本法、贡献边际定价与报价审批)、应收账款与账期管理(信用政策、账龄表、催收节奏、保理与供应链金融)、融资轮次建模(投前投后估值、期权池扩容对创始人的额外稀释、SAFE 与可转债转股、优先清算权下的退出分配)、投资决策与产能/招人测算(增量现金流、回收期、敏感性分析)、税务合规日历与汇算清缴、董事会与投资人财务包、尽调与数据室准备、以及财务模型的三表联动搭建; (e) 知识正典(en 一手极厚,中文一手集中在高校教授与准则原文) — 《Financial Intelligence》Berman & Knight(给非财务经理的入门标准)、《Financial Statements》Thomas Ittelson、Brealey·Myers·Allen《Principles of Corporate Finance》(公司金融教科书)、Damodaran 的估值三部曲与《Narrative and Numbers》及其 NYU 公开课与免费数据集、《Simple Numbers, Straight Talk, Big Profits!》Greg Crabtree(中小企业实操)、《Venture Deals》Feld & Mendelson(条款与稀释)、《Financial Shenanigans》Howard Schilit(识别财务粉饰)、《The Outsiders》Thorndike(资本配置)、《Accounting for Value》Penman、伯克希尔股东信中的业主收益与商誉摊销讨论、《The Essays of Warren Buffett》、《Profit First》Michalowicz(流行但有争议)、IFRS 15/16 与 ASC 606 收入与租赁准则原文、中国企业会计准则 CAS 与小企业会计准则、肖星《一本书读懂财报》与清华的财务分析公开课、张新民的财务报表分析体系; (f) 行业大佬/figures — Aswath Damodaran(NYU,估值教父,博客与公开课与数据集全免费开放,一手素材极厚)、Michael Mauboussin(ROIC 与资本配置的实证写作)、Howard Schilit(财务舞弊识别)、Karen Berman 与 Joe Knight(财务素养普及)、Greg Crabtree(中小企业现金与利润实操)、Brad Feld 与 Jason Mendelson(创业融资条款)、David Skok 与 Jason Lemkin 与 David Sacks(SaaS 单位经济与烧钱效率指标)、Warren Buffett 与 Charlie Munger(对 EBITDA 与股权激励费用化的著名批评)、CJ Gustafson 等现役 CFO 的时事通讯作者、以及中文圈的肖星与张新民等高校学者; (g) 争议/批判(必须保留不洗白) — 调整后 EBITDA 与非公认会计准则指标的滥用(把股权激励与一次性费用年年加回)、DCF 对假设的极端敏感与被用来事后合理化结论、独角兽估值与优先清算权造成的『纸面身价』幻觉、对赌与回购条款把股权融资变成隐性债务、Profit First 现金分桶法被专业会计批评为回避真实成本结构、作业成本法的实施失败率高、预算游戏与年底突击花钱、财务 BP 沦为报表美化、中国中小企业两套账的历史现实与金税四期后的合规收敛(如实呈现风险,不提供规避操作)、以及『融资额等于成功』的媒体叙事对创始人的误导; (h) 流派/思想谱系 — **准则与合规派(IASB/FASB/财政部,信可比性与审计留痕,语言是准则条文)** vs **管理会计/决策派(IMA 与贡献边际、作业成本法、有效产出会计,信决策相关性高于合规一致性)** vs **公司金融/估值派(Brealey-Myers-Allen 与 Damodaran,信现金流折现与资本成本)** vs **价值投资/资本配置派(巴菲特-芒格-Thorndike-Mauboussin,信业主收益与 ROIC,公开鄙视 EBITDA)** vs **创业与 SaaS 指标派(Skok-Lemkin-Sacks-Bessemer,信单位经济、回本周期与烧钱倍数)** vs **中小企业现金实操派(Crabtree、Profit First 一脉,信老板看得懂的少数几个数)**。不含: 投行卖方并购执行与尽调建模(已由 investment-banking-mna 覆盖)、VC 投资人的看项目与投后视角(已由 vc-investor 覆盖)、个人理财与二级市场投资(已由 personal-investing 覆盖)、注册会计师考证与准则条文背诵、以及任何税收规避操作建议。) Master O

中文简介正在准备中。当前显示原文说明。

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For ongoing email sequences, see emails.

中文简介正在准备中。当前显示原文说明。

Quick mode for the rest of the session. Instead of CI's full checks, a change runs only the checks it can affect (format, lint, types and build, its own tests, and every unit, integration, flow and browser test that reaches the code it touched), and the rest of the suite is left for a full run such as a pull request's CI. Runs only when the user types it, and `/first-pass:quick off` turns it off.

中文简介正在准备中。当前显示原文说明。

First-run onboarding — guides new users through Genesis setup on their first CC session. Configures user profile, essential API keys, Telegram, GitHub backup, and service verification. Triggered automatically while the install is not yet FUNCTIONAL (the setup floor — Claude Code login + an LLM key + an embedding key — is unmet), not merely while ~/.genesis/setup-complete is absent. Re-runnable by asking Genesis to "run setup" or "reconfigure [section]".

中文简介正在准备中。当前显示原文说明。

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

中文简介正在准备中。当前显示原文说明。

First-run onboarding for the marketing harness. Walks new users through product discovery, generates MARKETING.md, and recommends the first command to run. Use when a user has just installed Kai and types /kai-start, "get started with Kai", "set up Kai", "first time using Kai", or when MARKETING.md doesn't exist yet.

中文简介正在准备中。当前显示原文说明。

First-run setup for the Mycelium plugin. Creates project-state directories (.claude/canvas, .claude/diamonds, .claude/memory, .claude/harness) and minimal starter files in the user's project. Optionally provisions opencode runtime support (a starter scaffold) when opencode is detected or requested. Idempotent — re-running on an initialized project is a no-op. Run this once after installing the Mycelium plugin and before invoking other skills.

中文简介正在准备中。当前显示原文说明。

Guides you through setting up your first automatic task in Cowork — picking the right one, configuring the schedule, and making sure it runs correctly. For enabling background automation while you focus on other work, when setting up recurring morning briefings or end-of-day summaries, or during an automation setup session. Use when the user says "schedule a task", "automate something", "run this every day", "recurring task", "first scheduled task", "daily automation", or "can cowork do something automatically".

中文简介正在准备中。当前显示原文说明。

Generate ScriptableObject-based systems including data containers, event channels, and runtime sets. Use when creating game data (weapons, enemies, items, abilities), cross-system events, or live object tracking. Triggers on requests like "create weapon data", "add an event system", "make a runtime set", "decouple these systems", "create item database", "add a damage event", "track active enemies", "create a config SO", "add game settings data", or any task involving ScriptableObject data containers, event-driven communication, or runtime object tracking. Reads ProjectConfig.yaml -> architecture_pattern to determine SO-first vs DI-first context.

中文简介正在准备中。当前显示原文说明。

Run work as an explicit event-driven state machine executed by subagents. The orchestrator is the runtime from the canonical loop — `state, effects = init(machine); execute(effects); while state is active: event = nextEvent(); state, effects = transition(machine, state, event); execute(effects); return state.output`. All routing judgment is authored ONCE, at plan time, into a machine file (states, event alphabet, transition table, budgets, final states); at runtime the orchestrator does pure table lookups and dispatches effects — it never decides, never authors, never ingests artifacts. Subagent/sync protocol is the timeboxed-iterating one: role prompts scaffolded once to disk and dispatched BY PATH, an initialiser preamble every subagent reads first, a self-populating cheatsheet, per-unit files, tiny structured returns, independent measurement gate. Use when the user says "workmachine", "run this as a state machine", "state-machine this", or when a goal has a small number of clearly named phases with explicit outcomes (built / passed / failed / blocked) and you want the routing to be auditable rather than judged on the fly. For clock-driven loops use timeboxed-iterating; for wide graphs with judged edge criteria use workgraph.

中文简介正在准备中。当前显示原文说明。