Amey-Thakur
- 1k skills
- 0 followers
- 2 days ago last updated
- ▌ Spaced Repetition · amey-thakurSchedule review at increasing intervals so knowledge is retained with minimal total time. Use when you must remember material long-term rather than pass an immediate test.
- ▌ Media Processing Queue · amey-thakurRun transcoding, thumbnailing, and extraction as queued background work with progress, retries, and failure visibility. Use when media processing takes long enough that it cannot happen in the request.
- ▌ Upload Pipeline Design · amey-thakurMove a file from the user's device to durable storage and a processed state, with validation, progress, and recovery at every stage. Use when building any feature that accepts files.
- ▌ Agent Board Reporting · amey-thakurAssemble an investor or board update from source metrics with agents that draft, fact-check every number, and surface bad news rather than bury it. Use when periodic reporting eats days and the numbers keep needing correction.
- ▌ Agent Compliance Desk · amey-thakurRun continuous compliance with agents that map controls to evidence, collect it on a schedule, and flag drift before an audit finds it. Use when preparing for or maintaining a certification and evidence gathering is a periodic fire drill.
- ▌ Agent Debate Protocol · amey-thakurHave agents argue opposing positions from the same evidence, then synthesize, so the strongest case for each option is heard before deciding. Use when a decision is genuinely contested and one agent's answer would hide the trade-off.
- ▌ Agent Ensemble Voting · amey-thakurRun the same task several times independently and combine the results by agreement, to damp variance on judgement calls. Use when output varies between runs and being consistently right matters more than being fast.
- ▌ Agent People Ops Desk · amey-thakurSupport the recurring people function with agents that maintain onboarding paths, keep policy documents current, prepare review inputs, and flag gaps, while every human decision stays human. Use when a growing team keeps reinventing process.
- ▌ Agent Quality Council · amey-thakurHold a consistent standard across everything a company ships, with agents that review against written criteria and escalate disagreements rather than averaging them. Use when quality varies by who happened to do the work.
- ▌ Agent Role Definition · amey-thakurWrite role cards that pin each agent to one charter with declared inputs, outputs, refusal rules, and non-overlapping scope. Use when assembling a multi-agent team and you need every agent to stay in its lane instead of all drifting toward the same work.
- ▌ Agent Strategy Review · amey-thakurRun a periodic strategy review with agents that check whether stated goals still match reality, argue the alternatives, and force an explicit continue or change decision. Use when quarterly planning repeats last quarter's plan by default.
- ▌ Agent Work Assignment · amey-thakurMatch work to the agent or person best able to finish it, with explicit capacity limits so nothing is assigned into an already full queue. Use when work is distributed by whoever is nearest rather than by fit and capacity.
- ▌ Code Of Conduct Enforcement · amey-thakurApply a code of conduct consistently, with a reporting path, proportionate responses, and records, so it protects people rather than decorating the repository. Use when adopting a code of conduct or handling a report.
- ▌ Invoicing And Receipts · amey-thakurProduce invoices and receipts that are accurate, immutable, and contain what tax authorities and customers require. Use when billing businesses or operating where invoices are legally regulated.
- ▌ Payment Reconciliation · amey-thakurMatch provider settlements against your own records so every charge, fee, refund, and payout is accounted for. Use when closing books, chasing a discrepancy, or building financial reporting.
- ▌ Scope Change Control · amey-thakurHandle new requests mid-project by making the trade-off visible rather than absorbing them silently. Use when a project is accumulating additions and the date is not moving.
- ▌ Realtime Scaling · amey-thakurScale collaborative sessions across instances with room routing, shared state, and controlled fan-out. Use when one server can no longer hold all active sessions.
- ▌ Realtime Testing · amey-thakurTest collaborative features against concurrency, reconnection, and ordering rather than only the single-user path. Use when a realtime feature works in development and breaks with real users.
- ▌ Environment Config · amey-thakurManage script and tool configuration through env vars, dotenv files, and layered precedence without leaking secrets. Use when wiring configuration for CLIs, scripts, and local development.
- ▌ Script Idempotency · amey-thakurWrite scripts whose reruns are always safe through check-then-act steps, atomic writes, and dry-run modes. Use when automation may run twice, die halfway, or need a safe retry.
- ▌ Agent Debugging Workflow · amey-thakurWork with an agent on a bug by supplying evidence and letting it form hypotheses, rather than asking it to guess from a description. Use when debugging with an agent's help.
- ▌ Agent Session Management · amey-thakurManage long agent sessions with checkpoints, context resets, and clear task boundaries so quality does not decay. Use when working with an agent over an extended piece of work.
- ▌ Partial Failure Handling · amey-thakurHandle operations that touch several services where some succeed and some fail, without leaving inconsistent state. Use when a single user action calls multiple systems.
- ▌ Performance Engineer Role · amey-thakurOperate as a performance engineer who sets budgets, gates regressions in CI, and runs profiling as a service other teams rely on. Use when latency, throughput, memory, or GPU utilization matters and you want measured wins, not folklore optimizations.
- ▌ Site Reliability Engineer · amey-thakurOperate as a site reliability engineer who runs production to an error budget and holds toil below a hard cap. Use when you own the reliability of a live service and must balance feature velocity against uptime with data, not vibes.
- ▌ Technical Program Manager · amey-thakurOperate as a technical program manager who drives a multi-team program to a date by tracking dependencies, burning down risk, and reporting the truth upward. Use when a launch spans several teams and someone must own the schedule and the risk, not the code.
- ▌ Capital Allocation · amey-thakurDecide where to spend limited money and attention across competing opportunities, with a consistent basis for comparison. Use when planning a budget or choosing between investments.
- ▌ Async Communication · amey-thakurRun write-first collaboration with the right document types, response-time norms, and meetings reserved for what writing cannot do. Use when improving distributed-team communication or cutting meeting load.
- ▌ Mentoring Engineers · amey-thakurGrow engineers through goal-anchored mentoring, calibrated stretch work, and questions before answers. Use when mentoring individuals or building a team's growth practice.
- ▌ One On One Meetings · amey-thakurRun one-on-ones the report owns, splitting career growth from status, with notes that compound. Use when establishing 1:1 practice as a manager or getting more from 1:1s as a report.
- ▌ Process And Threads · amey-thakurChoose between processes, threads, and asynchronous concurrency based on isolation, memory sharing, and failure behaviour. Use when deciding how to run work concurrently.
- ▌ Feature Engineering Tabular · amey-thakurEngineer features for tabular models (aggregations, encodings, interactions) that add signal without leaking. Use when building features for a tabular ML or Kaggle problem, where features often matter more than the model.
- ▌ Kaggle Competition Workflow · amey-thakurApproach a Kaggle (or any ML competition) systematically: trustworthy validation, strong baseline, then disciplined iteration. Use when entering a data competition and want to place well without wasting the timeline.
- ▌ Idempotent Consumers · amey-thakurMake message consumers safe under at-least-once delivery with natural idempotency or a transactional dedup store. Use when building queue/stream consumers or debugging duplicate side effects.
- ▌ Embedded Memory Constraints · amey-thakurFit firmware into kilobytes with static allocation, measured stack sizing, and linker-map budgeting. Use when developing on microcontrollers or debugging overflows and fragmentation on-device.
- ▌ Entity Component System · amey-thakurModel game objects as entities with data components processed by systems, and know when ECS complexity pays. Use when structuring game architecture or escaping deep inheritance hierarchies.
- ▌ Github Actions Workflows · amey-thakurWrite CI workflows that are fast, readable, and cheap, with the right triggers, caching, and matrix strategy. Use when setting up or fixing automation on a repository.
- ▌ Cuda Kernel Basics · amey-thakurWrite first CUDA kernels that map work onto the grid, coalesce global memory, and keep enough warps resident to hide latency. Use when hand-writing or reviewing a CUDA kernel and it runs far below the bandwidth or FLOPs the card should reach.
- ▌ String Externalization · amey-thakurMove user-facing text out of code into catalogs with stable keys and context, so translation becomes possible without touching logic. Use when preparing a product for translation or fixing hardcoded strings.
- ▌ Node Backend Setup · amey-thakurBootstrap a Node.js backend with ESM, typed config, graceful shutdown, and structured logging from the start. Use when starting a Node service or hardening one that grew without foundations.
- ▌ Knowledge Transfer · amey-thakurMove understanding from one person to others so critical knowledge does not leave with them. Use before someone changes role or when one person is the only one who understands something.
- ▌ Fine Tuning Vs Prompting · amey-thakurDecide between prompting, retrieval, and fine-tuning with eval-first discipline and honest data requirements. Use when someone proposes fine-tuning or a prompt has hit its ceiling.
- ▌ Agent Code Review Loop · amey-thakurRun an author agent and a reviewer agent in a loop with a strict finding format, a mandatory verification pass, and a convergence rule that ends it. Use when you want agent-to-agent code review that improves the diff instead of spinning forever on style or re-flagging fixed issues.
- ▌ Agent Content Newsroom · amey-thakurRun a publishing cadence with agents that plan a calendar, research and draft against a brief, fact-check claims, and queue posts for human approval. Use when content output is sporadic and quality varies with whoever wrote it.
- ▌ Agent Fundraising Room · amey-thakurPrepare a raise with agents that assemble the narrative, stress-test it as an investor would, and organise diligence material, while the founder owns every conversation. Use when preparing to raise and the story keeps changing between meetings.
- ▌ Agent Handoff Protocol · amey-thakurDesign each handoff between two agents as an explicit artifact contract with a context budget and a rule for what must survive the crossing. Use when work passes from one agent to the next and the receiver keeps losing constraints, re-deriving decisions, or drowning in raw transcript.
- ▌ Agent Human Checkpoint · amey-thakurPlace human approval at the points where being wrong is expensive or irreversible, with enough context to decide quickly. Use when agents perform work that has real consequences.
- ▌ Agent Marketing Studio · amey-thakurProduce campaigns with agents that research the audience, draft variants against a brief, check claims and brand voice, and leave publishing to a human. Use when marketing output is inconsistent or bottlenecked on one person writing everything.
- ▌ Agent Procurement Desk · amey-thakurEvaluate vendors with agents that build a comparable requirement matrix, research each option, check security and data terms, and prepare a recommendation for human sign-off. Use when choosing tools or suppliers and comparisons keep drifting on vendor marketing.
- ▌ Agent Training Academy · amey-thakurTurn internal knowledge into role-based learning paths with agents that build, test, and keep material current as systems change. Use when onboarding is slow because knowledge lives in people rather than in material.
- ▌ In App Messaging · amey-thakurDeliver messages inside the product where they are contextual and non-interruptive, using the right surface for each urgency. Use when a message relates to what the user is doing right now.
- ▌ Failed Payment Recovery · amey-thakurRecover revenue from failed recurring charges with retries, clear notice, and a graceful path back, without harassing customers. Use when involuntary churn from card failures is material.
- ▌ Build System Design · amey-thakurDesign builds that are fast, reproducible, and cacheable, so developers wait less and CI costs less. Use when builds are slow, flaky, or produce different results locally and in CI.
- ▌ Paved Road Adoption · amey-thakurGet teams onto the supported path through incentives and migration support rather than mandates. Use when a better platform exists and teams are not moving to it.
- ▌ Platform As Product · amey-thakurRun an internal platform with users, feedback, and adoption metrics rather than as a mandated standard. Use when platform adoption is poor or teams complain about the tools they are required to use.
- ▌ Roadmap Communication · amey-thakurCommunicate roadmaps with now/next/later horizons, honest commitment levels, and audience-shaped views. Use when publishing product direction or managing the fallout of roadmap changes.
- ▌ Project Retrospective · amey-thakurReview a completed project to extract what should change next time, focusing on systems rather than individuals. Use at the end of a project or a significant phase.
- ▌ Full Text Search Design · amey-thakurDesign a text search feature with the right analyzer, fields, and matching model so results are relevant rather than merely returned. Use when adding search to a product or replacing a LIKE query that no longer works.
- ▌ Zero Cost Abstractions · amey-thakurVerify that abstractions actually compile away by inspecting generated code and measuring, and know the costs that remain. Use when writing performance-critical Rust/C++ or judging whether an abstraction is free.
- ▌ Code Freeze Management · amey-thakurManage a code freeze with a scoped declaration, risk-classed changes, a fast exception process, and a planned thaw. Use when you need to stabilize a codebase ahead of a release, a holiday peak, or a high-stakes event without halting all work.
- ▌ Technical Interviews · amey-thakurPrepare for and perform in technical interviews with a practice system, aloud reasoning, and honest calibration. Use when preparing for coding, system design, or behavioral rounds.
- ▌ Support Response Writing · amey-thakurWrite replies that answer the question, respect the customer's time, and avoid the phrases that make people angrier. Use when writing any customer-facing support message.
- ▌ Dependency Scanning Setup · amey-thakurConfigure automated dependency and vulnerability scanning at a cadence people will actually act on. Use when dependencies drift or vulnerabilities go unnoticed.
- ▌ Plural And Gender Rules · amey-thakurHandle plurals, grammatical gender, and agreement using locale plural categories rather than an if-else on count. Use when a string contains a number or refers to a person or object with gender.
- ▌ Monorepo Workspaces · amey-thakurRun a JavaScript/TypeScript monorepo with workspaces, task orchestration, and internal package versioning that scales. Use when managing multiple packages in one repo or when a growing monorepo's builds and installs get slow.
- ▌ Typescript Generics · amey-thakurWrite TypeScript generics that infer well and stay readable, and know when a generic is not worth it. Use when designing typed reusable functions or APIs, or untangling generic signatures nobody can read.
- ▌ Deliberate Practice · amey-thakurImprove at a skill through focused repetition at the edge of ability with immediate feedback, rather than through accumulated hours. Use when you have plateaued despite continued practice.
- ▌ Context Window Management · amey-thakurBudget tokens across system prompt, history, and retrieval, with compaction that keeps what matters. Use when building long-running LLM applications or debugging context overflow and mid-conversation amnesia.
- ▌ Agent Capacity Planning · amey-thakurKnow what the company can actually take on this cycle, in agent budget and human hours, and refuse work beyond it. Use when everything is committed and nothing finishes.
- ▌ Agent Company Blueprint · amey-thakurCompose specialist agent desks into one operating company with a shared ledger, a weekly cadence, and human approval gates on anything binding. Use when you want agents to run the recurring operations of a business rather than a single project.
- ▌ Agent Context Isolation · amey-thakurGive each agent in a system only the context it needs, so failures stay contained and context stays clean. Use when designing a multi-agent system and deciding what each agent sees and shares.
- ▌ Agent Escalation Ladder · amey-thakurDefine what gets escalated, to whom, and how fast, so problems reach a decision maker at the right moment rather than too early or too late. Use when issues either sit unresolved or interrupt the wrong people constantly.
- ▌ Agent Partnerships Desk · amey-thakurResearch, qualify, and prepare partnership approaches with agents, leaving the relationship and the commitment to a human. Use when business development is ad hoc and partner conversations start without preparation.
- ▌ Agent Pricing Committee · amey-thakurConvene agents to model pricing options, argue them from customer, competitor, and margin angles, and hand a human a decision pack. Use when setting or changing prices and the discussion keeps going in circles.
- ▌ Agent Specialist Router · amey-thakurRoute each request to the agent best suited to it, with a fallback and an explicit unknown path, instead of one generalist handling everything. Use when tasks vary enough that one prompt serves none of them well.
- ▌ Agent Vendor Operations · amey-thakurTrack every vendor's cost, renewal, usage, and access with agents that flag waste and surface renewals before they auto-renew. Use when software spend grows quietly and nobody knows what is still in use.
- ▌ Delivery Tracking · amey-thakurKnow whether a message was accepted, delivered, opened, and acted on, and treat failures as events rather than statistics. Use when messages are assumed delivered and support tickets say otherwise.
- ▌ Pricing Change Migration · amey-thakurChange prices or plan structure without breaking trust or billing, deciding who moves, when, and with what notice. Use when raising prices, restructuring plans, or retiring a legacy tier.
- ▌ Chain Of Thought Prompting · amey-thakurAsk a model to reason before answering when the task needs intermediate steps, and know when it costs more than it gives. Use for multi-step reasoning, and avoid it for simple retrieval or formatting.
- ▌ Role And Persona Prompting · amey-thakurAssign a role to shape expertise, register, and priorities, without pretending it grants knowledge the model lacks. Use when output should read as written by a particular kind of expert for a particular audience.
- ▌ Realtime Data Sync · amey-thakurKeep client state current with server changes using subscriptions, deltas, and resync, without drift or memory growth. Use when a UI must reflect data that other users or systems are changing.
- ▌ Version History UX · amey-thakurKeep and present document history so users can see what changed, who changed it, and restore safely. Use when edits are shared or when accidental loss must be recoverable.
- ▌ Search Indexing Pipeline · amey-thakurGet data into a search index reliably and keep it current, with reindexing, partial updates, and a defined staleness budget. Use when search results lag reality or a schema change requires a full rebuild.
- ▌ Agent Refactoring Workflow · amey-thakurDirect an agent through a refactor in verifiable steps with tests as the safety net, rather than one large rewrite. Use when restructuring code with agent assistance.
- ▌ Architecture Decision Records · amey-thakurCapture each significant architecture decision as a short, immutable record of context, decision, and consequences with a tracked status. Use when a choice is costly to reverse or crosses teams and the reasoning must outlive the people who made it.
- ▌ Bar Raiser Interviewing · amey-thakurInterview as an Amazon-style bar raiser who holds an independent veto and judges each candidate against the long-term hiring bar. Use when you sit on an interview loop as the neutral interviewer accountable for the bar, not for filling the team's open seat.
- ▌ Design Doc Google Style · amey-thakurWrite a Google-style design doc that argues a decision through context, goals, and rejected alternatives before code is written. Use when a change is large enough that picking the wrong approach is expensive to undo.
- ▌ Postmortem Review Board · amey-thakurRun an org-level board that grades incident postmortems against a quality bar, promotes cross-cutting fixes to owned work, and reads across incidents for trends. Use when your organization writes enough postmortems that reviewing them one at a time hides the systemic pattern.
- ▌ Prfaq Working Backwards · amey-thakurWrite an Amazon PR-FAQ that starts from a launch-day press release and hard customer questions so an idea is tested on the customer before it is built. Use when proposing a new product or feature and you need to prove it is worth building.
- ▌ Open Source Maintainer Role · amey-thakurOperate as a company-employed open source maintainer who runs governance, licensing hygiene, and community health for a project the business depends on. Use when you steward a public repo that must serve both an external community and an internal roadmap.
- ▌ Cash Flow Management · amey-thakurManage the timing of money in and out so the business can pay what it owes when it is due. Use when growing fast, when payment terms are long, or whenever runway is under a year.
- ▌ Competitive Strategy · amey-thakurDecide where to compete and how to sustain an advantage, rather than assuming a better product wins. Use when entering a market, responding to a competitor, or explaining why you will win.
- ▌ Issue And Project Tracking · amey-thakurStructure issues, labels, and boards so the tracker reflects reality and answers what is being worked on. Use when the backlog has grown beyond what anyone reads.
- ▌ Gpu Memory Hierarchy · amey-thakurPlace data across the GPU memory tiers so a kernel is limited by math rather than by repeated trips to HBM. Use when a kernel is memory-bound, when deciding what to stage in shared memory or L2, or when register spills are stalling a hot loop.
- ▌ JS Tooling Selection · amey-thakurChoose the JavaScript/TypeScript bundler, test runner, and linter for a project by its type, not by fashion. Use when setting up a toolchain or deciding whether to migrate an existing one.
- ▌ Typescript Narrowing · amey-thakurNarrow union types safely with guards, discriminated unions, and exhaustiveness checks. Use when working with values that could be several types, or when the compiler will not let you access a property you know is there.
- ▌ Agent Dependency Manager · amey-thakurTrack cross-desk and external dependencies so blocked work is visible early and the blocker has an owner. Use when work stalls waiting on somebody else and nobody notices until the deadline.
- ▌ Agent Executive Briefing · amey-thakurProduce a short honest briefing across every desk on a fixed cadence, surfacing decisions needed rather than activity performed. Use when leading a business through agent desks and needing one readable view.
- ▌ Agent Postmortem Council · amey-thakurRun a team of postmortem agents that builds the timeline, analyzes causes, drafts corrective actions, and reviews for blamelessness and completeness. Use after an incident when you need a rigorous, blameless writeup and owned action list instead of a hasty narrative that pins it on a person.
- ▌ Agent Red Team Blue Team · amey-thakurRun attacker and defender agents in a fix-and-re-attack loop so exploitable bugs get found, triaged, fixed, and verified before ship. Use when you want a system probed and hardened by an agent team rather than one pass of review.