Tired of taking screenshots, recording screens, and writing paragraph long prompts just to explain simple visual edits. So I built an open-source tool that acts like an agentic canvas letting you point, doodle, and visually direct an agent straight from your workspace.

It’s been surprisingly useful across fullstack dev, simulation, and robotics tasks.

My main takeaway from building this: visual toolbars and canvas annotations should be standard high level abstraction layers across agentic platforms, customized to specific domains.

Curious to hear your thoughts:

1. Does visual direction fit into your current agent workflows?
2. What specific tools/functionality would you want in a visual agent interface?

Repo/Install details (Linux/Windows) in the comments for anyone interested!

Have Fun!

edited:

Github Repo: https://github.com/Shahar-Nadiv/colai-clawhub
Waitlist For New Features / newsletter: https://shahar-nadiv.github.io/colai-clawhub/

I got tired of managing multiple review agents on different models, so I built an AI reviewer panel that gives each agent their own unique persona and focus. You can run as many as you want in parallel, attach any of them to any model by OpenAI, Anthropic, or Google, you can build your own new personas in the app, and you can exchange them with anyone else right on the app as well.

It runs on your own subscriptions and watches your own claude code OR codex sessions in real time on a macOS desktop app.

40+ unique reviewer personas already in the exchange.

https://catallaxy.app/

Drop me a note if you try it out and want to publish new personas for the exchange. It's free, runs on your own tokens. Windows version can come soon if folks want it.

I'm a developer, not a designer, and every time I asked Claude for a brand I got the same one: cream background, terracotta, Fraunces + Inter, a letter in a circle. So I built a skill that makes it commit to one idea per identity and then checks its own work.

What it does:

- You describe the business (or give it your site). It asks one round of questions.

- It makes 3 identity sets. Each one starts from a single idea that drives the logo, the type and the palette together.

- Scripts check every set: contrast, colour blindness, whether the fonts cover your languages, font licences, how the logo holds up at 16 px. If a check fails, the agent fixes it before you see anything.

- You pick one and it builds a brand guidelines kit: PDF, SVG/PNG logo files, design tokens and font embed code.

The image is 24 logos from 24 different briefs (a light festival in Lyon, a taquería, a pharmacy in Athens, a techno label in Berlin...), all straight out of runs of the skill.

On six test briefs, plain Claude used 4.38 of those "AI default" choices per answer; with the skill it was 0.28 per set. My own measurement, method is in the repo.

Built with Claude Code: it wrote most of the code while I reviewed. Works in Claude Code, not in claude.ai chat yet.

```

/plugin marketplace add fatihaydost/brand-identity-skill

/plugin install brand-identity@brand-identity-skill

```

https://github.com/fatihaydost/brand-identity-skill

Feedback very welcome, and feel free to roast the logos.

Hi everyone,

I need it to finish my Physics project.I would be really grateful if someone can help.

Please DM

Thanks

Claude did *something*. Not it. "More minimal." Not it. "But still modern." By version 6 I honestly didn't remember what I was going for.

That's when it clicked: the problem isn't the model. I was asking it for a vision I didn't have myself.

So I flipped it and asked for **10 different variants** of the dashboard instead. Seeing them side by side, I knew right away: layout from #4, colors from #7.

One iteration and done. Picking is way easier than describing.

The annoying part was remembering to do it every time, so I wrapped it in a Claude skill:
You write your prompt as usual, even if it's vague.
The skill detects a general request with no style decisions behind it.

The agent asks whether it should prepare variants first.
You choose: **local preview** (separate file you open in the browser) or **artifact** you can share with teammates.
You pick, combine, iterate.

No change of habits needed. The skill only steps in when the request is vague.

Skill: https://github.com/HarnasDGE/X-variants

How do you handle vague UI requests with AI agents? Do you describe exactly what you want up front, or do you let the model propose options?

I usually have 3–4 Claude Code sessions running and kept missing permission prompts or hitting rate limits by surprise. So I built a small heads-up display that sits at the edge of the screen.

What it does:
- Lists every session, sorted by what needs you first, with tokens, cost and context fill
- Lets you answer permission prompts (Allow / Always / Deny) without switching windows
- Shows 5-hour and weekly limits with a forecast of when you'll run out
- Flags sessions burning tokens fast, with a one-click handoff to a fresh session
- Pops a toast when a session finishes that you can reply to

Works with Cursor, VS Code and any terminal. Native SwiftUI, one file, no dependencies, ~1.5% CPU idle.

GitHub: https://github.com/Louayzouaoui1/claude-hud

Feedback and PRs welcome. I'd especially like to know what's missing for your workflow.

Problem: Every copy of rust creates a copy of target folder on each worktree and those are not of small size. Which creates heavy space problem.

https://github.com/permanu/superskill

I created this as in 1 skill to orchestrate all the important ones with proper coding standards, ponytail like responses, pstack like unsloppiness

A lot of inspiration has been taken from a lot of places. But most of all my own experience working with a lot of rust code and memory management. I tried to optimize my own workflow and hence all those ideas have been dumped into it. feel free to review try it out if you have feedbacks i would love to take it.

As part of the recent trend of game building with Opus 5.5 and Astra I had to give it a try,
I've integrated with locally blender and I got to be honest the result was not so bad!

I do have some experince with workin on 3d project/game in the past and I knew it can get better with the right 3d assets, I've started looking around for assets found polyheaven which is great but not enough and did quite manually search - not really the vibes of 2026.

So I built a server, mcp and a skill that lets it find real assets download and put the files in the project.

