Tag: Systems Engineering
Browse our exclusive articles!
Why a Merged Branch Suddenly Conflicts: Squash-Merge Divergence
You squash-merged a branch cleanly, kept working on the same branch, opened a new pull request — and it says CONFLICTING, on files nobody else touched. The branch isn't broken; squash merge quietly spent it.
Making a Claude Code Skill Trigger Reliably — and How to Measure It
A perfectly written skill that never fires is worthless. Whether it fires is decided by one thing — its description — and you can measure and tune that instead of guessing.
Writing a Claude Code Skill That Mutates a Real Store
Most skills hand back text or a file — a mistake there is a bad paragraph. A skill that writes to a live database or content store is different: a mistake is duplicated, corrupted, or lost data. The build discipline has to change with it.
Where Claude Code Skills Live — and the Rule That Keeps Them Tracked
You spent an afternoon building a skill. By default it landed in a personal folder that no repo sees and no teammate has. That's real work sitting outside version control.
Anatomy of a Claude Code Skill — and Why Progressive Disclosure Is the Whole Trick
A skill looks like a folder with a Markdown file in it. What makes it work is not the content — it is when each part of that content loads.