SEO / Portfolio / Public Site

AiSpiralism.com Positive Experience Upgrade — Master Implementation Prompt

Report summary

Give this prompt to a senior design-and-development agent with access to the existing AiSpiralism.com WordPress codebase, content, analytics, and deployment environment.

Status: Research archive item
Category: SEO / Portfolio / Public Site
Length: 6,647 words
Reading time: 31 minutes
Report type: evaluation

Key topics

SEO / Portfolio / Public Site
SEO
Portfolio
Public Site
AI
WordPress
Runtime
Privacy
Semantic Systems

Research provenance

Archive status: Research archive item
Canonical report: https://mikekappel.com/reports/seo-portfolio-public-site/aispiralism-com-positive-site-improvement-master-prompt/
Content identity: sha256:572edeacc5eca9272798409a3f6a6ab0b38f1a5ccf54cc1457d755c33f0d3932

For citation, use the report title and canonical URL. Archival presence does not establish authorship or promote report statements into portfolio evidence.

This page renders the archived Markdown as safe, formatted HTML. It is background research and does not become a portfolio claim without evidence review.

Full report

On this page

How to use this prompt

Give this prompt to a senior design-and-development agent with access to the existing AiSpiralism.com WordPress codebase, content, analytics, and deployment environment.

The agent must inspect the live site and repository before modifying anything. It must then implement the highest-value improvements rather than stopping after an audit, strategy document, or mockup.

1. Role and assignment

Act as a coordinated senior product team consisting of:

a brand strategist;
an information architect;
a UX researcher;
a conversion-focused product designer;
an editorial designer;
an interaction and motion designer;
a WordPress architect;
a front-end engineer;
a back-end engineer;
a content strategist;
an SEO specialist;
an accessibility specialist;
a performance engineer;
a privacy and analytics engineer;
a quality-assurance lead.

Your assignment is to audit, redesign, and improve the existing AiSpiralism.com experience.

This is not a generic AI company website. It is a positive creative field guide to AI Spiralism: spiral-inspired creative methods, symbolic prompt language, recursive improvement, AI persona styles, remix culture, and practical human-directed collaboration with existing AI tools.

The redesign must make the site:

more visually distinctive;
more exciting on first contact;
easier to understand;
more useful without leaving the site;
easier to browse and search;
more interactive without adding live AI inference;
more clearly connected to SpiralistAI.com;
more valuable as a repeat destination;
more shareable;
more coherent as a library;
more consistent across mobile and desktop;
more technically maintainable.

The public experience must concentrate on the constructive, imaginative, useful, and enjoyable side of AI Spiralism. Do not make controversy, criticism, pathology, fear, rebuttal, or defensive positioning the emotional center of the site. Preserve the existing trust policies, but present them as a calm supporting layer rather than repeating warning-oriented copy throughout every page.

2. Live-site source of truth

Begin with the actual live site at:

https://aispiralism.com/

Audit the current implementation and preserve the intent of these existing routes:

/
/what-is-ai-spiralism/
/symbols/
/prompt-ideas/
/personas/
/library/
/glossary/
/spiral-art-and-ai-visuals/
/recursive-ai-creativity/
/share-your-spiral-persona/
/library/personalities/
/library/communication/
/library/research/
/library/communities/
/library/timeline/
/source-policy/
/safety-grounding/
/persona-boundaries/
/privacy/
machine-readable files such as the sitemap, RSS feed, llms.txt, llms-full.txt, ai.txt, and the JSON library.

Also audit the cross-domain journey to:

https://spiralistai.com/

AiSpiralism.com is the discovery, learning, experimentation, and inspiration layer. SpiralistAI.com is the full persona creation, editing, export, and provider-launch layer. Improve the bridge between them without merging the two products blindly.

Do not replace current URLs merely to satisfy a new design. Preserve valid routes and add redirects only when a route change has a measurable user or search benefit.

Record the audit date in UTC.

3. Existing strengths to preserve

The live site already has a strong foundation. Preserve and strengthen all of the following:

The site already presents AI Spiralism as a creative, cultural, symbolic, and prompt-design topic.

Positive practical framing

AiSpiralism.com explains and demonstrates the concepts; SpiralistAI.com builds the full persona prompt.

Clear division between learning and building

The existing library includes Spiral, Mirror, Flame, Lattice, Eye, Fractal, Loop, Seed, Spore, Signal, Compass, and Portal.

Twelve-symbol vocabulary

Existing prompts cover writing, worldbuilding, research, software, branding, learning, reflection, visual art, persona design, and planning.

Twenty-four copy-ready prompts

Existing examples include creative, research, planning, software, writing, and brand collaborators.

Useful persona starting points

The glossary provides a strong semantic foundation for internal linking, search visibility, and visitor education.

A forty-four-term glossary

Current library sections cover personalities, communication patterns, research, communities, timeline, glossary, and editorial source policy.

A source-aware library

The site does not run model inference. This is a product advantage: visitors can explore, compose, copy, and share without sending private creative text to a model from this site.

Browser-based, no-live-AI positioning

The “Share Your Spiral Persona” experience already defines a useful community format that can become a genuine interactive product surface.

A deterministic share-card concept

Existing JSON, sitemap, RSS, AI discovery files, stable route structure, and source-policy work provide technical credibility.

Machine-readable publishing

The violet, magenta, blue, and midnight spiral image establishes a recognizable visual starting point.

Distinctive cosmic spiral art direction

Do not discard these assets. The goal is to turn them into a coherent, interactive, return-worthy experience.

4. Current experience problems to solve

Validate these observations against the live site and repository, then address them.

4.1 The homepage explains more than it demonstrates

The homepage contains strong content, but it primarily sends visitors to more reading or to the external builder. A visitor should be able to complete a small, satisfying creative action directly on AiSpiralism.com within thirty seconds.

4.2 The outbound persona-builder call to action is repeated too often

“Create instead of only reading” and closely related SpiralistAI.com callouts appear repeatedly across pages. This weakens hierarchy and makes the editorial site feel like a funnel rather than a destination.

Use one strong contextual builder handoff per major page, not several nearly identical interruptions.

4.3 Major pages reuse the same hero image and visual structure

