Skip to content

Add CCC Site Kit scripts under site-kit/ - #4

Draft
RiCSaucd wants to merge 1 commit into
mainfrom
claude/new-session-3p09ot
Draft

Add CCC Site Kit scripts under site-kit/#4
RiCSaucd wants to merge 1 commit into
mainfrom
claude/new-session-3p09ot

Conversation

@RiCSaucd

@RiCSaucd RiCSaucd commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Adds the CCC Site Kit shell scripts and their README to the repository.

What changed

New site-kit/ folder containing, verbatim as supplied:

  • build.sh — wires rendered assets and stamps the config onto the engine
  • deploy.sh — publishes the built dist/SLUG/ folder to Vercel
  • use-stock.sh — copies a stock asset set into work/SLUG/
  • README.md — the kit's own documentation

(SLUG above stands in for the slug value read from site.config.mjs.)

They live in a subfolder rather than at the repo root because the root of this
repository is the Claude Code / Hermes connection setup (setup.sh,
.claude/settings.json), which the kit is unrelated to.

The root README.md gains a short site-kit/ section and an updated repository
structure tree.

Notes for review

  • Two copies of build.sh were supplied; they are byte-identical, so only one is
    committed.
  • The scripts are not runnable as-is from this repository. The kit README
    refers to site.config.mjs, render.mjs, stamp.mjs, and the engine/,
    templates/, render/, reference/, and stock/ folders, none of which are
    present here.
  • The scripts assume a macOS shell environment and are committed unmodified, so
    these are carried over as-is rather than fixed: #!/bin/zsh shebangs, and
    build.sh calls sips (macOS only) along with ffmpeg, ffprobe, and bc
    without checking they are installed. build.sh also does no error handling if
    ffprobe returns an empty duration, which would make the bc fps computation
    fail confusingly.

Happy to follow up with a portability pass if that is wanted.

Adds the build, deploy, and use-stock shell scripts and the kit README
verbatim as provided, in a site-kit/ subfolder so they stay separate from
the Hermes connection setup at the repo root.

Two identical copies of build.sh were supplied; only one is committed.

The root README gains a site-kit section noting that the supporting files
the kit README references (site.config.mjs, render.mjs, stamp.mjs, and the
engine/, templates/, render/, reference/, and stock/ folders) are not in
this repository, and that the scripts target a macOS shell environment.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019deVPV6cpzdoFzkk6VAKXq
@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants