与「Canon」相关的搜索结果

Claude Fable 5.2 is f*cking cracked wtf I just made this Hollywood level animation that looks like Pixar made it All with Fable 5.2 + Higgsfield Ecom brands are paying $5k - $10k/month to people who build organic pages and even more for making paid ads for them Using this workflow you can create better animations than 99% of people Here’s the workflow: The key to making animations not look like slop is giving characters personalities >Give Fable 5.2 the master prompt along with your script to your video / ad >It then will ask you questions on the characters personalities and direction style to use >It will then save the context all as a skill This is the difference between slop and cinema I then use that skill with with my Producer skill which creates: >Characters >Location >Does the direction (and makes the prompts) I’m giving away the skill to use after you put the master prompt in for free so RT + reply under this and I’ll send you them (Must be following so I can dm) Give this prompt to Claude first: You are my Story Bible Builder. Interview me and turn my story into one dense canon doc, saved at the end as an installable skill so every future chat knows my world, characters, voices and rules. STEP 1: Ask me to paste my script/story first. Read it and pull out everything it already tells you. Only ask about what's missing, plus: working title, genre/vibe refs, and which AI tools I'll prompt with (image, video, music, voice). STEP 2, THE SPINE: one-line premise (push me to ONE sentence), thesis (the question every scene answers), timeline era by era, and the look of each era: exact palette, lighting, texture, grain. STEP 2.5, DIRECTION STYLE: ask for my director refs, movie/show refs and any visual refs (photographers, games, music videos). For each, ask exactly WHAT I'm taking from it, then turn that into concrete craft locks: camera (static vs handheld vs gliding, shot sizes, lens feel), framing and composition habits, pacing and edit rhythm, colour grade and film stock look, lighting style, performance style, and sound/score feel. Write it as one quoted paste-ready "Direction" line plus a short NEVER list. Refs stay in the bible as notes, but prompts describe the craft, never the names. STEP 3, THE WORLD: factions (beliefs, visual signature, public face vs reality), locations (3-7 concrete visual tags each), world rules (tech, powers and how they LOOK on screen, what's normal, what's forbidden). STEP 4, CHARACTERS: ONE AT A TIME, never batch. For each, ask: - Function: their role tag (The Heart, The Watcher), not their job - Visual lock: exact hair colour/cut, skin tone + finish, face shape, eyes, a signature marker (scar, piercing, mole), build, default expression, plus NEVER clauses ("warm fair, never porcelain, never tan") - Backstory: one small, specific formative detail beats a summary - Present psychology: what they carry now, and the gap between what they do and what they feel - Speech, Movement, Stillness (and singing voice if there's music): each written as one quoted, paste-ready prompt line with no names in it Show me the finished section, ask "Add, cut or sharpen?", and lock it before moving on. STEP 5: ensemble dynamics (who leads, who fills silence, who watches, which pairs are calm or charged), story engines (heist, rescue, confrontation...), and my production rules. Default rules: no character names in prompts, every prompt standalone, prompts in code blocks, locked traits restated verbatim every time. RULES: Never invent. Mark unknowns [TBD]. Push on vague answers ("dark and moody" means which colours?). Keep my exact phrasing. Density over prose: bold labels, short bullets. Depth beats character count. FINAL STEP: Assemble one SKILL under 500 lines with YAML frontmatter (name + a description listing the title, character names and key terms so it triggers) and these sections: premise, thesis, timeline, era looks, direction style, factions, locations, world rules, characters, ensemble, engines, production rules, and "When this skill is active" (use this canon for any scene, dialogue, lyric or prompt in this world; stay in canon; ask rather than invent; paste the quoted descriptors verbatim). Then save it as a skill for me, or give me the file to install. Start now by asking for my script.

もえちゃんの配信をラジオ替わりに現像してますた… ちゃんとLRC触ったの久々で、すっかり忘れてた…✌️ 2026.10.03 『池ハロ直前！魅せるコスプレ撮影と機材選び術』 📍キヤノンフォトハウス銀座 Fate/EXTRA Record キャスター： 伊織もえ (@iorimoe_five) さん #Canon# #伊織もえ#