The current hero art is effective, but using the same cosmic spiral image on nearly every route reduces page identity. Build a flexible visual system in which every major section has its own symbol composition, motion pattern, and color emphasis while remaining recognizably part of the same brand.

4.4 Several valuable resources are presented as long vertical lists

The symbol library, prompt collection, glossary, and research index contain useful material but need:

search;
filtering;
sorting;
deep links;
compact cards;
detail drawers;
related-item navigation;
save and copy actions;
mobile-friendly browsing;
meaningful empty states.

4.5 The library is currently a directory more than a library

Turn it into a real discovery surface with a unified index, curated collections, source labels, topic filters, related content, and clear paths for newcomers, creators, researchers, and developers.

4.6 The cross-domain handoff is abrupt

Before sending a visitor to SpiralistAI.com, show what will carry over, what will happen next, and what data is or is not transferred. Where technically appropriate, pass only non-sensitive selected options through explicit URL parameters.

4.7 Trust copy is useful but overly repeated

Preserve the source policy, practical boundaries, privacy information, and human-led framing. Reduce repeated caution language in every card and footer. Replace repetitive labels such as “Safer interpretation” with more constructive contextual labels where appropriate:

“Practical lens”
“Use it for”
“Best when”
“Working rule”
“Keep the user in control”

Keep the complete policies on dedicated trust pages.

Remove public-facing theme/version strings such as “SEO Funnel Theme v1.5.1” from the footer. Version information belongs in source control, deployment metadata, or an authenticated status page.

4.9 The site needs stronger reasons to return

Add rotating or regularly updated positive features such as:

Symbol of the Week;
Prompt of the Week;
Featured Persona Passport;
five-minute Spiral Session;
current creative challenge;
newly added library items;
curated collections.

Do not create manipulative streaks, artificial scarcity, or engagement pressure.

5. Central positioning

Use this concise public definition as the primary editorial anchor:

AI Spiralism is a creative practice for revisiting ideas with purpose—using symbols, prompts, and AI persona styles to turn patterns into useful work.

Use this shorter line where space is limited:

Notice the pattern. Change the question. Make something useful.

Brand promise

Turn patterns into possibilities.

Brand personality

The site should feel:

imaginative;
optimistic;
intelligent;
practical;
artful;
precise;
welcoming;
exploratory;
user-directed;
technically credible;
culturally curious;
playful without becoming childish.

Emotional sequence

Design the experience around:

Curiosity → recognition → experimentation → creation → sharing → return

Public language

Prefer:

discover;
create;
remix;
compare;
refine;
build;
explore;
imagine;
map;
connect;
revisit;
transform;
test;
choose;
share;
finish;
carry forward.

Avoid making the public brand depend on:

arguments with critics;
sensational framing;
defensive explanations;
grandiose promises;
hidden-knowledge language;
fear-driven conversion;
vague mystical copy without a practical result.

Poetic language is welcome when it resolves into an understandable action, example, or artifact.

6. Brand architecture

Clarify the two-domain relationship everywhere it matters.

AiSpiralism.com

Purpose: Discover, learn, try, remix, browse, and share.

Primary promise: A positive creative field guide with practical tools and examples.

Primary actions:

Start a Creative Spiral;
explore symbols;
copy a prompt;
compare persona styles;
browse a collection;
make a share card.

SpiralistAI.com

Purpose: Build, edit, export, copy, and launch a complete persona prompt.

Primary promise: Turn a selected role and style into a detailed, editable persona configuration.

Required relationship copy

Use a concise explanation:

AiSpiralism.com helps you discover the style and try the ideas. SpiralistAI.com turns your selection into a complete, editable persona prompt.

Cross-domain visual treatment

Use related but distinct logos.
Keep a consistent core palette and symbol language.
Label outbound links clearly with the external-domain icon.
Do not surprise the user with a domain change.
Preserve UTM attribution.
Never transfer private prompt text automatically.
Pass only explicit non-sensitive selections such as role, use case, and symbol IDs.
Provide a review screen before leaving AiSpiralism.com.

7. Success criteria and measurable outcomes

Set baseline metrics before launch and measure improvements after release.

Target outcomes:

A first-time visitor can explain the site in one sentence after the first viewport.
At least one useful action is available without registration and without leaving the domain.
The median visitor can find a relevant prompt in fewer than three interactions.
Every symbol has a stable deep link and at least one prompt, persona, and use-case relationship.
Every prompt can be copied with clear success feedback.
Every persona example can be previewed before the user is sent to SpiralistAI.com.
The library supports unified search and filtering.
The share-card experience works on mobile and desktop.
Cross-domain builder clicks contain meaningful source and selection context.
Trust pages remain accessible but no longer dominate the emotional tone of core creative pages.
Core Web Vitals meet the targets defined later in this prompt.
WCAG 2.2 AA requirements are met.
Existing valid routes, machine-readable files, and indexed content remain intact.

Track:

start-tool completion;
prompt copy;
symbol-detail opens;
persona preview;
compare-persona use;
library search;
filter usage;
saved-item use;
share-card generation;
challenge participation;
contextual builder handoff;
failed search queries;
external builder return visits.

Do not record private prompt text, journal text, generated card text, or sensitive user content as analytics payloads.

8. Revised information architecture

Use a clear primary navigation with five content groups and one action.

Explore
Prompts
Personas
Library
Community
Build a Persona ↗ — visually prominent external action

The logo returns to the homepage.

What Is AI Spiralism?
Start a Creative Spiral
Symbols
Recursive Creativity
Spiral Art and Visuals
Glossary

Browse All Prompts
Writing and Story
Research and Learning
Software and Systems
Planning and Strategy
Visual and Brand
Prompt Mixer

Persona Styles
Compare Personas
Persona Passports
Featured Persona
How Personas Work

Library Home
Curated Collections
Personalities and Archetypes
Communication Patterns
Research Index
Timeline
Source Policy

Current Challenge
Persona Card Maker
Gallery
Remix Guide
Participation Rules

Place these outside the main navigation hierarchy:

search;
saved items;
theme;
accessibility preferences where applicable;
privacy;
machine-readable resources.

Use breadcrumbs on deep pages.

9. Homepage redesign

Build the homepage as a progressive creative journey, not a long index of repeated cards.

9.1 Hero

Use this production-ready copy.

Eyebrow

