Nazar Kvyatkovsky

The pattern works for any MCP server where you need multi-account access - not just Linear.

The key is TOOL_PREFIX. It namespaces every tool so they don't collide: org1_linear_search_issues → hits Org 1 org2_linear_search_issues → hits Org 2 No collisions, full access to both.

Claude only lets you connect ONE Linear org at a time. If you lead across multiple products - you're stuck switching between them. We hit this on our team. Here's the solution 🧵

Over-engineering is one of the most expensive mistakes mobile teams make - and it usually starts on day one. Here’s how I think about building mobile architecture that survives real-world chaos and actually ships. linkedin.com/pulse/build-ap…

Great reflection exercise. Prompt I used: ➡️ "Now that you can remember everything I’ve ever typed here, point out my top five blind spots and strengths."

🔥 Strengths - Execution speed - Strong product intuition - Full ownership mindset - Fast learning - Quality obsession

When you work with AI daily and feed it your tasks, ideas, and decisions, it becomes the only “teammate” that sees everything. So I asked mine to break down my work style - and the results hit hard.

Check the updated Human Interface Guidelines & new UI kits: Toolbars - developer.apple.com/design/human-i… Adopting Liquid Glass - developer.apple.com/documentation/… Icons - developer.apple.com/design/human-i… Human Interface Guidelines - developer.apple.com/design/human-i…

Continuity Across Devices: • Design for flow: user should feel like they’re “continuing” not “switching” when moving from iPhone to iPad to Mac. • Keep your core structure/components consistent—adapt visuals, not meaning.

Biggest design shift from Apple just dropped at #WWDC25: “Liquid Glass.” If you want your app to feel truly native in iOS, iPadOS, and macOS, here’s what you need to know and how to start using it. 🧵👇