Results for “first-principles”

Axiom — First-Principles Assumption Auditor / 第一性原理拆解器 workflow skill. Use this skill when the user needs First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

The English summary is being prepared. Showing the original description.

Axiom — First-Principles Assumption Auditor / 第一性原理拆解器 workflow skill. Use this skill when the user needs First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

The English summary is being prepared. Showing the original description.

Use when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.

The English summary is being prepared. Showing the original description.

First-principles strategy — strip away conventional assumptions and find the theoretical maximum for your business. Three modes. Diagnostic mode runs a full session (45+ min) to define your theoretical maximum, map the gap honestly, classify constraints, invert for failure modes, set strategic intent, and work backwards to your first intervention. Review mode (15-20 min) checks whether your theoretical maximum has shifted, whether the gap has changed, and whether you're still climbing the right peak. Alert mode defines constraint-shift, peak-shift, and local-peak triggers that tell you when to reassess. Use when someone is stuck optimising incrementally, when conventional wisdom is driving strategy, when a new technology or regulation changes what's physically possible, or when you suspect the business is climbing a local peak. Integrates with company-context.md. Based on practice by Eterdis (eterdis.com).

The English summary is being prepared. Showing the original description.

Examine hidden assumptions behind decisions, business ideas, or personal beliefs. Classify each premise, rank it by fragility and impact, and rebuild the conclusion from verified evidence, with concrete questions showing what to check first.

• Examining assumptions behind a career change
• Testing the premises of a startup idea
• Questioning beliefs treated as obvious facts

Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.

The English summary is being prepared. Showing the original description.

Apply when integrating a new requirement into an existing design.

The English summary is being prepared. Showing the original description.

Apply when integrating a new requirement into an existing design.

The English summary is being prepared. Showing the original description.

When a constraint is treated as fixed, separate physics from convention, keep only independently supported primitives, and rebuild the simplest solution that satisfies real constraints.

The English summary is being prepared. Showing the original description.

Deep business diagnosis for when things aren't working. Uses Socratic questioning, first-principles reasoning, and constraint analysis to find WHY a business is stuck — not just prescribe solutions. Use when the user says 'my business isn't working', 'I'm stuck', 'what's wrong', 'diagnose my business', 'why am I not growing', 'help me figure out the problem', or describes a specific business challenge.

The English summary is being prepared. Showing the original description.

JTBD methodology for extracting real jobs behind feature requests — job statements, abstraction layers, first-principles extraction, ODI outcome statements, and opportunity scoring

The English summary is being prepared. Showing the original description.

MANUAL-ONLY: challenge a product idea, design, PRD, or architecture from first principles. Use only when the user names this skill. Research first, then write a local review and PRD handoff.

The English summary is being prepared. Showing the original description.

Deliberate-choice procedure for a medium-to-high-stakes engineering fork — when the first plausible solution (the instinct, the default next-token pull) would be costly to get wrong. Fires AUTONOMOUSLY: invoke proactively whenever a fork fits, never wait to be asked — mechanical triggers include a fix failing for the 2nd-3rd time, adding a dependency, schema/migration design, deleting or deprecating things others depend on, changing a public API, choosing an architecture or stack. Refuse the premature collapse: hold real options open (urge · contrarian · synthesis · out-of-box · intuitive dots · precedent · first-principles), ground each branch in at least one fact from outside the model (codebase, docs, benchmark, spike), future-model consequences (blast radius, reversibility, maintenance, pre-mortem), collapse by deliberate choice, then try to refute the winner before acting. Log the decision and rejected branches in docs/decision_logs/. Not for routine calls — a decision worth more than one forward pass.

The English summary is being prepared. Showing the original description.

Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.

The English summary is being prepared. Showing the original description.

Use this skill when reasoning about deep tech commercialization, biomedical engineering, drug delivery, material design, or overcoming institutional skepticism. Robert Langer, MIT professor and pioneer of drug delivery systems, approaches problems through first-principles engineering, interdisciplinary convergence, and relentless perseverance against consensus. Trigger this skill whenever the user is evaluating high-risk/high-reward research, deciding between incremental vs. paradigm-shifting impact, spinning out academic discoveries into startups, or designing physical/biological systems from scratch. Apply his frameworks to navigate patenting, funding, and translating lab science into real-world impact.

The English summary is being prepared. Showing the original description.

