New Features are awesome and some of them are for good. GitHub brought you some secret features that are no more a secret. and is spreading like a 🔥.
Let's not waste time and strike is down...
Making your README Platter
Prerequisite : Markdown writing skills
Step 1 : Making a repository.
-
+sign is where you have to hit. - select new repository.
Step 2: Naming Conventions.
Name the Repository same as your GitHub Username. No other way allowed.
Then a special message pops out see below.
Make the Repository Public as to show the changes and Readme Platter to whoever visit your profile.
Step 3: Give a Nice touch..
This is what's on your part to play with. I am done here.
If you wants any of the suggestions. or do not know what to write.
You can consider my repository as an example.
Hey 👋🏼 I’m Utkarsh Yadav
I build production-ready systems from day one — fast to ship, cleanly architected, and designed to scale without rewrites
Best suited for early-stage startups, founders, and teams that value speed and correctness.
Full-Stack Engineer • Systems Builder • Early-Stage Problem Solver
🧠 What I Do
Next.js • React • Node.js • TypeScript RAG Pipelines • LangChain • Vector Databases Kafka • RabbitMQ • Event-Driven Architecture AWS • GCP • Docker • Kubernetes
⚡ Full-Stack Engineering
Scalable APIs, clean UI, maintainable codebases
🤖 AI & LLM Systems
LLMs integrated into real products, not demos
🌐 Distributed Systems
High-throughput, fault-tolerant backends
☁️ Cloud & DevOps
Infrastructure that scales without drama
🛠 Tech Stack
🚀 How I Think
- I optimize for long-term velocity, not quick hacks
- I care deeply about system design & trade-offs
- I write code that teammates actually enjoy maintaining
- I ship fast — but…
Top comments (1)
I haven't tried this yet, but one of the early screenshots I saw from GitHub showed that you can use your
.githubrepo, instead of a<username>repo, and that will also work.