Alexey Chechet

Building Gissen: a headless visual editor for Vue 3. The Vue equivalent of Puck. Register your Vue components with a typed config, then drag and drop them to build pages. Output is plain JSON you render anywhere. This is the editor canvas working — drag, reorder, nest, delete.

@techNmak useful list! one thing i'm trying to square: it says "use commands instead of sub-agents" but also "have feature-specific sub-agents," and "vanilla claude code beats complex workflows" right above five big ones. how do you decide which to reach for?

Someone finally documented how to actually use Claude Code. 58K+ stars. claude-code-best-practice. Direct from Boris Cherny and team: ➡️ Always use plan mode, give Claude a way to verify ➡️ Ask Claude to interview you using AskUserQuestion tool ➡️ Use Git Worktrees for parallel development ➡️ /loop - schedule recurring tasks for up to 7 days ➡️ Code Review - fresh context windows catch bugs the original agent missed ➡️ Make phase-wise gated plans with tests for each phase → Use cross-model (Claude Code + Codex) to review your plan ➡️ CLAUDE[.]md should target under 200 lines per file ➡️ Use commands for workflows instead of sub-agents ➡️ Have feature-specific sub-agents with skills instead of general QA or backend engineer ➡️ Vanilla Claude Code is better than complex workflows for smaller tasks → Take screenshots and share with Claude when stuck ➡️ Use MCP to let Claude see Chrome console logs ➡️ Ask Claude to run terminal as background task for better debugging ➡️ Use cross-model for QA - e.g. Codex for plan and implementation review ➡️ Context rot kicks in around 300-400k tokens, don't let sessions drift past that ➡️ Rewind > correct, /rewind back to before the failed attempt instead of polluting context ➡️ /schedule - cloud-based recurring tasks that run even when your machine is off ➡️ Auto mode instead of dangerously-skip-permissions, a model-based classifier decides if each command is safe ➡️ Build a Gotchas section in every skill, add Claude's failure points over time The community workflows included: ➡️ Superpowers (234K stars), brainstorming → git worktrees → subagent-driven development → TDD ➡️ Everything Claude Code (219K stars), /ecc:plan → /tdd → /code-review → /security-scan → merge ➡️ Matt Pocock Skills (138K stars), /grill-with-docs → /to-prd → /triage → /tdd → /handoff ➡️ Spec Kit (114K stars), specify → clarify → plan → tasks → implement → analyze ➡️ gstack (112K stars), office-hours → CEO/eng/design reviews → spec → qa → ship → canary ➡️ Cross-Model (Claude Code + Codex) Workflow ➡️ RPI (Research Plan Implement) ➡️ Ralph Wiggum Loop for autonomous tasks The billion-dollar questions it addresses: ➡️ What exactly should you put inside CLAUDE[.]md, and what should you leave out? ➡️ When should you use command vs agent vs skill? ➡️ Why does Claude still ignore CLAUDE[.]md instructions, even when they say MUST in all caps? ➡️ Can we convert a codebase into specs and have AI regenerate the exact same code from those specs alone? ➡️ Should you rely on Claude Code's built-in plan mode, or build your own planning command? The daily habits: ➡️ Update Claude Code daily ➡️ Start your day by reading the changelog ➡️ Follow r/ClaudeAI, r/ClaudeCode on Reddit Repost it. Bookmark it. 👇 Here's the GitHub Repo: github.com/shanraisshan/c…

@ocavue 1k well earned. a type-safe headless layer is the real win here, not the framework count. congrats 🎉

1,000 ⭐ for ProseKit 🎉 A headless, type-safe toolkit for building rich text editors on ProseMirror, with first-class support for React, Vue, Svelte, Preact, Solid & vanilla JS. What are you building with it?

@aidenybai the question before swapping: is it 3x faster from a better algorithm, or from handling fewer edge cases? a "drop-in" that quietly picks a different winner on px-2 px-4 hands you visual bugs that are miserable to trace. how's the conflict-resolution parity?

Introducing cnfast A 3x faster drop-in replacement for `cn` npx cnfast migrate

Write-up: dev.to/yukos1221/buil… Repo: github.com/gissen-dev/gis…

