figmaAug 13, 2026

Try These 10 Skills—And Show Off Your Own | Figma Blog (opens in new tab)

Skills are plain-text Markdown instructions that help Figma’s agent apply a designer’s preferences, workflows, and judgment. The post argues that skills are useful not only for engineers but also for codifying creative approaches, such as easing curves, typography, image audits, and motion principles. Figma now lets users create, preview, edit, and iterate on skills directly in the product, with some also compatible with Figma’s MCP server. ## What Figma skills enable - Designers can create skills from: - A reference design frame - Specific instructions or guidelines - Repeated personal workflows - The agent can draft a skill, which users can preview and test in chat. - Skills can be refined by: - Editing instructions and formatting - Asking the agent for recommendations - Opening the Markdown editor for manual changes - Skills can capture individual design judgment and help teams reproduce a consistent point of view. - Some skills work with Figma’s MCP server and third-party agents. ## Examples of personal design skills - `/image-audit` checks whether images in a file can be exported and places a report on the canvas. - `/shader-starter` helps users write more effective shader prompts. - `/make-a-type-scale` creates a type scale from selected text and generates corresponding font variables. - `/ease-like-miggi` applies the author’s preferred easing curves to motion keyframes, allowing teammates to use the same motion style. ## `/xray-scan`: Create radiographic image effects Created by Adele Ix, this skill transforms a photo or description into a realistic X-ray image. - Produces two visual treatments: - Glowing white lines on black - Darker tones on white - Supports layered monochrome collages with glowing edges. - Is especially suited to combining multiple scans into a unified composition. ## `/find-animation-opportunities`: Identify missing motion Created by Emil Kowalski of Linear, this skill reviews a design and suggests where animation could improve the experience. - Identifies elements that should animate and areas that may be over-animated. - Recommends: - What should move - Where the motion should occur - Exact animation values - Suggestions can be implemented manually in Figma Motion or applied by the agent. - Works best when focused on one frame with contextual information, such as the target persona. - It can also be asked which elements should remain static. ## `/camera-pan-and-zoom`: Animate static compositions Created by Mallory Dean, this skill adds camera-like movement to a static design. - Builds a nested camera rig around selected content. - Supports pan, zoom, and roll animations. - Can create directed sequences, such as touring a grid of cards before zooming out to reveal the full composition. - The skill is intended to make static compositions feel more cinematic and dynamic. ## Practical takeaway Designers can use skills to turn personal techniques and repeatable creative decisions into reusable tools. Start with a focused workflow, test the generated skill in Figma, and refine its Markdown instructions until it reliably produces the desired result.

markdownfigmadesign-systemsai-agent+2

discordAug 11, 2026

Discord Update: August 11, 2026 Changelog (opens in new tab)

Discord’s August 11, 2026 update focuses on profile customization, safer content discovery, and improved social features. It also expands Discord to Meta Quest, adds desktop game embeds, and continues a broader settings redesign. Behind the visible features, Discord upgraded its desktop client to Electron 42, bringing modest CPU improvements. ### Profile and Social Features - Desktop users can format their bios with a WYSIWYG editor instead of memorizing Markdown. - Profiles can now be set to private and shown to everyone, only members of smaller servers, or only friends. - Friend requests can include a note explaining why the request was sent. - New profile Frames are available in the Discord Shop for additional customization. ### Spoiler Channels - Servers can create spoiler text channels that require members to confirm they want to view the content. - This provides an alternative to marking an entire channel as Age Restricted. ### Game Sharing and Meta Quest - Desktop users can mention games with commands such as `@game Palworld`. - Discord embeds the selected game in the message when it has a Discord profile. - Mobile support for game mentions is planned. - Discord is now available on Meta Quest, allowing users to keep the app visible while using other VR experiences. ### Settings and Desktop Improvements - The settings redesign renames **Activity** to **Games & Apps**. - **Content & Social** is now called **Messaging Permissions**. - Related settings, including authorized apps, connections, operating-system-specific pages, and keybindings, have been consolidated. - Several settings pages received updated language and styling, including Data & Privacy and Activity Privacy. - The desktop app now runs on Electron 42, improving maintenance and providing incremental CPU-usage reductions. Discord’s update combines convenience features with ongoing usability and infrastructure work. Users interested in smaller fixes can consult Discord’s patch-note archive or the community bug megathread on r/DiscordApp.

markdowndiscorddesktop-appelectron+3

githubAug 4, 2026

How the GitHub legal team used Copilot CLI to streamline their workflows (opens in new tab)

