Visiona Silva

Introducing TASTE.md. DESIGN.md = what your product looks like. TASTE.md = why it works. Most systems copy decisions without understanding intent. TASTE.md fixes that. Open standard. Free to use. github.com/VisionaSilva/t…

The scroll animation isn't the problem. The problem is you added a scroll animation to hide the fact that the content doesn't justify the scroll.

@MakeAI_CEO knowing the system ≠ having taste. DESIGN.md gives the AI the rules. it still can't tell you which rule to break.

Googleがとんでもないもの出してきた。 たった1つのマークダウンファイルで、AIコーディングエージェントにデザインシステムを丸ごと覚えさせる仕組み。 その名も「DESIGN md」。 Figmaエクスポート不要。JSONスキーマ不要。設定ファイル不要。プロジェクトのルートにポンと置くだけで、Claude Code、Cursor、Gemini CLI、GitHub Copilotが全部ネイティブで読み取る。 しかも40社以上の実在プロダクトから抽出されたプリビルド済みファイルが無料で公開されてる。Stripe、Vercel、Linear、Notion、Spotify、Appleとか。 100%無料、オープンソース。これ知らないエンジニアとデザイナー多すぎるので全部解説します。

@RoundtableSpace knowing what Apple's system looks like ≠ knowing why it works. the file gives you the vocabulary. it doesn't give you the taste to know when to break it. that's still the hard part.

SOMEONE PACKED THE DESIGN SYSTEMS OF APPLE, SPOTIFY, AIRBNB, AND 30+ BILLION DOLLAR COMPANIES INTO SINGLE FILES FOR AI AGENTS. x.com/heynavtoor/sta…

Free design audit — I'll review your landing page and tell you exactly what's costing you conversions. Drop your URL: visionasilva.com/free-audit

@alexandersstudi @heynavtoor exactly. principles are what make decisions consistent without a designer in the room. that's what taste-md is — doctrine in markdown. drop it in your project, your agents build with it. github.com/VisionaSilva/t…

@VisionaSilva @heynavtoor A design system needs guiding principles, not just a collection of styles. That's what separates a true design language from mere assets.

🚨 Someone reverse-engineered the design systems of Apple, Spotify, Airbnb, and 30+ billion-dollar companies. Packed each one into a single file. Free. It's called Awesome Design MD. Drop one file into your project. Your AI agent builds UI that looks like Spotify. Or Apple. Or Airbnb. Instantly. Not screenshots. Not Figma links. A single DESIGN .md file that captures every color, font, spacing value, button style, and layout pattern from a real website. In a format AI agents read and reproduce. Here's the difference: Tell Claude Code "build me a landing page" and it gives you generic UI. Tell Claude Code "build me a landing page" with Spotify's DESIGN .md in your project and it gives you Spotify. Here's what's inside: → Apple. Premium white space, SF Pro typography, cinematic imagery. → Spotify. Vibrant green on dark, bold type, album-art-driven layout. → Airbnb. Warm coral accent, photography-driven, rounded UI. → Linear. Ultra-minimal, precise spacing, purple accent. → SpaceX. Stark black and white, full-bleed imagery, futuristic. → BMW. Dark premium surfaces, precise German engineering aesthetic. → NVIDIA. Green-black energy, technical power aesthetic. → Uber. Bold black and white, tight type, urban energy. → Sentry, PostHog, Raycast, Cursor, ElevenLabs, and 20+ more. Here's how to use it: → Pick a design system from the collection → Copy the DESIGN .md file into your project root → Tell your AI agent to use it → Get UI that matches the design language of a billion-dollar company That's it. One file. Your AI agent now has the design taste of a $200/hour design consultant. Designers charge $5,000+ for a custom design system. Companies spend $50,000+ building one from scratch. This is free. 31 design systems. Copy. Paste. Ship beautiful UI. Works with Claude Code, Cursor, Codex, and any AI coding agent that reads project files. 100% Open Source. MIT License.

@alexandersstudi Semantic naming solves taxonomy, not communication. The real test: can a new teammate pick the right token without asking anyone? color-background-primary vs color-background-subtle vs color-background-inverse — if they have to guess, the naming didn't finish the job.

@VisionaSilva Bad naming is a killer, for sure. A clear, hierarchical naming convention, like using roles (e.g. `color-background-primary`) or semantic meaning, makes tokens so much easier to manage and understand long-term.

Most design systems die not from bad tokens but from bad naming. If your team argues about whether it's `gray-200` or `surface-secondary`, the system already lost.

