u/Artilas_Digital

I'm not a CAD person. Every time I needed a simple bracket for a 3D print, I lost an evening fighting a modeling app I barely knew.

text-to-cad is a plugin that lets your coding agent do the CAD part for you. You describe the part, and the agent generates a real 3D model as STEP, GLB, STL or 3MF files.

And it goes further than just making shapes. It runs design for manufacturing checks, generates engineering drawings, and connects to 3D printing, sheet metal and CNC fabrication services.

It works with the agents you probably already use: Claude Code, Codex, Cursor, Gemini and Grok. Install is literally telling your agent to install it from the repo, or two commands if you prefer doing it yourself. Everything runs locally through uv.

The part I liked most is the viewer. In Claude Desktop, models show up as cards in the chat that you can orbit and point at. Claude can see what you selected. In a terminal, you get a link that opens the model in your browser.

Is it perfect? No. Complex mechanical assemblies still need someone who knows what they're doing to check the result. And the first start downloads a runtime, so you need a network connection. But for quick functional parts, this saves a LOT of time.

Field	Value
Stars	17,075
Forks	1,755
Last release	2026-10-05
Languages	Python 66.1%, JavaScript 28.9%, TypeScript 3.9%

https://github.com/earthtojake/text-to-cad

I've tried a bunch of AI video tools, and most of them give you one clip and leave the rest to you. OpenMontage goes after the whole production.

You describe what you want in plain language, and your agent handles research, scripting, asset generation, editing and final composition. It's an agentic system, so it runs inside the coding assistant you already use.

My favorite feature: start from a video you already love. Paste a YouTube video, a Short, a Reel, a TikTok or a local clip. It analyzes the pacing, scenes, keyframes and style, then gives you 2 or 3 different concepts, a cost estimate, and a sample before full production.

And it's not only image slideshows. For free workflows it can build real video from stock footage and open archives.

The showcase videos in the README are honestly fun to watch. A sci-fi trailer, a 60-second animated short about a lonely banana, a documentary about salt. Each one ships with its full prompt, pipeline and cost so you can reproduce it.

Is it perfect? No. The best-looking results lean on paid generation models, so costs add up, and there's a lot to learn before your first polished video. But if you make content and you're comfortable with agents, this is a seriously powerful setup.

Field	Value
Stars	63,513
Forks	8,084
Last release	None
Languages	Python 70.1%, HTML 18.5%, JavaScript 5.5%

https://github.com/calesthio/OpenMontage

If you've outgrown Streamlit but you don't want to learn React, this might be what you're looking for.

Taipy is an open-source Python framework for building data and AI web applications. The pitch is simple: you write Python, Taipy handles the frontend. No JavaScript, no CSS, no HTML. You define your data pipeline, your UI components, and your callbacks all in Python, and it renders a real web application you can actually deploy to production.

Where it pulls ahead of Streamlit is in the production side. Taipy has a proper scenario and pipeline management system built in, so you can define multi-step data workflows, track their execution, compare results across runs, and manage versioning. For data science teams that need to go beyond a prototype dashboard and into something their organization actually relies on, that matters a lot. It also handles multi-page apps, user authentication, and large datasets without the "rerun the whole script on every interaction" pattern that Streamlit uses.

That said, the learning curve is steeper. Streamlit's magic is that you can have something on screen in five lines. Taipy asks you to think about your application's structure upfront, which pays off later but feels heavier at the start. Some of the more advanced features have documentation that could be clearer, and the community is smaller than Streamlit's, so you'll find fewer Stack Overflow answers when you get stuck.

19,432 stars, Apache-2.0 licensed, active development. If you're a data scientist or ML engineer whose Streamlit prototypes keep turning into production apps, give Taipy a serious try before reaching for a JavaScript framework.

https://github.com/Avaiga/taipy

Most UI libraries are fine until you need to make a component look meaningfully different from the default, and then you find yourself fighting the library. Storefront UI, from the Vue Storefront (Alokai) team, is built around that exact problem, and it narrows its scope to one domain, eCommerce, which is why it ships the components a store actually needs rather than a generic kit.

