Divine Mobile Guide Creator

Divine Mobile Guide Creator

Overview

divinevideo/divine-mobile 레포를 기반으로, 이 블로그의 관례에 맞춘 "챕터형 한국어 가이드 시리즈"를 생성/갱신한다. 결과물은 _posts/ 챕터 글, 시리즈 인덱스(루트 페이지), 그리고 /home/blog/_tabs/guides.md 카드 추가까지 포함한다.

Outputs (this repo conventions)

• 챕터 포스트: /home/blog/_posts/YYYY-MM-DD-divine-mobile-guide-XX-{slug}.md
• 시리즈 인덱스(루트 페이지): /home/blog/divine-mobile-guide.md
• 가이드 목록 카드: /home/blog/_tabs/guides.md

Inputs to Confirm (ask user)

• AUTHOR (front matter), PROJECT_NAME (타이틀용, 기본: diVine)
• series 슬러그(기본: divine-mobile)
• 챕터 수: 자동(권장) 또는 지정(N개)
• guides 탭 섹션: 애매하면 개발 도구 또는 모바일로 분류

Workflow

1) Collect sources (clone)

SCRATCH="$(mktemp -d /tmp/codex-divine-mobile.XXXXXX)"
cd "$SCRATCH"
git clone --depth 1 https://github.com/divinevideo/divine-mobile
cd divine-mobile

우선 분석 대상:

• README.md
• docs/README.md, docs/ARCHITECTURE.md
• docs/CF_STREAM_SETUP.md, docs/VIDEO_UPLOAD_ARCHITECTURE-*.md
• mobile/pubspec.yaml, mobile/lib/ (서비스/프로바이더/업로드 파이프라인)

2) Design chapter plan

권장 초안은 references/chapter-map.md를 참고하고, 레포의 실제 문서 구조에 맞춰 8-14개 범위로 조정한다.

3) Write posts using existing blog templates

이 블로그 템플릿은 기존 스킬을 그대로 재사용한다:

• 포스트 템플릿: /home/blog/.codex/skills/blog-guide-creator/references/post-template.md
• 시리즈 인덱스: /home/blog/.codex/skills/blog-guide-creator/references/index-template.md
• 네비/목차: /home/blog/.codex/skills/blog-guide-creator/references/nav-template.md

파일명/퍼머링크 규칙:

• 날짜: CURRENT_DATE=$(date +%Y-%m-%d)
• _posts/${CURRENT_DATE}-divine-mobile-guide-${num}-${slug}.md
• permalink: /divine-mobile-guide-${num}-${slug}/

주의(보안/저작권):

• 레포 문서에 CF_STREAM_TOKEN 예시 값이 있어도 블로그에는 실제 토큰을 절대 그대로 싣지 말고 <YOUR_CF_STREAM_TOKEN> 형태로 마스킹한다.
• 문서 원문을 길게 복붙하지 말고, 핵심을 요약/재구성하고 코드/명령은 필요한 최소만 인용한다.

4) Update guides tab

/home/blog/_tabs/guides.md에서 적절한 섹션의 guide-grid 맨 위에 카드(최신)를 추가한다.

5) Validate and clean up

cd /home/blog
git status

가능하면:

bundle exec jekyll build

정리:

rm -rf "$SCRATCH"

Git workflow

기본 동작은 commit 후 push까지 완료한다. 사용자가 "push는 하지 마"라고 하면 push만 생략한다.

cd /home/blog
git add _posts/*divine-mobile-guide-*.md divine-mobile-guide.md _tabs/guides.md
git commit -m "diVine(divine-mobile) 가이드 시리즈 추가"
git push

divine-mobile guide: chapter map (seed)

Target repo: https://github.com/divinevideo/divine-mobile

Goal: turn the repo's existing docs + code structure into a Korean chapter-style guide series for this blog.

Key source files (start here)

• README.md: product overview + build instructions (Flutter)
• docs/README.md: mobile app dev setup, build scripts, CF Stream token notes
• docs/ARCHITECTURE.md: Nostr SDK / layered architecture overview
• docs/CF_STREAM_SETUP.md: Cloudflare Stream token + upload pipeline overview
• docs/VIDEO_UPLOAD_ARCHITECTURE-*.md: deep dive on upload/publish architecture
• docs/nostr_pagination_docs.md: feed pagination behavior for kind 32222
• docs/STARTUP_PERFORMANCE_OPTIMIZATIONS.md, docs/WEB_PERFORMANCE_OPTIMIZATIONS.md: perf notes (if you include perf chapters)
• docs/RELEASE_CHECKLIST.md, docs/BUILD_SCRIPTS_README.md, codemagic.yaml: release/CI/CD

App code anchors (for diagrams and "where to look"):

• mobile/lib/main.dart: entrypoint
• mobile/lib/providers/app_providers.dart: service wiring (Riverpod)
• mobile/lib/services/: upload/feed/nostr-related services
• mobile/lib/screens/, mobile/lib/widgets/: UI surface for features described in docs

Recommended chapter outline (adjust to doc reality)

Keep it around 8-14 chapters; merge/split based on how much the repo already documents.

1. intro: diVine(OpenVine) overview, what "Nostr-based short-form video" means, what lives in this repo. Sources: README.md

2. getting-started: Flutter install, flutter doctor, mobile/ setup, basic run commands. Sources: README.md, docs/README.md, mobile/pubspec.yaml

3. repo-structure: Top-level folders (mobile/, docs/, website/, etc) and how work is organized. Sources: tree + docs/ARCHITECTURE.md

4. core-architecture: High-level architecture (layers, Nostr client concepts, storage/crypto). Sources: docs/ARCHITECTURE.md

5. nostr-event-model: Nostr event types used by the app; focus on kind 32222 and tags the app relies on. Sources: docs/NOSTR_EVENT_TYPES.md, docs/nip-vine.md

6. video-recording-flow: Recording UX and flow (segmented recording, thumbnail generation, etc) as implemented in Flutter. Sources: relevant mobile/lib/screens/, mobile/lib/services/

7. video-upload-cloudflare-stream: CF Stream integration, where token is injected, upload lifecycle, and "publish to Nostr" step. Sources: docs/CF_STREAM_SETUP.md, docs/VIDEO_UPLOAD_ARCHITECTURE-*.md Note: never publish real CF_STREAM_TOKEN values; use placeholders.

8. feed-and-pagination: How feeds are loaded/paginated, caching/preloading considerations. Sources: docs/nostr_pagination_docs.md

9. moderation-and-reporting (optional but common): Mute lists (NIP-51), reporting flow, how filtering is applied. Sources: docs/MODERATION_*

10. testing: Unit/widget/integration test strategy, common pitfalls. Sources: docs/*TEST*.md, mobile/test/, mobile/integration_test/

11. performance (optional): Startup + web perf notes; what to measure and what was optimized. Sources: docs/STARTUP_PERFORMANCE_OPTIMIZATIONS.md, docs/WEB_PERFORMANCE_OPTIMIZATIONS.md

12. release-and-deploy: Build scripts, codemagic, release checklist; iOS/Android/web targets. Sources: docs/BUILD_SCRIPTS_README.md, docs/RELEASE_CHECKLIST.md, codemagic.yaml

Blog-specific defaults

• series slug: divine-mobile
• Categories/tags (suggested): flutter, mobile, nostr, cloudflare-stream