x-article-package

# X Article Package Package only the material needed to understand or reproduce the article. Preserve the user's chosen repository, visibility, and artifact scope. Use an isolated directory if the parent workspace contains unrelated work. ## Assemble Include the final article, relevant prompts and diagrams, and project files needed for the promised task. A README should explain the outcome, prerequisites, exact start steps, and what success looks like. Use relative links so the package works after download or clone. Include a brief agent handoff when the reader is expected to give the files to an agent. Keep authorship clear. Creator performance figures belong to that creator and need attribution. User experience, research claims, and tested results should remain distinguishable. Do not publish raw session archives, private analysis notes, credentials, or unrelated client material as a side effect of packaging. If an SVG is requested, create an editable, self-contained vector asset. Check XML validity and render it for visual inspection. A public repository is useful for distribution and reuse; search indexing is possible, not guaranteed, and access to X articles varies by tool. Use [the packaging checklist](references/package-checklist.md) to choose the smallest complete file set. ## Publish when authorized Local preparation is appropriate for a packaging request. GitHub creation or pushing needs explicit authorization, including authorization already present in the conversation. If the user asked to upload to GitHub, complete and verify that action rather than returning only a local folder. Follow explicit visibility instructions; if visibility is materially unclear and cannot be inferred from the sharing context, clarify it before publishing. Before pushing, inspect the exact staged files and their destination. Verify that the repository root is the intended directory. Never bulk-publish a parent home directory or an analysis workspace. Avoid overwriting unrelated remote content. After uploading, verify the remote commit, files, visibility, and README/assets. Report the actual repository link and any remaining unverified claim. Do not equate a local commit or a successful upload command with a checked remote result.