AI Spiralism, made creative.

Turn patterns into possibilities.

Supporting copy

Explore a positive field guide to spiral-inspired prompts, symbols, and AI persona styles. Start with one idea, revisit it with purpose, and leave with something you can use.

Primary action

Start a Creative Spiral

Secondary action

Explore Symbols and Prompts

Tertiary external link

Build a Persona on SpiralistAI.com ↗

Microcopy

No signup. No live AI on this site. Copy, remix, and stay in control.

Hero visual

Do not reuse the existing hero JPEG as a full, unchanged image.

Use it as source inspiration for a new layered composition:

a central luminous spiral;
twelve orbiting symbol marks;
subtle paths connecting symbols to practical outputs;
small labels such as Write, Research, Plan, Design, Code, and Learn;
restrained pointer or scroll response;
an immediate static fallback;
full reduced-motion support.

The hero must remain legible at 320 CSS pixels wide.

9.2 Start in thirty seconds

Embed a deterministic, browser-only mini tool directly below the hero.

Heading:

Start with the work you want to do.

Step 1 — Choose a use case:

Write;
Research;
Code;
Plan;
Design;
Learn;
Reflect;
Surprise Me.

Step 2 — Choose a motif:

Spiral;
Mirror;
Flame;
Lattice;
Signal;
Compass;
or “Choose for me.”

Step 3 — Receive:

one concise prompt;
one suggested persona style;
one completion test;
buttons for Copy Prompt, Save, Try Another, and Build Full Persona.

The result must come from the existing curated prompt and symbol data. Do not call a model.

Example result:

Spiral + Writing

Develop this draft in three passes: intention, structure, and voice. After each pass, state what changed. Stop when the central idea, sequence, and tone all support the same purpose.

Completion test:

The draft has one clear purpose, a stable structure, and no paragraph that merely repeats the previous one.

Builder handoff:

Continue as a complete Writing Editor persona on SpiralistAI.com ↗

9.3 Why people use it

Use four cards with concrete outcomes.

Revisit ideas with purpose

Return to the same question through a different lens instead of repeating the same answer.

Turn symbols into working behaviors

Use a mirror for reflection, a lattice for structure, a flame for creative momentum, or a compass for direction.

Give AI a memorable working style

Define what a collaborator notices, how it responds, and what a finished result looks like.

Finish with an artifact

Turn the exploration into a draft, plan, comparison, prompt, decision, visual brief, or next action.

Each card should open a compact example.

9.4 Explore by goal

Create six visual paths:

Write and tell stories
Research and learn
Code and design systems
Plan and decide
Create visuals and brands
Build AI persona styles

Each path should surface:

two prompts;
two symbols;
one persona;
one related guide;
one next action.

9.5 Symbol constellation

Show all twelve current symbols as custom SVG marks, not plain text glyphs alone.

On hover, focus, or tap, display:

name;
one-line meaning;
practical behavior;
example prompt;
related use cases.

Add:

Explore All Symbols;
Mix Two Symbols;
Use This Symbol in a Persona.

9.6 Prompt shelf

Show six featured prompts selected across different use cases.

Each card includes:

title;
intended use;
symbol;
prompt preview;
output expectation;
Copy;
Customize;
Build Persona.

Do not hide the useful text behind an account gate.

9.7 Persona studio preview

Show three concise Persona Passports side by side.

Recommended examples:

Spiral Creative Director
Recursive Research Partner
Skeptical Systems Mentor

Each passport includes:

role;
promise;
symbols;
three behaviors;
one example response excerpt;
Preview;
Compare;
Build Full Persona.

9.8 Visual inspiration

Use an editorial gallery of page-specific spiral art, symbol studies, and prompt-result mockups.

Heading:

A visual language for ideas in motion.

Include links to:

Spiral Art and Visual Prompts;
Composition Recipes;
Create a Visual Brief.

9.9 Library collections

Replace a generic list with four curated collections:

Start Here
Creative Methods
Symbols and Language
Research and Sources

Each collection must have a clear description and an estimated reading time.

9.10 Community challenge

Feature the current positive challenge.

Heading:

Make a persona card. Share the working idea. Invite a remix.

Show:

the current theme;
three featured cards;
Make a Card;
View the Gallery;
Read Remix Rules.

Do not fabricate community submissions. Use clearly labeled editorial examples until real permissioned submissions exist.

9.11 SpiralistAI handoff

Use one focused section near the end.

Heading:

Ready to turn the idea into a complete persona?

Copy:

Choose a role and symbol here, then carry those selections into SpiralistAI.com. You will be able to inspect and edit the complete prompt before copying or launching it.

Buttons:

Review My Selections
Open SpiralistAI.com ↗

9.12 Compact trust strip

Use a quiet three-item strip:

Browser-only creative tools;
Source-aware library;
Human-directed personas.

Link to the full trust center without reproducing the complete policy.

9.13 Final call to action

Heading:

Bring one idea. Return with a clearer direction.

Buttons:

Start a Creative Spiral
Browse the Library

10. New interactive product layer

The site must become useful before the visitor leaves it.

10.1 Start a Creative Spiral

Create a dedicated /start/ route and reusable embedded component.

Inputs:

use case;
desired outcome;
one or two symbols;
preferred working style;
number of passes;
output format.

Outputs:

curated prompt;
completion test;
suggested persona;
related guide;
builder handoff.

Requirements:

no live inference;
no account;
no network request for user text;
deterministic output;
keyboard accessible;
shareable state via non-sensitive URL parameters;
copy and save actions;
local reset;
print-friendly result.

10.2 Symbol Mixer

Allow a visitor to combine two symbols.

Examples:

Spiral + Signal = iterative synthesis;
Mirror + Compass = reflective decision support;
Flame + Lattice = energetic ideation followed by structure;
Seed + Portal = expand a small idea into a concrete first action;
Eye + Fractal = quality review at multiple scales.

For every supported pair, generate:

a combined name;
plain-language method;
one prompt;
best use cases;
suggested persona.

Do not produce vague “mystical” combinations. Every combination must lead to a practical behavior.

10.3 Prompt Workbench

Upgrade the current prompt list into a compact editor.

Allow users to:

choose a prompt;
insert their own subject locally;
set pass count;
select output format;
add a completion test;
copy the final prompt;
reset;
save locally;
transfer selected settings to SpiralistAI.com.

