人工智能重新设计
- 作者仓库星标 0
- 作者仓库 pythh
- 领域
- 设计与多媒体
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @ugobe007 · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
访问现场并记录: 标题清晰度:是否用一句话阐述了产品价值? Hero CTA:具体(URL 输入、电子邮件)还是模糊(“开始”)?现有的最佳文案:找到一条有效的台词——将其提升为英雄。排版:独特的配对还是通用的单重国际米兰?
在`ideas.md`中编写三种不同的方法,每种方法定义:设计运动、色彩哲学、版式系统、布局范式、签名元素、动画哲学。选择一个并完全提交——在每个 CSS/组件文件的顶部记录所选的样式。反模式:紫色渐变、过度圆角、整页居中的英雄、青色作为主要的金融科技口音。经过验证的黑暗人工智能/金融科技调色板:
元素·规则英雄标题·动作动词+结果,≤6 个单词。例如,*“自动化您的投资管道。”* 英雄副标题 · 命名代理人,说明其职责,以创始人唯一的工作 CTA 标签结尾 · 动词 + 代理人姓名。例如,*“激活 PYTHIA”* 而不是 *“入门”* 管道副本 · 每个步骤 = 代理执行的操作,而不是用户执行的操作
源自产品名称(pythh.ai → PYTHIA,Delphi 的甲骨文) 为其提供一个神话或原型锚以便记忆 写一个句子起源: *“以先于其他人看到未来的 Delphi 高级女祭司命名。”* 如果有用,请定义首字母缩略词(PYTHIA = 预测产量和论文启发式智能代理) 使用名称作为主要 CTA 动词:*“激活皮提亚”*
单个`/activate`路线,`Step`状态:`entry → scanning → results → pipeline`线英雄CTA:步骤1-条目:全屏URL输入,从`sessionStorage`预填充,在前进之前验证。第 2 步 — 扫描:6 步进度跟踪器、交错计时器(1000–2000 毫秒/步)、脉冲代理头像、完成后自动前进。第 3 步 — 匹配结果:排名卡(名称、公司、角色、匹配分数、信号分数、部门标签)。可展开的详细信息:为什么匹配 + 最近的信号 + 电子邮件目标面板。 PYTHIA 洞察总结上面的列表。底部 CTA:全角琥珀色“使用 [Agent] → 运行管道”。
为外展自动化产品构建`src/lib/emailInference.ts`:优先级·模式·置信度1·`firstname@domain`·高2·`firstname.lastname@domain`·高3·`firstinitial.lastname@domain`·中
在构建组件之前生成图像。使用`generate_image`用于: 英雄背景(抽象的深色纹理匹配设计理念) 代理头像(时尚的 AI 图标 - 不是脸,不是抽象艺术) 仪表板/管道 UI 模型(深色模式产品屏幕截图样式) 拒绝任何看起来像抽象艺术、迪斯科球或库存插图的结果。使用更具体的 UI/仪表板语言重新生成。
# AI SaaS Redesign Skill
End-to-end process for redesigning a SaaS landing page and building an interactive AI agent pipeline UX. Follow phases in order.
## Phase 1 — Evaluate the Existing Site
Visit the live site and record:
- **Headline clarity**: Does it state the product value in one sentence?
- **Hero CTA**: Specific (URL input, email) or vague ("Get Started")?
- **Best existing copy**: Find the one line that works — elevate it to the hero.
- **Typography**: Distinctive pairing or generic single-weight Inter?
- **Color dominance**: Any single overused color (e.g., cyan) to reduce?
- **Redundant sections**: Anything duplicated by a better visual element?
Save findings before proceeding.
## Phase 2 — Design Philosophy
Write three distinct approaches in `ideas.md`, each defining: Design Movement, Color Philosophy, Typography System, Layout Paradigm, Signature Elements, Animation Philosophy. Select one and commit fully — document the chosen style at the top of every CSS/component file.
**Anti-patterns:** Purple gradients, excessive rounded corners, full-page centered hero, cyan as dominant fintech accent.
**Proven dark AI/fintech palette:**
- Background: `oklch(0.13 0.01 264)` (deep obsidian)
- Primary accent: `oklch(0.696 0.17 162.48)` (emerald green)
- Secondary accent: `oklch(0.769 0.188 70.08)` (amber orange)
- Fonts: Space Grotesk Bold (display) + JetBrains Mono (data values)
Full token set: `references/design-tokens.md`
## Phase 3 — Copy Strategy
| Element | Rule |
|---|---|
| Hero headline | Action verb + outcome, ≤6 words. e.g., *"Automate your investment pipeline."* |
| Hero subheadline | Name the agent, state what it does, end with the founder's only job |
| CTA label | Verb + agent name. e.g., *"Activate PYTHIA"* not *"Get Started"* |
| Pipeline copy | Each step = what the agent does, not what the user does |
| Closing line | Always end the agent intro with the user's minimal obligation |
**Highest-converting closing pattern:** *"You approve. You show up. That's it."*
## Phase 4 — Name the AI Agent
1. Derive from the product name (pythh.ai → PYTHIA, the Oracle of Delphi)
2. Give it a mythological or archetypal anchor for memorability
3. Write a one-sentence origin: *"Named for the high priestess of Delphi who saw the future before anyone else."*
4. Define the acronym if useful (PYTHIA = Predictive Yield & Thesis Heuristic Intelligence Agent)
5. Use the name as the primary CTA verb: *"Activate PYTHIA"*
Agent appears in: hero activity card, "Meet Your [Agent]" section with avatar + origin story, all pipeline milestone copy, footer tagline.
## Phase 5 — Activation Flow Architecture
Single `/activate` route, `Step` state: `entry → scanning → results → pipeline`
Wire hero CTA:
```tsx
sessionStorage.setItem("pythia_url", url);
navigate("/activate");
```
**Step 1 — Entry:** Full-screen URL input, pre-populate from `sessionStorage`, validate before advancing.
**Step 2 — Scanning:** 6-step progress tracker, staggered timers (1000–2000ms/step), pulsing agent avatar, auto-advance on completion.
**Step 3 — Match Results:** Ranked cards (name, firm, role, match score, signal score, sector tags). Expandable detail: WHY MATCHED + RECENT SIGNAL + EMAIL TARGETS panel. PYTHIA insight summary above list. Bottom CTA: full-width amber "Run Pipeline with [Agent] →".
**Step 4 — Pipeline Feed:** Left: milestone stream (auto-advancing, 3–8s stagger). Right: sidebar with stage tracker + confirmed meetings. Meeting milestones show amber Approve / Reschedule / Decline buttons. On approve: milestone confirms, meeting added to sidebar.
Milestone types: `match | pitch | outreach | response | meeting | brief`
Full component patterns: `references/pipeline-component-patterns.md`
## Phase 6 — Email Inference Engine
Build `src/lib/emailInference.ts` for outreach-automation products:
| Priority | Pattern | Confidence |
|---|---|---|
| 1 | `firstname@domain` | High |
| 2 | `firstname.lastname@domain` | High |
| 3 | `firstinitial.lastname@domain` | Medium |
| 4 | `lastname@domain` | Medium |
| 5 | `firstinitiallastname@domain` | Low |
| 6 | `pitches@`, `deals@`, `dealflow@` | Fallback (pitch) |
| 7 | `info@`, `contact@`, `hello@` | Fallback (generic) |
Domain inference: maintain `FIRM_DOMAIN_MAP` for known firms. For unknowns, slugify (lowercase, strip "Capital/Ventures/Partners/Fund/Group", remove spaces, append `.com`).
Surface in two places:
- Match results expanded card → "PYTHIA EMAIL TARGETS" panel with confidence badges
- Pipeline outreach milestones → chip row of tried addresses, checkmark on primary
Full implementation: `references/email-inference-template.ts`
## Phase 7 — Image Generation
Generate images **before** building components. Use `generate_image` for:
- Hero background (abstract dark texture matching design philosophy)
- Agent avatar (sleek AI icon — not a face, not abstract art)
- Dashboard/pipeline UI mockup (dark-mode product screenshot style)
**Reject any result** that looks like abstract art, a disco ball, or a stock illustration. Regenerate with more specific UI/dashboard language.
Upload with `manus-upload-file --webdev` and use the returned CDN URL directly in code.
## Sections: Remove vs. Keep
| Section | Decision | Reason |
|---|---|---|
| "How [Agent] Works" step list | Remove if activation flow exists | The interactive flow IS the explainer |
| "Powered by / Backed by" logo bar | Remove on dark backgrounds | Dark logos on dark bg are invisible |
| Generic 3-up feature cards | Replace with agent story | Agent narrative converts better |
| Live signals / data table | Keep | Demonstrates real product value |
| Testimonials | Keep | Social proof anchors credibility |
按说明文件中的顺序排列。
第一阶段——评估现有场地
第二阶段——设计理念
第三阶段——复制策略
第 4 阶段 — 为 AI 代理命名
第 5 阶段 — 激活流程架构
文件/命令 -> ideas.md · oklch(0.13 0.01 264) · oklch(0.696 0.17 162.48) · oklch(0.769 0.188 70.08) · references/design-tokens.md · /activate · Step · entry → scanning → results → pipeline
内容校验值 -> 674bdca01ffd
当前原文的自动摘译,尚未人工审校。
第一阶段——评估现有场地
访问现场并记录: 标题清晰度:是否用一句话阐述了产品价值? Hero CTA:具体(URL 输入、电子邮件)还是模糊(“开始”)?现有的最佳副本:找到有效的一行——将其提升为英雄。排版:独特的配对还是通用的单重国际米兰?