GitHub’s legal team used Copilot CLI to turn repetitive legal work into customizable internal tools without relying on traditional software engineering. By expressing workflows, standards, and policies in plain language and Markdown, lawyers built systems that improved consistency, reduced drafting time, and preserved human oversight. The post argues that domain expertise can be operationalized into useful AI tools by anyone who can clearly define a process. ## Building a Contract Drafting Style Guide - Principal Product Counsel Ngandu Kasuku created **terms-ai** to manage varied commercial agreements involving data, infrastructure, and product integrations. - The tool stores instructions, drafting resources, workflows, and reference documents in a version-controlled repository. - An internal style guide enforces plain-language drafting and replaces repetitive prompt copying with consistent guidance. - A library of approved agreements lets the tool draw on prior work for addenda and new contracts. - Sensitive agreements remain in a controlled internal environment rather than the open-source repository. - Kasuku reports cutting drafting and review time roughly in half while producing more consistent provisions. - The main insight was that AI could support a lawyer’s own judgment and working style, not merely perform isolated tasks. ## Turning Legal Workflows into Plain-Language Instructions - Online Safety Counsel Jesse Geraci began with a workflow for analyzing source code in **DMCA** notices. - Copilot instructions covered triage, code comparison, license checks, circumvention review, policy references, and report templates. - Instead of traditional programming, the workflow encoded legal reasoning through structured instruction files. - Different modes were created for clients and lawyers, including faster client analysis, escalation recommendations, deeper legal review, and arguments for both sides. - The system later grew into a desktop application supporting contract review, NDA triage, risk assessment, compliance checks, and response drafting. - Reusable skills and agents handle tasks such as intake, playbook alignment, risk scoring, evidence verification, escalation, and report assembly. - Legal teams can still customize the system through readable Markdown, while human review remains essential. ## Broader Lessons for Nontechnical Teams - Repetitive work in almost any profession can be a starting point for automation. - Clear definitions of methodology, standards, and desired outputs can substitute for extensive programming knowledge. - Teams should begin with one bottleneck, use Copilot CLI to prototype a solution, and expand based on real usage. - These tools are decision-support systems—not replacements for professional judgment. Teams can use Copilot CLI to turn their existing expertise into repeatable, transparent workflows while retaining control over sensitive data and final decisions.

markdownaiopen-sourcedesktop-app+3

githubJul 15, 2026

GitHub for Beginners: Your roadmap to mastering the GitHub essentials (opens in new tab)

GitHub for Beginners presents a step-by-step roadmap from understanding version control to collaborating on projects through GitHub. It explains the essential Git concepts, account setup, repository creation, Markdown, and the GitHub flow. The central message is that beginners can master GitHub by learning a small set of practical tools and following a repeatable workflow. ## Understanding Version Control and Git - Version control tracks file changes over time, allowing developers to see what changed, when, and why. - Git replaces confusing file copies such as `final_v2` or `FINAL_actually` with a complete change history. - Git uses three main areas: - **Working directory:** where files are edited - **Staging area:** where changes are prepared for saving - **Local repository:** where committed history is stored - Core commands include: - `git status` to inspect changes - `git add` to stage changes - `git commit` to save a snapshot - “Pushing” code means uploading local commits to GitHub. ## Securing and Personalizing a GitHub Account - A GitHub account acts as a developer identity and should be protected with two-factor authentication. - 2FA can be enabled under **Settings → Password and authentication**. - Recovery codes should be downloaded and stored securely, such as in a password manager. - A profile README can serve as a public portfolio describing skills, projects, and interests. - The README appears on the profile when stored in a public repository named after the user’s GitHub username. ## Essential Git Commands - Beginners do not need to memorize all of Git; a small group of commands supports most daily workflows. - Important commands include: - `git config --global user.name "..."` to identify commits - `git init` to create a repository - `git clone <url>` to copy a remote repository locally - `git add .` to stage changes - `git commit -m "message"` to save changes - `git switch -c <branch>` to create and enter a branch - `git push` to upload commits - `git pull` to retrieve and merge remote changes - `git merge <branch>` to integrate another branch ## Creating a First Repository - A repository is a project’s home base: it stores files, tracks history, and supports collaboration. - To create one: - Select **New** from the GitHub dashboard - Choose a name - Set it as public or private - Optionally initialize it with a README - A `.gitignore` file excludes generated files, dependencies, system files, and temporary build output from version control. - A license communicates how others may use or share the project. ## Writing with Markdown - Markdown is a lightweight text-formatting language used throughout GitHub. - It powers READMEs, issues, pull requests, and comments. - Simple symbols and optional HTML tags can create readable documentation without complex tools. ## Following the GitHub Flow - GitHub flow provides a repeatable process for contributing safely: 1. Clone the repository 2. Create a branch 3. Make changes 4. Commit the work 5. Push the branch to GitHub 6. Open a pull request - Pull requests let colleagues review changes before they are merged. - The workflow applies to many shared projects, including repositories containing reusable AI prompts or other collaborative resources. Start with the basic Git commands, protect and document your GitHub profile, then practice the branch-and-pull-request workflow on a small repository. These fundamentals provide a practical foundation for contributing to larger team projects and open source.

