Jun Lee

This commit **updates the documentation style guide** by adding new sections to the `src/content/docs/style-guide/documentation-content-strategy/writing-guidelines.mdx` file. It introduces guidance on **progressive complexity** and the **inclusion of use cases** within documentation content. This **enhancement to the documentation content strategy** aims to improve the clarity and practical utility of future project documentation. The changes provide clearer directives for content creators, ensuring more structured and user-centric explanations.

This commit significantly **improves the clarity and accuracy of the Cloudflare One Traffic Policies documentation** through an "ELI5" review of 11 root-level files. It addresses terminology, expands acronyms, restructures dense sections, and adds critical caveats and examples to enhance user understanding. Specifically, the changes clarify explanations for application types in `application-app-types.mdx`, expand acronyms and define CNAME records in `domain-categories.mdx`, add identity-based policy examples and caveats in `identity-selectors.mdx`, highlight limitations for managed service providers in `managed-service-providers.mdx`, and clarify resolver policy usage in `resolver-policies.mdx`. This **documentation enhancement** ensures users have a more comprehensive and understandable guide for configuring Cloudflare One's traffic policy features.

This commit delivers significant **documentation improvements** for **Cloudflare One's Egress Policies**, focusing on enhanced clarity and detailed explanations across several key areas. It provides an **ELI5-style simplification** for complex topics such as dedicated egress IPs, BYOIP, IP geolocation, and the two-step evaluation process for host selectors. This **maintenance work** aims to make the documentation more accessible and comprehensive, ensuring users have a clearer understanding of traffic management features, including introductory concepts, load balancing, and catch-all policies.

This commit significantly **clarifies and enhances the Cloudflare One DNS Policies documentation**. It introduces plain-language explanations, spells out critical acronyms (e.g., DNSSEC, DoH), and provides detailed context for policy evaluation phases and the nuances of `Allow` and `Override` actions. Furthermore, the update expands prerequisites for **testing DNS filtering** and adds important callouts regarding **timed policy duration** and timezone inference, alongside fixing a broken Gateway link. This comprehensive **documentation improvement** aims to significantly boost user understanding and reduce potential misconfigurations within the **Cloudflare One traffic policies** subsystem.

This commit significantly **improves the clarity and accuracy of Cloudflare One HTTP Policies documentation**. It involves **rewriting introductions and explanations** for complex topics such as **policy evaluation order**, **TLS decryption limitations**, and **HTTP/3 inspection behavior**, including important cautions about bypasses. The **documentation update** also fixes outdated UI navigation paths, simplifies antivirus scanning criteria, and clarifies SNI visibility, ensuring users have a more precise understanding of policy configuration and its implications.

This commit introduces an **Adversarial Review** step into the **ELI5 skill**'s workflow, enhancing its explanation generation process. This **new feature** adds a critical Step 9 to the `SKILL.md` definition, where a subagent is prompted to perform a detailed, automated review of the generated content. The addition aims to improve the quality and robustness of the "Explain Like I'm 5" responses by incorporating an automated, adversarial critique.

This commit significantly **improves the clarity and accuracy of the Cloudflare One network policies documentation**. It **rewrites introductory sections** to better explain policy evaluation order, the role of Allow policies, and defines key jargon like SNI and CIDR. Additionally, it adds crucial **security caution notes** regarding IP override policies and non-HTTP protocols bypassing filtering, while also **correcting the dashboard navigation path** for configuring SSH logging policies. This **documentation improvement** enhances user understanding and ensures the content accurately reflects security best practices and configuration steps for **Cloudflare One traffic policies**.

This commit **updates the Cloudflare One documentation** to provide accurate navigation instructions for various **traffic policy** features within the Cloudflare dashboard. It specifically revises guides for accessing **firewall policies**, creating and managing **rate limiting policies**, and enabling **managed rulesets**, now directing users to utilize the `Dashbutton` component. This **documentation maintenance** ensures users can correctly locate and configure these critical security settings, improving the overall user experience by preventing confusion caused by outdated UI instructions.

This commit significantly **improves the clarity and accuracy of the Cloudflare One Network Firewall packet filtering documentation**, addressing factual errors, defining jargon, and clarifying critical concepts across 13 pages. This **documentation improvement and maintenance** effort enhances user understanding of policy creation, best practices, rate limiting, and managed rulesets within the **Cloudflare One Network Firewall** subsystem. By reducing assumptions about reader expertise and updating internal `eli5` guidelines for clear writing, the changes aim to make it easier for users to correctly configure and troubleshoot their network security policies. The scope covers various aspects from `add-policies.mdx` to `traffic-types.mdx`, ensuring a more accessible and precise resource for users.

