usmanasifbutt
- 5 skills
- 0 followers
- 6 hours ago last updated
- ▌
- ▌ Django Backend Engineering · usmanasifbutt bundleEngineering standards for building Django/DRF backend services — multi-brand factory architecture, an ObjectSerializer + DataScrubber pipeline, Keycloak/Principal auth, an in-house Celery task wrapper, PostgreSQL-native upserts, structlog, and safe migrations. Load this before writing or reviewing any backend feature (views, models, serializers, tasks, queries, auth, caching, search) in a Django service. Also load when scaffolding a NEW Django service so it inherits these conventions.
- ▌ Production React Engineering · usmanasifbutt bundleHow to build a production, server-rendered React frontend the disciplined way — a multi-tenant/multi-brand layered structure, hand-rolled component primitives with CSS Modules, a custom SSR router, plain Redux + a custom Fetcher framework (no React Query), Keycloak-via-BFF-cookie auth with role predicates, an HTTPApi/fetch client, a Redux-integrated search abstraction over a hosted search SaaS or Elasticsearch, Formik+Yup forms, lightweight SVG charts, and code-split loadable components. Load this BEFORE writing or reviewing ANY frontend code — components, hooks, routes, Redux state, API calls, auth/protected routes, forms, search, charts, config/feature flags, or tests — and when scaffolding a new React frontend that should follow these conventions.
- ▌ Production Infrastructure Devops · usmanasifbutt bundleHow to run production infrastructure and delivery the disciplined way — Terraform (a versioned reusable-modules repo consumed by thin PR-automated live configs), AWS networking/VPC/EKS/IAM, Kubernetes via Helm + Helmfile, GitOps with ArgoCD, managed data services (RDS/Redis/broker/search) wired in through an instance→inventory→attachment pattern, secrets via a parameter store + External Secrets, observability (Prometheus/Thanos/CloudWatch + uptime/on-call/error-tracking as code), and the delivery side — multi-stage Docker images, cached GitHub Actions pipelines, content-addressed image tags, GitOps-driven rolling deploys, and revert-based rollback. Load this BEFORE writing or reviewing ANY infrastructure or delivery code — Terraform modules/live config, VPC/IAM/security groups, EKS/node groups, Helm charts/Helmfile values, ArgoCD Applications, secrets wiring, DNS/CDN/certificates, Dockerfiles, docker-compose, CI/CD workflows, or deployment/rollback plans — and when bootstrapping a new service, environment, or
- ▌ Production Safe Django Migrations · usmanasifbutt bundleHow to write Django schema & data migrations that deploy to a live, high-traffic PostgreSQL database with zero downtime — using a timeout-aware migration base class, concurrent indexes, lock/statement timeouts, expand-contract multi-release changes, batched RunPython, and a migration linter. Load this BEFORE writing, reviewing, or editing ANY migration (makemigrations output, RunPython/RunSQL, indexes, adding/removing/altering columns, constraints, foreign keys, or data backfills) in any Django service — and when setting up migration safety in a new Django service.