markdownopen-sourcegithubgit+3

tossJun 19, 2026

Going Beyond Expertise (opens in new tab)

Technical Writers (TWs) can contribute far beyond writing documentation: they can lead product teams and build systems that turn knowledge into an organizational asset. Toss’s Knowledge System Team created “todoc,” an internal platform that makes documentation easier to write, centralizes scattered knowledge, and enables AI access. Its broader goal is to make documentation emerge naturally from daily work and remain accurate without constant manual maintenance. ## TWs as Product Owners and Makers - The author leads a product team of developers, designers, and TWs. - Their responsibilities include: - Setting product direction, roadmap, and priorities - Interviewing users and bringing insights to the team - Planning features - Building features directly with AI tools - TW expertise is especially valuable because TWs have deeply considered: - Why documents are difficult to read - What makes documentation effective - How information should be structured for AI consumption ## Why Toss Built Todoc Todoc was launched to address weaknesses in Toss’s existing documentation environment. - Static-site-generated documentation required users to: - Clone a repository - Write Markdown - Submit pull requests - Wait for review - This workflow was familiar to developers but created major barriers for designers, PMs, and other non-developers. - Existing documentation tools accumulated outdated policies, unfinished notes, and unexplained content, creating “documentation debt.” - Knowledge was fragmented across: - Static sites - Documentation tools - Code - Collaboration messengers - Individual employees’ knowledge After its beta launch, Todoc grew to more than 500 documents and 40,000 valid pages, with over 1,000 monthly users. ## Todoc’s Four Core Values ### Easy Documentation for Everyone - Anyone can create or edit documents immediately. - Content can be connected from GitHub, documentation tools, internal messengers, and other sources. - The platform removes the technical and procedural barriers to documentation. ### AI-Ready Knowledge - Well-organized documentation can be used by team bots and other AI tools. - Todoc supports API, CLI, and MCP access. - Teams use it for request bots, product specifications, and other workflows. ### A Single Source of Truth - Todoc consolidates scattered sources into complete, centralized documents. - Users can determine which information is current without searching across multiple systems. - The platform serves as the organization’s SSoT (Single Source of Truth). ### Scalable Infrastructure - Teams no longer need to select, build, or maintain their own documentation infrastructure. - Each team can have its own space on a shared platform. - The model is being expanded to Toss affiliates. ## Automating Documentation Quality and Maintenance Lowering the barrier to writing creates a new challenge: maintaining quality. - TW judgment is being converted into: - AI proofreading - Automated document reviews - Bots that generate initial drafts - Todoc is also designed to create documentation automatically from: - Decisions and discussions in internal messengers - Code changes - Ongoing project conversations - The system aims to update documents without relying on someone remembering to maintain them. - It evaluates whether knowledge is still valid by checking: - Whether policies match implemented code - Whether information is actively used - How recently it was updated ## The Evolution of TW Expertise The role is shifting from writing excellent documents manually to designing systems that consistently produce and maintain excellent documentation. - Experience understanding why documents are hard to read becomes standards for human- and AI-readable content. - Judgments about what makes a good document become criteria for AI review and automated editing. - Expertise in identifying outdated information becomes a system for validating knowledge. - TWs increasingly focus on: - Creating places where knowledge can gather - Defining quality standards - Encoding human judgment into systems - Generating documentation through normal work - Keeping knowledge continuously updated The practical vision is an organization where outdated documents trigger their own notifications, project work leaves behind organized records, and recurring explanations are preserved for future employees. Toss’s Technical Writing Chapter is therefore working to systematize TW expertise and establish documentation governance so teams can document effectively without constant manual intervention.

markdownaigithubmcp+4

githubJun 9, 2026

From one-off prompts to workflows: How to use custom agents in GitHub Copilot CLI (opens in new tab)