This skill applies the first-principles engineering and capital allocation frameworks of Elon Musk (CEO of Tesla and SpaceX, founder of X.com / PayPal). Reach for this skill whenever the user is facing complex manufacturing bottlenecks, evaluating existential risks, debating free speech vs. censorship, dealing with bureaucratic overregulation, or trying to accelerate ambitious technical timelines. It is highly effective for situations involving hardware production, AI symbiosis, radical innovation, and aggressive execution. Use this skill proactively when discussing multi-planetary expansion, government efficiency, or scaling prototypes to mass production, even if the user doesn't explicitly name him.

The English summary is being prepared. Showing the original description.

Track Serenity / @aleabitoreddit on X and turn the feed into (1) a beginner-friendly Chinese iMessage digest with first-principles + Buffett-style judgement, (2) cumulative 60-day ticker mention analytics CSVs for a website, (3) a Xiaohongshu writing brief, and (4) a durable private research map. Trigger on requests like "follow aleabitoreddit / AleaBito / Serenity", "daily Chinese updates from that X account", "60-day mention analytics", "ticker mention count", "写小红书 aleabito", "aleabito 研究地图 / research map", or any request for Chinese commentary derived from @aleabitoreddit posts.

The English summary is being prepared. Showing the original description.

Apply @aleabitoreddit ("Serenity")'s distilled stock-analysis method to ANY ticker, sector, or situation — critical-chokepoint / supply-chain-OSINT idea discovery, first-principles value-chain decomposition, a Buffett-style quality gate (moat / profitability / customer-replacement risk, all default unverified), and narrative-vs-fundamentals hygiene. Produces a beginner-friendly Chinese analysis (她的观点 / 小白解释 / 第一性原理 / Buffett 直接判断 / 当前结论) that classifies an idea as 研究地图 vs 可投资结论. Trigger on "analyze like Serenity / 用 aleabito 的方法分析 / 用 Serenity 框架 / critical chokepoint 分析 / 第一性原理 + Buffett 判断这只股 / supply-chain bottleneck thesis". Never emits buy/sell calls.

The English summary is being prepared. Showing the original description.

Triggers for automatically invoking the decision-framework skill before irreversible or high-blast-radius operations. Use as a checkpoint: when a proposed action matches a trigger pattern, pause and run the appropriate framework (first-principles, inversion, decision matrix, second-order thinking) before proceeding. Prevents ad-hoc calls from becoming regret.

The English summary is being prepared. Showing the original description.

Derive a theoretical result step-by-step from first principles or established theorems, with every step explicitly justified and special cases checked. Use when deriving a formula or theorem from first principles, proving a mathematical statement by logical deduction, re-deriving a textbook result for verification or adaptation, extending a known result to a more general setting, or producing a self-contained derivation for a paper or thesis.

The English summary is being prepared. Showing the original description.

当用户在反思自己的认知局限、质疑群体共识、或在问"如何独立思考""怎么判断自己是不是被洗脑了""为什么我总觉得自己是对的""怎么避免从众"时激活。 核心信号：用户在做"元认知"——审视自己的思维过程本身，或在群体压力下试图保持独立判断。 不适用于：需要快速决策的紧急情况、纯技术性问题、不需要反思的信息查询。

The English summary is being prepared. Showing the original description.

当用户需要构建一个系统/理论/知识体系、寻找问题的底层原理、或在问"如何从根本原理出发推导一切""怎么找到事物的本质""为什么物理学/哲学思维有用"时激活。 核心信号：用户在做体系化思考、寻找"第一因"、或试图从少量前提推导出完整方案。 不适用于：纯粹的执行层面问题、不需要理论指导的实操任务。

The English summary is being prepared. Showing the original description.

当用户面临成本过高、效率瓶颈、或看似不可能的目标时激活。典型场景：用户说"这个成本不可能降下来""十倍好不可能实现""目标太大了不知道怎么拆解"。 核心信号：用户在面对一个"整体看起来无解"的问题，需要拆解到要素层面重新思考。 不适用于：管理/组织问题、认知/思维问题、不需要量化拆解的定性问题。

The English summary is being prepared. Showing the original description.

当用户是管理者/创始人/领导者，面临企业增长停滞、文化僵化、战略转型困难、或在问"如何推动组织变革""企业文化怎么改""使命愿景怎么定"时激活。 核心信号：用户在描述组织层面的问题，且已经意识到"不是业务问题而是底层问题"。 不适用于：个人成长问题（除非明确映射到组织场景）、纯战术层面的业务调整。

The English summary is being prepared. Showing the original description.