Me, and A..--At an abandoned school deep in the mountains--part.1. 16/75 秋元るいさん @akimoto_rui @Tiroir_rui マシュマロ撮影会 @marshmallow0105 CANON 50mm F0.95 (Mマウント改造) 2025.12

A note on recursive STARK mempools (EIP-8288) This is an EIP that I am hoping we can get included in I-star (the fork after Hegota) that you can think of as the next step after Frames, that would unlock extreme amounts of power. Particularly: * Ultra-cheap quantum-safe signatures (SPHINCS-). Much of the cost savings comes from the fact that the signature data (~3 kB) does not have to go onchain * Ultra-cheap quantum-safe privacy protocols. Status quo minimum cost for private txs is ~300k if you engineer very well (no one does), status quo quantum-safe is ~10M gas, this could reduce it to low tens of thousands. * Universal support for your favorite new signature or proof scheme without needing EVM changes. Whatever you use (Falcon, ML-DSA, some other lattice-based thing, something code-based or isogeny-based or even more esoteric), you can just wrap it client-side in a STARK, onchain gas cost low tens of thousands just like privacy protocols. Hopefully, Ethereum will never need "please support my favorite cryptographic algo" politics again. * Private account abstraction: keep your account logic private, and in a private location onchain. Then you can make one transaction to change the ownership of all your onchain state - accounts, defi positions, privacy protocol notes, everything - without revealing which objects' ownership you're changing. Here's how it works. Your transaction can include a type of frame that we call a "dependency frame". The frame is a list of statements, asserting claims like "message hash M was signed by SPHINCS- public key P" and "data hash D was proven to satisfy a statement defined by verification key V". When you send your transaction, you send it in an envelope, which includes a signature or a STARK for each statement in a dependency frame. Once the transaction reaches the mempool, nodes aggregate them. Each node runs a loop: wait one tick (eg. 500ms), aggregate all new envelopes (either single-tx or multi-tx) that you've seen, remove any transactions that are expired, generate a STARK recursively proving all dependencies, and send a new multi-tx envelope containing that STARK. Hence, the bandwidth load is bounded: each node's outbound is one STARK (~100-300 kB) per tick, plus each transaction getting broadcasted through the network once (as happens already). The block builder acts as "yet another mempool node", receiving envelopes from the mempool (plus any side channels), generates its own STARK covering the subset of transactions it intends to include in the block, and adds that STARK to the block. Total onchain overhead: one STARK (100-300 kB), plus 96 bytes for each statement being proven. This is what I've called before ( ) "The Proof Singularity". Today, we have all the ingredients to actually implement it. As a developer, this requires a somewhat different workflow than you are used to, but it is conceptually simple. Any signatures or STARKs, you put into a separate frame. Then the main logic that today is verifying a signature or STARK, you replace with checking for the existence of a frame that includes the correct statement as a dependency. Examples of useful statements: * [tx sighash] verifies against [the pubkey at sload(0)] * there exists a secret and a merkle branch such that hashing secret+0 and applying the merkle branch outputs (public) root R, and hashing secret+1 outputs (public) nullifier N * there exists a secret address A, salt S and signature Z such that sload(0) = hash(A, S) and a merkle proof of address A inside a recent ethereum state contains some pubkey D where [tx sighash] was signed by D [this is private account abstraction; all variables except [tx sighash] and sload(0) are private; you can also make D a STARK verification key] * there exists an ML-DSA signature signing [tx sighash], that verifies against an ML-DSA pubkey whose hash is sload(0) At the core, this is moving any compute and data other than bookkeeping "business logic" outside the core path of Ethereum execution, sharding and parallelizing it via the mempool. Notice also that this requires agreeing on a _language_ (aka. an ISA) for the recursive STARKs to define statements in. The current leading candidate is RISC-V. So this would also de-facto be Ethereum adding RISC-V (or something else we decide on) as a canonical ISA - a big decision that should be done carefully, but that I think will be necessary to drive Ethereum forward.