Custom agents in GitHub Copilot CLI turn repeated terminal tasks into reusable, consistent workflows. Defined as Markdown profiles in a repository, they encode team-specific expertise, tools, standards, and safety rules instead of relying on one-off prompts. This makes workflows easier to review, version, share, and reuse across the CLI, IDE, and GitHub. ## What Custom Agents Are - A custom agent is a specialized Copilot agent configured through a Markdown file. - Its profile specifies: - Role and area of expertise - Available tools - Required standards and procedures - Guardrails and expected output formats - Teams can tailor agents to requirements such as: - WCAG accessibility standards - Formatting and testing conventions - Security and privacy policies - Review and ownership requirements - Because profiles live in the repository, they can be versioned, reviewed, and shared like code. ## Creating and Using Agents in Copilot CLI - Invoke Copilot CLI from the terminal and use the `/agent` command to select an agent. - Store the profile in the repository’s `.github/agents` directory. - Agent files use YAML frontmatter and typically end in `.agent.md`, such as `accessibility.agent.md`. - The profile defines the agent’s name, description, model, tools, instructions, scope, and guardrails. - Copilot CLI is especially suitable for these agents because it can execute scripts, call APIs, inspect repositories, and work directly with command-line tooling. ## Automating Repeated Workflows Custom agents are most useful for recurring tasks that span the terminal, IDE, and pull requests. - A security audit agent can: - Run standard checks across repositories - Group findings by Critical, High, Medium, and Low severity - Produce a pull-request-ready checklist with owners and next steps - It can use tools such as `gitleaks`, `trivy`, `semgrep`, `gh`, `git`, and `jq`. - Agents should prefer existing repository configuration files, including `.semgrep.yml`, `.trivyignore`, and `.gitleaks.toml`. - Missing security tools should be reported as coverage gaps rather than replaced with invented results. - Instructions can require secrets to be redacted, inclusive terminology, and consistent date formats. - Ownership mappings can assign findings to teams based on affected paths, using `CODEOWNERS` when available or defined defaults otherwise. Custom agents provide a practical way to capture team expertise once and apply it consistently. Start by converting a repetitive, execution-heavy task into a narrowly scoped `.github/agents` profile with explicit tools, outputs, and safety rules.

markdownyamlgithub-copilot-clisast+4

discordJun 4, 2026

Discord Patch Notes: June 4, 2026 (opens in new tab)

Discord’s June 4, 2026 patch focuses on usability, performance, accessibility, and bug fixes across desktop, Android, and iOS. Major updates include a mobile call-confirmation prompt, an 8% improvement in median desktop startup time, a redesigned Account settings page, and a clearer voice-invite embed. The release also addresses numerous layout, navigation, accessibility, and platform-specific issues. ## New Features and Improvements - **Mobile call confirmation** - Adds a confirmation step after tapping call buttons in direct messages. - Helps prevent accidental calls. - **Faster desktop startup** - Improved median startup times by approximately 8%, or around 650 milliseconds. - Additional performance work is planned. - **Redesigned Account settings** - Updates visuals and wording to match the broader User Settings redesign. - Moves Devices, Family Center, Account Standing, and Multi-Factor Authentication into nested Account pages. - **Improved voice-invite embeds** - Displays the relevant server and channel. - Shows the number of users currently in the voice channel. - Adds animated avatars and hover details for usernames. ## General Bug Fixes - Fixed Android custom status text crowding the clear button. - Corrected iOS event behavior involving external Markdown links, mentions, sharing, QR login, themes, notifications, and profile images. - Fixed guest server invites getting stuck in onboarding or application flows. - Improved handling of long nicknames, wrapped time indicators, event descriptions, community announcements, and high zoom levels on desktop. - Corrected inaccurate Android search results when combining `has:forward` with Media, Links, or Files filters. - Fixed mobile navigation issues, including the Set Status back button. - Prevented empty Bluesky handle submissions from bypassing form validation. - Removed incorrect or unreachable keyboard shortcut hints and scrollbars. - Improved tab navigation and focus behavior for accessibility. - Fixed visual inconsistencies involving rounded corners, themes, font scaling, gradients, cursors, borders, and tinting. - Corrected invite, server discovery, event, and profile interactions that opened the wrong view or failed silently. - Improved behavior at high zoom levels and in smaller windows, including Shop filters and Event Details modals. The patch is intended to make Discord more reliable and polished across platforms. Users may not receive every fix immediately because the changes are still rolling out individually.

markdowndiscordandroidios+4

lineMay 7, 2026

ODW #5: Building a RAG System with a Vector DB and Agent Skills (opens in new tab)

The workshop demonstrated how a lightweight RAG system can make large collections of technical documentation easier for developers and AI agents to use. Using ChromaDB, Swift Evolution proposals were indexed locally and exposed to Claude Code through MCP. Agent skills then simplified searches by teaching the agent which collection, metadata, and query practices to use. The approach improves document discovery and can support code generation and review. ## Why RAG Is Needed - Large application teams maintain extensive documentation and architectural guidelines. - Developers often spend significant time searching for information about: - Introducing dependencies - Resolving build errors - Following architectural rules - Asking experts can solve problems, but consumes time for both the questioner and the responder. - RAG provides AI agents with structured, searchable knowledge so they can answer questions more accurately using internal documents. ## Building a RAG System with ChromaDB - The workshop used ChromaDB, an open-source local vector database with Python and JavaScript client libraries. - Swift Evolution proposals served as the sample dataset: - Approximately 500 Markdown documents - Consistent structure and proposal IDs such as `SE-0400` - Metadata including implementation status and authors - Participants indexed the documents locally and connected the database to Claude Code through an MCP tool. - This allowed the coding agent to retrieve and reference Swift language proposals during conversations. ## Improving Search with Agent Skills - MCP exposes the available database tools, but the agent still needs to know: - Which collection contains the relevant data - Which metadata fields are useful - How to formulate effective queries - A dedicated `searching-swift-evolution` skill encoded this knowledge, including: - The `swift-evolution` collection name - Proposal ID formats such as `SE-0255` and `ST-0001` - Metadata such as `Status` and `Authors` - A recommendation to query in English - With the skill, users could issue simple requests such as “Investigate SE-0500” without explaining the database structure or MCP workflow. - The workshop also covered skill mechanics, authoring best practices, and practical skill development. - Participants later indexed their own Markdown documents, created search skills, and learned how to deploy the database to LY Corporation’s internal Flava cloud for sharing. ## Potential Applications - Natural-language document search can make internal technical knowledge significantly more accessible. - Coding agents can retrieve relevant documentation automatically before: - Generating code - Reviewing code - Checking compliance with architectural or implementation guidelines - Combining RAG with agent skills or Claude Code sub-agents can embed organizational knowledge directly into development workflows. ## Workshop Design and Results - The online workshop used demonstrations by instructors and mock participants. - More than 1,000 people attended. - Its structure balanced lectures and hands-on exercises: - Lectures explained the core concepts concisely. - Practical demonstrations showed how to apply the system to real work documents. - This balance helped participants understand both the underlying ideas and their practical use. Overall, the workshop showed that a local vector database plus MCP and well-designed agent skills can provide a simple, effective foundation for searchable engineering knowledge and AI-assisted development.