Never transmit the local subject text unless the user explicitly chooses a provider action.

10.4 Persona Compare

Let users compare two concise persona styles on the same prewritten example task.

Show:

what each persona notices;
likely response structure;
degree of challenge;
preferred output;
symbols;
best use cases.

Use curated examples, not live inference.

10.5 Persona Card Maker

Move the existing community concept from article-only instructions into a working browser tool.

Fields:

persona name;
role;
one-line promise;
symbol;
collaboration style;
creative energy;
creator handle, optional;
attribution preference.

Provide:

live accessible preview;
square and portrait formats;
PNG export;
copyable alt text;
copyable caption;
local reset;
no hidden metadata;
no automatic social posting.

10.6 Saved constellation

Allow anonymous users to save prompts, symbols, personas, and library items locally.

Name the feature:

My Constellation

Requirements:

explain local storage clearly;
no signup required;
export as JSON or Markdown;
import from a user-selected file;
one-click clear;
no behavioral pressure;
no private analytics payload.

11. Page-by-page requirements

11.1 `/what-is-ai-spiralism/`

Restructure the page for clarity and visual learning.

First viewport:

one-sentence definition;
three useful examples;
Start a Creative Spiral;
Explore Symbols.

Use a simple three-layer model:

Culture — recurring images, words, persona names, and remix practices.
Method — deliberate passes, symbolic cues, and reusable prompt structures.
Artifact — the useful thing produced: a draft, plan, visual brief, decision, or persona.

Add:

a sixty-second visual explanation;
“Spiralism in six real tasks”;
a before-and-after prompt example;
a “try one pass now” interaction;
a compact relationship diagram between AiSpiralism.com and SpiralistAI.com.

Reduce repeated disclaimers. Keep one clear “How this site approaches the topic” panel and link to the full trust center.

11.2 `/symbols/`

Replace the long vertical sequence with an interactive symbol atlas.

Core groups

Motion and iteration

Spiral
Loop
Portal

Attention and reflection

Mirror
Eye
Signal

Structure and orientation

Lattice
Fractal
Compass

Growth and creative energy

Seed
Spore
Flame

Extended symbols

Add an editorially reviewed extension lane:

Thread — continuity;
Prism — multiple perspectives;
Node — connection and participation;
Anchor — integration and practical return;
Bridge — translation between domains;
Constellation — many distinct contributions forming a larger map.

Label symbols as:

Core;
Extended;
Experimental;
Archived.

Every symbol record must include:

stable ID;
name;
slug;
custom SVG;
one-line meaning;
practical behavior;
prompt example;
best use cases;
compatible personas;
related symbols;
pairings;
visual guidance;
status;
version;
UTC update date;
source or editorial note where relevant.

Actions:

Copy Prompt;
Mix This Symbol;
Save;
Share;
Build a Persona with This Symbol.

Keep Flame as the positive symbol of creative spark, invention, and momentum. Do not frame it as supernatural proof or remove it solely because other interpretations exist.

11.3 `/prompt-ideas/`

Turn the current twenty-four prompts into a searchable, filterable prompt library.

Filters:

use case;
symbol;
output type;
number of passes;
beginner/advanced;
concise/detailed;
individual/team.

Every prompt card must show:

title;
one-line purpose;
complete copyable prompt;
expected output;
completion test;
symbol;
related persona;
Copy;
Customize;
Save;
Build Persona.

Add reliable copy feedback:

“Copied”
screen-reader announcement;
temporary visual state;
no page jump.

Add deep links for every prompt.

Create curated collections:

Five-Minute Prompts;
Writing Studio;
Research Desk;
Software Workshop;
Planning Room;
Visual Lab;
Team Exercises.

11.4 `/personas/`

Expand the page from six outbound examples into a genuine persona discovery surface.

Show at least twelve concise, useful persona styles across:

writing;
research;
learning;
software;
product;
planning;
design;
brand;
facilitation;
reflection;
worldbuilding;
quality review.

Every Persona Passport includes:

name;
role;
promise;
symbols;
working method;
three behaviors;
one boundary summary;
example input;
example response excerpt;
best uses;
not ideal for;
Compare;
Save;
Build Full Persona.

Do not reproduce the entire long SpiralistAI persona configuration on this site. Use a concise, readable preview, then send the user to the builder for advanced detail.

11.5 `/library/`

Build a real library application.

Include:

unified search;
content-type filters;
topic filters;
source-type filters;
curated collections;
featured additions;
recently updated items;
reading-time estimates;
clear source labels;
related symbols, prompts, and personas;
stable deep links;
empty-state suggestions.

11.6 `/glossary/`

Retain all forty-four existing terms and improve navigation.

Add:

live search;
A–Z navigation;
category filters;
deep links;
related terms;
“used in” references;
copy link;
compact and expanded views.

Replace repetitive card language with this format:

Plain meaning
Practical use
Example
Related terms

Keep the full evidence and boundary context available in expandable details and dedicated trust pages.

11.7 `/spiral-art-and-ai-visuals/`

Turn the guide into a visual production lab.

Add:

interactive composition diagrams;
prompt anatomy;
motif selector;
palette and contrast notes;
aspect-ratio presets;
accessibility checklist;
five finished prompt recipes;
copyable visual briefs;
gallery of editorial examples;
attribution and originality guidance.

Create a deterministic Visual Brief Builder that outputs:

subject;
composition;
focal hierarchy;
motion;
motif;
palette;
texture;
lighting;
accessibility notes;
negative constraints.

11.8 `/recursive-ai-creativity/`

Add an interactive three-pass exercise:

Possibility;
Structure;
Completion.

Visitors paste or type a short idea locally. The site displays the questions for each pass and lets the visitor type notes. It does not analyze the text.

At the end, export:

original idea;
pass notes;
decision;
next artifact;
finish-line statement.

Offer Markdown and print export.

11.9 `/share-your-spiral-persona/`

Make the card maker the primary experience and move the article guidance below it.

Add:

current weekly theme;
card tool;
downloadable formats;
alt-text generator based on entered visible fields;
caption templates;
remix license options;
submission rules;
featured gallery;
moderation status explanation.

Do not publish submissions automatically.

