Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Package Fit Checklist

Use this quick checklist before extracting code into p4o.

1) Rule of three

Do you have at least two consumers now (or very soon)?

2) Boundary and cohesion

Can you explain the module in one sentence, and do all exports match that purpose?

3) API stability

Can you keep a small, stable API with versioning discipline?

4) Independence

Can it run with explicit inputs instead of app globals?

5) Testability

Can it be tested without booting the entire app stack?

6) Footprint

Does it avoid pulling in large frameworks for a tiny feature?

7) Ownership

Is there a clear owner to maintain versions and docs?

If the answer is yes for most points, it is a strong package candidate.