skills/build-company-operating-system/references/package-design-rules.md

# Usable company-package design

## Entry point

Create one obvious beginner entry file in `00_START_HERE`. It must explain what the company is, what is confirmed, what is still open, which files are authoritative, what must happen first, and what the operator must not do without approval.

## Document separation

Use a central map plus separate documents for strategy, brand, offers, production or delivery, tools/accounts, security, finance, law, marketing, prompts, metrics, and plans. Do not hide operational templates or copy-ready prompts inside a giant handbook.

Split when a section has a different owner, review cadence, sensitivity, source of truth, or day-to-day use. Merge only when separation creates navigation without operating value.

## Prompts and roles

Maintain an approved role/chat map, master prompts, task prompts, required inputs, output contracts, tool permissions, confidentiality rules, and human-review gates. Never embed secrets. Mark provider-specific instructions as current-research dependent.

## Operating area

Provide separate locations for new unsorted input, approved active work, work awaiting review, released records, and measured results/lessons. Do not mix drafts with approved company truth.

## Rebuild and cleanup

When rebuilding an existing package:

1. inventory all files;
2. identify canonical, duplicate, superseded, incomplete, and conflicting items;
3. create the proposed new map;
4. map every old item to keep, migrate, merge, archive, or delete;
5. show exact destructive targets and recovery method;
6. obtain approval;
7. migrate and verify before any approved removal.

Prefer dated archives over deletion unless the user explicitly requests permanent removal.