markdownai-agentmcprag+4

cloudflareApr 17, 2026

Introducing the Agent Readiness score. Check to see if your site is agent-ready (opens in new tab)

Cloudflare argues that websites must evolve beyond browser and search-engine compatibility to become usable by AI agents. Its new Agent Readiness score evaluates whether sites support standards for discovery, content access, bot control, and agent capabilities. Early data shows adoption is extremely low, creating both a challenge and an opportunity for sites that adopt these standards early. ## Agent readiness across the web - Cloudflare analyzed the 200,000 most visited domains, excluding categories unlikely to need agent interaction. - The resulting Cloudflare Radar dataset tracks adoption of AI-agent standards and will be updated weekly. - robots.txt exists on 78% of sites, but most files target traditional search crawlers rather than AI agents. - Only 4% of sites declare AI usage preferences through Content Signals. - Just 3.9% support Markdown content negotiation via `Accept: text/markdown`. - MCP Server Cards and API Catalogs based on RFC 9727 appear on fewer than 15 sites, showing how early these standards remain. ## The Agent Readiness score Site owners can test their websites at **isitagentready.com**. Cloudflare scans the site and scores it across four dimensions: - **Discoverability:** robots.txt, sitemap.xml, and Link Headers under RFC 8288. - **Content:** Markdown for Agents. - **Bot Access Control:** Content Signals, AI-specific robots.txt rules, and Web Bot Auth. - **Capabilities:** Agent Skills, API Catalogs, OAuth discovery standards, MCP Server Cards, and WebMCP. - The tool also checks commerce standards such as x402, Universal Commerce Protocol, and Agentic Commerce Protocol, though these do not yet affect the score. - Each failed check includes a prompt that can be handed to a coding agent for implementation. The service itself supports agents through a stateless MCP server with a `scan_site` tool and publishes Agent Skills documents explaining how to implement each supported standard. ## Discoverability for AI agents - robots.txt helps agents understand crawl permissions and locate sitemaps. - Sitemaps provide a structured list of site paths, reducing the need to discover content by following every HTML link. - HTTP Link headers, defined by RFC 8288, expose important resources directly in responses without requiring agents to parse page markup. - Sites can use headers such as `rel="api-catalog"` to point agents toward machine-readable capabilities. ## Making content easier to read - `llms.txt` provides an LLM-oriented reading list at the site root, describing the site and linking to important content in a format designed for model context windows. - Markdown content negotiation lets agents request a clean Markdown version of a page with `Accept: text/markdown`. - Cloudflare measured token reductions of up to 80% compared with HTML, improving speed, cost, and the likelihood that agents can consume an entire document within their context limits. Cloudflare’s recommendation is to evaluate sites with the Agent Readiness tool and adopt the relevant standards incrementally. With current adoption so low, early support can make a site significantly easier for AI agents to discover, understand, authenticate with, and use.

markdowndatabase-designai-agentcloudflare+4

cloudflareMar 11, 2026

Slashing agent token costs by 98% with RFC 9457-compliant error responses (opens in new tab)

