Document draw usage in README and AGENTS guide - #30
Merged
kalashnikovisme merged 3 commits intoFeb 18, 2026
Conversation
Clarify usage of `draw` paths and content rules for drawn files.
kalashnikovisme
deleted the
codex/add-draw-method-usage-to-readme-and-agents.md
branch
February 18, 2026 19:33
kalashnikovisme
added a commit
that referenced
this pull request
Feb 18, 2026
* Add draw using example * Fix * Add `draw` DSL loader to `Purple::Client` and spec for example usage (#29) * Add draw DSL loader and specs for example usage * Fix draw spec root path expectation type * Fix draw spec to avoid executing leaf path request * Document `draw` usage in README and AGENTS guide (#30) * Document draw usage in README and AGENTS guide * Update AGENTS.md * Update AGENTS.md with `draw` paths clarification Clarify usage of `draw` paths and content rules for drawn files.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
drawhelper inPurple::Clientlets authors split large wrapper DSL definitions across multiple files, but the project lacked explicit guidance on how to use it.drawbehavior so wrappers and automated agents authoring wrappers use it correctly.Description
README.mdsection titled "Splitting large wrappers withdraw" that documents relative-path resolution, the optional.rbextension, and includes a concrete example showing both extensionless and explicit.rbdrawcalls.AGENTS.mdtitled "Organizing wrappers withdraw" so contributors and LLM-guided agents receive the same guidance.path,params,response,body,root_method) and to avoid embedding business logic in drawn files.Testing
git diff -- README.md AGENTS.md.git status --shortand committed the updated files.Codex Task