This commit **updates the documentation** for the **`eli5` skill**, providing clearer guidelines for its appropriate use within the agents system. It adds detailed examples of good candidates and scenarios where the skill should be skipped, effectively **narrowing its intended scope**. This **documentation enhancement** aims to improve user understanding and ensure the `eli5` skill is applied correctly, preventing misuse and improving overall agent performance.

This commit **introduces a new ELI5 skill** into the agent system, designed to **simplify technical documentation** by providing clear, "Explain Like I'm 5" explanations. It establishes a new **`.agents/skills/eli5`** directory, containing the core skill definition (`SKILL.md`), a comprehensive `README.md`, and various supporting reference guides. These guides include content type detection criteria, pattern libraries with before/after examples, and templates for consistent simplification. This **new capability** significantly enhances the agent's ability to generate more accessible and understandable content, improving clarity and user comprehension across various technical topics.

This commit significantly **enhances and restructures the documentation for Cloudflare One Traffic Policies**, focusing on improved clarity and user onboarding. It introduces new, detailed **"Get Started" guides for DNS, HTTP, and Network filtering policies**, while extensively rephrasing and expanding the main **Traffic Policies overview** (`index.mdx`). Additionally, numerous internal links across various **Cloudflare One documentation pages** (e.g., DLP, Gateway, Remote Browser Isolation) are updated to reflect the new `get-started` path, ensuring consistent navigation and a more intuitive learning experience. This **documentation improvement and refactoring** aims to make understanding and implementing traffic policies much more accessible.

This commit performs a **documentation fix** by updating image file paths within the `src/content/changelog/security-center/2026-02-19-threat-events-graphs.mdx` entry. It addresses broken image links, ensuring that the **Security Center changelog** correctly displays visuals for the "threat events graphs" feature. This **maintenance** task improves the accuracy and readability of the project's historical release notes, specifically for users reviewing past updates related to the **Security Center**.

This commit introduces a **new feature** to the `DirectoryListing` **component**, enabling an alternative display mode for directory contents. Specifically, a new `button` prop has been added to `src/components/DirectoryListing.astro`, allowing directories to be rendered as a grid of buttons with associated styling. The **documentation** for the `DirectoryListing` component in `src/content/docs/style-guide/components/directory-listing.mdx` has been updated to include details on this new prop and provide usage examples. This enhancement offers more flexible and visually distinct presentation options for directory listings within the project.

This commit performs **documentation maintenance** by **fixing a broken link** within the `src/content/release-notes/browser-rendering.yaml` file. Specifically, it updates the URL found in the description for the 'New Web Bot Auth headers' entry. This ensures that users accessing the **release notes** can correctly navigate to the referenced information, improving the overall accuracy and usability of the documentation.

This commit **updates the documentation** for **D1 and Remix integration**, specifically within the `d1-and-remix.mdx` example. It introduces a new recommendation for developers to consider **React Router over Remix** for new projects, providing clearer guidance on framework choices. Furthermore, the documentation is enhanced to detail the correct method for accessing **D1 bindings within Remix `LoaderFunction`**. This **documentation update** improves the clarity and practical advice for developers integrating D1 with Remix applications.

This commit significantly **refactors** the **Opencode agent's code example review process** by introducing a new subagent (`review-code-examples.md`) with comprehensive instructions and methodology. This **enhancement** aims to improve the quality and consistency of code examples across documentation, including stronger guidelines for formatting and API usage. It also incorporates **bug fixes** and **documentation improvements** for specific **Durable Objects examples**, such as adding the necessary `WranglerConfig` for `ReadableStream` and ensuring correct API usage. The changes streamline the review command and reinforce checks for the latest Cloudflare APIs.

This commit **updates the documentation** for the **`review-code-example` command**, located at `.opencode/command/review-code-example.md`. It introduces a **mandatory validation step** for code block fences, requiring contributors to use a Python script to ensure proper formatting. This **documentation update** is a **maintenance** task that enhances code quality by enforcing consistent code example presentation. The change impacts contributors by adding a new, explicit requirement for submitting code examples, ensuring all code blocks adhere to project standards.

This commit **introduces documentation** for a new **Opencode command**, `/review-code-example`, by adding the `review-code-example.md` file. This document comprehensively outlines the command's prompt, workflow, PR-specific logic, and scoring criteria for reviewing code examples. This **new capability** enhances the **Opencode system** by providing clear guidance for a new **code review automation feature**, enabling users to understand and leverage its functionality.

This commit **removes** the `review-code-example` command from the **CLI interface**. This is a **temporary removal** of a planned feature, indicating that the **code example review functionality** is not yet ready for public use. Users will no longer be able to invoke this command, with plans to reintroduce it once its development is complete.