design-rationale
Investigate why code is shaped this way. Git and PRs first, then every evidence category that actually exists (tickets, docs, chat, observability, errors, analytics). Every claim is labeled Direct / Supported / Inferred / Speculative / Unknown. Never treat code as its own intent. Apply when the user asks why a design exists, why a flag is off, or why a threshold is what it is. Use subsystem-walkthrough for runtime behavior. Use dissect to audit entities. Use proving-change-safety before merge.
What is this resource?
Investigate why code is shaped this way. Git and PRs first, then every evidence category that actually exists (tickets, docs, chat, observability, errors, analytics). Every claim is labeled Direct / Supported / Inferred / Speculative / Unknown. Never treat code as its own intent. Apply when the user asks why a design exists, why a flag is off, or why a threshold is what it is. Use subsystem-walkthrough for runtime behavior. Use dissect to audit entities. Use proving-change-safety before merge.
Review the original project for installation steps, licenses, compatibility and updates. This directory provides discovery links, not downloadable or verified code.
Installation
For repositories supported by the Skills CLI, you can typically start with:
npx skills add afaraha8403/balakitCheck the repository instructions and select the intended skill before installing. This command may not apply to every source.
Safety & attribution
This is an external resource, not independently security-audited by this directory. Inspect permissions, scripts and changes before using it with your files or accounts.