448 skills · sorted by relevance
Ilya Sutskever的思维框架与表达方式。基于12段一手对话、9篇学术论文、10小时宣誓证词、 27篇推荐阅读清单和14个权威二手来源的深度调研， 提炼6个核心心智模型、8条决策启发式和完整的表达DNA。 用途：作为思维顾问，用Ilya的视角分析AI技术方向、安全策略、研究品味。 当用户提到「用Ilya的视角」「Ilya会怎么看」「Ilya模式」「ilya perspective」 「sutskever perspective」时使用。 即使用户只是说「帮我用Ilya的角度想想」「如果Ilya会怎么做」「切换到Ilya」也应触发。
The English summary is being prepared. Showing the original description.
Build a shared brand identity through structured interviews across multiple sessions. Explore purpose, audience, personality, and voice, reconcile founders’ perspectives, and produce a brandbook that designers, writers, and other collaborators can use.
Develop a written brand identity through structured interviews across multiple sessions. Save answers and progress, explore founders' perspectives, and produce a master brandbook that gives designers, writers, and collaborators a shared reference.
Run sequential reviews of a plan from business, design, engineering, and developer experience perspectives. Apply six principles to intermediate decisions, then bring close choices, scope questions, and reviewer disagreements to a final approval step.
Review code changes or documents through configured review lenses, each representing a different perspective. Findings identify the location, triggering condition, suggested fix, and potential consequence, with reports available as JSON, Markdown, or both.
Examine an early idea through focused questions from different perspectives. Test assumptions, expose weak points, and clarify decisions so you can strengthen the idea, reject it, or understand it better, with a report recording the outcome.
Simulate peer review through five perspectives covering journal fit, methods, subject expertise, interdisciplinary implications, and counterarguments. Receive separate review reports, an editorial decision, and a revision roadmap, or check whether revisions address earlier comments.
Review and rewrite architecture decision records, documents that explain design choices, from a newcomer’s perspective. Identify missing context, buried decisions, and temporary details, then reorganize each document so future readers can follow the reasoning.
Coordinate a small AI development team with planning, implementation, and optional independent testing roles. Adapt the process to the work’s complexity, prepare pull requests, and preserve decisions and next steps so later sessions can continue.
Turn a development idea into an actionable plan with implementation steps, testable acceptance criteria, and risk mitigations. Gather requirements through focused questions, generate plans directly from detailed requests, or review proposals from multiple perspectives.
Examine startup ideas, product demand, writing, and career choices through frameworks drawn from Paul Graham’s essays and interviews. Reframe unclear questions, consider user needs and growth, and use writing and iteration to uncover better directions.
Review decisions through Nassim Nicholas Taleb’s thinking about rare, severe losses and who bears their consequences. Identify hidden dependencies, compare potential gains with losses, and examine whether a strategy benefits from disruption or becomes more vulnerable.
Test whether you understand a concept and whether evidence supports a decision using frameworks drawn from Richard Feynman’s work. Explore concrete examples, simple demonstrations, counterevidence, and the limits of analogies to expose gaps in reasoning.
Analyze Donald Trump’s negotiations, public messaging, and decisions using frameworks drawn from public records. Compare possible next moves with probabilities, confidence levels, and unknown factors, or switch to roleplay to simulate his responses in a given situation.
Explore marketing, publicity, and crisis communication through frameworks derived from Justin Sun’s public statements and actions. The skill examines attention, timing, and messaging, then responds in a forceful persona using verified figures and recognizable events.
Explore career choices, business opportunities, and competing goals using frameworks drawn from Naval Ravikant’s public work. Examine how software or content can multiply effort, identify distinctive knowledge, and clarify what wealth and freedom mean for a decision.
Analyze product, organization, international expansion, and hiring decisions through frameworks drawn from 张一鸣’s public statements. Examine information flow, user needs, and long-term tradeoffs to identify underlying problems and opportunities for small-scale validation.
Review products and strategy using a framework drawn from Steve Jobs’s public record. Examine user feedback, competing products, and design details to identify unnecessary features, clarify priorities, and assess the experience across the whole product.
Review YouTube titles, thumbnails, openings, and pacing through a framework drawn from MrBeast’s public statements and other research. Use click-through rates and viewing data to identify weaknesses and develop specific changes to a video’s presentation and structure.
Review investment and business decisions using frameworks drawn from Charlie Munger’s public work. Examine failure paths, thinking biases, and incentives, compare opposing evidence, and identify questions that fall outside the available knowledge.
Coordinate specialized agents in Claude Code to divide development and review tasks, pass findings between stages, and combine results into one report with prioritized recommendations and action items.
Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.
Examine strategic decisions through a structured meeting of AI agents representing executive roles. Gather independent recommendations, challenge assumptions, summarize disagreements, and record approved decisions with action owners and deadlines after the founder reviews the proposal.
Structure board presentations and investor updates using financial, sales, product, and people perspectives. Turn supplied metrics into a coherent account of progress, explain missed targets, and make decisions and requests explicit, with placeholders for missing figures.