dprakash2101
- 29 skills
- 0 followers
- 9 hours ago last updated
- ▌ Production Debugging · dprakash2101Investigate live or production-like .NET failures using logs, traces, metrics, dumps, and configuration evidence. Use for production diagnosis; do not mutate production state or deploy fixes without explicit authorization.
- ▌ Dependency Management · dprakash2101Assess, remove, add, or upgrade .NET/NuGet dependencies safely. Use for unused-package cleanup, package warnings, framework compatibility, vulnerability remediation, or explicit dependency changes; not for routine product code with no dependency decision.
- ▌ Distributed Workflows · dprakash2101Design or change .NET message handlers, background services, retries, idempotent operations, and multi-system workflows. Use when work crosses process/service boundaries or can execute more than once.
- ▌ Dotnet Implementation · dprakash2101 bundleImplement production .NET or ASP.NET Core behavior within an existing codebase. Use for features, enhancements, fixes after diagnosis, and requested refactoring; not for review-only or investigation-only work.
- ▌ Google Bigquery Dotnet · dprakash2101 bundleImplement or review Google BigQuery access from .NET with Google.Cloud.BigQuery.V2. Use only for BigQuery queries, jobs, result mapping, authentication, performance, or query-cost concerns.
- ▌ Google Firestore Dotnet · dprakash2101Implement or review Google Cloud Firestore persistence in .NET. Use only for Google.Cloud.Firestore document models, reads/writes, queries, transactions, batches, indexes, or Firestore cost/modeling decisions.
- ▌ API Endpoint Deprecation · dprakash2101Plan, implement, or review deprecation and eventual removal of a customer-facing API endpoint. Use for endpoint replacement, version retirement, deprecation metadata, migration windows, usage verification, or explicit removal work.
- ▌ Google Cloud Pubsub Dotnet · dprakash2101 bundleImplement or review Google Cloud Pub/Sub publishers and pull subscribers in .NET. Use only for Google.Cloud.PubSub.V1 messaging, subscriber workers, acknowledgement behavior, or Pub/Sub delivery concerns.
- ▌ Relational Database Dotnet · dprakash2101 bundleImplement or review relational database access from .NET for PostgreSQL or Oracle. Use for ADO.NET/provider SQL, connections, transactions, commands, provider-specific mapping, or database retry decisions; compose with ef-core-safety when EF Core behavior is involved.
- ▌ Aspnet Core API Development · dprakash2101Create a new customer-facing ASP.NET Core API endpoint or API surface. Use for new controllers/minimal endpoints and their request, validation, service, integration, response, and OpenAPI flow; not for small changes to an existing endpoint.
- ▌ Code Quality · dprakash2101Improve or assess quality of changed C#/.NET code under Clean-as-You-Code and analyzer/Sonar expectations. Use for requested quality work or while polishing a substantive implementation; do not trigger repository-wide legacy cleanup.
- ▌ Git Workflow · dprakash2101Perform safe Git branch, stage, commit, and push operations for engineering work. Use only when the user requests Git operations or they are an explicit required step; never infer permission to commit or push.
- ▌ Unit Testing · dprakash2101Add or improve focused automated tests for production .NET behavior. Use for new or materially changed testable business logic and regression fixes; optional for explicitly identified POCs.
- ▌ Context Reset · dprakash2101Reorient work when the user interrupts, replaces the objective, or redirects an in-progress coding task. Use only when the newest instruction makes prior intent or plans obsolete.
- ▌ Safe Terminal · dprakash2101Run and recover from terminal commands safely, especially after malformed, corrupted, or unexpectedly failing CLI commands. Use for shell troubleshooting or commands that could affect tools, credentials, configuration, or data.
- ▌ Ef Core Safety · dprakash2101Design, implement, or review Entity Framework Core queries, writes, migrations, and DbContext usage. Use only when a .NET task changes EF Core persistence behavior or investigates database performance/correctness.
- ▌ Dotnet Security · dprakash2101Threat-model, implement, or review security-sensitive .NET and ASP.NET Core behavior. Use for authentication, authorization, secrets, untrusted input, uploads, outbound URLs, cryptography, or an explicit security review; not for routine style review.
- ▌ Poc Development · dprakash2101Build a clearly identified .NET proof of concept or experiment to test technical feasibility. Use only when the user or repository context explicitly marks the work as POC, spike, prototype, or experimental.
- ▌ Bug Investigation · dprakash2101Diagnose a .NET defect from symptom to root cause and minimal fix. Use for unexpected behavior, exceptions, regressions, data loss, or production defects; diagnosis alone does not authorize code changes.
- ▌ Production Hotfix · dprakash2101Diagnose and implement an urgent production fix with minimal blast radius and fast evidence-based validation. Use only when the request or context identifies a production incident or hotfix.
- ▌ Exception Handling · dprakash2101 bundleDesign or review .NET exception handling, including catch boundaries, recovery, translation, cancellation, and logging ownership. Use when adding or changing exception paths or centralized handlers; load the API reference only for customer-facing HTTP boundaries.
- ▌ Production Logging · dprakash2101Design or review structured .NET logging for production and high-volume APIs. Use when adding/changing logs, defining logging ownership, reducing noise/cost, or protecting sensitive observability data.
- ▌ Shared Code Impact · dprakash2101Assess and constrain changes to shared .NET components. Use before modifying shared helpers, middleware, extensions, DTOs/models, mappers, DI registration, auth, serialization, SDKs, or common libraries.
- ▌ API Contract Safety · dprakash2101Preserve and evolve ASP.NET Core API contracts safely. Use when changing routes, verbs, headers, parameters, DTOs, JSON, status/errors, enums, auth, versioning, or public interfaces.
- ▌ Dotnet Architecture · dprakash2101 bundleDesign or assess architecture for substantial .NET and ASP.NET Core changes. Use for new APIs, major features, new integrations, or layering decisions; not for routine localized edits that preserve an established design.
- ▌ Targeted Validation · dprakash2101Choose and run proportionate validation after a coherent code change. Use near completion of implementation, fixes, refactors, or dependency changes; not after every edit.
- ▌ Code Review · dprakash2101Review .NET changes for concrete correctness, regression, security, contract, concurrency, and test risks. Use for review requests, pull requests, or diffs; do not modify code unless separately requested.
- ▌ Diff Review · dprakash2101Review the final working-tree diff for scope, regressions, secrets, and accidental changes. Use before declaring code-changing work complete or before staging a commit.
- ▌ Task Router · dprakash2101Classify a software request just enough to select a safe, proportionate workflow. Use at the start of implementation, investigation, review, testing, or Git work when the needed workflow is not already obvious.