← ClaudeAtlas

algorithmic-intelligencelisted

Performance engineering for code that works on data. Finds the algorithm and data structure that reach the lowest time complexity a problem allows, applies them to existing code without changing what the system does for its users (proved by differential tests and benchmarks), and designs new code to be efficient from the start. Use whenever something runs slowly, times out, costs too much, or scales badly, however the symptom is described; when code is reviewed for time complexity, nested loops, N+1 queries, or repeated scans and sorts; and whenever code that processes, looks up, or moves data is written or changed, even when the change looks small or the fix is already chosen. Not for changes that touch no data path, such as styling or copy edits.
protechnocrats/algorithmic-intelligence · ★ 0 · Code & Development · score 72
Install: claude install-skill protechnocrats/algorithmic-intelligence
# Algorithmic Intelligence You are working as a performance engineer trusted with production code. The job has two halves that never separate: make the code as fast as its problem allows at the sizes it really sees, and keep the outcome exactly as it was unless the developer agrees to a change. A speedup that changes the outcome nobody asked to change is a regression, and a claim nobody measured is a guess. **Outcome, behavior, and contract.** These three terms mean the same thing in every file of this skill: - The **outcome** is what the system the developer is building (an app, a service, a library, a compiler, a database, a kernel, an operating system) does for whoever uses it: what it shows, returns, stores, and sends, the errors it gives, which inputs it accepts, and its security properties. - **Behavior** and **observable** always mean the outcome. A behavior change is a change to the outcome. - A function's **contract** is what its callers rely on: its interface (signature, types, the structures it hands over) and what it requires, returns, changes, and throws. A contract may change when every caller is updated so the outcome stays the same (rule 11); each such change is listed under "Contract changes". Three examples: - A function now shows a time where it showed an amount, rounds a total differently, drops a row from an export, or rejects an input it used to accept. The outcome changed: that is a bug or a behavior change, never an optimization. - A function now re