Skip to content

Latest commit

 

History

History
165 lines (125 loc) · 4.48 KB

File metadata and controls

165 lines (125 loc) · 4.48 KB

Promotion Plan — EasyTalk AI

Positioning

One-liner: Click any UI element. Copy an AI-ready component spec.

Problem: AI coding tools need precise UI context, but describing elements manually is slow and error-prone.

Solution: EasyTalk AI turns a single click into a structured, AI-readable spec.


Target Users

User Why They Care
Product designers Hand off UI specs to AI dev tools without writing selectors
Frontend devs using AI Give Claude Code / Cursor / Codex exact element context
AI coding users Stop describing UI in words — click and paste
Indie hackers Speed up UI iteration with AI
Design system builders Extract component specs for documentation

Core Message

English: EasyTalk AI helps you turn any webpage UI element into an AI-ready component spec.

Chinese: EasyTalk AI 可以把网页上的任意 UI 元素转换成 AI 能理解的结构化组件描述。

Short tagline: Click any UI element. Copy an AI-ready component spec.


Launch Channels

1. GitHub (Day 1)

  • Polish README
  • Add repository topics
  • Create v1.0.0 release
  • Add screenshots to README

2. Personal Website / Blog (Day 1–3)

  • Write a short post: "I built a Chrome extension that turns clicks into AI specs"
  • Include a demo GIF
  • Link to GitHub

3. Twitter/X (Day 1–3)

  • Short demo clip (30s)
  • Before/after tweet: "Describing UI to AI vs. just clicking it"
  • Tag relevant communities

4. 小红书 (Day 1–3)

  • Short tutorial in Chinese
  • Show the workflow: click → copy → paste → AI generates code
  • Keep it practical and visual

5. 即刻 (Day 1–3)

  • Share as a daily build/maker project
  • Ask for early feedback

6. V2EX (Day 3–7)

  • Post in "分享创造" section
  • Chinese-focused: explain the problem and solution clearly
  • Include installation instructions
  • Expect both positive and critical feedback

7. Chrome Web Store (After polishing)

  • Submit after privacy page and screenshots are ready
  • Tag as Developer Tools / Productivity

8. Product Hunt (After stable feedback)

  • Only after real user testimonials exist
  • Prepare a demo video and launch post

Example Posts

Twitter/X

"Describing UI to AI tools is painful. 'The blue button with 12px padding, rounded corners...'

Now I just click it. ✨

EasyTalk AI generates an exact spec — selectors, styles, layout, everything.

Paste → AI understands. No description needed.

Free, open source, no data leaves your browser."

V2EX

"分享一个给 AI 编程用的 Chrome 扩展:点击网页元素 → 复制 AI 能理解的组件描述

用 Cursor / Claude Code / ChatGPT 写前端的时候,最烦的就是描述界面元素: '那个蓝色的按钮,padding 12px,圆角 8px,hover 变深……'

我做了一个 Chrome 扩展,点击任意元素就能生成结构化描述:

  • CSS Selector、类名、ID
  • 视觉属性(颜色、字体、间距、阴影、边框)
  • 布局上下文(父容器、flex 方向、兄弟元素)
  • 动画和 $keyframes

复制 → 粘贴到 AI → 搞定。

纯本地运行,无 API 调用,不上传任何数据。 开源 MIT。

欢迎试用和反馈 👇"


Screenshot Checklist

  • Extension popup UI (300px width)
  • Blue overlay + tooltip on a webpage element
  • Generated YAML output
  • Generated Markdown output
  • Cmd+C component spec output
  • Multi-select mode with colored overlays
  • Pasted output in ChatGPT / Claude
  • Short demo GIF (15–30s)

Chrome Web Store Checklist

  • 128×128 icon
  • 48×48 icon
  • 16×16 icon
  • At least 1 screenshot (1280×800 or 640×400)
  • Short description (132 chars max)
  • Detailed description
  • Privacy policy URL (use GitHub PRIVACY.md)
  • Developer email
  • Test install from clean Chrome profile
  • Verify all permissions are explained

GitHub Launch Checklist

  • README is polished
  • PRIVACY.md exists
  • License file present
  • Repository description is set
  • Topics are set
  • v1.0.0 release tag created
  • Packaged .zip attached to release
  • Screenshots in README

Long-Term Content Ideas

  • "How to use AI to refactor any UI component" (tutorial)
  • "From click to component: EasyTalk AI workflow" (video)
  • "5 ways AI coding users waste time describing UI" (blog post)
  • Comparison: Manual description vs. EasyTalk AI spec
  • Integration examples: Cursor, Claude Code, ChatGPT