Setting Up Bloomineasy, Part Three: Creative Follow-Up Prompts After the Design Pass

Once install and design are grounded, use sharper prompts to turn Bloomineasy into a specific content product.

Move beyond generic branding prompts with creative follow-up prompts for positioning, taxonomy, homepage structure, article clusters, widgets, and critique passes.

Prompt in campaigns, not chores

After Part One and Part Two, the app should be installed, verified, and visually grounded. That is when prompting can become more creative, because the agent has a working system and a design source of truth.

The best follow-up prompts ask for an outcome, a point of view, and a review step. Instead of asking for a generic homepage or generic SEO checklist, ask the agent to make choices, show alternatives, explain tradeoffs, and wait before editing.

• Setting Up Bloomineasy, Part One: Install the Vanilla Starter
• Setting Up Bloomineasy, Part Two: Add DESIGN.md and Run the Design Pass

Find a sharper creative direction

This prompt is for the moment when the site works but still feels too close to a starter. It asks for distinct creative directions before implementation, so the project owner can choose a direction instead of reviewing a random first draft.

Creative direction prompt

The verified Bloomineasy install and DESIGN.md pass are complete. Read DESIGN.md, the current homepage, article listing, article page, nav, footer, widgets, and site settings. Do not edit yet.

I want this site to become [SITE NAME], a content-led site for [AUDIENCE] who need [PRIMARY JOB TO BE DONE]. Propose three distinct creative directions that could fit the brand. For each direction, include: homepage thesis, visual mood, navigation story, article library strategy, widget strategy, tone sample, what to avoid, and one risk. Recommend one direction and explain why. Stop and wait for my choice before editing.

Shape taxonomy as a reader journey

Bloomineasy taxonomy is not just filing. Categories, sectors, and sub-sectors become browsing paths, article URLs, sitemap entries, and editorial planning structure. This prompt asks the agent to design taxonomy around what readers are trying to understand.

Reader-journey taxonomy prompt

Design the Bloomineasy taxonomy for [NICHE] as a reader journey, not a folder dump. Use DESIGN.md and the chosen creative direction. Create 4-6 categories, each with 3-5 sectors and 3-5 sub-sectors. For every category, explain the reader question it answers, the search intent it supports, the article types it should contain, and the widget behavior it should inherit. Include URL-safe slugs, 20 starter article ideas, and a recommendation for whether to create the taxonomy through the admin UI, AI Category Wizard, or a seed script. Do not apply changes until I approve.

Make the homepage a useful content surface

A Bloomineasy homepage should not become a thin marketing splash page unless the project truly needs that. The homepage can introduce the site, show paths into the article library, surface categories, and use widgets as meaningful next steps.

Homepage concept prompt

Redesign the public homepage for [SITE NAME] using the approved creative direction and DESIGN.md. Keep Bloomineasy's content-first purpose visible. Propose a homepage that includes: a clear editorial promise, reader pathfinding, featured categories, latest or selected articles, one useful widget zone, one primary CTA, one secondary CTA, and a footer that helps readers continue. Avoid generic SaaS hero copy. Before editing, show the section plan, sample copy, data dependencies, and any site settings I need to fill in.

Plan article clusters before writing

The strongest Bloomineasy sites will usually grow through clusters: groups of articles that answer a real set of reader questions and link to each other intentionally. This prompt makes the agent plan the cluster before drafting.

Article cluster prompt

Create a 12-article cluster for [TOPIC] inside this Bloomineasy site. Use the approved taxonomy and DESIGN.md. For each article, provide title, slug, reader problem, search intent, excerpt, target category/sector/sub-sector, suggested internal links, widget recommendation, SEO title, SEO description, and publish priority. Include one hub article, six practical guides, three comparison or decision articles, and two glossary or reference articles. Do not write full drafts until I approve the cluster plan.

Make widgets feel editorial

Widget prompts work better when they explain why a CTA, form, snippet, or custom block belongs in a specific content context. The goal is not more widgets. The goal is the right next step at the right point in the library.

Editorial widget prompt

Review the approved taxonomy and article cluster plan. Design a Bloomineasy widget strategy that feels editorial, not bolted on. Recommend which CTA cards, CTA banners, contact forms, snippets, or custom blocks should appear at category, sector, sub-sector, and article level. Use inherit, replace, add, and none modes intentionally. For each recommendation, explain the reader moment, the business goal, the zone, and the reason it should or should not inherit. Do not implement until I approve.

Use a critique pass before shipping

A good final prompt asks the agent to inspect what changed against the actual product constraints. Bloomineasy has public design freedom, but it also has admin workflows, article routes, SEO behavior, Content11 ingestion, widgets, and auth boundaries that should stay intact.

Pre-ship critique prompt

Audit the current Bloomineasy customization before I ship it. Compare the implementation against DESIGN.md, the approved creative direction, the taxonomy plan, and Bloomineasy product constraints. Check homepage, blog listing, article page, contact page, legal pages, widget preview, admin sign-in, admin article editing, sitemap behavior, and responsive layout. Report issues first, grouped by severity, then propose a small fix plan. Do not make changes until I approve the fixes.