Cloudflare argues that HTML error pages are poorly suited to AI agents, wasting tokens while offering little actionable guidance. It now provides RFC 9457-compliant Markdown and JSON responses for Cloudflare-generated errors, including instructions on whether to retry, wait, stop, or escalate. The structured formats reduce payload size and token usage by more than 98% compared with HTML. ## Problems with HTML Error Pages - Cloudflare errors often result from customer policies or edge conditions, including: - DNS or host configuration problems - WAF, geographic, ASN, or bot restrictions - Rate limits - Traditional responses contain large amounts of HTML, CSS, and human-oriented text. - Agents may struggle to identify: - What went wrong - Whether retrying is appropriate - How long to wait - Whether human intervention is required - Custom Error Rules are configuration-dependent and therefore cannot provide a consistent contract across websites. ## RFC 9457 Structured Responses - Cloudflare now supports structured responses for all 1xxx-class errors. - Clients can request: - `Accept: text/markdown` - `Accept: application/json` - `Accept: application/problem+json` - Markdown responses include: - YAML frontmatter with machine-readable fields - “What happened” and “What you should do” guidance - JSON responses expose the same information as a flat object. - Support for Cloudflare-generated 4xx and 5xx errors is planned next. ## Machine-Readable Error Guidance Responses include stable fields such as: - `error_code`, `error_name`, and `error_category` for classification - `retryable` and `retry_after` for automated backoff - `owner_action_required` to indicate when the agent should stop or escalate - `ray_id`, `timestamp`, and `zone` for debugging and support This allows agents to implement durable control flow without scraping HTML or interpreting changing prose. ## Compatibility with RFC 9457 Cloudflare’s JSON format follows the standard Problem Details structure: - `type`: Documentation URL for the error - `status`: Actual HTTP status code - `title`: Short problem description - `detail`: Explanation of the specific occurrence - `instance`: Identifier for the individual error, corresponding to the Ray ID Cloudflare-specific operational fields are included as RFC 9457 extension members. Clients that do not recognize those fields can safely ignore them. ## Example: Rate Limiting A Cloudflare 1015 response identifies the request as rate-limited and includes: - HTTP status `429` - Error code `1015` - Category `rate_limit` - A description stating that the website owner’s configuration caused the limit - A Ray ID and timestamp - Retry-related guidance for implementing backoff The change is automatic across Cloudflare’s network. Browsers continue receiving HTML, while agents receive structured instructions when they explicitly request Markdown or JSON.

markdowncloudflarejsonrate-limiting+3

githubFeb 13, 2026

Automate repository tasks with GitHub Agentic Workflows (opens in new tab)

GitHub Agentic Workflows bring coding agents into GitHub Actions, allowing developers to describe repository tasks in Markdown instead of complex YAML. They can automate issue triage, documentation, testing, code cleanup, CI investigation, and reporting while preserving human oversight through permissions, sandboxing, logging, and review. The post presents the technology, now in technical preview, as an extension of CI/CD rather than a replacement for deterministic build and release pipelines. ## Markdown-Defined Repository Automation - Developers describe desired outcomes in plain Markdown and add the workflow to a repository. - The workflow runs in GitHub Actions using configurable coding agents such as: - GitHub Copilot CLI - Claude Code - OpenAI Codex - Because workflows operate within GitHub Actions, they benefit from repository context, audit logs, permission controls, and sandboxed execution. ## Examples of Continuous AI GitHub describes these workflows as “Continuous AI”: AI-powered automation integrated throughout the software development lifecycle. - **Issue triage:** Summarize, label, and route new issues. - **Documentation maintenance:** Update READMEs and documentation after code changes. - **Code simplification:** Find opportunities for improvement and open pull requests. - **Test improvement:** Evaluate coverage and add valuable tests. - **Quality hygiene:** Investigate CI failures and suggest targeted fixes. - **Reporting:** Produce recurring reports on repository health, activity, and trends. These tasks are difficult to implement with traditional deterministic YAML workflows because they require interpretation, judgment, and code changes. ## Relationship to CI/CD - Agentic workflows are intended to augment, not replace, existing CI/CD systems. - Traditional pipelines remain responsible for deterministic builds, tests, and releases. - Agentic workflows handle higher-level tasks involving analysis, recommendations, and repository maintenance. - GitHub Actions provides the infrastructure needed for controlled execution and observability. ## Guardrails and Human Control - Security is presented as a core design requirement, particularly against unintended behavior and prompt injection. - Workflows run with read-only permissions by default. - Write operations require explicit approval through “safe outputs,” which are designed to make changes pre-approved and reviewable. - The overall approach emphasizes inspectability, defined boundaries, and human review rather than unrestricted autonomous changes. ## Adoption Across Teams - GitHub Next reports using workflows to replace repetitive chores and assemble useful information for developers. - Home Assistant uses them to analyze large numbers of issues and identify important trends. - The Cloud Native Computing Foundation applies them to documentation automation and organizational reporting. - Carvana uses them for engineering work spanning multiple repositories. GitHub Agentic Workflows are best viewed as a controlled way to add AI judgment to repository operations. Teams should begin with focused, reviewable maintenance tasks and expand usage as they gain confidence in the workflows’ behavior and safeguards.

markdownai-agentci-cdgithub-actions+3

cloudflareFeb 12, 2026

Introducing Markdown for Agents (opens in new tab)

