varuntej07
- 4 skills
- 0 followers
- 11 hours ago last updated
- ▌ Big O Police · varuntej07 bundleFind where a different data structure or algorithm would measurably reduce time or space cost, prove the win with a complexity argument and a verification step, and refuse the ones that do not pay. Use for requests to make something faster, reduce memory, fix a slow endpoint, page, query, build, job or test suite, explain why something is O(n^2), decide which data structure fits, review an algorithm, or audit a codebase for performance. Apply when the user says something is slow, hangs, times out, spikes memory, gets worse with more data, degrades at scale, or asks what to use instead of a list, loop, scan, or repeated query. Works on any language, runtime, or storage engine. Report only by default; change code only when the user explicitly asks for fixes.
- ▌ Trace Failure · varuntej07 bundleTrace and explain software failures from the real initiating actor through the technical break and observable impact before proposing a fix. Use for pasted exceptions, browser console errors, compiler and type errors, failed builds or deployments, backend and database errors, authentication failures, third-party API errors, background job or agent failures, startup crashes, partial-success incidents, and broken behavior with no explicit error such as an endless spinner. Apply when the user asks what happened, why it happened, who encountered it, what the impact is, or for the right fix after the failure is understood.
- ▌ Walkie Talkie · varuntej07 bundleAudit a completed product feature from the perspective of every affected user and actor, tracing the observable journey through actual code, runtime behavior, data, side effects, and recovery paths. Use after implementing a feature in any product layer, including UI, APIs, background jobs, notifications, authentication, permissions, payments, uploads, synchronization, real-time media, AI or agent actions, integrations, migrations, hardware, mobile, desktop, or web. Apply when validating UX completeness, production readiness, edge cases, lifecycle behavior, concurrency, failure recovery, accessibility, privacy, performance, compatibility, observability, or whether the built implementation matches the intended experience.
- ▌ Abstraction Police · varuntej07 bundleSweep a codebase for nearly-duplicated abstractions that should be unified and for premature abstractions that should be inlined, then report ranked findings with file and line evidence. Use for requests to find duplication, audit code health, review copy-pasted logic, check whether the same concept is implemented twice, find drifted constants or hand-synced contracts, decide whether code needs an abstraction, or clean up before or after fast feature growth. Apply when the user says code feels repetitive, asks what to refactor, asks whether two similar functions or components should be merged, or wants a duplication audit of a module, layer, or the whole repository. Report only by default; change code only when the user explicitly asks for fixes.