private-contentlisted

# Private Repository Content Guidelines You are creating content for a **private repository**. Private repos aren't visible externally, so content can freely include competitive analysis, internal strategy, and links to private resources. ## General Principles - Write for team members who understand the project context - Internal shorthand and references are acceptable - Focus on decision rationale and trade-offs - Document "why" decisions were made, not just "what" - Link to private repos and internal resources - Include pre-announcement feature discussions - Document abandoned approaches for historical context ## By Artifact Type ### Design Documents - Include competitor analysis with names and direct comparisons - Document internal stakeholder discussions and decisions - Include exploratory thinking and ideas that may not pan out - Reference internal business rationale for decisions - Reference designs/issues in any repo ### Issues - Mention competitors by name in analysis - Include internal business rationale - Reference exploratory ideas that may not pan out - Assume reader knows internal context - Reference issues in any repo (private or public) ### Pull Requests - PR body can include internal rationale and context - Reference competitor analysis or internal discussions - Mention exploratory approaches considered - Commit messages can include internal context - Reference issues/PRs in any repo ### Code Comments - Code comments can assume team knowledge - Referen