aman-bhandari
- 21 skills
- 0 followers
- 6 hours ago last updated
- ▌ Os Lens · aman-bhandariUse when the student wants to see what the OS does when Python code runs. Wraps dis, sys.settrace, tracemalloc, strace, and /proc inspection. Invoke with /os-lens.
- ▌ Partner System · aman-bhandariCore Partner behavior for the AI Engineer Lab. Automatically applies to every session. Defines session modes, partnership philosophy, brainstorm integration, and interaction patterns. Writes exercise scaffolds, never solution code. Always asks why. Connects everything to production. Stays aware of DONE/NOW/NEXT at all times.
- ▌ Blog Drafting · aman-bhandariGenerates blog post outlines from exercises and learnings for portfolio building. Triggers on /blog, blog idea, or after significant exercises. Produces structure and key points only -- the student writes the prose. Maintains a running ideas backlog in blog-drafts/ideas.md. Prioritizes topics that demonstrate hireable AI engineering skills.
- ▌
- ▌ Faang Loop Simulation · aman-bhandariRuns a full 5-round FAANG AI Engineer interview simulation. Triggers on /faang-loop or when student declares FAANG-readiness. Rounds — coding, ML theory, ML system design, research depth, behavioral. Ruthless scoring. 8/10 average = ready. Below = specific gaps flagged and re-run scheduled.
- ▌ Adr Capture · aman-bhandariALWAYS activate when the student makes a high-level design choice -- library selection, database choice, mathematical approach, architecture pattern, or trade-off decision. Captures an Architectural Decision Record proving leadership-level thinking. Invoke with /adr.
- ▌ Code Reviewing · aman-bhandariDeep coach-style code review of code the student wrote. Triggers on /review or REVIEW prefix. Checks understanding first (why decisions were made), then correctness, then all standards (type hints, error handling, no print, meaningful names, docstrings, edge cases), then production thinking. Never rewrites code -- points to problems, the student fixes them.
- ▌ Trend Scouting · aman-bhandariActively scans the AI engineering landscape using WebSearch for trending repos, blogs, job postings, new tools, and framework releases. Triggers on /trends, during weekly reflections, or when checking industry relevance. Surfaces findings relevant to current topic and flags curriculum adjustments.
- ▌ System Checking · aman-bhandariAudits and upgrades the learning system itself. Evaluates coaching effectiveness, curriculum alignment with market, skill quality, architecture health, and architecture currency. Triggers on /system-check, during Friday reflections, or when the system suspects underperformance. Every check produces at least one concrete improvement. This is how the system evolves.
- ▌ Session Start · aman-bhandariStarts every session with context sync, time check, and collaborative planning. Triggers on /checkin, start session, or session start. Reads PROGRESS.md and ROADMAP.md, knows exactly where we left off, asks how much time is available, then plans the session together. No rigid format -- adapts to 15 minutes or 5 hours.
- ▌ Debug Systems · aman-bhandari bundleUse when the student encounters an error, says something is broken, or asks for debugging help. Enforces a three-layer debugging protocol: reproduce, trace the mental model, check OS state, identify production failure mode. Invoke with /debug.
- ▌ Evolution Log · aman-bhandariActivate at the end of every Topic completion. Generates a System Evolution Log comparing code complexity, identifying meta-patterns mastered, documenting intentional agent stress-tests, and evaluating the student's growth trajectory. Invoke with /evolution.
- ▌ Spaced Reviewing · aman-bhandariTracks concepts the student has learned and schedules recall questions using FSRS-inspired spaced repetition. Triggers on /review-deck, quiz me, or at session start when concepts are due. Maintains a JSON deck in reflections/spaced-review-deck.json. If you cannot explain it from memory, you do not know it.
- ▌ Systems Trace · aman-bhandariUse when introducing a new Python/ML/AI concept, explaining how code works, or when the student asks 'what happens when...'. Generates a three-layer explanation: Mental Model (runtime trace), OS/Hardware Model (kernel/memory), Production Model (what breaks at scale).
- ▌ Review Systems · aman-bhandariSystems-aware code review that extends the standard code-review skill. Checks resource management, memory footprint, GIL implications, fd hygiene, and failure modes at scale. Invoke with /review-systems.
- ▌ Architect First · aman-bhandari bundleForces a planning phase before any code is written. Triggers on /architect or at the start of BUILD sessions. Requires the student to articulate inputs, outputs, failure modes, and data flow before implementation begins. Inspired by Copilot Plan Mode and production engineering practices.
- ▌ Learn In Public · aman-bhandariGenerates daily short-form social posts AND long-form technical blog drafts. Triggers on /post (short daily) or /longform (topic-milestone technical post). Short-form solves social anxiety by removing friction. Long-form is a learning technology — writing is understanding, not marketing. Never preachy, never cringe.
- ▌ Mock Assessing · aman-bhandari bundleSimulates technical assessments calibrated to real AI engineer interview patterns from 100+ analyzed take-home assignments and hiring processes. Triggers on /assess, test me, or mock interview. Three modes -- quick (15 min), milestone (45 min), and interview (4-round simulation). Scoring is ruthless. 8/10 means hireable.
- ▌ Progress Updating · aman-bhandariUpdates PROGRESS.md with session entry and captures exactly where we stopped. Triggers on /progress, update progress, or at end of session before commit. Tracks what was done, what was learned, where we are in the flow, and what comes next. The repo never lies.
- ▌ Weekly Reflecting · aman-bhandariFriday depth test from memory. Triggers on /reflect, weekly reflection, or friday reflection. The student writes answers from memory with NO code lookup allowed. Gaps in writing equal gaps in understanding. Connects to spaced review deck, trend scout, and system check for a complete weekly audit.
- ▌ Adversarial Review · aman-bhandariActivate before accepting any implementation or architecture. Shift from teacher to Chief Systems Architect. Try to break the student's design with production failure scenarios. Record stress-tests in session logs as Leadership Stress Tests.