Craft
Skills
What I actually use, and five briefs you can hand to an agent. These are working rules, not a costume of someone else's taste.
Product
Flows, prototypes, and the sentence a feature has to earn before it ships.
Cosverse AIStart from the job a person is trying to finish, not from the component library.
Cosverse, case studiesA rough screen early, so the argument happens before the code hardens.
Product workEngineering
The interface layer I reach for when a product needs routing, server code, and a fast front.
Cosverse, this siteThe contract between the screen and the system. If it is muddy, the UI cannot save it.
Full-stack work since 2020Still the floor. The 30-day streak was how I learned to finish a screen.
ArchiveApplied AI
Several models in one place, with a bill and a memory that make sense to a person.
Cosverse AIImages in, a decision a person can check. Plants, helmets, plates.
Varaksha, helmet studyTabular problems. Who leaves, and what the data can actually support.
Churn modelRooms
Making a student entrepreneurship cell function on the technical side.
E-Cell, VIT BhopalNotes on the tools, so the thinking is inspectable.
This site, MediumBriefs
Copy one into an agent when you want the decision to sound like this practice.
One room for many models
If a person needs several models, the product should not make them keep three tabs and three bills in their head.
Name the person who was not in the repo
A farmer, a rider, a customer about to leave. If you cannot name them, you are still rehearsing.
The sentence has to be true
Do not invent a metric, a user count, or a trophy score to make a page feel finished.
Draw the flow before the framework
Argue about the path on a rough screen. Code is the wrong place to discover the product is confused.
A title is a calendar
Founding member is a queue of concrete decisions. Ship the next true thing, then say what shipped.