The hard part of building a drag-and-drop editor for Vue wasn't the UI - it was syncing SortableJS with a reactive store. Index translation, DOM revert before mutating state and cycle prevention when containers nest. Wrote it all up, first deep dive on Gissen. Link in reply.

@benjamincanac useTour built-in means one less onboarding-tour lib to bolt on. small thing and genuinely nice quality of life. awesome!

Nuxt UI v4.9 is out! 🔥 🧭 New useTour composable 📅 Calendar month & year pickers ✂️ Unstyled mode to bring your own design system 🎯 Consistent focus styles across every component ...and much more on: github.com/nuxt/ui/releas…

@GraphQL observability events are the sleeper feature here — everyone'll cheer the spec correctness but that's the one i'll actually use day to day. nice work!

🚀 GraphQL.js 17 is out! This is a major milestone for #GraphQL GraphQL.js 17 brings low level execution APIs, observability events, spec correctness and more. graphql.org/blog/2026-06-1…

@moraes_c_ nice! maintainers have wanted this for years and it took the ai-pr flood to finally ship it. overdue but very welcome. the bypass list is the right touch too — keeps it from punishing your reliable regulars

PR limits are live 🚀 Repo admins can now cap how many open PRs a user without write access can have at once, with a bypass list for trusted contributors. A big step toward helping maintainers manage contribution volume and reduce PR noise.

@tannerlinsley @kapa_ai @algolia the 95% is great but the 5% you caved on is the actually-interesting data. curious whether those were tanstack-specific gotchas (the stuff "agent-first" is supposed to erase) or genuinely hard judgment calls (the stuff no framework fixes)?

Over the last week on TanStack.com, we increased performance/responsiveness, debugged a bunch of edge cases, updated top-level, library-level and docs navigation, added AI-powered answers via @kapa_ai, improved and simplified search via @algolia, removed unnecessary cruft/chrome/layout and a ton of other little moments of polish/buff. As a means of proving and testing TanStack as a viable and reliable agent-first framework, all of this was done by simply prompting Codex to make the desired changes and iterating only on what was visible in the preview, trying my hardest not to use any technical knowledge and trusting the process. I'd say it went amazing about 95% of the time! I *did* cave a few times and abuse my institutional know-how 😉 but I also used those moments as an opportunity to improve the skills and context we feed to agents to be even better. All of this to say... we're gearing up for a very exciting TanStack-wide change very soon that's been in the works for months. I am so excited, I it's going to take things to the next level in a way no one expects! Hope you enjoy the upgrades and changes. Stay tuned.

@andrii_sherman wow! not a maintainer inconvenience but a supply-chain hole. drizzle is 11.5M downloads/week with no way to ship a patch. if a CVE drops tomorrow, hundreds of thousands of apps stay exposed while the maintainer's locked out. that's an incident

We need to bring more attention to the situation we have with npm. Drizzle releases are completely blocked by npm because of "too many published versions" (we have 1397 versions) There is no way for us to delete old versions, unpublish old versions, or really do anything except contact the support team. Of course, we did that >3 weeks ago, but there has been no action from the npm team at all. Drizzle has >11.5M downloads/week and is used by hundreds of thousands of developers across the globe, yet we're getting no help from npm It's not like only 10 people are blocked. There are many teams and developers waiting for us to ship important features, improvements, and fixes (Imagine receiving a security report in this situation and having zero ways to release a patch). Npm support keeps sending bot replies saying they need more time to handle the case I'm begging someone to help us find anyone from the npm team who can help us delete old versions that are not used by anyone anymore, or at least give us a way to ship releases again ps why is having 1397 releases a problem at all?

@srimalireddi genuinely love the goal here, the contact-form-into-the-void is one of the web's oldest dead ends. one thing i'm stuck on though: why voice? most visitors are at a desk or open office where talking out loud to a site won't happen. what makes them talk to this vs text chat?

Today we're launching Founding Agent. For 25 years, a website's answer to "I have a question" has been a search box and a contact form that goes nowhere. So visitors leave - and you never know they were there. Founding Agent is a voice AI agent that lives on your site and actually talks to people. It answers their real questions instantly, qualifies who's a fit, and books the meeting while they still care. It feels like a real conversation because retrieval runs in under 10ms. No lag, no "thinking" dots. It's built on the same infra 1500+ developers are already using at @usemoss Websites have been one-way mirrors for too long. Time they answered back. Early access 👇