The design philosophy is the interesting part: instead of large, opinionated, hard-to-override components, it ships small flexible base pieces (Button, Checkbox, Modal) plus copy-pasteable complex examples it calls Blocks (ProductCard, checkout steps) built from those bases and plain Tailwind utilities. So you own the composed component and can restyle it freely, rather than passing a hundred props to bend a black box.

What's inside:

- Works for both React and Vue, and is framework-agnostic at the design-system level

- Base components that are WCAG AA accessible out of the box, which the README correctly frames as both an ethical and, in the US, a legal requirement that's genuinely time-consuming to build yourself

- eCommerce-specific components you won't find in a generic kit: ProductCard, QuantitySelector, checkout components

- Copy-pasteable Blocks for the complex, store-specific pieces, so you paste and own the code instead of importing a rigid component

- Composables like useDropdown that abstract the fiddly UI interaction logic

- A Tailwind preset that maps the config to CSS variables, a typography package for third-party fonts, and pixel-perfect Figma files so design and engineering stay aligned

- A performance claim they put a number on: the standard eCommerce pages they build with it hit 95 to 100 on Lighthouse mobile

The honest framing: this is a mature, backed project rather than a hot new drop, and its whole reason to exist is the customization-and-scaling problem specific to storefronts. If you're building a store, the eCommerce focus and the copy-paste Blocks model are a real advantage over a general-purpose library. If you're building anything that isn't a store, a general kit will serve you better, since half of what makes this valuable is the eCommerce-specific pieces you wouldn't use. It's also tied to the Tailwind and Vue Storefront ecosystem, so it fits best if you're already in that world.

MIT, 2,636 stars and 481 forks as of writing, verified via the GitHub API.

https://github.com/vuestorefront/storefront-ui

I'm going to be honest with you. For months I treated my coding agent like a vending machine. Type a request, get code back, move on with my day.

And it never actually worked the way I wanted it to.

The agent would build the wrong thing. Confidently. Then explain itself in ten paragraphs when one sentence would've done the job. It jumped straight into code before either of us tested whether the approach was even right. Sound familiar?

I used to think a better prompt would fix that. It doesn't. What actually fixes it is a process wrapped around the agent, something that makes it stop and ask before it starts guessing.

That's exactly what I found in Matt Pocock's Skills For Real Engineers repo.

These are his own skills. The ones he uses every single day doing real engineering, not vibe coding. Each one targets one specific failure mode instead of trying to be some do-it-all framework. And they're built small on purpose, so you can actually read them, tweak them, and make them yours. Two install paths too: a Claude Code plugin that's a managed bundle updating on its own, or a skills.sh copy that drops editable files straight into your project.

Here's what's inside:

- grill-me and grill-with-docs: a relentless interview that makes the agent ask YOU clarifying questions before it writes a single line. No more guessing and hoping.

- A shared-vocabulary trick built around a CONTEXT.md file, so the agent learns your project's actual jargon instead of burning twenty words on something one word already covers

- tdd, code-review, and diagnosing-bugs: a red-green-refactor loop, a two-axis review split across separate sub-agents, and a real reproduce-first debugging loop for the bugs that actually hurt

- to-tickets and wayfinder, for breaking a huge spec into tracer-bullet tickets so work that's bigger than one session stays navigable instead of a mess

- A /setup-matt-pocock-skills command that asks which issue tracker and labels you use before it touches your repo

One thing I'll flag honestly: don't install both the plugin and the skills.sh copy. The README warns you'll end up with every skill twice. Pick one and go.

It's MIT licensed, one guy built the whole thing, and it's already sitting at 249,433 stars. That's not nothing.

If your agent keeps guessing wrong and you're tired of babysitting it, go look at this one. It's the closest thing I've found to actually fixing that.

https://github.com/mattpocock/skills

It's time to stop babysitting your agent. Go set it up right, and tell me in the comments if grill-me changes things for you the way it did for me.