A Three-Part Sprint to Stabilize the Pipeline

Day 32 turned into a three-part effort over consecutive sessions. The theme was simple: make the storypack pipeline reliable end-to-end so every story can ship without manual cleanup.

Part 1 - Fix Visual Drift at the Source

The biggest issue was visual inconsistency. A prompt-enhancement bug caused scenes to drift into photo-realism and characters to look too similar. I fixed the prompt logic and locked in a strict rule:

  • Style guide images are for human review only
  • All generators must use the text-based visualStyle from the JSON

That change stopped image bleed and gave characters distinct visual identities again.

Part 2 - Simplify the Storypack Structure

Next was workflow structure. I consolidated the generation steps into a clear four-phase flow and standardized the storypack folder layout:

  • Phase 1: Story JSON + Korean localization
  • Phase 2: Asset generation (style guide, characters, cover, scenes, ending cards)
  • Phase 3: Markdown generation (EN + KO)
  • Phase 4: Deploy + build

This phase also introduced dynamic personality titles in likelyPersonalities and made ending cards mandatory by default. Jekyll & Hyde’s 16 endings now ship with story-specific titles in both languages.

Part 3 - Complete Deployment + Jekyll Redeploy

The last piece was deployment. The pipeline could deploy JSON, scenes, cards, and markdown, but library entry markdown was still manual. I added a catalog entry generator that outputs EN + KO entries and is now deployed alongside everything else.

At the same time, I cleaned out the old Jekyll artifacts and redeployed the regenerated story using the new structure:

  • Scene images now deploy to src/assets/stories/[id]/
  • Covers use [id]-cover.webp
  • Catalog entries deploy into src/content/novels/ and src/content/novels-ko/

The result: Jekyll can be redeployed cleanly without leftover files or missing library entries.

Why This Matters

A pre-generated product only works if the pipeline is complete. Every missing artifact becomes a future bug. After these three sessions, the workflow is finally cohesive: JSON, assets, markdown, cards, and catalog entries now ship together.

Next

Now I can move faster without breaking consistency. The plan is to apply the same pipeline to upcoming story packs and focus more on story quality and distribution.