ai saas redesign

Design Community

Skill notes

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?

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:

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

Phase 4 — Name the AI Agent

Derive from the product name (pythh.ai → PYTHIA, the Oracle of Delphi) Give it a mythological or archetypal anchor for memorability Write a one-sentence origin: "Named for the high priestess of Delphi who saw the future before anyone else." Define the acronym if useful (PYTHIA = Predictive Yield & Thesis Heuristic Intelligence Agent) Use the name as the primary CTA verb: "Activate PYTHIA"

Phase 5 — Activation Flow Architecture

Single /activate route, Step state: entry → scanning → results → pipeline Wire hero CTA: 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] →".

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@ugobe007 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
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?

02
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:

03
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

04
Phase 4 — Name the AI Agent

Derive from the product name (pythh.ai → PYTHIA, the Oracle of Delphi) Give it a mythological or archetypal anchor for memorability Write a one-sentence origin: *"Named for the high priestess of Delphi who saw the future before anyone else."* Define the acronym if useful (PYTHIA = Predictive Yield & Thesis Heuristic Intelligence Agent) Use the name as the primary CTA verb: *"Activate PYTHIA"*

05
Phase 5 — Activation Flow Architecture

Single `/activate` route, `Step` state: `entry → scanning → results → pipeline` Wire hero CTA: 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] →".

06
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

07
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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.