Open-Doc Framework Lets AI Coding Agents Handle Content While Locking Down Document Layout

·1 views

Developer Simon Liu has released open-doc, an open-source framework designed to fix a recurring problem with AI coding agents producing poorly formatted documents. While agents handle written content well, they consistently fail at document layout tasks such as page breaks, margins, and table-of-contents pagination. Open-doc addresses this by having the framework enforce all structural and layout rules, leaving agents responsible only for generating content. The project was inspired by open-slide, a React-based slide framework built by developer 1weiho that embeds agent instructions directly within the project folder via an AGENTS.md file. By bundling layout rules and usage guidelines alongside the code, open-doc ensures agents always have the context they need without relying on per-conversation prompting.

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)

Prompt Injection: How Attackers Hijack Customer-Facing AI With Plain Text

Prompt injection is a security vulnerability where attackers embed instructions inside user messages or external content to manipulate an AI into bypassing its guidelines. Because language models treat all input — system prompts, retrieved documents, and user messages — as a single undifferentiated stream of tokens, they cannot inherently distinguish legitimate instructions from malicious ones. Attackers can exploit this in multiple ways, including smuggling commands inside support messages, poisoning web pages that AI crawlers index, or tricking an agent into leaking private data through crafted tool calls. Unlike traditional software exploits, prompt injection requires no malicious code — it relies entirely on the model's core design feature of following instructions. Strengthening system prompts offers partial protection but is not a complete defense, making prompt injection a persistent and underappreciated risk for any AI system that reads untrusted content.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

JSON Key Order Bug Caused Flaky CI Tests, Not AI Model Drift

A developer investigated a flaky integration test that passed locally but repeatedly failed in CI due to mismatched JSON key ordering in API responses. The root cause was a server function that iterated over a Python set to build a dictionary, since sets do not guarantee insertion order, causing key sequences to vary across processes. The test itself worsened the problem by comparing raw response text instead of parsed JSON structure, making any harmless reordering a hard failure. The fix involved two changes: replacing the set iteration with ordered field traversal, and rewriting the assertion to compare parsed, key-sorted dictionaries rather than raw strings. The case highlights that brittle string-based assertions on serialization details — not AI-generated code per se — are a common source of environment-sensitive test failures.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

White-Label ICT Vendors Bear the Brunt When Resellers' AI Agents Fail

White-label ICT software vendors are increasingly absorbing the support burden when AI voice agents deployed by resellers make poor decisions or errors, according to an analysis published on DEV Community. Unlike traditional telephony issues, AI agent failures manifest as judgment calls rather than error codes, making them difficult to diagnose without full access to prompts, tool configurations, and call logs that resellers control but cannot inspect. Support tickets often travel through multiple intermediaries before reaching the vendor, losing critical context at each step and consuming days of unbillable engineering time. The core problem is that white-label arrangements were designed around deterministic software, where a reseller's misconfiguration was visible and isolated, but AI systems introduce shared accountability that was never formally defined. Vendors are urged to redraw support boundaries, restrict reseller tool permissions, and establish clearer ownership over AI configuration before incidents erode the platform's reputation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AWS Solutions Architect Exam: Practical Lessons on Cloud Design and Cost Efficiency

Engineering teams increasingly treat AWS cloud migration as a standard operational requirement rather than a future-facing goal. Designing high-availability applications on AWS involves strategies such as Auto Scaling Groups across multiple Availability Zones, S3 and CloudFront for static asset delivery, and Multi-AZ RDS deployments for database resilience. Key preparation lessons for the Solutions Architect certification include understanding decoupling and asynchronous processing, enforcing least-privilege IAM policies, and evaluating storage class trade-offs. Official resources like the AWS Well-Architected Framework and the AWS Architecture Center are recommended for building accurate foundational knowledge. Experts emphasize that certification readiness is less about memorizing service limits and more about developing judgment to balance security, performance, and cost.

0 comments Read more at DEV Community