I'm a frontend developer who builds web interfaces, landing pages, portfolio sites and web apps — mainly with React, Next.js, TypeScript and Tailwind CSS. Alongside that I build custom Discord bots and automation tools, which is where a good share of my client work comes from.

What I care about on the frontend is the stuff users actually feel: pages that load fast on a mid-range phone, layouts that don't break at awkward widths, interfaces that work with a keyboard and a screen reader, and markup that search engines can read properly.

I also handle the backend pieces a project needs — API routes, form handling, authentication, a database layer — enough to ship what I build end to end. I'm straight with clients about the line: if a project needs heavy backend architecture or infrastructure work, that's not my specialism and I'll say so up front.

Where I'm strongest

• Performance is a requirement, not a polish step. Images sized and lazy-loaded, fonts subset, bundles kept small, third-party scripts questioned. A landing page that takes six seconds on mobile has already lost the visitor.
• Accessible by default. Semantic HTML, real focus states, keyboard-operable components, labelled forms, colour contrast that passes. It costs nothing when built in from the start and is expensive to retrofit. Full conformance still needs manual testing with assistive tech, so I flag what I've verified rather than claiming a blanket pass.
• Responsive means every width, not three breakpoints. Layouts tested through the awkward in-between sizes where most sites quietly break.
• Components over copy-paste. A design system small enough to hold in your head, so adding a section later doesn't mean rebuilding one.
• SEO handled in the markup. Proper heading order, meta and Open Graph tags, descriptive alt text, sensible URLs — the parts that are actually under a developer's control.
• Handover you can use. Readable code, a setup guide and notes on how to change the things you'll want to change.

Public source, links resolve, code is there to read.

Repo: Itzzikram/Rimuru · TypeScript

Multipurpose bot covering moderation, automated giveaways, social integrations and server utilities. Multipurpose bots usually rot — features pile up until every addition risks breaking something older. This one is built as isolated command modules over a typed Prisma data layer, so features go in independently and schema changes are migrations instead of guesswork.

Closest reference point if you want a custom bot: same structure, adapted to your server's roles, rules and workflows.

Notes

• Command modules are self-contained and independently testable
• Prisma gives a typed boundary between handlers and the database, so schema drift shows up at compile time
• Scheduled work like giveaway resolution survives a restart instead of living in memory

TypeScript Discord.js Prisma MongoDB

flowchart LR
    DS["Discord gateway<br/>events and interactions"] --> RT["Event router"]
    RT --> CMD["Command modules<br/>slash commands"]
    RT --> EVT["Event handlers<br/>joins, messages, reactions"]
    CMD --> SVC["Service layer<br/>shared logic"]
    EVT --> SVC
    SCH["Scheduler<br/>giveaways, reminders"] --> SVC
    SVC --> DB["Database<br/>Prisma and MongoDB"]
    SVC --> EXT["External APIs<br/>webhooks, integrations"]
    SVC --> RES["Response builder<br/>embeds and components"]
    RES --> DS

Repo: Itzzikram/DemonZ-Ripper · TypeScript · 5 stars

A monorepo that captures 3D assets from WebGL scenes and exports them to GLB, glTF 2.0, OBJ and Unreal UAsset. The part I'd point a frontend client at is the interface: a React UI streaming live progress from a long-running backend job, which is a genuinely awkward UI problem — partial state, failures mid-run, and progress that has to stay readable while it updates.

Notes

• React frontend driving and monitoring a long-running job without freezing or lying about state
• Fastify and Puppeteer backend orchestrating headless browser work
• Four export formats generated from one intermediate representation
• Containerised with deployment configuration included

TypeScript React WebGL2 Fastify Puppeteer Docker

Repo: Itzzikram/Discord-Advance-Cloner · TypeScript + Rust

Automation tool that replicates server structure — roles, channels, permissions, webhooks, threads, emojis — against an API that aggressively rate-limits. The interesting work is failure handling: exponential-backoff retry and fallback paths so a partial failure degrades instead of dying halfway through.

Notes

• Exponential backoff with fallback, so transient errors don't abort a whole run
• Cross-platform builds for Windows, Linux and macOS
• Performance-sensitive path in Rust behind a TypeScript interface

TypeScript Rust Docker

Repo: Itzzikram/Discord-Unban-Platform · Rust

Included honestly: this one is me pushing past my comfort zone rather than a core skill. It's a moderation platform built to learn Rust and event-driven architecture — Kafka for task orchestration, Redis to coordinate rate limits across workers, Postgres for an audit trail, JWT and RBAC for approvals.

I'm not selling myself as a distributed-systems engineer. I'm showing that I'll take on unfamiliar territory and see it through, which is usually the thing that actually matters on a project.

Rust Kafka Redis PostgreSQL Docker

Landing pages and portfolio sites are a large part of my work, so here's the actual pipeline rather than a vague promise of quality.

flowchart LR
    BRIEF["Brief or Figma<br/>goals and content"] --> BUILD["Component build<br/>React and Tailwind"]
    BUILD --> NEXT["Next.js<br/>static or incremental rendering"]
    CONTENT["Content source<br/>MDX, JSON or CMS"] --> NEXT
    FORMS["Forms and leads<br/>API route to email or CRM"] --> NEXT
    NEXT --> CI["GitHub Actions<br/>build and checks"]
    CI --> EDGE["Vercel or Netlify<br/>CDN edge delivery"]
    EDGE --> USER["Visitor"]
    EDGE -.->|"audited"| LH["Lighthouse<br/>performance, a11y, SEO"]

What that buys you

• Statically rendered where possible, so pages arrive fast and rank properly
• Content editable without touching layout code
• Forms that actually reach your inbox or CRM, with validation and spam handling
• Every push built and checked before it goes live
• Measured against Lighthouse rather than assumed to be fine

How a project runs

GitHub activity metrics