SShortSingh.
Back to feed

Developer builds Astro integration that writes visual edits directly to source files

0
·2 views

A developer has released @sudodevstudio/astro-ai, an open-source development-only integration for the Astro web framework that allows visual editing without a separate CMS or authoring system. The tool lets users click any element on a rendered page and writes the resulting change directly to the original .astro, .jsx, or .tsx source file, keeping visual and manual edits in the same codebase. Simple changes like text edits and node reordering are handled deterministically without calling an AI model, while complex requests such as making a section responsive are routed to Codex or Claude CLIs. The integration uses @astrojs/compiler-rs and Babel to parse source files and instruments supported elements with data attributes linking DOM nodes to their source locations and ranges. It is available via npm and aims to eliminate the reconciliation conflicts that arise when a visual editor maintains a second representation of the same content.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How to Regression-Test an AI Agent Without Breaking on Synonyms

A software experiment explored how to build a reliable regression suite for an LLM-powered customer support agent that can produce different wording on each run. The core challenge is that strict text-matching assertions fail when the model rephrases responses, while loose checks can miss genuinely dangerous behaviour like an agent autonomously approving refunds. The proposed solution uses a scenario dataset paired with behaviour-focused evaluators that check actions and outcomes rather than exact wording. Each evaluator enforces its own pass threshold independently, with safety-critical checks set to 100% and language-quality checks allowed a small margin of error. The suite fails the build if any single evaluator misses its bar, ensuring no category of failure can be masked by strong performance elsewhere.

0
ProgrammingDEV Community ·

Developer builds browser-only tool suite to stop accidental data leaks via online formatters

A developer has launched OmniTools Pro, a suite of 16 developer utilities designed to process data entirely within the browser, with no backend server involvement. The tool was created in response to a common but overlooked risk: popular online formatters and debuggers often carry ad trackers and may silently transmit pasted data to external servers. This poses a serious privacy threat when developers paste sensitive content such as API keys, customer PII, or authorization headers into these tools. OmniTools Pro uses native browser APIs like crypto.subtle and JSON.parse to handle all processing locally, meaning no outgoing POST requests are made. The project is also built as an offline-first Progressive Web App, and is available for public testing at omnitools-pro.surge.sh.

0
ProgrammingDEV Community ·

Developer Builds Git-Committed AI Coding Memory System After 3 Months, 542 Lessons

A developer who identified a core flaw in AI coding agents — their inability to retain project-specific corrections between sessions — built a lightweight graph-based memory system to address it. The system stores single-sentence lessons tied to specific files, commands, or keywords, and surfaces them to the agent at the exact moment they are relevant, not at session start. After three months, the repository holds 542 lessons, most written by agents themselves, with over 5,000 recalls logged. Recent improvements include specificity-ranked recall, whole-word keyword matching, and semantic understanding of task intent beyond literal keywords. The tool is open source under the MIT license, requires no vector database or network calls, and costs roughly ten tokens per recall.

0
ProgrammingDEV Community ·

Developer builds AI-assisted Godot game, finds sprite consistency needs strict pipelines

A developer rebuilt a Warhammer 40k-inspired game called Ashgate Siege in Godot 4, generating approximately 95,000 lines of GDScript and all sprites using AI agents in around five hours. The project revealed that AI-generated 2D sprite games are harder to manage than 3D, because each sprite is an independent image with no shared geometry to enforce visual consistency across frames. To address issues like drifting proportions, inconsistent lighting, and misaligned walk cycles, the developer shifted to treating image generation like a strict API call, using highly detailed, constraint-heavy prompts that specified exact canvas sizes, grid layouts, color keys, and pose names. Generated sprite atlases were then processed through an automated importer and validated against a test suite running over 17,000 silhouette checks and a 600-frame combat simulation. The core lesson drawn was that nondeterministic AI output requires deterministic, automated enforcement at every downstream stage of the pipeline.