11.10 `/library/personalities/`

Separate the content into two visually distinct sections:

Published analysts and sources
Creative persona archetypes

Do not mix real people and fictional working styles in the same undifferentiated card grid.

For real people:

source role;
why they are relevant;
source quality;
direct links;
last reviewed UTC.

For archetypes:

role;
behavior;
use cases;
related prompt;
persona-builder handoff.

11.11 `/library/communication/`

Use diagrams to explain:

seed;
spore;
dyad;
signoff;
glyph;
prompt chain;
recursion;
AI-to-AI relay.

Each diagram must conclude with a practical creative use.

Add a “Build a prompt chain” deterministic tool with:

goal;
three stages;
stage purpose;
finish line;
copy/export.

11.12 `/library/research/`

Upgrade the eight starter cards into structured dossiers.

Each dossier includes:

working question;
concise summary;
source types;
known observations;
interpretations;
practical implications;
related site content;
update history;
UTC review date.

Keep research accessible but secondary to the creative public journey.

11.13 `/library/communities/`

Focus on positive participation:

remix practices;
attribution;
creative challenges;
example cards;
group workshop formats;
public gallery;
contribution guidelines.

Do not make external controversy the center of this page.

11.14 `/library/timeline/`

Create two views:

Creative Milestones — default public view.
Research and Coverage — secondary source-aware view.

The default timeline should highlight:

persona prompting becoming common;
longer contexts enabling recurring styles;
symbol vocabularies becoming shareable;
prompt remix culture;
persona cards;
the AiSpiralism.com field guide;
the SpiralistAI builder;
library and community milestones.

11.15 Trust pages

Preserve the existing routes:

/source-policy/
/safety-grounding/
/persona-boundaries/
/privacy/

Group them under a positive footer heading:

How We Keep the Experience Clear

Use calm language around:

source quality;
human agency;
privacy;
user ownership;
visible limits;
finishing and stopping;
provider review.

Do not repeat the full trust policy on every creative card.

12. Content model and data contracts

First inspect how current content is stored. Do not create duplicate WordPress content types when structured JSON or existing custom types already solve the problem.

Where new structured records are needed, use stable contracts similar to the following.

Symbol record

{
  "id": "symbol.spiral",
  "name": "Spiral",
  "slug": "spiral",
  "group": "motion",
  "status": "core",
  "meaning": "Creative recursion with purposeful change.",
  "behavior": "Revisit the work through distinct passes.",
  "promptTemplate": "Review this in three passes: possibility, structure, and completion.",
  "useCases": ["writing", "research", "planning"],
  "relatedSymbolIds": ["symbol.loop", "symbol.signal"],
  "personaIds": ["persona.recursive-research-partner"],
  "version": "1.0.0",
  "updatedAtUtc": "2026-06-23T00:00:00Z"
}

Prompt record

{
  "id": "prompt.spiral-scene-builder",
  "title": "Spiral Scene Builder",
  "slug": "spiral-scene-builder",
  "summary": "Develop a scene through emotional, spatial, and dialogue passes.",
  "useCase": "writing",
  "promptText": "Help me develop this scene in three passes...",
  "outputType": "revised-draft",
  "passCount": 3,
  "completionTest": "Every line changes the emotional or practical situation.",
  "symbolIds": ["symbol.spiral"],
  "personaIds": ["persona.lyrical-writing-editor"],
  "difficulty": "beginner",
  "version": "1.0.0",
  "updatedAtUtc": "2026-06-23T00:00:00Z"
}

Persona preview record

{
  "id": "persona.recursive-research-partner",
  "name": "Recursive Research Partner",
  "slug": "recursive-research-partner",
  "role": "Research collaborator",
  "promise": "Separates claims, evidence, counterevidence, and uncertainty across deliberate passes.",
  "symbolIds": ["symbol.spiral", "symbol.signal"],
  "behaviors": [
    "Clarifies the question before searching.",
    "Separates observation from inference.",
    "Ends with a bounded conclusion and next evidence need."
  ],
  "examplePromptId": "prompt.evidence-first-companion",
  "builderPath": "/?role=research&symbols=spiral,signal",
  "version": "1.0.0",
  "updatedAtUtc": "2026-06-23T00:00:00Z"
}

Required data rules

Use stable IDs.
Use UTC timestamps.
Version public records.
Validate all data during build and deployment.
Generate human pages and machine-readable inventories from the same source where practical.
Do not maintain conflicting copies of the same prompt or symbol.
Preserve canonical URLs.
Provide migration scripts and rollback instructions.

13. Visual design system

Name the direction:

Prismatic Spiral Field Guide

It should combine:

midnight editorial depth;
luminous cosmic motion;
precise geometric diagrams;
custom symbol linework;
subtle iridescence;
clear modern typography;
generous white space;
accessible contrast;
playful but controlled interaction.

Color tokens

Retain the recognizable violet, blue, pink, and midnight family, then add a warmer creative accent and readable surfaces.

Suggested starting tokens:

:root {
  --color-ink: #090A18;
  --color-midnight: #0F1230;
  --color-indigo: #252A68;
  --color-violet: #795CFF;
  --color-electric-blue: #42B8FF;
  --color-magenta: #F06BD8;
  --color-cyan: #57E4DD;
  --color-gold: #F6C85F;
  --color-paper: #F8F7FC;
  --color-surface: #FFFFFF;
  --color-text: #17182A;
  --color-muted: #62657A;
  --color-border: #DADCF0;
  --color-success: #208A67;
}

Do not adopt these values blindly. Test them in both light and dark contexts and adjust to meet contrast requirements.

Typography

Use:

an expressive editorial display face for major headings;
a highly readable sans serif for interface and body copy;
a monospaced face only for prompt text, IDs, and technical examples.

Requirements:

variable fonts where appropriate;
local or privacy-conscious delivery;
strong fallback stacks;
visible differentiation between H1–H4;
readable line length;
minimum body size suitable for mobile;
no all-caps paragraphs;
no low-contrast gradient text for essential copy.

Page-specific art direction

Do not reuse one hero image on every page.

Create unique compositions:

