Mitko Tschimev

[Sergej Kunz @deacix]

On 1inch's 7th birthday, I am able to take a moment to reflect and be proud of everything we have achieved as a team.

Seven years ago, 1inch was created with the goal of making DeFi more efficient, more secure, and putting the user first.

During this time, we have made our mark on DeFi, introducing many innovations that have now become central to our industry. This includes the creation of DEX aggregation back in 2019, the intent-based approach to cross-chain swaps, and one of the most extensive suites of APIs, now used by the biggest names in crypto, including Coinbase, OKX, Binance, MetaMask, Ledger, and more.

Thinking back to our launch, DeFi was a niche concept. However, it is now about to become a key part of the global finance. As an industry, we are set to experience significant transformation, and only those that adapt while maintaining their core identity will survive.

1inch is perfectly positioned for this future.

Finally, I would like to say thank you to everyone who supported us over the years, both inside and outside of 1inch. This is just the beginning. It's time for the next chapter.

Watch this space.

[Mitko Tschimev @MTschimev]

7/ Process evolves weekly:
• `.cursorrules` (architecture)
• `implement-SKILL.md` (checklist)

Reviewers teach agents. Agents learn.

Agents don't replace review. They shift what reviewers review.

Part 4 of AI automation series. Full writeup in bio.

[Mitko Tschimev @MTschimev]

We built AI agents that write production code.

Here's what reviewing agent code actually looks like: 🧵

[Mitko Tschimev @MTschimev]

6/ PR description quality matters.

Agent writes:
• What changed
• Why
• Testing approach
• Rollback plan

Good description → trust faster → approve faster.

Consistency beats variability.

[Sergej Kunz @deacix]

Trying something new.

I've been wanting to explain @1inch in a way that actually feels alive — not whitepapers, not jargon. So I'm starting Founder Stories: a series where I walk through how 1inch works through different multiverse worlds.

Episode 1 is about Pathfinder. In a futuristic universe, jumping between galaxies means finding the optimal route across a sea of options. That's exactly what Pathfinder does for your swap.

Made with AI. First try. Be gentle 😄

[1inch Devs @1inchdevs]

If you’re a Web3 dev, the rules change every day
But it only takes minutes to catch up

Build trading agents & integrate 1inch APIs with a single prompt

Just use the 1inch Business MCP server - or install it as a Claude skill.

npx skills add 1inch/1inch-ai

[Mitko Tschimev @MTschimev]

If you've consolidated your design system in Figma:

One page or multiple files?
What worked? What broke?

(Shout-out to [Ilya Kolebayev](https://t.co/PEL21YUe0r) for helping with the PoC.)

[Mitko Tschimev @MTschimev]

Design system in Figma: one page or many files?

We're consolidating everything into **one Figma page**—all components, all compositions.

Why? Integration with code should be *way* easier.

One export target. Simpler CI. Less "which file has the latest button?" chaos.

[Mitko Tschimev @MTschimev]

The trade-off:

✓ Easier automation (design-to-code, token exports)
✗ Harder to navigate at scale?
✗ Collaboration conflicts when 5 designers work on the same page?

We're testing if one page can handle 40+ components without breaking.

[Mitko Tschimev @MTschimev]

@pencilit What's your design-to-code stack?

Have you made it work with:
• Figma + MCP?
• https://t.co/NAiM5DypHI (@pencilit) or Stitch?
• Something else?

Drop your setup 👇

https://t.co/1TEbwIRDwm

[Mitko Tschimev @MTschimev]

Design systems: Figma looks good, but agentic coding workflows? Not so much.

I'm exploring https://t.co/sjcRwid0l1 (@pencilit) + Google Stitch for design-to-code automation.

The goal: Figma ↔ https://t.co/sjcRwid0l1 ↔ code (bidirectional sync)

Tried many setups. None feel optimal yet.

[Mitko Tschimev @MTschimev]

@pencilit The breakthrough will be tooling that treats design systems as *living code* — not export artifacts.

[Mitko Tschimev @MTschimev]

8/8

Part 3 of our Jira-agent automation series.

Full article:
https://t.co/YIKdZBBK2s

[Mitko Tschimev @MTschimev]

1/7

We let an AI agent write production code in CI.

Jira ticket → GitHub Actions → full PR with tests + review.

No human touches the keyboard.

Here's the agent chain:

[Mitko Tschimev @MTschimev]

7/8

Ticket → PR in one run.

✅ Self-reviews
✅ Tests (unit + integration + E2E)
✅ Pushes branch
✅ Transitions Jira

Your team reviews the PR, not the ticket.