How I Built Nexus Skill Swap Platform

Start with a swap, not a feed

Nexus exists because Kush Gangwal wanted a skill swap platform, not another timeline. A user offers a skill, another user requests one, and the product has to make a match feel safe enough to start a session.

That constraint decided the stack. React.js for the client, Node.js for the API, SQLite so the first version could deploy on Vercel, and Auth0 so identity was not a weekend password table.

The four loops that matter

Search has to work by skill name. Authentication has to stay out of the way. A session has to exist as a record, not a chat dump. A rating has to land after the session so the next stranger has evidence.

If those four loops work, Nexus is a product. If they do not, it is a form. Kush Gangwal Full Stack Developer work is usually this: pick the loops, then write the smallest API that keeps them honest.

What I would change next

A later Nexus would move off SQLite when write volume grows and would add better matching than exact skill strings. The current version is already a complete demonstration of the Nexus Skill Swap Platform idea.