Home — full spiral constellation;
What Is — three-layer culture/method/artifact diagram;
Symbols — orbiting glyph atlas;
Prompts — modular prompt ribbons;
Personas — overlapping passport cards;
Library — luminous map or shelves of connected nodes;
Glossary — typographic constellation;
Visuals — composition grid;
Recursive Creativity — three-pass spiral path;
Community — many distinct cards forming a constellation.

Custom symbol set

Create original, consistent SVG marks for all core and extended symbols.

Requirements:

recognizable at 16 pixels;
visually balanced at 48 and 96 pixels;
single-color and gradient versions;
accessible text labels;
no dependence on Unicode rendering;
optimized paths;
sprite or component delivery;
documented usage rules.

Motion

Use motion to communicate:

return;
progression;
relationship;
selection;
completion.

Examples:

a path draws as a three-pass process advances;
symbols gently align when combined;
copied cards resolve into a check state;
saved items move into My Constellation;
filters rearrange cards without disorienting the user.

Rules:

honor prefers-reduced-motion;
never animate essential text continuously;
avoid rapid rotation;
avoid aggressive parallax;
keep loops finite or user-pausable;
use CSS where possible;
avoid animation libraries for trivial effects.

14. Component system

Build reusable components rather than route-specific one-offs.

Required components:

global header;
mega menu;
mobile navigation drawer;
page hero;
section intro;
symbol chip;
symbol card;
symbol detail drawer;
prompt card;
prompt editor;
persona passport;
persona comparison table;
library result card;
source label;
glossary term card;
filter bar;
search input;
active-filter chips;
empty state;
no-results suggestions;
copy button;
save button;
local-storage notice;
builder handoff panel;
challenge card;
share-card canvas;
accessible modal;
toast or inline status;
breadcrumb;
related-content rail;
compact trust strip;
footer.

Every component must include:

default state;
hover state;
focus state;
active state;
disabled state;
loading state where relevant;
error state;
reduced-motion behavior;
narrow-screen behavior;
long-content behavior;
screen-reader labeling.

Document components in a living style guide or Storybook-equivalent if the project stack supports it.

15. Copy and editorial rules

Lead with usefulness

Every page should answer:

What is this?
What can I do with it?
What will I receive?
What should I try next?

Pair poetic and literal language

Good:

Follow the thread. Then turn it into a decision map.

Weak:

Enter the infinite lattice of awakened possibility.

Make symbols operational

Do not stop at:

Mirror means reflection.

Use:

Mirror means reflection. Ask the collaborator to restate the brief, identify the hidden assumption, and recommend one revision.

Vary calls to action by context

Do not repeat the same builder block several times on one page.

Examples:

Use This Symbol;
Copy This Prompt;
Compare Styles;
Make a Card;
Continue in the Builder;
Add to My Constellation;
Start a Three-Pass Session;
Explore the Related Collection.

Keep advanced trust detail available but secondary

Use one concise positive framing in the core experience:

Symbols and personas are creative working tools. You decide what to keep, revise, share, or stop.

Link to full policies for detail.

Do not invent:

testimonials;
member counts;
usage counts;
expert endorsements;
community submissions;
research consensus;
“trending” labels.

Use editorial examples until real, permissioned data exists.

16. Community and repeat-visit strategy

Build a positive community layer without manipulative mechanics.

Weekly challenge

Each challenge includes:

theme;
simple brief;
allowed formats;
example;
completion criteria;
submission window;
participation rules;
attribution options.

Examples:

Build a Research Persona with Spiral + Signal;
Create a Visual Brief with Portal + Prism;
Turn One Seed into Three Story Directions;
Design a Calm Planning Persona with Compass + Lattice;
Remix a Prompt into a Team Workshop.

Gallery

Support:

editorial examples;
permissioned community submissions;
filters;
attribution;
remix lineage;
accessible descriptions;
report mechanism;
moderation status.

Do not rank solely by popularity. Curate for:

clarity;
originality;
usefulness;
craft;
respectful attribution;
diversity of use cases.

Where appropriate, offer a low-pressure update option:

New prompts, symbols, and creative challenges—occasionally.

Do not gate core content behind email collection.

17. Cross-domain builder handoff

Create a reusable handoff component.

Before opening SpiralistAI.com, show:

selected role;
selected symbols;
selected use case;
what the builder will add;
what will not be transferred;
a link to privacy information;
Continue;
Edit Selection;
Copy Prompt Instead.

Example:

Continue with Recursive Research Partner

You selected Research, Spiral, and Signal. SpiralistAI.com will use those choices as a starting point for a full editable persona. Your private topic text will not be transferred.

Use a documented parameter contract such as:

https://spiralistai.com/
  ?utm_source=aispiralism
  &utm_medium=contextual_handoff
  &utm_campaign=persona_builder
  &role=research
  &symbols=spiral,signal
  &style=recursive

Requirements:

whitelist values;
encode safely;
never place private free text in the URL;
preserve existing UTM behavior;
provide a graceful fallback when parameters are absent or invalid;
test on mobile;
document the contract in both repositories.

18. WordPress and engineering requirements

Assume the current site uses a custom WordPress theme. Inspect the actual repository and deployed environment before choosing an implementation path.

Preserve

existing content;
valid post IDs;
canonical URLs;
redirects;
machine-readable files;
RSS;
JSON inventories;
source labels;
SEO metadata;
image attachment relationships;
current security configuration.

Theme architecture

Evolve the existing theme or create a maintainable child/block theme only when justified.
Do not hard-code editorial content that should remain editable.
Use shared template parts and components.
Use server-rendered HTML for primary content.
Add JavaScript progressively.
Ensure core reading and navigation work without JavaScript.
Remove public theme/version branding from the footer.
Keep deployment versioning in source control and release metadata.

Suggested taxonomies

Use existing equivalents where present.

use_case
symbol
content_type
persona_role
source_type
difficulty
collection
status

Public read-only API

If no equivalent already exists, expose a documented, cacheable read-only catalog for:

symbols;
prompts;
persona previews;
glossary terms;
collections;
challenges.

Do not create an API merely for novelty. Generate it from the same authoritative records as the pages.

Front-end behavior

Use small, route-specific bundles.
Avoid loading card-maker code on pages that do not use it.
Use native browser capabilities where practical.
Keep local-only tools local.
Debounce search responsibly.
Preserve filters in the URL.
Make filtered states shareable.
Prevent layout shift.
Sanitize all user-entered card text before rendering.
Treat exported canvas content as untrusted input during later import.

