合同会社アイデアル

Spark 2.0 is here! 🚀 We’re redefining what’s possible on the web with a streamable LoD system for 3D Gaussian Splatting. Built on Three.js, you can now stream massive 100M+ splat worlds to any device from mobile to VR using WebGL2. All open-source. Dive into the tech 👇

Seedance V2 This used to take people month of study and practice on Adobe Flash, now it can be done with Seedance V2, not perfect but this is the worst it will be. 15 seconds, stylized 2D hand-drawn animation, overhead battlefield on aged yellow lined notebook paper, clear blue horizontal ruled lines and a red left margin line always visible, fine paper grain, pencil marks, ink strokes, minimal classroom-material aesthetic at the start. The entire video must preserve the same paper world from start to finish. No live action, no 3D rendering, no realistic human faces, no modern objects, no narration, no subtitles. Core concept: A childish classroom doodle of an ancient war gradually transforms into a legendary illustrated battlefield, then collapses back into scribbles after the climax. The escalation must feel smooth, intentional, and visually magical, as if imagination is taking over the page. Army design: Two opposing ancient armies drawn first as simple colored stick figures, one faction in red, one faction in blue. Dense infantry blocks with spears and swords, cavalry units with long lances, banner carriers, archers. At first they are crude doodles with simple line limbs and circular heads. As the battle intensifies, they evolve step by step into more detailed inked warriors with clearer armor silhouettes, horses, weapons, helmets, capes, and expressive movement, but still remain inside a hand-drawn 2D illustrated style on paper. Visual progression and timing: 0-3 seconds: Wide top-down view of a large notebook-paper battlefield. Rough stick-figure armies face each other across the page. The drawing feels playful and simple at first. The camera slowly glides forward over the paper as both sides begin charging. Tiny horses gallop, infantry rushes, arrows are sketched into existence and start falling. Everything still looks like rough schoolbook doodles. 3-7 seconds: The first major collision. Spears thrust, swords swing, cavalry crashes into cavalry, formations break apart. With each impact, the art style upgrades. Simple stick limbs become stronger ink lines, bodies gain armor shapes, horses gain muscular form, banners gain flowing detail, shadows and dust marks appear. The battlefield becomes denser, faster, more dramatic. Red and blue strokes smear across the page with the force of combat. 7-11 seconds: The battle reaches full transformation. The once-crude doodles are now a glorious hand-illustrated ancient war scene, still clearly drawn on notebook paper but far more detailed and cinematic. The camera pushes into a central duel between two opposing generals on horseback. Their weapons clash with a powerful burst of ink lines and paper tremor. Around them, infantry and cavalry continue fighting in layered motion, arrows rain down, fallen soldiers scatter across the ruled lines. 11-15 seconds: At the peak of the duel, one final strike lands. A shockwave ripples through the page. The detailed warriors, horses, banners, and battle effects suddenly break apart into loose pencil scribbles, sketch fragments, and drifting paper-line debris. The great war rapidly collapses back into childish rough doodles, then into scattered marks and unfinished lines, as if the imagination has burned out. End on the overhead notebook page with the battlefield reduced to messy hand-drawn remnants. Animation and motion: Smooth fluid motion, strong timing, readable silhouettes, at least 24fps feel. The escalation from crude doodle to epic illustrated warfare must be gradual and continuous, not abrupt. Impacts should feel sharp and rhythmic. Keep all action legible from overhead. Maintain strong contrast between the innocent notebook-paper setting and the seriousness of the war. Atmosphere: Starts playful and curious, grows intense and heroic, peaks as a mythic battlefield, then ends with a strange quiet after the collapse. The whole piece should feel like a child’s imagination turning into an epic war vision on paper.

Introducing Fire-PDF, our new Rust-based parsing engine 🔥 - Convert PDFs into markdown 5x faster - Extract full tables and preserve formulas - Zero config required

seedance2.0を使って 自分で躍った動画をiphoneで撮って（左） キャラクターイラストに踊らせた（中・右） 入力画像は最後にあるが、必ずしもパースやポーズが動画と一致してなくても躍ってくれる 結構感動がある　楽しすぎる プロポーズ/なとり　踊ってみた

💫Anime intro created in 1hr with Seedance 2 Full explanation of how I did this in the comments below. If this interests you please consider engaging 💙

GAVE MY INSTAGRAM TO CLAUDE. What followed? 30.1M views in 10 days. No face cam. No trends. No posting daily. Just copy + artificial intelligence. These 7 prompts took my content from invisible to unavoidable:

GPT-5.4 Thinkingに 「ロボットアニメの主人公が乗る最先端のデザインを設計して」 という一言を伝えて数回壁打ちしてから、GPT-Image-2 で生成させてみた ヤバすぎんだろこのクオリティ

So this is a highly curated collection of 400+ DESIGN.md that’s editable and promptable. Just one click to change styles, turn into branding, mobile versions, slide decks and site sections like hero, testimonials & footers. It’s a superpower for creating landing pages & presentations.

[excitedly] I've been having fun with Gemini 3.1 Flash TTS, the audio tags are really flexible, you can do so much with them. [like dracula] I can't believe things like that just work.

A single 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 file just hit 15K GitHub stars. (derived from Karpathy's coding rules) Andrej Karpathy observed that LLMs make the same predictable mistakes when writing code: over-engineering, ignoring existing patterns, and adding dependencies you never asked for. If you've used AI coding assistants, you've hit all of these. But here's the thing: If the mistakes are predictable, you can prevent them with the right instructions. That's exactly what this 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 does. You drop one markdown file into your repo, and it gives Claude Code a structured set of behavioral guidelines for your entire project. This is a big deal. - Built entirely around prompt engineering for AI coding assistants - No framework, no complex tooling, just one .md file that shapes behavior Developers are moving past "use AI to write code" and into "engineer the AI's behavior so the code is actually good." The Claude Code ecosystem is growing fast, and the best tools in it aren't always software. Sometimes they're just well-crafted instructions. 100% open-source. I've shared a link to the GitHub repo in the next tweet!