Ankit Karki

1.9K posts

Ankit Karki banner
Ankit Karki

Ankit Karki

@ankitdotkarki

Product Design SecurityPal || #HalaMadrid

Nepal Katılım Ocak 2015
1.1K Takip Edilen897 Takipçiler
Ankit Karki
Ankit Karki@ankitdotkarki·
By the end, the theatre had some glossy eyes, whistles, and claps and I was right there clapping along 👏 If you think Nepali movies “suck” or you care about stories that matter go watch this one. It deserves your ticket.
English
0
0
0
13
Ankit Karki
Ankit Karki@ankitdotkarki·
A unflinching look at the Nepali Badi community, told with the kind of honesty Nepali cinema rarely dares to attempt. @swastimakhadka ? Absolute powerhouse. Her performance pulls you in. Hands down one of her best performances!
English
1
0
0
15
Ankit Karki retweetledi
Lenny Rachitsky
Lenny Rachitsky@lennysan·
My biggest takeaways from @jenny_wen (design lead at @AnthropicAI): 1. The traditional design process is breaking down. The classic discover-diverge-converge loop that designers have relied on for years doesn’t work when engineers can spin up seven coding agents and ship a working version before a designer finishes exploring options. 2. Design work is splitting into two distinct modes. The first is supporting execution: consulting with engineers as they build, giving feedback, polishing in code. The second is setting short-range vision, now scoped to three to six months instead of multi-year roadmaps. The vision work is still critical because when everyone can build anything fast, someone needs to point the team in a coherent direction. 3. Build trust through speed, not perfection. Anthropic ships products early, labels them research previews, and then iterates publicly based on real feedback. Jenny argues that what actually degrades a brand isn’t launching something rough; it’s launching something rough and then going silent. If you ship fast, respond to feedback visibly, and keep improving, users will trust you more, not less. 4. The most overlooked hire in design right now is the cracked new grad. Most companies are hiring senior designers with deep experience. Jenny argues that early-career people with blank slates, fast learning curves, and no attachment to legacy processes may be uniquely suited to this moment. They don’t carry baked-in rituals that are now obsolete, and their lack of expectations can actually be an advantage. 5. Chat as an interface isn’t going away. Despite expectations that chatbots were a temporary stop on the way to richer UIs, Jenny sees chat as a permanently valuable interface because it offers infinite flexibility. But she expects a hybrid future where models increasingly generate UI elements on the fly for specific tasks (like the interactive widgets Claude recently shipped) while chat remains the connective tissue between them. 6. Jenny went from design director (12 to 15 reports) back to IC. She questioned whether middle management had a safe future and wanted hands-on time during a period of rapid change. The IC time is giving her hard skills she wouldn’t have gained while managing. 7. AI will likely get better at taste and judgment. Jenny says designers may be holding onto “taste” as a moat too tightly. But someone still has to be accountable for what ships, the same way an engineer is accountable for AI-generated code. 8. Hire three archetypes: strong generalists, deep specialists, and “cracked new grads.” Strong generalists are “block-shaped” (80th percentile across multiple skills). Deep specialists are top 10% in one area. Cracked new grads—the most overlooked—have no baked-in processes and learn new tools fastest. 9. Figma is still essential, but for different reasons than before. Jenny says Figma remains the best tool for rapidly exploring 8 to 10 different design directions on a canvas, something that coding tools handle poorly because they’re too linear and create investment bias toward one direction. For micro-level visual and interaction decisions, spatial exploration still beats sequential iteration. 10. Low-leverage work is often the highest-leverage thing a manager can do. Jenny pushes back on the conventional management advice to ruthlessly prioritize only high-leverage tasks. She points to leaders who obsessively dogfood the product, repro bugs, and personally fix small issues—activities that seem “below” a senior leader but create deep product familiarity, set a cultural tone of care, and earn trust from the team in ways that strategic planning never can. Watch our full conversation: youtube.com/watch?v=eh8bcB…
YouTube video
YouTube
Lenny Rachitsky@lennysan