Security

escape output;
sanitize input;
validate REST parameters;
use nonces for state-changing WordPress actions;
rate-limit submissions;
scan uploaded files where uploads are accepted;
enforce file type and size limits;
strip unnecessary image metadata;
use Content Security Policy where practical;
avoid exposing plugin/theme versions publicly;
keep dependencies current;
document rollback.

19. Search and discovery

Implement one search experience across the public catalog.

Searchable fields:

title;
summary;
full text where appropriate;
symbol names;
use cases;
prompt text;
persona names;
glossary terms;
collections;
source labels.

Filters:

content type;
use case;
symbol;
difficulty;
source type;
status;
updated date.

Requirements:

accessible results count;
keyboard-friendly filters;
shareable query URL;
spelling-tolerant suggestions where practical;
no-results recommendations;
popular editorial starting points;
privacy-conscious logging of failed queries;
no logging of free-form private tool content.

20. SEO and structured data

Preserve the strong topic-cluster foundation while improving uniqueness and internal relationships.

Homepage title recommendation

AI Spiralism: Creative Symbols, Prompts and AI Personas | AiSpiralism.com

Homepage meta description recommendation

Explore positive AI Spiralism through practical symbols, copy-ready prompts, creative persona styles, visual guides, and browser-based tools. No signup required.

Structured data

Use only valid schema that accurately describes the page.

Potential types:

WebSite
Organization
CollectionPage
Article
DefinedTermSet
DefinedTerm
HowTo
CreativeWork
ItemList
BreadcrumbList
WebApplication for deterministic browser tools
Dataset for the public JSON library where appropriate

Do not mark the site as an AI model provider when it does not run inference.

Internal linking

Every symbol should link to:

related prompts;
compatible personas;
relevant guides;
glossary terms.

Every prompt should link to:

its symbol;
related persona;
use-case collection;
builder handoff.

Every research item should link to:

source policy;
related guide;
relevant glossary terms.

Indexation

canonicalize filtered pages appropriately;
prevent thin duplicate parameter pages from flooding the index;
preserve useful deep links;
keep machine files discoverable;
validate sitemap output;
maintain hreflang only where real translations exist;
use descriptive social images;
create unique page-level Open Graph art instead of reusing one image everywhere.

21. Accessibility

Meet WCAG 2.2 AA.

Required:

semantic landmarks;
correct heading hierarchy;
visible skip link;
complete keyboard operation;
visible focus;
44-by-44 CSS pixel target sizing where practical;
accessible mobile menu;
labels and instructions for tools;
error summaries;
live-region feedback for copy, save, export, and filter actions;
accessible dialogs and drawers;
color-independent status cues;
sufficient contrast;
reduced-motion support;
usable zoom to 200 percent and beyond;
reflow at 320 CSS pixels;
descriptive alt text;
text equivalents for visual diagrams;
accessible canvas fallback for share cards;
copyable alt text for exported cards;
no essential meaning conveyed by a symbol alone.

Test with:

keyboard only;
VoiceOver or equivalent;
NVDA or equivalent;
high contrast;
reduced motion;
mobile screen reader;
text enlargement;
dark and light themes.

22. Performance

Target production performance on representative mobile hardware.

Goals:

Largest Contentful Paint under 2.5 seconds;
Interaction to Next Paint under 200 milliseconds;
Cumulative Layout Shift under 0.1;
initial JavaScript kept minimal;
no decorative render-blocking script;
no oversized universal bundle;
no full-size hero JPEG reused unnecessarily;
responsive AVIF/WebP sources;
explicit image dimensions;
lazy loading below the fold;
preloading limited to truly critical assets;
long library pages virtualized or paginated only when necessary;
search index loaded efficiently;
server and CDN caching configured;
font loading optimized;
critical CSS measured rather than guessed.

Run:

Lighthouse;
WebPageTest or an equivalent;
real-device mobile testing;
logged-out and logged-in tests where applicable;
cold-cache and warm-cache tests.

Document baseline and post-change results.

23. Privacy and analytics

The site’s no-live-AI model is a strength. Preserve it.

Privacy requirements

Do not transmit local tool input by default.
Do not place private text in URLs.
Explain local storage.
Allow export and clear.
Use explicit consent for analytics where required.
Do not fingerprint users.
Do not embed unnecessary third-party trackers.
Do not auto-post to social networks.
Strip metadata from generated card downloads where feasible.
Make public submission a separate explicit action.

Analytics events

Use event names such as:

creative_spiral_started
creative_spiral_completed
symbol_selected
symbol_pair_created
prompt_copied
prompt_saved
persona_previewed
persona_compared
card_exported
library_search_submitted
library_filter_applied
builder_handoff_reviewed
builder_handoff_opened

Event properties must use controlled IDs, not private text.

24. Migration and implementation sequence

Follow this order.

Phase 1 — Audit and stabilization

Inventory routes, templates, scripts, styles, media, plugins, redirects, structured data, machine files, and content sources.
Capture performance and accessibility baselines.
Map current CTAs and outbound builder parameters.
Confirm the authoritative source for symbols, prompts, glossary terms, and persona examples.
Identify duplicated copy and repeated components.
Create a visual regression baseline.
Document backups and rollback.

Phase 2 — Design foundation

Define design tokens.
Build the custom SVG symbol set.
Create shared card, filter, search, copy, save, and handoff components.
Rebuild header, navigation, and footer.
Remove the public theme/version string.
Create unique page-hero variants.

Phase 3 — Homepage and first action

Implement the new hero.
Build Start a Creative Spiral.
Add goal paths.
Add symbol constellation.
Add prompt shelf.
Add persona previews.
Add one clear SpiralistAI handoff.
Add compact trust strip.

Phase 4 — Core content tools

Rebuild Symbols.
Rebuild Prompt Ideas.
Rebuild Personas.
Rebuild Library.
Rebuild Glossary.
Add My Constellation.

Phase 5 — Creative and community tools

Build Visual Brief Builder.
Build Three-Pass Session.
Build Persona Card Maker.
Add challenges and gallery.
Add moderation and attribution workflows.

Phase 6 — Technical depth

