Featured Article
Why ShipGlows should be fed with project pitches
ShipGlows understands your project corpus better when each project has a short pitch that is easy to update.
Menu Open navigation menu Close navigation menu
ShipGlows Blog
Long-form editorial pages for the decisions behind the framework.
The docs explain the contracts. The skills explain the workflow moves. The blog is where ShipGlows can argue a position in detail when the answer needs more than a card or a FAQ entry.
All Articles
Focused pieces for questions that need a stronger argument.
2026-07-09
Why ShipGlows keeps public code and private data in separate repositories
ShipGlows separates framework code from durable private operator data so versioning, backups, and privacy boundaries stay coherent.
Open article2026-07-08
How to keep your project pitches current for ShipGlows
A short refresh at the right time is enough to keep your project corpus usable for ShipGlows.
Open article2026-06-28
Why ShipGlows should not rush global primitives for profiles and tags
Global primitives look elegant, but they hard-freeze semantics, debugging posture, and runtime obligations earlier than ShipGlows can safely support.
Open articleOther Editorial Surfaces
The blog is indexed. Some long-form pages still live as standalone routes.
Existing explanatory pages such as “Why not just prompts?” remain valid standalone surfaces when they own a narrow route intent.