Follow-Up Packs
Create concrete stack packs from this template in the order below unless product priorities change.
Recommended Order
| Order | Pack | Why next | First evidence to collect |
|---|---|---|---|
| 1 | learn/stacks/decision-ladder.md | Helps choose stacks before deep pack work | Current lab app goals, target platforms, release constraints |
| 2 | learn/stacks/android-kotlin-compose/ | Strong near-term app opportunity with real platform friction | Android docs, Compose samples, Gradle commands, emulator/device gates, signing and Play policy |
| 3 | learn/stacks/distribution/ | Cross-cutting signing, packaging, stores, installers, releases | Android, Windows, desktop, web, and mobile release docs |
| 4 | learn/stacks/local-first-data/ | Needed by offline-first apps and user-owned data workflows | SQLite, sync, backup, export, encryption, migration docs |
| 5 | learn/stacks/tauri-2/ | Strong desktop candidate with native permissions and bundling risks | Tauri 2 docs, plugin permissions, updater, signing, installers |
| 6 | learn/stacks/windows-app-sdk-winui/ | Native Windows opportunity with packaging and store complexity | Windows App SDK docs, MSIX, signing, Store policy, WinUI samples |
Follow-Up Rule
Do not start a concrete pack with broad web research. Start from this template, fill docs-index.md, then answer the operational files in order.
Useful First Prompt
Run /plan-learn for [stack slug]. Use learn/stacks/_template/ as the required output shape. Focus on official docs, starter commands, package/sign/release gates, platform pitfalls, and reference apps. Do not clone or run third-party code without approval.