public-contentlisted

# Public Repository Content Guidelines You are creating content for a **public repository**. Public repos are visible to anyone, so content must not leak competitive intelligence, internal strategy, or references to resources external readers can't access. ## General Principles - Write for external contributors who lack organizational context - Clear explanations without assuming internal knowledge - Professional but approachable tone - Explain "why" for non-obvious decisions - Be helpful to first-time contributors ## Restrictions - Focus on user value and technical merit - Avoid competitor names, especially in negative contexts - Omit internal business strategy and rationale - Only reference issues, PRs, and designs in public repos - Only link to public resources (no private repo links) - Keep language professional and welcoming - **No internal tooling references**: Never mention organization-internal workflows, proprietary tooling, or development processes that external contributors don't have access to ## By Artifact Type ### Design Documents - Focus on technical merit and user value - Avoid competitor names in negative contexts - Omit internal business strategy references - Polish language for external consumption - Write for readers without organizational context - Only reference issues/designs in public repos ### Issues - Focus on user value and technical merit - Avoid competitor names in negative contexts - Omit internal business strategy - Write for external c