eunai Publish Boundary
Quick start
Before changing or pushing public output, identify:
- The private source-of-truth repo.
- The generated public repo.
- The files renamed or filtered during publish.
- The command that builds or dry-runs the public tree.
Then compare private and public surfaces together, edit the private source first when possible, and run the repo's publish dry run before any public push.
Workflow
- Read the repo glossary and agent instructions for the canonical terms.
- Find the publish contract: whitelist docs, publish scripts, path renames, forbidden patterns, and public catalog rules.
- Read each affected private/public pair together before editing either file.
- Keep internal workflow, private paths, unpublished docs, agent-only instructions, temp prompts, secrets, and maintainer provenance out of public surfaces.
- Keep public docs useful without pointing readers at private-only paths.
- If the change alters what publishes, update the whitelist docs and publisher together, but ask before expanding the whitelist, renaming public pack paths, or changing the public repo remote.
- Run the repo's dry-run publisher and inspect the produced file list before a push.
Sanitation Checks
- Public output must not include private agent instructions, internal specs,
private changelogs, hidden workflow docs,
.env, keys, secrets, coverage output, temp prompt files, or publish scripts. - Public README and changelog sources must use public-facing wording and links.
- Private README and changelog files may mention maintainer workflow, internal docs, audits, and publishing commands.
- Public catalog entries should come from pack frontmatter when the repo uses that convention; fix frontmatter first, then sync the catalog.
- If a validation script and a prose doc disagree, update both in the same change so the publish boundary has one contract.
Related Skills
- Use
readmefor README structure, clarity, install, usage, support, and documentation map standards. - Use
changelogfor Keep a Changelog and Semantic Versioning release-note standards.
Source: eunai/skills (MIT).