Taste memory: naksha learns what you like
Compare real design directions side by side, tell naksha which ones work for you, and every later design starts from your taste instead of generic defaults.
New commands
/design-variants <task> [--count 2-5]builds 2–5 genuinely different directions for the same brief (3 by default), with a side-by-side comparison page.- Every pair differs on at least two of layout, type, color, density and ornament.
- If you have a taste profile, most directions lean into it and one "Wildcard" deliberately doesn't.
- Your constraints and brand apply to every direction.
/naksha-taste approve|reject <direction> [because …]records what you like and don't. With no arguments, it shows your taste profile.- Older signals fade: half weight after 90 days, ignored after 180.
- A direction you liked for one kind of project and rejected for another isn't treated as a conflict.
/design-variants Design a pricing page for a B2B analytics product
/naksha-taste approve A because the type hierarchy is clear; reject C: too busy
/design Build the checkout page ← now starts from your taste
/design and /naksha-status also read your taste profile. Taste is a preference: your request, constraints and brand always win. It's stored in your project's own .naksha/project.json and never sent anywhere.
30 roles, one source of truth
- naksha's team is now 30 roles: 28 specialists plus the Design Manager and Creative Director. Previously the "26" didn't match anywhere: the adapters listed 22, and the README and the site each showed a different 26.
- The Cursor, Windsurf, Gemini CLI and Copilot adapters, and the README team grid, are now generated from one roster. CI checks that they stay in sync, that every role appears on the site, and that the role count is correct wherever it's stated.
Upgrade
claude plugin update naksha # marketplace installs
git pull # inside your naksha-studio cloneFull changelog: https://github.com/Adityaraj0421/naksha-studio/blob/main/CHANGELOG.md