boomcode 0.5.4__tar.gz → 0.5.5__tar.gz

{boomcode-0.5.4 → boomcode-0.5.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boomcode
-Version: 0.5.4
+Version: 0.5.5
 Summary: BOOMCODE — AI coding CLI for Termux. Your app, BLAM, done!
 Author: zyvo9
 License: MIT

{boomcode-0.5.4 → boomcode-0.5.5}/boomcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boomcode
-Version: 0.5.4
+Version: 0.5.5
 Summary: BOOMCODE — AI coding CLI for Termux. Your app, BLAM, done!
 Author: zyvo9
 License: MIT

{boomcode-0.5.4 → boomcode-0.5.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "boomcode"
-version = "0.5.4"
+version = "0.5.5"
 description = "BOOMCODE — AI coding CLI for Termux. Your app, BLAM, done!"
 readme = "README.md"
 requires-python = ">=3.8"

{boomcode-0.5.4 → boomcode-0.5.5}/python/boomcode/__init__.py

@@ -6,4 +6,4 @@ hands over to the real installer (install.sh) which does everything
 else (core engine, deps, single-line live progress).
 """
 
-__version__ = "0.5.4"
+__version__ = "0.5.5"

{boomcode-0.5.4 → boomcode-0.5.5}/python/boomcode/layer/skills/lets-scroll/SKILL.md

@@ -71,18 +71,29 @@ Ask these in plain words. Accept answers in any language. Record the answers
 3. **Look & feel** — show the options by feel, one line each (default: **clay
    diorama**; alternates in `references/prompts.md`: papercraft, glossy toy,
    claymation, neon night, photoreal). One choice for the whole site.
-4. **Camera style** — ask by feel: *"should the camera walk through the world
-   (walkthrough) or dive down into it from above (fly-through)?"*
-   - walkthrough → architecture **A** (one continuous forward take — simpler,
-     recommended)
-   - fly-through, god's-eye → architecture **B** (dive + connector clips)
-   - If they want a fixed isometric camera the whole way, that's A with the
-     locked-iso clause from `references/prompts.md`.
-5. **How many scenes?** Offer 2 / 4 / 6 (6 is the max that stays smooth).
+4. **Site type** — what kind of journey? Show these picks, one line each:
+   - **Business tour** — walk through the shop/kitchen/office like a visitor
+   - **Product showcase / review** — the camera circles and closes in on ONE
+     product from all sides, close-up details, like a video review
+   - **Story journey** — how it's made / farm-to-table / idea-to-launch
+   - **Portfolio / gallery** — one beautiful vignette per work or project
+   The pick shapes the scene list (a product showcase builds every scene
+   around the same product; a tour builds one scene per place, etc.).
+5. **Camera style** — ask by feel, one line each:
+   - **Walkthrough** — the camera walks through the world like a visitor
+     (architecture **A** — one continuous forward take; simplest, recommended)
+   - **Fly-through** — the camera dives down into the world from above
+     (architecture **B** — dive + linking clips)
+   - **Orbit showcase** — for product review: the camera circles the product,
+     sweeps around it and pushes in on details (A with orbit moves from
+     `references/prompts.md` mid-leg move library)
+   - **Postcard view** — a fixed, postcard-pretty angle on every scene,
+     almost no camera movement (A with the locked-iso clause)
+6. **How many scenes?** Offer 2 / 4 / 6 (6 is the max that stays smooth).
    Then propose the scene list from their answer to #1 — each scene gets a
    subject, a short headline idea, one-line body, 0–3 tags; the last scene is
    the hero + call-to-action. Confirm the list with the user.
-6. **Phone version?** ("should the site also have a vertical version for
+7. **Phone version?** ("should the site also have a vertical version for
    phones?") — if yes, the kit doubles the video prompts (a 9:16 copy of each)
    — say plainly that it's about twice the generating work for them.