Skip to main content
The Collective// 06 Members

THE MINDS
BEHIND YANTRA.

The actual builders behind Yantra across architecture, frontend systems, backend infrastructure, scaffolding, documentation, and the shared product shell. No placeholders here.

KR

KrishKrishKrish

Product Architecture / Core Experience

Largest repo footprint across product systems, route logic, and engineering documentation.

Contributions

46 commits
  • Pushes the main product shape across dashboard systems, shared flows, and launch-facing surfaces.
  • Carries the heaviest footprint through feature code, docs, and API-adjacent implementation.
  • Keeps Yantra feeling like one system instead of a stack of disconnected pages.
Repo footprint
src/features / docs / app/api
RS

RishiRishiRishi

Frontend Surfaces / Responsive Quality

Frontend lane owner for responsive cleanup, public-facing surfaces, and higher-fidelity interaction quality.

Contributions

17 commits
  • Takes point on mobile fit, screen-size stability, and Lighthouse-minded frontend polish.
  • Assigned to the public certificate, portfolio, and Algorithm Void experience lane.
  • Keeps new surfaces aligned with the current Yantra visual language instead of inventing a second system.
Repo footprint
team brief owner for UI, Lighthouse, certificate, portfolio
TB

Tobe ChukwuTobe ChukwuTobe Chukwu

Backend / API Infrastructure

Backend-heavy footprint centered on services, routes, and data-connected system support.

Contributions

26 commits
  • Moves the server-side layer forward through backend services and route work.
  • Owns the strongest backend footprint in the current repo history.
  • Supports the data and API contracts that public and protected surfaces depend on.
Repo footprint
backend/src / app/api / supabase
PG

Pavan GopalaPavan GopalaPavan Gopala

Setup / Classroom Scaffolding

Infrastructure and support footprint across classroom scaffolding, layout touches, and engineering docs.

Contributions

9 commits
  • Owns the setup-and-support lane that makes later feature work easier to ship.
  • Pushes classroom placeholder structure, environment setup, and deployment-facing docs.
  • Helps keep the shell around Yantra coherent while deeper systems are still landing.
Repo footprint
app/classroom / docs/engineering / layout support
SW

SwayamSwayamSwayam

Frontend Support / Style Passes

Frontend support footprint across shared features, components, and the style layer.

Contributions

5 commits
  • Supports the UI lane with feature updates and shared component iteration.
  • Touches both styling and component structure to tighten the feel of the build.
  • Adds useful momentum in the layers users actually see first.
Repo footprint
src/features / src/components / src/styles
IB

IbrahimIbrahimIbrahim

Feature Support / Shared Layout

Early supporting footprint across shared feature work and top-level app structure.

Contributions

3 commits
  • Contributes to shared frontend surfaces and layout-level support where needed.
  • Helps steady the base application shell as new public and protected routes expand.
  • Acts as a support lane across the product instead of a single isolated feature.
Repo footprint
src/features / app/layout.tsx
JOIN THE BUILD // SHAPE THE FUTURE //JOIN THE BUILD // SHAPE THE FUTURE //JOIN THE BUILD // SHAPE THE FUTURE //JOIN THE BUILD // SHAPE THE FUTURE //

OPEN SOURCE.

We are constantly looking for visionaries to expand the capabilities of Yantra. Contribute to curriculum design, core engineering, and AI systems.