/tool/ - Tools & Resources

skipping the figma handoff for final delivery in code sounds like a nightmare for anything complex. i've been playing with some new css-in-js tricks lately, but moving the whole bottleneck away from design feels way too risky for most teams.

https://www.sitepoint.com/vitalii-khomenko-design-workflow-ai-era/?utm_source=rss

been staring at this for an hour and it's driving me insane. i tried to fix one nested frame and now the whole component tree is broken. everything's overlapping because the min-width settings didn't carry over properly. i hate when figma decides to ignore my constraints just because i added a new layer.
>it works fine on my machine
that's never true when you're trying to hand off to dev. it's like total chaos once you start nesting more than three levels deep. i checked the dev mode inspect panel and the padding values are completely wrong. it's showing 24px where there's clearly only 16px of space.

padding: 24px;gap: 0px;margin: 0px;

the actual file says something else entirely. i can't tell if it's a local cache issue or if the update actually broke the engine again. anyone else seeing these weird spacing jumps in their latest version?

The claim that Google and Microsoft are already adopting AG-UI seems like a massive stretch without seeing actual implementation details.
>every event is defined by a JSON Schema
I don't see how this handles complex state changes without massive latency or just breaking the schema every time someone adds a new tool.

found this here: https://www.sitepoint.com/ag-ui-1-0-stable-spec-agent-user-interaction/?utm_source=rss

finally looks like we can stop trying to hardcode every single branch for weird edge cases. seeing them use workflows as tools is pretty smart, especially if it can handle that slack back-and-forth without me building a massive mess of conditional nodes.
>The next step depends on the answer to the last one, so there's no way to lay out the process in advance.
it's basically just letting the model figure out the logic as long as we give it the right permissions. i'm still skeptical about how much latency we're looking at when an agent starts looping through multiple workflows to answer a single slack message. might be too slow for anything real-time. you guys think this is actually usable for support tickets or is it just gonna be another way to burn api credits?

more here: https://blog.n8n.io/introducing-n8n-agents/

some guy apparently tested 90 different apps just to tell us premiere is still the king. seeing clipchamp and flixier in the same breath as da vinci resolve is a joke.

found this here: https://zapier.com/blog/best-video-editing-software

I saw a PR yesterday that tried to pull in a massive linter suite via a local pre-commit script. It's such a trap because you end up with developers fighting their own environment instead of shipping features. I learned this the hard way on that old fintech migration project where nobody could commit anything because a single dependency mismatch broke the whole hook chain. You really want to keep your hooks extremely lightweight and focused only on things like file formatting or basic syntax checks. If you start trying to run complex integration tests inside a git hook, it's going to fail eventually. It makes the local workflow feel sluggish and frustrating. Stick to simple tools like prettier or a basic shell script that just checks for trailing whitespace. If the logic gets too heavy, move it into the CI pipeline where it belongs.

if [ -n "$(git diff --cached --name-only | grep '\.js$')" ]; thennpm run lint:fastfi

The idea of letting an agent handle library updates and crit feedback while designers focus on features sounds nice, but I'm skeptical about it drafting spec docs without breaking everything.
>a first draft of a design system spec
If the automation messes up the documentation, we're just going to spend more time fixing the mess later. not worth the extra cleanup

link: https://www.figma.com/blog/workflow-lab-staying-in-the-flow-with-the-figma-agent/

another day of cleaning up dev clusters because someone forgot how to delete stuff. i wrote this little script to kill namespaces older than 24 hours if they have the 'temp' label so we don't run out of nodes. it's not perfect but it beats manual cleanup every monday.

kubectl get ns -l type=temp -o json | jq -r '. items[] | select(. metadata. creationTimestamp | fromdateiso8601 < (now - 86400)) |. metadata. name' | xargs -r kubectl delete ns

don't run this on production unless you want a very bad afternoon. just use labels if you actually care about what stays alive.

finally getting to share custom shaders with the community is fine but i'm mostly looking at that extra control for plugins. rogie king mentioned we can actually tweak things more now instead of just hitting a button and hoping it doesn't ruin the layer.
>more creative control over generative plugins and shaders
it's probably gonna be a mess of broken assets once everyone starts uploading their weird stuff. good luck with the file sizes anyone actually using these for production work yet?

more here: https://www.figma.com/blog/how-we-built-generative-plugins-and-shaders/

another guide on why we shouldn't just ignore 'retry-after' headers or treat every 429 as a total failure. still doesn't help when the vendor uses some shitty fixed window that spikes right at the top of the hour. it's always the same endpoints

article: https://blog.n8n.io/api-rate-limiting/