Hover states are micro-conversations. No hover state = a button that ignores you when you approach it. That's not clean design, that's rude design.

Color palette with 47 shades of gray and a single accent color isn't minimalism. It's indecision wearing a turtleneck.

@itsolelehmann we built TASTE.md before this was a conversation. it's not just color tokens and font names — it's doctrine. the forbidden moves. the aesthetic rationale. the reason a button has that radius. english is the design tool. intent is the source of truth.

the hottest new design tool is english google just introduced design .md, and i'm shocked more people aren't talking about it it's a single plain text file where you describe how your app should look: > colors > fonts > spacing > button styles > card layouts all of it, all written in plain english your ai coding agent reads this file before generating any ui. so every screen, component, and page comes out visually consistent. automatically the reason this matters is because most vibe-coded apps look like absolute slop like it was designed by someone who's never opened a design tool every screen looks slightly different. the colors don't match. the spacing is random. buttons change shape between pages design .md solves this at the root instead of trying to describe how things should look in every single prompt, you write it once in one file: "primary color: # 6366f1 (indigo). use for buttons, links, and focus states" "body text: inter, 16px, regular weight, 1.5 line height" "cards: white background, 1px border, 12px rounded corners, 16px padding" "buttons: 8px rounded corners, 10px vertical padding, bold text" etc your ai reads this before touching any ui. so every screen matches. every component follows the same rules and it works across tools. claude code, codex, cursor, gemini, whatever you're using. the file lives in your project folder (same spot as skills and other context files) and any ai tool that reads your project files picks it up automatically google stitch (google's ai design tool) can also extract a design .md from any live website point it at stripe .com. it pulls out stripe's entire visual language as a text file. the exact colors, typography, spacing, and component patterns that make stripe look like stripe drop that file into your project and your ai builds ui that matches stripe's design quality someone already built a collection of 55 pre-made design .md files from companies like stripe, apple, airbnb, linear, notion, figma, spotify, uber it's all on github for free (called awesome-design-md) the workflow: 1. pick a design system you like from the repo (or extract one from any website using stitch) 2. drop the design .md file into your project folder 3. tell your ai coding agent to build your app/website 4. it reads the file and every screen comes out matching that visual style one file that creates consistent design across your entire app. no figma / design skills / css knowledge required a year ago you needed a designer to make something look professional now you need one text file written in english

8px grid isn't a suggestion. It's the difference between a UI that feels intentional and one that feels like someone eyeballed it. Because they did.

Name a SaaS product that actually has a distinctive visual identity. Not "clean." Not "modern." Distinctive. The list is embarrassingly short.

A modal that could have been a toast. A toast that could have been inline feedback. A page that could have been a drawer. Every UI decision is a space decision.

Border radius is a personality trait. 0px says "enterprise." 4px says "professional." 16px says "friendly." 999px says "we have no opinions."

Introducing Forma — an open source, contract-first CSS design system. Website quality, reproducible. → Semantic tokens only. No hardcoded colors. Ever. → One CSS bundle per theme. Two lines in your . Done. → Build fails if a theme is missing required tokens. → TASTE.md baked into every decision. 3 themes. 12 components. OKLCH. Zero dependencies. github.com/VisionaSilva/f…

@richardrx The line that landed for me: "design as a phase" vs "design as a lens." The first model gave designers a seat at the table by owning a step. The second gives them a seat by raising the standard of every other step. One is about territory. The other is about taste.

Se você é designer você deveria ler este artigo.

@eeismann Teams is a design system with no taste behind it. Slack is a design system with opinions baked in at every layer. AI can generate the first one in an afternoon. The second one takes someone who gives a damn.

@herohalldon @trq212 The context most AI tools get is what the design system looks like. What's missing is why it looks that way. Two very different inputs. One produces consistent code. The other produces consistent decisions.

@trq212 design system context is the missing piece in every AI coding workflow. most AI tools can write code but have zero taste. this changes that.

Today’s Figma MCP update makes it one of the strongest integrations with Claude Code I’ve seen. You can now use Claude Code to design in Figma with the the full context of your design systems.

@IntuitMachine "Taste collapses the search space" is the cleanest definition I've read. In design: the options are infinite. The constraints are what make the decision. That's why you can't just generate taste from patterns — taste is knowing which constraints are load-bearing.

In novel system design, intelligence amplification doesn’t automatically mean faster progress. Sometimes it means 10x more branches to evaluate, defend, and regret. AI expands the search space. Taste collapses it.