Design lead for Claude: The classic design process is dead. Here's what's replacing it. Jenny Wen (@jenny_wen) leads design for Claude at @AnthropicAI, was previously director of design at @Figma, and a designer at @Dropbox, @Square, and @Shopify. In our in-depth conversation, we discuss: 🔸 Why the classic discovery → mock → iterate design process is becoming obsolete 🔸 What a day in the life of a designer at Anthropic looks like, including her AI tool stack 🔸 Whether AI will eventually surpass humans in taste and judgment 🔸 Why Jenny left a director role at Figma to return to IC work 🔸 The three archetypes Jenny is hiring for now This conversation changed how I think about the future of design. Listen now 👇 youtu.be/eh8bcBIAAFo

English
49
120
1.4K
430K
Ankit Karki retweetledi
Corey Ganim
Corey Ganim@coreyganim·
This guy ran 400+ Cowork sessions and found the 17 practices that actually matter. Here's the full implementation checklist: Today (30 min) - Context Architecture □ Create folder: /Claude-Context/ □ Add about-me. md → Your role, priorities, 1-2 examples of your best work □ Add brand-voice. md → Tone + 2-3 samples of YOUR writing + phrases you hate □ Add working-style. md → "Ask before executing. Show plan first. Never delete without confirmation." □ Go to Settings → Cowork → Edit Global Instructions □ Paste: "Read _MANIFEST.md first. Load Tier 1 files only. Ask clarifying questions before starting." This Week - Project Setup □ Create _MANIFEST.md in your busiest project folder: → Tier 1: Source-of-truth docs (read first) → Tier 2: Domain folders (load when relevant) → Tier 3: Archive (ignore unless asked) □ Install 2 plugins: Productivity + one for your role □ Set up one /schedule task: → "Every Monday 7am, summarize my calendar and Slack, save to /weekly-briefings" Task Prompting Formula □ Define end state, not process □ Add uncertainty handling: "If unclear, flag it instead of guessing" □ Batch related tasks into one session □ For parallel work: "Spin up subagents to research these 4 vendors simultaneously" The Meta-Lesson Cowork rewards system engineering, not prompt engineering. Invest 2 hours in setup → write 10-word prompts that produce client-ready output.
Nav Toor@heynavtoor

x.com/i/article/2027…

English
9
41
363
76.4K
Ankit Karki retweetledi
Lenny Rachitsky
Lenny Rachitsky@lennysan·
Design lead for Claude: The classic design process is dead. Here's what's replacing it. Jenny Wen (@jenny_wen) leads design for Claude at @AnthropicAI, was previously director of design at @Figma, and a designer at @Dropbox, @Square, and @Shopify. In our in-depth conversation, we discuss: 🔸 Why the classic discovery → mock → iterate design process is becoming obsolete 🔸 What a day in the life of a designer at Anthropic looks like, including her AI tool stack 🔸 Whether AI will eventually surpass humans in taste and judgment 🔸 Why Jenny left a director role at Figma to return to IC work 🔸 The three archetypes Jenny is hiring for now This conversation changed how I think about the future of design. Listen now 👇 youtu.be/eh8bcBIAAFo
YouTube video
YouTube
English
88
304
3.1K
1.5M
Ankit Karki retweetledi
Mark Gadala-Maria
Mark Gadala-Maria@markgadala·
Claude Code in Figma isn't a feature. It's a hostile takeover of the entire dev handoff industry. Every "design-to-code" tool for the past decade has tried to make developers' lives easier. Figma just said "what if we made developers optional?" Here's what nobody's saying: the designer-developer handoff was never a technical problem. It was a political one. A negotiated border between two tribes with different languages, different incentives, and different ideas about what "done" means. Claude Code in Figma doesn't build a better bridge. It annexes the territory. The devs celebrating this as "finally, accurate specs!" are missing the plot. You're not getting better handoffs. You're getting automated out of the handoff entirely. That Figma file doesn't need you to interpret it anymore. It interprets itself. The real winners? Designers who always secretly resented waiting three sprints for their vision to get "technically feasible'd" into something unrecognizable. The real losers? Not developers. They'll just move up the stack. It's the entire ecosystem of handoff tools, design system consultants, and "bridging the gap" conference talks that just became solutions to a problem that no longer exists. Figma didn't integrate Claude Code. They declared independence from your sprint planning.
Figma@figma

