Authentication and sessions
Steam authentication links an external identity to protected routes and account actions.
SKINSFURY — A Full-Stack Gaming Marketplace
An independent product developed as a complex, multilingual platform for selling gaming items, with user accounts and operational workflows.
Independent product developed by Diogo Oliveira · Not client work · No commercial performance metrics are presented.
01 · Project overview
Turning a multi-step trade into a coherent product.
SKINSFURY is an independent product, not a project commissioned by a client. The public experience helps users review an offer, confirm the matching action through Steam and follow its status in their account.
The work goes well beyond a brochure website. The codebase brings together public content, authenticated flows, account areas, API communication, localisation and protected internal interfaces.
- Product type
- Independent gaming marketplace
- Main framework
- Next.js 15 App Router
- Languages
- English and Portuguese
- Public website
- skinsfury.com
02 · Technical challenges
Several systems, one understandable journey.
Asynchronous flows
Inventory, offer creation and status changes need clear intermediate, success and error screens.
Operations and payments
Offers, protection periods, payments and reconciliation have to stay aligned between the user, Steam and internal management.
API boundaries
Components use authenticated helpers and server-side bridge routes to keep responsibilities separate.
International structure
Language routes, translations and SEO metadata need to stay aligned.
Protected administration
Extensive operational tools require permissions, explicit confirmation for sensitive actions and separation from the public website.
03 · Architecture & development
A modular Next.js application with clear boundaries.
The App Router organises public pages, the authenticated product, the account area and server-side endpoints.
React and TypeScript support components and types, while Tailwind CSS and reusable components keep the responsive interface consistent.
NextAuth handles Steam sign-in and sessions. Authenticated helpers and bridge routes connect the interface to external services without exposing private credentials in the browser.
Sanity manages editorial content. The administration system is separate from the public experience and covers the management of users, inventory, bots, offers, payments, promotions, partners and business rules.
04 · Product experience
From first visit to using the platform.
The public landing page explains the offer and the process before sign-in. After Steam authentication, the application organises the inventory, the offer calculation, the payment method and the next steps of the trade.
The images show real product interfaces without exposing emails, wallets, Steam Guard codes, offer IDs or administration tools.
05 · Key features01 02 03 04 05 06 07 08
Features confirmed on the public website and in the code.
Steam authentication
Official Steam sign-in creates a session without asking for passwords or Steam Guard codes.
Inventory and offers
Authenticated views to select items, create offers and follow their status.
Account area
Profile, security, history, payment details and related tools organised by route.
Offers and Steam Guard
Protected tools inspect offers, validate items and direction, and confirm Steam actions only after explicit review.
Payments and withdrawals
Methods, limits, fees, statuses, protection periods, payment queues and reconciliation are part of the operational flow.
Multilingual experience
Routes and interfaces in English and Portuguese.
Content and support
FAQ, support, policies, partnerships and a blog integrated into the application.
Operational dashboard
Protected areas support users, inventory, bots, offers, payments, promotions, partners and business rules.
06 · Technologies used
A modern stack chosen for the product.
- Next.js 15 App Router
- React
- TypeScript
- Tailwind CSS
- NextAuth with Steam
- REST API integrations
- Payment integrations
- Sanity
07 · Development approach
Complexity organised into parts that can evolve.
Routes by responsibility
Marketing, application, account, blog and administration are separated so they can evolve without becoming one hard-to-maintain tree.
Reusable interfaces
Navigation, forms, dialogs, account views and cards reduce duplicated behaviour.
Explicit states and errors
Processing, success, error and account states have their own interfaces.
Presented safely
The case study explains the architecture without publishing credentials, private endpoints, real data or internal dashboards.
08 · Final product
A working platform, not a static concept.
The public product is live, and the codebase confirms a much broader application. It shows the ability to organise a substantial React and Next.js codebase, connect authentication and APIs, build responsive journeys and keep the product evolving technically.