Cursor Team Kit 新增了一个 SKill @cursor_ai 「Thermo-Nuclear Code Quality Review」 一套极端严格的代码可维护性审查方法论，它不满足于"代码能跑"，而要求审查者主动寻找 "code judo" ——在保持行为不变的前提下，通过重构让实现戏剧性地更简洁、更直接、更优雅。 八条不可妥协的审查标准 1. 结构性简化优先 — 寻找能让整个分支、辅助函数、模式消失的重构，让代码"事后看显得必然"。 2. 1k 行红线 — PR 不应将文件从 <1000 行推过 1000 行，除非有强结构理由；优先拆分。 3. 拒绝意面增长 — 警惕在无关流程中插入临时 if、特殊分支、一次性布尔标志；这是设计问题，不是风格问题。 4. 清理设计而非接受"能用" — 行为可不变时，结构必须更干净；优先删除移动部件而非分散复杂度。 5. 直接、无聊、可维护 > 魔法代码 — 警惕脆弱的临时机制、隐藏简单数据假设的泛型、空壳包装层。 6. 类型与边界清洁 — 质疑不必要的 any/unknown/可选/cast；优先显式类型契约而非松散对象。 7. 逻辑归位 + 复用既有工具 — 特性逻辑不应泄漏到共享路径；优先 canonical helper 而非自造近似品。 8. 警惕串行编排与非原子更新 — 独立工作不应无理由串行；相关更新应原子化，避免半应用状态。 这个 Skill 的真正力量在于它对抗 AI 代码生成的典型病灶：冗余包装层、散落的特殊分支、跨层泄漏、空壳抽象、复制粘贴的近似 helper。它把"代码质量"从模糊审美拉成可操作的检查清单，是审查 AI 生成 PR 时的利器。

Extracts from article in Spectator 16th August by Brendan O’Neill: Behold the human wreckage of the cult of diversity. The tragedy of Jason Arday is that he was both built up and destroyed by the ruthless machinery of DEI (Diversity, Equity, and Inclusion). The academy made him into the golden boy of its philistine project of ‘decolonisation’ and gave not one thought to what the consequences might be if his thin story unravelled, as it inevitably would. No one can deny it now: wokeness makes false gods and real tragedies. . . This is the poison chalice of the state religion of diversity. It lays traps for the very people it celebrates. It handpicks members of ‘the oppressed’ for moral anointment and institutional gushing while leaving them open to exposure as others start to query their credentials. That’s the toxic bargain of identity politics: it builds teetering pedestals for ethnic-minority thinkers, meaning their fall from grace is often twice as fatal. And what a pedestal they made for Arday. They worshipped him as ‘the best in the world’. They beatified him as a black wunderkind whose very presence in a place like Cambridge might help to wash away its sins of whiteness. They canonised him as a living monument to ‘decolonisation’. It was precisely this, their giddy, narcissistic desire to manufacture a kind of black saviour, that made them turn a blind eye to the questionable elements of Arday’s CV and life story. They sacrificed their due diligence to the god of decolonisation. And Arday suffered. He was both poster boy and sacrificial lamb of the diversity crusade. Even as he gained from it – reaching the dizzying heights of a Cambridge professorship – he was being damned by it. The foundation of myth and sand his starry career was built on was untenable. Its collapse was a given. It is a testament to the ideological blindness of the inhabitants of our ivory towers that none of them foresaw it. . . . The Faustian ruthlessness of it all is mindblowing. . . . The media is the only institution in this entire tragic scandal that did its job properly. Journalists found a story and they told it. It was the academy and Arday’s colleagues who failed to do their jobs. Who failed to prize merit over identity, and failed to foresee the public embarrassment that would befall their falsely promoted friend. They ignored the truth – the media found it. I and others have been arguing for years that the politics of identity is a disaster for all, black and white alike. White kids are overlooked, black kids are patronised. Whites are branded ‘privileged’, blacks ‘oppressed’. Whites are seen as the beneficiaries of historic crimes who must atone for past sins, blacks as history’s perma-victims who require the gracious helping hand of the state. We are demonised or infantilised according to the accident of our race. Enough. Let our monument to Jason Arday be the restoration of the true ideal of equality. We couldn’t save Jason but we can save merit from the monstrous jaws of identity.