Tired: code or canvas Wired: code AND canvas Introducing Claude Code to Figma

English
67
24
516
200.2K
Ankit Karki retweetledi
Cricket in Asia
Cricket in Asia@ICCAsiaCrickett·
Unbelievable crowd support for Nepal at the Wankhede stadium, Mumbai!🤯🇳🇵 World cricket truly needs Nepal to rise. ❤️
English
12
274
4.2K
52.3K
Ankit Karki
Ankit Karki@ankitdotkarki·
@pchamal How on companies? I do extended water fasts annually and understand how it works for humans.
English
0
0
0
29
Ankit Karki retweetledi
Pukar C. Hamal 🏔🗽 🌁
1) You can ask AI 2) If you don’t know how to do 1, you can ask AI how to ask the AI 3) If you don’t know how to do 2, see 1 Do you get it now?
English
0
1
3
225
UI/UX Savior
UI/UX Savior@UiSavior·
Are you a: - Graphic Designer - Illustrator - UI/UX Designer - Motion Graphics Artist - Brand Strategist - Art Director - Web Designer - Interaction Designer - Visual Designer - Product Designer - Creative Director - UX Researcher - Packaging Designer - Environmental Designer - Game Designer - 3D Designer Drop a "Hi!" in the comments and let’s connect with fellow design enthusiasts!
English
439
24
560
52.1K
Ankit Karki retweetledi
Figma
Figma@figma·
Your design is the prompt Bring your existing ideas to life with Figma Make #Config2025
English
98
668
4.5K
323.6K
Ankit Karki retweetledi
luis.
luis.@disco_lu·
Wanna see some quick off the cuff examples from behind the scenes on Figma Make?
English
20
24
579
106.4K
Ankit Karki retweetledi
Natasha Tenggoro
Natasha Tenggoro@natashatenggoro·
Figma Buzz is here! Proud of this one. It took time, care, and a lot of iteration. We built Buzz with brand designers and marketers in mind, making it easier for both to work side by side in Figma and turn brand assets into production-ready content. It’s in open beta starting today, can’t wait for you all to try it! Also, tune in tomorrow at 12:40pm PST for our design deep dive 👀 @figma #config2025
English
41
81
1K
59.6K
Ankit Karki retweetledi
Noah Levin
Noah Levin@nlevin·
Whew! Today at #Config2025 was the biggest set of launches we’ve ever had, and I’m so proud of this amazing team 🤩 Between Grids, Figma Sites, Figma Buzz, Figma Make, and Figma Draw — we’ve doubled our product offering! Check it out 👉 config.new 🧵
Noah Levin tweet media
English
53
230
2.1K
207.7K
Ankit Karki retweetledi
Dylan Field
Dylan Field@zoink·
With Figma Sites, I’m excited for teams to publish their designs directly to the web with a single click. #Config2025
English
64
136
1.7K
168.1K
Ankit Karki retweetledi
SecurityPal AI
SecurityPal AI@security_pal·
🏆 After an intense month-long mentorship + 2-day hackathon ⚡️, we're thrilled to announce the winners of Nepal Hacks @ SecurityPal: AI Unleashed, powered by NAAMII. Congratulations 🎉 to the top 3 teams 🥇🥈🥉 for their ingenuity, hard work, and impactful AI-powered security and compliance solutions. 🤖🔒 🙏 Thanks to all participants, mentors, judges & partners! #NepalHacks
SecurityPal AI tweet mediaSecurityPal AI tweet mediaSecurityPal AI tweet mediaSecurityPal AI tweet media
English
0
3
7
1.6K