Customize for Your Team

Use this page when forking the repository into an internal engineering handbook.

Policy Objective

Turn the public handbook into a team-specific source of truth without losing the verification model.

Scope

  • internal forks
  • private company prompts
  • approved tool lists
  • internal MCP and policy records

Audience

  • maintainers of a private fork
  • platform or developer-experience teams

Mandatory Requirements

  • keep public-source citations where they still apply
  • replace placeholder approvals with real owners and dates
  • remove examples that do not match your stack or policy
  • keep public and internal content clearly separated
  • add company-specific examples instead of rewriting every page
  • maintain one internal approval matrix for tools and MCP

Adoption Steps

  1. Copy the repo.
  2. Define owners.
  3. Replace policy starters with real approvals.
  4. Add internal prompts, templates, and stack examples.
  5. Keep validation automation enabled.

Exception Process

If a public page conflicts with internal policy, replace it in the fork and document the reason.

Audit Evidence

  • internal README or handbook index
  • approval matrix
  • internal policy pages

Verification Note

Fork guidance only. Internal examples and approvals must come from your organization.

Sources