appshot-core

Appshot Core — Foundation

Reference skill for all Appshot skills. Read this before executing appshot-videos or appshot-images.

Architecture

• Remotion 4.0 + React 18 + Tailwind CSS 3.4
• Config defines app metadata and brand only — scenes are custom .tsx files, not config entries
• Each project has an orchestrator component (e.g., FooPreview.tsx) that sequences custom scenes via Remotion <Sequence> + <SceneWrap>
• All primitives are brand-aware via a brand prop derived from the config's BrandColors

Project Context (auto-injected)

• Package manifest: !cat package.json 2>/dev/null || cat pubspec.yaml 2>/dev/null || cat app.json 2>/dev/null
• App colors: !find . -maxdepth 4 \( -name 'colors.xml' -o -name 'Colors.swift' -o -name 'colors.ts' -o -name 'theme.ts' -o -name 'Color.kt' -o -name 'tailwind.config.js' -o -name 'tailwind.config.ts' \) 2>/dev/null | head -5 | xargs head -50 2>/dev/null
• App icon: !find . -maxdepth 5 \( -name 'ic_launcher.png' -o -name 'icon.png' \) -type f 2>/dev/null | head -3
• Store metadata: !cat fastlane/metadata/en-US/full_description.txt 2>/dev/null || cat fastlane/metadata/en-US/description.txt 2>/dev/null || cat fastlane/metadata/android/en-US/full_description.txt 2>/dev/null
• README excerpt: !head -80 README.md 2>/dev/null

Extraction & Context Caching

Both appshot-videos and appshot-images use this extraction process. Results are cached to .appshot-context.json so extraction only runs once per project.

Check for cached context

Before scanning, check if .appshot-context.json exists in the project root. If it does:

1. Load and present a summary to the user
2. Ask: "I found a previous extraction. Confirm this is still correct, or re-scan?"
3. If confirmed, skip extraction and proceed to the calling skill's next phase
4. If re-scan requested, run extraction below and overwrite the file

Extraction steps

Step 1: Detect framework

Check for marker files in this order. Stop at the first match.