AI agents increasingly need structured, efficient access to web content, making traditional HTML a costly format for machine consumption. Cloudflare’s Markdown for Agents lets enabled websites serve HTML pages as Markdown when clients request `text/markdown`, reducing token usage and parsing overhead. The post argues that websites should treat AI agents as first-class visitors alongside humans and search engines. ## Why Markdown Matters for AI - Markdown conveys document structure with far less surrounding markup than HTML. - A Markdown heading such as `## About Us` uses roughly 3 tokens, compared with 12–15 tokens for an equivalent HTML heading. - The post’s HTML uses about 16,180 tokens, while its Markdown version uses approximately 3,150—a reduction of about 80%. - Converting HTML to Markdown inside an AI pipeline adds computation, cost, and complexity, and may not preserve the publisher’s intended structure. ## How Markdown for Agents Works - Cloudflare-enabled zones can respond to content negotiation requests containing: ```http Accept: text/markdown ``` - Cloudflare fetches the original HTML from the origin, converts it to Markdown at the network edge, and returns the converted response. - Clients can request Markdown with `curl`, while Workers-based agents can use a `fetch()` request with `Accept: "text/markdown, text/html"`. - Responses use `Content-Type: text/markdown` and include `Vary: accept`. - Existing coding agents, including Claude Code and OpenCode, already send compatible `Accept` headers. ## Token Estimates and Agent Workflows - Converted responses include an `x-markdown-tokens` header. - Agents can use this estimate to: - Determine whether content fits within a context window - Plan chunking strategies - Manage processing costs and limits ## Content Signals - Markdown responses include: ```http Content-Signal: ai-train=yes, search=yes, ai-input=yes ``` - These signals indicate that the content may be used for AI training, search results, and AI input, including agentic applications. - Cloudflare says future versions will support custom Content Signal policies. ## Availability - Cloudflare enabled Markdown for Agents on its Developer Documentation and Blog. - AI crawlers and agents can test the feature by requesting those pages with `Accept: text/markdown`. Web publishers can make their content more accessible to AI systems by supporting Markdown negotiation, while agents should request `text/markdown` whenever available to reduce tokens, parsing work, and processing cost.

markdownai-agentcloudflarecloudflare-workers+4

discordDec 15, 2025

Discord Patch Notes: November 4, 2025 (opens in new tab)

Discord’s November 4, 2025 patch focuses on faster startup and calls, more reliable streaming, improved notification processing, and a broad set of platform-specific fixes. Audio devices now initialize during call connection, reducing connection times by roughly 5–15%, while asset-fetch retries have reduced startup failures by about 80%. The release also improves Roblox streaming, iOS notification emojis, accessibility, navigation, and chat rendering. ## Performance and Reliability - Roblox streams on PC should no longer appear as blank or white frames, thanks to a more reliable capture pipeline. - Audio devices such as microphones now start while a call is connecting rather than afterward. - Notification targeting is up to five times faster, improving notification availability. - Asset-loading retries have significantly reduced startup failures that previously required closing and relaunching Discord. ## General Improvements - Desktop Quick Switcher returns more results when searching without a type filter. - Server administrators can now apply age restrictions to servers. - Discord fixed incorrect content-type headers for text attachments, including subtitle files. - Apple Maps link embeds work again. - Overlay dismissal correctly returns focus to the game. - Passkey prompts no longer appear when a passkey is already enabled. - Numerous layout, localization, tooltip, profile-editing, status, badge, and scrolling issues were corrected across desktop and mobile. ## Mobile and Platform Fixes - Custom emojis now render in iOS notifications. - Android fixes address unwanted vibration in Appearance settings, swipe navigation, role-management state resets, server-list rendering, chat loading, and bottom-navigation text truncation. - iOS fixes improve emoji-picker navigation, event controls, username rendering, server-join text, and message editing. - Desktop fixes include muted badge colors, profile-preview overlap, status resets, profile-editor blank screens, and localized button tooltips. ## Chat and Messaging - Fixed message spacing, forwarding layouts, reply-preview emoji overlap, and text-input positioning on iOS and desktop. - Android chat should no longer display a gray screen. - Forum-channel links and Markdown previews now render correctly. - Dark-mode forum previews no longer display links and mentions in black. - Spoilers render interactively and consistently, including inside code blocks. - Fixed potential crashes and visual issues when reacting to messages on iOS. - Desktop channel notification menus now display all available options. The patch is primarily a reliability and polish release, with the largest user-facing benefits coming from faster call connections, fewer startup failures, and more dependable streaming. Fixes may continue rolling out across platforms after publication.

markdowndiscordandroidios+4

discordSep 14, 2025

Discord Patch Notes: September 3, 2025 (opens in new tab)

