Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Designers, I created a task manager directly inside Photoshop coming soon... Features; - Task creation, Project collection, Linking Photoshop documents, Export linked project PSD's into one folder, and Notes. 100% Free btw.

14,712 Aufrufe • vor 9 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 Aufrufe • vor 1 Monat

Every project management tool was designed by project managers, for project managers. This one was designed for ADHD, dyslexic, and autistic brains instead. And it turns out that also makes it better for literally everyone who just wants to get work done without configuring a tool for two weeks first. It’s called Leantime. Most PM tools throw you straight into a task board and expect you to already know what a “sprint” is. Leantime is built around a different idea: tasks should trace back to a goal, not float in a backlog with no reason attached. → Ships with strategic planning tools, Lean Canvas, SWOT analysis, built to connect the “why” to the actual task list, not just a bare Kanban board → The same tasks render as Kanban, table, or list, whichever your brain processes better on a given day → Gantt-style milestone timeline, a built-in project wiki, and time tracking, all native, not four separate tools stitched together → Interface is deliberately built to reduce cognitive overload and context-switching, an actual design principle here, not an accessibility checkbox added later → Self-host via Docker in under an hour, your team’s entire project history stays on a server you control Jira was built assuming a certified project manager runs the workflow. Most teams are five people trying to ship something, not an enterprise PMO. Leantime is what a PM tool looks like when it’s built for the second group. Open source. AGPL-3.0. 10,000+ GitHub stars.

Harman

31,018 Aufrufe • vor 29 Tagen

One of the workflows I helped advance and lead for Destiny 2 was our static compositing pipeline for marketing visuals. When we were creating marketing content for #Destiny2, we always needed strong key visuals for weapons, characters, abilities, and other in-game elements. Unlike a traditional gameplay screenshot, where everything is baked into one static image, composited shots let us isolate individual elements and light them more precisely. That gave us a lot more flexibility to build scenes with better legibility, clearer focus, stronger lighting, improved contrast, and a more intentional overall look. One of the biggest strengths of compositing is having access to individual layers in Photoshop. That layered approach not only makes the editing process easier, but also makes the final artwork much more flexible. Images can be adapted for trailer motion graphics, reworked for print, or pushed further as creative needs evolve. Destiny 2 composites are built using Adobe Photoshop alongside in-game captures. Using advanced development tools, we light, capture, and isolate characters, weapons, and props directly from the game environment, all of which were originally created by the talented Bungie 3D art teams. Those assets are then brought into Photoshop, where they’re cut out and assembled into custom scenes using layered compositions and visual effects. The composites highlighted below are a few of the Destiny 2 pieces I’ve worked on that are meaningful to me. Let me know what your favorite is!

Biwald

67,750 Aufrufe • vor 1 Monat

The gap between a PM getting AI slop from Claude Code and one getting 10x output is about one hour of file structure. Three folders. > A knowledge folder with static context: who you work with, what each stakeholder cares about, reference material that rarely changes. > A projects folder where every task accumulates research, drafts, and artifacts that load instantly into your next session. > And a people folder that auto-updates from meeting transcripts through Granola's MCP. The people folder is the part that compounds. Build a skill that pulls what each person said in your last meeting, what they pushed back on, what they committed to. Now when you draft a message to your VP of Engineering, Claude Code already knows their communication preferences from 30 real conversations. That's context no prompt can replicate. Carl walked through this system on the episode and the compounding math stuck with me. Day 1, Claude Code knows nothing about your work. Day 30, it knows your stakeholders, your project history, your patterns. Day 90, it's surfacing connections across your work you haven't consciously noticed. Then layer on skills. A standup command that pulls from GitHub, Linear, your calendar, and your task folder in one shot. Website traffic compared against your LinkedIn posts this week. Analyses that would be impossible clicking between individual UIs, running before your first meeting. One hour of setup. Compounding returns every day after. The PMs typing prompts into a blank terminal and the PMs who built the operating system around it are already producing completely different categories of work. Build the operating system.

Aakash Gupta

82,865 Aufrufe • vor 4 Monaten

HERMES AGENT + OBSIDIAN IS A COMBINATION NOBODY IS TALKING ABOUT. Hermes ships with a bundled Obsidian skill. read, search, and create notes in your vault out of the box. why this combination is powerful: Hermes built-in memory is capped. MEMORY.md: 2,200 chars (~800 tokens). USER.md: 1,375 chars (~500 tokens). Obsidian vault has no cap. your agent writes research, session summaries, project context, and learned patterns as linked markdown notes. unlimited depth. the agent creates indexed notes by design. timestamps, backlinks, tags. every note connects to the knowledge graph. three ways to integrate: 1. BUNDLED OBSIDIAN SKILL (simplest) ships with Hermes. reads, searches, creates notes in your vault directly. hermes skills list | grep obsidian 2. OBSIDIAN MCP SERVER (deepest) 30+ tools: full-text search, tag lookup, note management, vault analysis, link analysis, orphan detection. add it via: hermes mcp 3. TELEGRAM + CRON → VAULT (always-on) set a cron job that writes daily summaries, research findings, or task reports directly into your Obsidian vault. your agent feeds the vault while you sleep. you review in Obsidian when you're ready. the unlock: Hermes memory handles what the agent needs to know per session (capped, injected). Obsidian handles everything the agent has ever learned (uncapped, searchable). short-term in Hermes. long-term in Obsidian. both accessible. both persistent. keep the vault scope narrow at first. start with one /Hermes folder. expand once you trust the workflow. 8 Loops Indise Hermes Agent👇

YanXbt

20,617 Aufrufe • vor 1 Monat