How to use Cortex
What's already working, what's still left to connect, and where each piece is waiting.
What this app already does today
A public site
Explains what Cortex is to anyone who joins the team, at the root address.
Sign-in
A password-free entry, plus a Google button that walks through real setup when you're ready for it.
Career quiz
A short set of questions that recommends fields to explore and lets you pick a focus.
Learn
One topic at a time, with video, photo, flashcard, and real-scenario review material where it exists.
Quizzes
Easy, medium, and advanced levels, with a self-check after each one.
Game mode
Solo rounds or a named challenge against a teammate, both earning credits.
Progress
A simple streak, topics learned, quizzes taken, and credits earned. No complicated charts.
Blog
Career-path articles, an interview, and a user story.
Mentoring
Mentor profiles and a request form, with credits reducing the program's cost.
Sample data
Every screen ships with realistic examples, and Settings can clear or restore them.
Works on your phone
Every screen was built and checked at a narrow width, not just on a laptop.
One visual language
A single design system token file paints the whole app, the site, and the component catalog.
What's still left to connect, and where each thing fits
Email sending
Confirmations and reminders. The key already has a reserved spot in .env.example (RESEND_API_KEY).
Backend and database
Today the data lives in your browser. The path to Neon Postgres is already written and tested: paste DATABASE_URL into .env.local, and the same app starts writing to Postgres. Zero lines of code, no screen changes. See src/lib/banco.ts.
Google login
The whole flow is built and switched off: the button on the sign-in screen, the step-by-step guide inside it, and the routes in src/app/api/auth. Paste GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and AUTH_SECRET into .env.local, and it's connected.
The OpenAI API
For writing, summarizing, or answering questions inside the app. The key has its own group in .env.example (OPENAI_API_KEY), and the route is born in src/app/api, on the server, never in the browser.
Notify whoever uses the app through a channel people actually check.
Automations
n8n is already in the project, with the file ready to spin up (n8n/docker-compose.yml) and a guide with two worked examples in n8n/README.md.
Storybook
This app's component catalog, already configured, with tokens applied and accessibility auditing on every component.
Where all of this is learned
Everything in the section above is taught in the workshop. It's not loose research on the internet, it's not trial and error. It's live, step by step, on top of this very project, which already came with all the sockets ready exactly for this.
Join the workshopThe two paths after that
Postgrad and MBA
For those who are already designers and want leadership with AI: AI in processes, in research ops, and in design ops.
Learn moreAI/UX Designer Program
For those who are already designers but don't yet apply AI day to day, and want to start using it.
Learn moreMy next steps
- 1Use the app with real data for a week and note what bugs me.
- 2Write the case for my portfolio, telling the problem and the decision.
- 3Join the workshop to connect the backend, login, and sending.
- 4Publish the case in the UX Unicórnio portfolio list.