Discord’s September 3, 2025 patch focuses on scaling, performance, mobile improvements, permissions, and a large collection of cross-platform bug fixes. Discord increased the default server capacity from 2.5 million to 25 million members while improving update processing and asynchronous operations for very large communities. The Android app also moved to React Native’s new architecture, with early results showing smoother performance, particularly on lower-end devices. ## Large-Server Improvements - Raised the default server member limit to **25 million**, up from 2.5 million. - Batched certain server updates and shifted more work to asynchronous processes to improve stability. - Added further improvements for large servers and those using Community features. - Continued work based on administrator feedback, including changes described in Discord’s Community Server Cleanup Report. ## Android and Mobile Updates - Upgraded Android to React Native’s new architecture across most of the app. - Early performance data shows: - Smoother app operation. - Fewer low-frame-rate problems. - Better behavior on lower-end devices. - Improved the mobile Shop with: - Faster loading. - Gifting. - Nameplate purchases. - A redesigned layout closer to the desktop experience. - Added camera-enable and camera-disable sound effects, especially useful when using keyboard shortcuts. - Improved mobile rendering and behavior for Markdown, member statuses, thread lists, voice-region menus, browser settings, and rotated layouts. ## Server Management and Permissions - Increased the pinned-message limit from **50 to 250**. - Added a dedicated permission for pinning and unpinning messages, separating it from **Manage Messages**. - Fixed issues involving: - Role assignment during Server Onboarding. - Reordering roles on iOS. - Server subscriptions and subscription modals. - Community server icons. - Server Insights announcement-channel charts. - Twitch integration’s Force Sync button. - Nitro boosts and localized Japanese formatting. ## General Usability Fixes - Mobile member lists now correctly display “Can’t Wait For” and “Obsessed With” status messages. - Fixed profile views that could become impossible to close after rapidly opening mutual-friend profiles. - Corrected poll notification placeholders on Android. - Restored proper Markdown rendering on mobile Event pages. - Fixed Quick Switcher search prefixes such as `!`, `@`, `#`, and `*`. - Improved DM context-menu hitboxes and fixed several spacing, padding, alignment, and tooltip issues. - Corrected invalid invite embeds, owner crown alignment, role and app badge positioning, and Friend Suggestions layout. - Fixed desktop pop-out windows incorrectly displaying a menu bar. ## Notifications, Themes, and Accessibility - Automod incident notifications now follow users’ existing push-notification settings. - Fixed randomly changing client theme colors. - Improved visibility and formatting for light-theme Student Hub search placeholders. - Corrected localization issues involving Nitro Home and other interface elements. - Fixed several unreadable, misaligned, or incorrectly sized buttons and controls. ## Platform-Specific Fixes - **iOS:** Fixed thread-list flickering, browser selection, voice-region menu backgrounds, role reordering, phone-related interface behavior, and channel details after rotation. - **Android:** Fixed phone country-code controls, app badge alignment, poll notifications, and mobile layout issues. - **Windows:** Corrected navigation from Action Center notifications. - **macOS:** Fixed an unclickable title bar. - **Desktop/Web:** Resolved issues with custom keybind warnings, pop-out windows, search, tooltips, subscription flows, and various menus. Discord says all listed fixes have been merged, though they may still be rolling out gradually across platforms.

markdownandroidiosmacos+3

discordAug 21, 2025

Introducing the Community Server Cleanup Report for August 2025 (opens in new tab)

Discord’s August 2025 Community Server Cleanup Report introduces the first wave of updates aimed at giving moderators, administrators, and game developers more control over their servers. The changes improve server management, onboarding, and Forum channels by fixing usability bugs, expanding feature availability, and improving accessibility. Discord says these improvements are part of an ongoing effort to make community management easier. ## Server and Channel Management - Unread mentions in Voice and Stage channels now appear in Suggested Channels for members who have not enabled “Show All Channels.” - The Role list in Permission settings now includes a right-click delete option. - Mod View now works on servers without the Community feature enabled. - Channel description editing has improved Markdown support. - Role changes now update correctly in Settings on Android and iOS. ## Community Onboarding and Server Guide - Disabling the Community feature now also disables the Server Guide if it was previously active. - The Server Guide supports screen readers for better accessibility. - A mobile bug that trapped users in an infinite Server Onboarding exit loop has been fixed. ## Forum Channel Improvements - Forum channels are now available on all server types, without requiring the Community feature. - Forum post editing on iOS has been improved. - Members can no longer bypass required Forum post tags. - Shift, Home, and End key behavior is now consistent when browsing Forums. - Users are no longer incorrectly affected by Slowmode when a Forum is full and their post cannot be created. - Closing Threads works correctly in Gallery View. - Posts from blocked users are hidden in Forums, as they are in regular channels. - Discord also made general cleanup improvements to Forum sorting and tagging. Discord presents these fixes as the beginning of a longer series of community-focused updates. Moderators and game developers can expect further improvements targeting server administration and member experiences.

markdowndiscordandroidios+4