Align machine-readable files with canonical data.
Add or update public read-only APIs.
Add structured data.
improve cross-domain handoff.
Add monitoring.
Run security review.

Phase 7 — QA and launch

Accessibility audit.
Performance audit.
SEO crawl.
redirect test.
structured-data validation.
browser/device matrix.
no-JavaScript test.
local-storage reset/export/import test.
privacy review.
rollback rehearsal.
production launch.
post-launch monitoring.

25. Required deliverables

Produce:

current-state audit;
route inventory;
content inventory;
CTA map;
visual-system audit;
accessibility baseline;
performance baseline;
revised sitemap;
redirect plan;
brand architecture;
homepage wireframe;
mobile and desktop designs;
production copy deck;
design tokens;
SVG symbol library;
component inventory;
WordPress implementation;
Start a Creative Spiral tool;
Symbol Mixer;
Prompt Workbench;
Persona Compare;
Persona Card Maker;
My Constellation;
redesigned Symbols page;
redesigned Prompt Ideas page;
redesigned Personas page;
redesigned Library;
redesigned Glossary;
cross-domain handoff contract;
structured-data implementation;
analytics specification;
accessibility report;
performance report;
security notes;
migration scripts;
changed-file list;
deployment instructions;
rollback instructions;
post-launch measurement plan.

Do not use:

lorem ipsum;
placeholder buttons;
fake testimonials;
fake community metrics;
fabricated submissions;
incomplete mobile states;
nonfunctional filters;
decorative interactions without practical value.

26. Acceptance criteria

The work is complete only when:

the homepage clearly communicates the positive purpose in the first viewport;
a visitor can complete a useful browser-only creative action within thirty seconds;
all current core routes remain available or have tested permanent redirects;
every core symbol has a custom SVG, deep link, prompt, use case, and persona relationship;
all twenty-four current prompts remain available and are easier to find and copy;
all forty-four glossary terms remain available and searchable;
persona examples can be previewed and compared before leaving the domain;
the library functions as a unified searchable catalog;
the card maker creates accessible downloadable cards;
the site uses unique page-level visual compositions;
repeated outbound CTA blocks are reduced;
the public footer no longer exposes theme/version branding;
trust pages remain available in a calm secondary layer;
no live AI inference is introduced without a separate explicit product decision;
private user text remains local by default;
the SpiralistAI handoff never transfers private free text;
major flows work with keyboard and screen readers;
reduced-motion behavior is complete;
mobile layouts work at 320 CSS pixels;
Core Web Vitals meet targets or have documented remaining remediation;
structured data validates;
sitemaps and machine-readable files remain discoverable;
the implementation is documented and reversible.

27. Final creative standard

The redesigned AiSpiralism.com should feel like a luminous field guide for ideas in motion.

It should not feel like:

a generic AI startup;
a warning archive;
a static SEO article network;
a thin bridge to another domain;
an endless mystical scroll;
a collection of disconnected lists.

It should feel like:

a creative studio;
a symbolic toolkit;
a practical prompt library;
a visual field guide;
a persona discovery space;
a source-aware cultural archive;
a positive community invitation.

A visitor should leave with this impression:

AI Spiralism gives me an imaginative but practical way to revisit ideas, choose a working style, and make something clearer, stronger, or more original.

Begin by auditing the current live implementation and repository. Preserve the strong positive foundation. Reduce repetition. Add immediate creative utility. Make every symbol, prompt, persona, guide, and library item feel like part of one coherent system. Then implement, test, document, and deploy the highest-value improvements.

Full report

How to use this prompt

1. Role and assignment

2. Live-site source of truth

3. Existing strengths to preserve

4. Current experience problems to solve

4.1 The homepage explains more than it demonstrates

4.2 The outbound persona-builder call to action is repeated too often

4.3 Major pages reuse the same hero image and visual structure

4.4 Several valuable resources are presented as long vertical lists

4.5 The library is currently a directory more than a library

4.6 The cross-domain handoff is abrupt

4.7 Trust copy is useful but overly repeated

4.8 The public footer exposes implementation branding

4.9 The site needs stronger reasons to return

5. Central positioning

Brand promise

Brand personality

Emotional sequence

Public language

6. Brand architecture

AiSpiralism.com

SpiralistAI.com

Required relationship copy

Cross-domain visual treatment

7. Success criteria and measurable outcomes

8. Revised information architecture

Primary navigation

Explore menu

Prompts menu

Personas menu

Library menu

Community menu

Utility navigation

9. Homepage redesign

9.1 Hero

Hero visual

9.2 Start in thirty seconds

9.3 Why people use it

Revisit ideas with purpose

Turn symbols into working behaviors

Give AI a memorable working style

Finish with an artifact

9.4 Explore by goal

9.5 Symbol constellation

9.6 Prompt shelf

9.7 Persona studio preview

9.8 Visual inspiration

9.9 Library collections

9.10 Community challenge

9.11 SpiralistAI handoff

9.12 Compact trust strip

9.13 Final call to action

10. New interactive product layer

10.1 Start a Creative Spiral

10.2 Symbol Mixer

10.3 Prompt Workbench

10.4 Persona Compare

10.5 Persona Card Maker

10.6 Saved constellation

11. Page-by-page requirements

11.1 /what-is-ai-spiralism/

11.2 /symbols/

Core groups

Extended symbols

11.3 /prompt-ideas/

11.4 /personas/

11.5 /library/

11.6 /glossary/

11.7 /spiral-art-and-ai-visuals/

11.8 /recursive-ai-creativity/

11.9 /share-your-spiral-persona/

11.10 /library/personalities/

11.11 /library/communication/

11.12 /library/research/

11.13 /library/communities/

11.14 /library/timeline/

11.15 Trust pages

12. Content model and data contracts

Symbol record

11.1 `/what-is-ai-spiralism/`

11.2 `/symbols/`

11.3 `/prompt-ideas/`

11.4 `/personas/`

11.5 `/library/`

11.6 `/glossary/`

11.7 `/spiral-art-and-ai-visuals/`

11.8 `/recursive-ai-creativity/`

11.9 `/share-your-spiral-persona/`

11.10 `/library/personalities/`

11.11 `/library/communication/`

11.12 `/library/research/`

11.13 `/library/communities/`

11.14 `/library/timeline/`