Get live statistics and analysis of Kris Puckett's profile on X / Twitter

If you're building an iOS app with Claude Code - copy and paste this into your CLAUDE.md file. It prevents 90% of the issues I hit in the first month: Essential Rules for iOS work with @claudeai 1. Never let AI modify .pbxproj files. Create files with Claude Code, add them to Xcode manually. One corrupted project file will waste hours. 2. Document platform gotchas immediately. Hit an iOS 26 API issue? Add it to CLAUDE.md that session. "NO .background() before .glassEffect()" saved me from repeating that mistake 50+ times. 3. Use feature flags for experimental code. Toggle new features on/off without rebuilding. Makes rolling back instant when something breaks at 11pm. 4. Always request debug logging. Ask Claude Code to add Logger statements for complex flows. Future you will thank past you when debugging async camera issues. 5. Test after every change!! Clean build folder (Cmd+Shift+K), run on device, verify in console. Catch issues before they compound. 6. Keep conversations focused on single components. Don't ask to "refactor the whole app" Smaller scope = better results. 7. Document what changed in session. End every major change with a markdown file explaining what broke, how it was fixed, and rollback steps. I built a performant, full featured iOS app this way. Zero project corruption. Every session leaves the codebase better than it found it.

I challenged myself to build Epilogue almost entirely using @claudeai Claude Code - going from zero to launch without traditional design tools. Just my words, vision in my head, and endless amounts of feedback. I'm pretty proud of how it turned out.

Dang this is pretty rad instrument.com/work/nike-digi…

Still can't believe who @figma got as a guest speaker for Config.

Do you ever look at your color palette and ask: “What the #FFFFFF was I thinking?”

I’ve never been more stoked to join a company. Thanks @Dropbox @DropboxDesign

Yo this @figma Make presenter should have been the entire keynote MC - incredible presence, timing, and confidence. Public speaking is a craft and skill - this is a fantastic demo in that regard.

It's a gift to type these words: I'm joining @DropboxDesign. I can't thank y'all enough for the support, DMs, and passing my info along. I couldn't have done this without this amazing community. I'm so stoked to get started.

I challenged myself to build Epilogue almost entirely using @claudeai Claude Code - going from zero to launch without traditional design tools. Just my words, vision in my head, and endless amounts of feedback. I'm pretty proud of how it turned out.

I've never been more grateful to type these words: started a new role with @Shopify. Can't thank y'all enough for all the support and love the past few months. Joining such a legendary design team is a wild dream come true.

It's a gift to type these words: I'm joining @DropboxDesign. I can't thank y'all enough for the support, DMs, and passing my info along. I couldn't have done this without this amazing community. I'm so stoked to get started.

While I’m making big announcements, I’m unbelievably excited to join @InVisionApp working for @TheOlmstead and the team. Such an honor to join InVision and I can’t wait to get started.

Life wouldn’t be an adventure without epic challenges to conquer. I’m leaving @invisionapp, taking a few days to breathe, then I’m off to find my next epic challenge.

Couldn’t sleep last night out of excitement. It’s like the first day of school: trapper-keeper and all. I’m on a plane headed to SF to meet up with the incredible new team @mercury. So grateful to be on this journey as a new design manager.

If you're building an iOS app with Claude Code - copy and paste this into your CLAUDE.md file. It prevents 90% of the issues I hit in the first month: Essential Rules for iOS work with @claudeai 1. Never let AI modify .pbxproj files. Create files with Claude Code, add them to Xcode manually. One corrupted project file will waste hours. 2. Document platform gotchas immediately. Hit an iOS 26 API issue? Add it to CLAUDE.md that session. "NO .background() before .glassEffect()" saved me from repeating that mistake 50+ times. 3. Use feature flags for experimental code. Toggle new features on/off without rebuilding. Makes rolling back instant when something breaks at 11pm. 4. Always request debug logging. Ask Claude Code to add Logger statements for complex flows. Future you will thank past you when debugging async camera issues. 5. Test after every change!! Clean build folder (Cmd+Shift+K), run on device, verify in console. Catch issues before they compound. 6. Keep conversations focused on single components. Don't ask to "refactor the whole app" Smaller scope = better results. 7. Document what changed in session. End every major change with a markdown file explaining what broke, how it was fixed, and rollback steps. I built a performant, full featured iOS app this way. Zero project corruption. Every session leaves the codebase better than it found it.

It's been a wild few months. Finished a design contract with Facebook. I got to work with the most amazing humans @underbelly. Now I'm just resting up, without a job. The wildest of all the wild is that in 2 weeks @KatyMPuckett and I are becoming parents. #girldad & stoked

I'm a 7 on the #Enneagram. It means I'm an enthusiast. This little number helped me understand so much about myself. What's your number? If you haven't taken the test, I'll give away 3 codes. Just comment below.