@rauchg truest thing about building agents right now. I mean the intelligence got cheap, which finally exposed how much of the job was never intelligence, for example integration, permissions, and data nobody wanted to wire up. good to see the boring layer getting some love

The hardest part of building an agent is not building the agent. It’s the data. It’s, ironically, figuring out OAuth, tokens, credentials, scopes… We have AGI sitting there, waiting to be unleashed. Vercel Connect solves for both security and ease of use. It’s delightful

@_hyf0 genact. it generates totally fake but very official-looking terminal activity, I mean compiling, downloading, "kernel modules." drop it in tab 11 and now you genuinely can't tell which of your tabs is doing real work and which is lying to you

Currently I have 10+ terminal tabs running agents to do various things. I often get lost while staring the screen, like don’t know which tab should I open while waiting. Wanna Cook something in the terminal that’s totally meaningless to read so I can relieve my brain.

@addyosmani the line i keep chewing on is the one you toss out — teams absorbed how the system fit together just by reading each other's diffs. that byproduct is what's dying, and agents can't hand it back. they triage fine, the shared mental model doesn't come free now

@posva @antfu7 awesome! are you giving these stable ids/codes? that's the bit that makes agents reliable — they match the code, not the message string, so rewording doesn't break their autofix. without it "agent cheat code" is kinda fragile

Over the years, in Vue, we have added a lot of dev only warnings at runtime to help developers With @antfu7 we want to improve these with structured diagnostics: enforcing good practices for errors and pretty print output that is actionable (agents autofix cheat code) Introducing nostics, errors worth reading!

@shadcn yeah "intelligence as borrowed" lands. fable proved it — 72 hours, pulled same day, zero notice. only thing missing imo is the abstraction layer. a backlog's useless if every plan in it needs the exact model that just got yanked, so build for model portability too

In light of what happened, I'm doubling down on skills like /improve. A frontier model got pulled. If it happened once, it's gonna happen again. Fable today. 4.9 tomorrow or maybe gpt 6 one day. So, treat intelligence as borrowed. Drain intelligence when it's available. Build a catalog of plans today. Then implement later with a cheaper, open source, or a model you control. Build the backlog now. github.com/shadcn/improve

@tannerlinsley normalizing by react is smart, but it only cancels the AI noise if inflation is uniform — and i doubt it is. agents scaffolding greenfield lean toward the new hotness, so tanstack catches more bot tailwind than legacy react-router in old apps. trend's real, just flattered a bit

AI's effect on the NPM ecosystem has made absolute number of downloads a decreasingly helpful metric, so I’ve been using this "download share relative to React" view way more lately. This chart compares Next, React Router, React Router Framework Mode, TanStack Router, and TanStack Start. The big names are still big obviously, and we have a long ways to go, but the trend for TanStack is undeniably exciting 😊 tanstack.com/stats/npm?pack…

@anthonygore isn't this just No Silver Bullet again? the lines of code were never the hard part, the decisions behind them were. all AI does is make that really obvious now. though i'm not sold that decisions are a fixed budget — feels like bigger systems just spawn more of them

Before AI the number of humans needed to make software was linked to the number of lines of code to be written. After AGI the number of humans needed will depend on the number of decisions needed to be made. Decisions will be things like “how should this new feature look?” etc. The software may be enormous, but if it doesn’t require many decisions to be made about it, it may only need one dev to maintain. And vice versa.

@pnpmjs Awesome, thanks for the improvement

We have created a new GitHub action that you can use to setup both pnpm and a JS runtime - node, deno, or bun: github.com/marketplace/ac…

Repo (MIT): github.com/gissen-dev/gis… npm install gissen Pre-alpha — properties panel and MCP server come next Building in public, feedback welcome

Building Gissen: a headless visual editor for Vue 3. The Vue equivalent of Puck. Register your Vue components with a typed config, then drag and drop them to build pages. Output is plain JSON you render anywhere. This is the editor canvas working — drag, reorder, nest, delete.