Superpowers Style Prompt Creation Note

assetactive

Superpowers Style Prompt Creation Note

Source: superpowers-style-prompt-creation-note.md (ingested 2026-03-28)

• I created the Superpowers-style plan at /C:/Users/mesha/Desktop/GitHub/github.com/morphism-systems/morphism/docs/superpowers/plans/brand-theme-finalization.md. It captures the visual thesis, positioning, file scope, and the execution checklist for the hybrid editorial-paper plus clean-digital AI look you described. It is currently untracked.

Paste this into Claude Code as the working prompt:

You are working in the Morphism monorepo at:

C:\Users\mesha\Desktop\GitHub\github.com\morphism-systems\morphism

Read these first:

  1. AGENTS.md
  2. docs/reference/design/brand-and-design-system.md
  3. docs/superpowers/plans/platform-elevation-and-audit.md
  4. docs/superpowers/plans/brand-theme-finalization.md

Task: Finalize the Morphism public website brand/theme and landing-page positioning so it reads as minimal, VC/YC/market-oriented, and operationally credible.

Target outcome: The site should feel like a hybrid of:

  • editorial paper / old-school scientific publication / documentary aesthetics
  • clean digital AI product design

Desired cues:

  • subtle paper or print texture
  • archival / publication composition
  • serif display moments
  • red highlighter / annotation / markup accents
  • crisp modern UI panels
  • dynamic command window / terminal motif
  • restrained motion
  • strong information hierarchy
  • strong buyer clarity above the fold

It must NOT feel like:

  • generic purple dark-mode SaaS
  • glassy particle-heavy AI startup branding
  • an academic research lab homepage
  • a museum-piece editorial site with weak product clarity

Primary positioning: Morphism governs AI-assisted engineering across repos, teams, and workflows.

Homepage message hierarchy:

  • Headline should be close in sharpness to: "Govern AI-assisted engineering."
  • Subhead should emphasize policy checks, audit trails, rollout controls, and workflow discipline
  • Proof points should be simple and market-legible: works in CI, multi-repo, audit export, open-source core
  • Mathematical language should move below the first screenful

Implementation scope:

  • switch default theme from violet-theorem to midnight-editorial
  • simplify and flatten the logo
  • remove the current particle/mesh-heavy hero treatment
  • redesign the hero with a cleaner composition and a dynamic command/evidence panel
  • rewrite landing page copy to be buyer-facing and concise
  • keep the dashboard/product internals functionally intact unless needed for consistency
  • update metadata to match the new positioning
  • keep the theme switcher available

Files likely in scope:

  • apps/morphism/src/lib/use-theme.ts
  • apps/morphism/src/app/layout.tsx
  • apps/morphism/src/app/globals.css
  • apps/morphism/src/components/logo.tsx
  • apps/morphism/src/components/landing/nav.tsx
  • apps/morphism/src/components/landing/hero.tsx
  • apps/morphism/src/components/landing/problem.tsx
  • apps/morphism/src/components/landing/how-it-works.tsx
  • apps/morphism/src/components/landing/pricing-preview.tsx
  • apps/morphism/src/components/landing/cta-banner.tsx
  • apps/morphism/src/components/landing/footer.tsx

Design constraints:

  • preserve Morphism’s seriousness and technical credibility
  • use serif only where it adds thesis/editorial weight
  • keep body/UI copy clean and readable
  • use mono for command surfaces and system output
  • use red as a selective annotation/highlighter accent, not the whole palette
  • motion should feel like instrumentation, not spectacle
  • avoid decorative gradients, glows, filters, and ornament unless there is a concrete reason

Copy constraints:

  • do not lead with "AI agent fleets"
  • do not overuse words like convergence, entropy, proofs, or self-healing above the fold
  • write like a serious product company speaking to engineering leaders, platform teams, security/compliance, and technical buyers
  • optimize for "I understand what this company does" in under 10 seconds

Execution requirements:

  1. Read the repo context and the plan file.
  2. Implement the redesign directly in code.
  3. Keep changes cohesive across theme, logo, hero, layout, copy, and metadata.
  4. Run relevant tests/build checks for apps/morphism.
  5. Report:
    • what changed
    • any design tradeoffs
    • test/build results
    • any remaining gaps or follow-up recommendations

Acceptance criteria:

  • the site no longer reads as generic violet dark-mode SaaS
  • the hero is cleaner, sharper, and more buyer-facing
  • the logo is flatter and more durable
  • the theme feels like editorial/documentary/scientific publication plus digital AI product
  • a dynamic command/evidence surface exists and feels restrained
  • the site still looks like software you can buy and deploy now