Loading video...

Video Failed to Load

Go Home

Never underestimate colored lineart ✒️🎨 Make your coloring process faster with this auto action asset! 🔗 Download here: How to use: 1️⃣ Download & load the asset in Clip Studio Paint 2️⃣ Merge your coloring layers into one 3️⃣ Select the coloring layer & run the auto action 4️⃣...

26,203 views • 10 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

THIS GUY JUST REBUILT A $35,000 ANIMATED SITE FOR $12. IF YOU RUN A WEB STUDIO, YOU SHOULD PROBABLY KEEP SCROLLING. Every agency billing $100-149/hr is selling you five departments wearing one invoice. Here’s each one - collapsed into a single agentic session. LAYER 1 - THE CONCEPT ROOM (Claude) Reads the brief, pulls references, and scripts the scroll: what the visitor feels at second 3, second 15, second 40. → Used to be a strategist and a wall of mood boards. Now it’s a conversation. LAYER 2 - THE MOTION STUDIO (Higgsfield) Cinematic clips from 30+ generative models - hero shots, transitions, ambient loops - all matched to the story from Layer 1. → Used to be a motion artist on retainer. Now it’s a prompt. LAYER 3 - THE DEV TEAM (Claude Code) Scaffolds the site, writes the GSAP ScrollTrigger timelines and Lenis smooth-scroll, extracts frames, optimizes every asset. → A full scroll-driven build with zero hand-coded keyframes. LAYER 4 - THE DESIGN DEPT (baked-in cinematic layer) Six effects, zero config: film grain, particles, vignette, glass cards, color tints, scroll pacing. → The polish that justified the invoice - now it ships by default. LAYER 5 - THE QA PASS (Claude) Checks load speed, mobile breakpoints, and whether the scroll actually lands - then rewrites whatever doesn’t. → Used to be a client call and a revision cycle. Now it’s one more turn in the same session. Five departments. One operator. One pass. A strategist, a motion artist, a developer, a designer, and a QA lead - weeks of handoffs - now run in a single session. For a Claude subscription and a few dollars of Higgsfield credits. The studio was never selling talent. It was selling overhead. And the overhead just became five layers. Follow me, reply “website” to this post and I will send you the step-by-step Playbook 👇

ZEUS⚡️

134,166 views • 12 days ago

HOW TO DODGE EVERY SKILLSHOT IN LEAGUE OF LEGENDS SO YOU GET ACCUSED OF SCRIPTING - Script in your mind - Draw out how far, wide, fast an ability is relative to your character thats all the easy stuff that I have been preaching already you can find in my free discord for improvement however one thing that League coaches fail to explain is the human aspect of it every game you play in League of Legends, every single person in the game is constantly building their profile in a game on how they operate both sides are constantly trying to mind f*ck each other to land and dodge skillshots. I have broken it down into layers the three layers to dodging are layer 0 - no dodge (unconscious) layer 1 - dodge (conscious) layer 2 - no dodge (conscious) Notice how in the clip in a challenger game below Olaf shoots a layer 0 skillshot, but because I am playing at a layer 1, I dodge his axe. Now the Thresh hook gets a little deeper bare with me, because I built the profile that I will dodge an ability in that moment, he thinks that I won't dodge and is shooting a hook at a layer 2 thinking that I will dodge at a layer 2 also. However I know that he knows I will likely not juke and walk straight so I make the conscious choice to dodge AGAIN playing at a layer 1 resulting in me dodging the hook, of course he could be accounting for my tumble but the point still stands. There are many deeper things to consider like zoning abilities, environment etc but you generally want to always play at a layer 1 until you gain more data in a game to adapt. However one thing that always stays true throughout my 13 years of playing League is in teamfights that have gone on for awhile, human beings tend to panic and default to layer 0 of shooting abilities, so if your able to operate at layer 1 as a teamfight progresses, you will likely dodge that one final skillshot that wins you the game. study the saskio way

Tony Chau

185,544 views • 8 months ago

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇

YanXbt

34,368 views • 19 days ago