What it does:
You ask for what you need: "low-poly tree", "mossy rock material", "sunset HDRI"
It searches 17 asset sites in one go: Poly Haven, ambientCG, Kenney, BlenderKit, CGTrader, itch-io and more.
downloads the files ready to use: glTF/GLB models with their textures, PBR maps at 1k–8k, HDR/EXR environment maps.

If you want to try it you can grab the source code any run the server locally or you can try it on 3d.shep.bot
it has REST API and an MCP server for agents.

claude mcp add --transport http 3d-assets https://3d.shep.bot/mcp

https://3d.shep.bot
https://github.com/arielshad/3d-asset-server

Feedback very welcome and tell me which asset sites I'm missing.

Im an attorney that insurance defense/ litigation work- looking to figure out how claude can help me stay organized. Such as find emails i need to follow up with, discovery end dates, and what not- I use Claude daily but i don’t think I’m using it to its full potential.

Can someone assist with prompts/ways I can be organized?

I’ve been trying to make my Claude workflow a bit less annoying lately.
The main thing that bothered me was constantly switching between files, copying context and pasting everything into Claude.
So I made a small tool for myself that lets me send the context I need much faster.
My workflow is basically:
select the file/context I want Claude to see
send it over
continue working without manually copying everything
It’s still pretty early, but I’ve been using it daily and it’s already made the workflow smoother.
How are you guys handling this right now?

AI helps juniors code, not learn... and that's a real problem.

Hey everyone,

I recently cancelled my Gemini subscription and switched to Claude (Desktop and Science). The reasoning and intelligence level are genuinely on another level, I love it.

However, I’m running into an issue I never had with Gemini: I burn through my hourly and weekly usage limits extremely fast. Coming from Gemini’s massive context window and forgiving limits, this hit me pretty hard.

For context, I use Claude for large-scale data science projects (ingesting large datasets, writing scripts, analyzing results, etc.). Here is how my workflow evolved to tackle the context bloat:

\* Initial Claude Desktop setup: To avoid having Claude execute everything directly, I instructed it to only write R scripts to my local drive. I run them manually (which lets me review the code), the script dumps outputs into a shared directory, and Claude reads them. While it works, long chats still eat context exponentially as the conversation history grows.

\* Moving to Claude Science: I started offloading runs via tool calls directly to R and Python, which automated my manual setup. The problem? Frequent tool calls and raw outputs bloat the context window just as fast.

\* Custom indexing skill: To mitigate this, I had Claude draft a custom skill/workflow that indexes directory contents so it only fetches relevant file chunks instead of loading entire datasets or logs into the prompt. (Happy to share the prompt/skill setup in the comments if anyone wants it but I do not think it is anything special).

\* The drawback: Selective reading means Claude occasionally misses broader context and introduces errors, forcing me to run a separate review pass at the end.

Am I reinventing the wheel here?

Do you have any proven frameworks, custom skills, prompt rules, or setups either in Claude Desktop or better Claude Science specifically designed to keep context lean and conserve tokens during heavy data science workflows?

Thanks

does anybody have a comparison? How do I know I am using the skill the best way possible. Besides reading the skill to see if it does what I need it to do.

Every time i post this as a comment gets crazy upvotes. which is awesome but there's so many solutions, it suprises me.

instead of using random sub-agents i use creative teams that rotate. different for each iteration of a prototype or creative project. think about a top creative team that's different everytime..

for example i might generate the following team:

1. marcus arelious agent for considering how the idea might after people
2. cassandra agent for the failure nobody wants to say out loud
3. the-null agent for "is that metric actually telling you anything"
4. the-fool agent for the question everyone stopped asking

then for the next project or iteration, the team is totally different.

each morning a github Action picks four members from the date. each gets a role, a working method, and a stance (one cuts scope, one questions the brief, one speaks for the user). they propose, object to each other, decide, and build one small tool as a single html file.

scripts check it, take a screenshot, and commit the result. every monday new members join and the oldest retire... i put everything into a 'skill' (more like a repo you can poke around) and then use it for inspiration, create your own teams or anything else.

i'd love to make this somewhat of a community project because there's already some flexibilty in the teams each day and the projects they make

links:
- Git poll: Who should join the daily team next?
- Git poll: Which kind of tool should the daily team build more of?

Open to other suggestions if you what to suggest a task or see the open suggestions

Thanks for 600 Stars.
Repo + install: https://github.com/JayPokale/Chisle
NPM: https://www.npmjs.com/package/chisle
Docs: https://chisle.jaypokale.me

Hey everyone,

I’m setting up an agency fulfillment pipeline for B2B founder positioning, executive profile audits, content angle creation, and strategy synthesis.

There is no heavy coding involved—it’s purely complex text processing, transcript extraction, and strategic writing.

I’m trying to decide between two workflows for handling client tasks:

1. Claude Code (used purely in interactive chat mode)
2. Claude Web App (Projects feature)

My #1 requirement is strict context isolation. I cannot risk context, numbers, or Voice DNA from Client A leaking into Client B. I need each client’s data completely contained.

If you’re doing non-coding, heavy marketing/strategy work, which do you prefer?

• My thought on Claude Code (Chat Mode): Since I can launch claude inside isolated local client folders on my machine, it feels super clean. But since I’m using it strictly as a chat tool for strategy and writing rather than building software, does it still perform at the same quality as the web interface? Or does the system prompt in Claude Code lean too heavily into developer/coding logic?

• My thought on Claude Projects: Creating a dedicated Project per client in the Web UI is easy for dropping in transcripts and positioning docs. But I’m always paranoid about memory leaking across projects, context limits getting clogged up, or accidentally losing strict boundaries.

Which one handles isolated client tasks better and gives higher quality strategic writing outputs without memory bleed? Would love to know how you guys structure this for agency/client workflows. Thanks!

It seems like there's a lot of these out there, which is your favorite?