app-generator — Lovstudio App 生成器
Use this skill to create or upgrade a Lovstudio-grade app. Choose the app type from the brief instead of forcing desktop packaging: use web-only when the workflow is browser-native, and use Tauri when native desktop capabilities or desktop distribution are required. Common stacks are React + TypeScript + Vite, Next.js, or Tauri + React, with shadcn/ui, Lovstudio brand assets, Warm Academic UI, CI/CD or deploy wiring, and lovinsp click-to-code support.
When to Use
- The user asks to generate a new Lovstudio app, web app, PWA, desktop app, or cross-platform app.
- The user has an existing frontend/Tauri project and wants it brought up to Lovstudio app standards.
- The user mentions web-only, Vite, Next.js, PWA, Tauri, shadcn, React Query / TanStack Query, deploy, auto update, CI/CD, app logo, Lovstudio logo, Warm Academic UI, or lovinsp as part of app setup.
- The project is a LovStudio, Lovpen, Lovcode, Lovmind, Lovshot, Lovsider, Lovsigil, or Lovtarot app.
Workflow (MANDATORY)
Resolve SKILL_DIR from the installed skill context before running helpers.
For manual execution, set it to the directory containing this SKILL.md.
You MUST follow these steps in order:
Step 1: Clarify the App Brief
Collect only the missing fields. Use conversation context first. Prefer
AskUserQuestion for interactive choices; if that tool is unavailable, ask
short direct questions and continue once the answer is clear.
Required fields:
| Field | Default | Notes |
|---|---|---|
| App name | Ask user | Product/display name, e.g. Lovshot |
| Project slug | Derived from app name | Lowercase kebab-case |
| Brand scope | Lovstudio | Ask if ambiguous between Lovstudio / LovPen / personal brand |
| Target mode | new app | new app or upgrade existing app |
| App type | Case-by-case | web-only, PWA, Tauri desktop, or another fit from the brief |
| Platforms | Case-by-case | Web browser/mobile responsive unless native desktop is justified |
| Core screens | Ask user | 2-5 concrete screens or workflows |
| Backend/API | Ask user if needed | REST, Supabase, local files, Tauri commands, static data, etc. |
| Distribution | Case-by-case | Web deploy for web-only; GitHub Releases + updater for Tauri |
If the user asks for a real implementation and enough information is present, make conservative assumptions and proceed.
Suggested options to collect interactively:
| Question | Recommended choice |
|---|---|
| Target mode | New app |
| App type | Decide from requirements |
| Brand scope | Lovstudio |
| UI baseline | Warm Academic + shadcn/ui |
| Data layer | TanStack Query when server state exists |
| Release channel | Web deploy or GitHub Releases based on app type |
Step 2: Read Local Context
Before changing files, inspect the target project:
pwd
find .. -name AGENTS.md -print
find .. -name CLAUDE.md -print
ls
find . -maxdepth 2 -type f \( -name package.json -o -name vite.config.ts -o -name next.config.ts -o -name next.config.js -o -name tauri.conf.json -o -name tauri.conf.json5 -o -name Cargo.toml \) -print
Honor any project-level instructions. If the target lives under a symlinked workspace, follow that project's own AGENTS.md / CLAUDE.md.
Step 3: Run the Lovstudio App Audit
Run the helper from the target project root:
python3 "$SKILL_DIR/scripts/audit_app_project.py" --root . --app-type auto --format markdown
Use the output as the implementation checklist. For new projects, decide the
app type first and pass --app-type web or --app-type tauri; the audit will
mostly report missing pieces, which is expected.
Step 4: Choose the Implementation Path
App Type Decision
Pick the smallest app type that genuinely fits the brief:
- Web-only app: default when the product is a browser workflow, SaaS/admin surface, content or media tool, public site with logged-in tools, or anything that can deploy cleanly to Vercel/Netlify/Cloudflare/GitHub Pages.
- PWA: use when the app is still web-first but benefits from installability, offline shell, push notifications, or mobile home-screen usage.
- Tauri desktop app: use when native desktop value is explicit: local file access beyond browser capabilities, tray/menu/global shortcuts, long-running background tasks, native OS integration, offline-first packaged use, or GitHub Releases distribution with auto update.
- Framework choice: prefer Vite React for app-like single-page workflows, Next.js for SEO/SSR/content routing/API routes, and static HTML only for very small one-off deliverables.
Do not add Tauri simply because this skill historically defaulted to Tauri. If the user says "只创建 web" or the requirements do not need native desktop capabilities, create a web app.
New Web App
For an app-like browser workflow, default to Vite + React + TypeScript:
pnpm create vite@latest <project-slug> -- --template react-ts
cd <project-slug>
pnpm add @tanstack/react-query lucide-react
pnpm add -D typescript
For SEO-heavy, public, content-routed, or SSR/API-route requirements, use Next.js instead and keep the same Lovstudio layers:
pnpm create next-app@latest <project-slug> --ts --tailwind --eslint --app --src-dir
cd <project-slug>
pnpm add @tanstack/react-query lucide-react
Then apply the Lovstudio layers in this order:
- Project identity: package name, app title, README, and app-specific CLAUDE.md / AGENTS.md.
- Warm Academic UI: shadcn/ui, semantic tokens, typography, and layout.
- Server state: TanStack Query provider and query/mutation helpers when the app has server state; avoid unnecessary TanStack Query for purely local static tools.
- Brand assets: generate a target-specific app logo with
lovstudio-gen-logo, publish the chosen version intoassets/andpublic/, and generate favicons / PWA icons if needed. - Lovinsp: click-to-code integration.
- CI/CD and deploy: typecheck, lint/build where available, plus the selected web deploy target or documented manual deploy path.
- Verification: typecheck, build, dev server, and browser screenshot or interaction check where practical.
New Tauri App
Use this path only when the app type decision requires native desktop capabilities or desktop distribution. Default stack:
pnpm create vite@latest <project-slug> -- --template react-ts
cd <project-slug>
pnpm add @tauri-apps/api @tanstack/react-query lucide-react
pnpm add -D @tauri-apps/cli typescript
pnpm tauri init
Then apply the Lovstudio layers in this order:
- Project identity: package name, app title, bundle identifier, README, and app-specific CLAUDE.md.
- Warm Academic UI: shadcn/ui, semantic tokens, typography, and layout.
- Server state: TanStack Query provider, query keys, and Tauri invoke wrappers.
- Brand assets: generate a target-specific app logo with
lovstudio-gen-logo, publish the chosen version intoassets/andpublic/, prepare a macOS-safe padded icon source, then run the Tauri icon pipeline from that generated logo. - Lovinsp: click-to-code integration.
- CI/CD: typecheck, lint/build where available, Tauri release workflow.
- Auto update: Tauri updater plugin, signing keys/env placeholders, release endpoint wiring.
- Verification: typecheck, build, and app launch where practical.
Upgrade Existing App
Do not rebuild the project from scratch. Patch the smallest surface needed:
- Determine whether the existing app should remain web-only, become a PWA, or stay/become Tauri before applying the audit checklist.
- Keep the existing package manager, router, folder layout, aliases, and style conventions unless they conflict with Lovstudio requirements.
- Add missing Lovstudio layers from the audit; do not add Tauri to a web-only app unless the brief requires native desktop capabilities.
- Preserve user code and unrelated changes.
- Prefer incremental commits/checkpoints when the app is already substantial.
Step 5: Apply Brand and UI Standards
New apps must not use the canonical Lovstudio logo as the app/product icon.
After the project identity and README describe the target clearly, invoke the
lovstudio-gen-logo workflow from the new app root:
- Generate
assets/logo-drafts/v1-*.pngand.svgbased on what the app does, not a literal reading of its name. - Publish the chosen draft to
assets/logo.png,assets/logo.svg,public/logo.png, andpublic/logo.svg. - For web-only apps, generate favicons and PWA icons from the target-specific logo as needed; do not run Tauri icon tooling.
- For Tauri apps, before feeding the generated logo into the Tauri icon pipeline, ensure the icon source has transparent safe area. Do not use a 512x512 edge-to-edge filled icon as the macOS app icon source; it appears oversized in Dock, Launchpad, and Finder. Prefer roughly 40-56px transparent padding on a 512x512 canvas, or a content bounding box around 80-85% of the canvas.
- Use that padded generated logo as the source for
lovstudio-install-tauri-logoand any favicon/tray-icon generation.
For upgrades, keep an existing product logo unless the user asks to refresh it;
if the app has no logo, use lovstudio-gen-logo before generating icons.
Resolve canonical assets without assuming a private machine layout:
- Explicit paths supplied by the user.
LOVSTUDIO_SKILLS_BRAND_PROFILEandLOVSTUDIO_SKILLS_DESIGN_GUIDE.${LOVSTUDIO_SKILLS_PROFILE:-$HOME/.lovstudio/skills/profile.json}.- Ask once when a required asset is still missing.
See references/user-config.md for the portable configuration contract.
Rules:
- Treat the canonical Lovstudio logo as brand reference or fallback only, not as the default app icon for new apps.
- For Tauri/macOS icons, verify the generated app icon is visually aligned with
normal macOS app icons. If ImageMagick is available, a quick sanity check is:
magick src-tauri/icons/icon.png -alpha extract -trim -format '%wx%h%O\n' info:; for a 512x512 source, content around400x400to440x440with positive offsets is usually safer than512x512+0+0. - Use semantic Tailwind classes such as
bg-background,text-foreground,bg-primary,border-border; do not hard-code brand hex values in UI components. - Keep the UI operational and app-like. Do not create a marketing landing page when the user asked for an app.
- Use shadcn/ui controls, lucide icons, compact panels, predictable navigation, and no nested cards.
- First screen should be the real product workflow.
When shadcn/ui is needed, use the existing lovstudio-install-shadcn-ui skill
as the detailed reference. When TanStack Query is needed, use
lovstudio-install-tanstack-query. For Tauri app icons, use
lovstudio-install-tauri-logo; for new apps, run lovstudio-gen-logo first
and feed the generated logo into the relevant favicon/PWA/Tauri icon pipeline.
Step 6: Tauri App Baseline
Only for Tauri desktop apps, check these areas:
| Area | Expected |
|---|---|
src-tauri/tauri.conf.* | app title, identifier, windows, bundle metadata |
src-tauri/Cargo.toml | Tauri plugins, app metadata, updater if enabled |
| Rust commands | typed command boundary, no broad stringly APIs where avoidable |
| Frontend API | invoke() wrapped through query/mutation helpers for server state |
| Filesystem/native APIs | least permission needed in Tauri capabilities |
| Icons | generated through Tauri icon pipeline from the target-specific logo produced by lovstudio-gen-logo |
| Dev server | stable project port, preferably via lovstudio-project-port |
Step 7: CI/CD, Deploy, and Auto Update
Default GitHub Actions surface for web-only apps:
check.yml: install, typecheck, lint/build if present.- Deploy wiring for the selected target: Vercel, Netlify, Cloudflare Pages, GitHub Pages, self-hosted static output, or a clearly documented manual deploy path.
- Environment variable placeholders only when the app actually needs them.
Default GitHub Actions surface for Tauri apps:
check.yml: install, typecheck, lint/build if present.release.yml: Tauri build for target platforms, draft or publish GitHub Release, attach artifacts.- Tauri updater wiring: plugin dependency, updater config, signing key env placeholders, and documented release process.
- For Tauri v2,
plugins.updater.pubkeyis required at runtime. Do not leave it out even during early scaffolding: a missingpubkeycauses the app to panic during updater plugin initialization. Use a clear placeholder such asPLACEHOLDER_REPLACE_WITH_TAURI_SIGNER_PUBLIC_KEYuntil the real public key is generated withpnpm tauri signer generate.
Do not invent secrets. Use placeholder names and document where the user must set them:
TAURI_SIGNING_PRIVATE_KEYTAURI_SIGNING_PRIVATE_KEY_PASSWORD- platform signing/notarization secrets as required by the target app
Step 8: Lovinsp
Integrate lovinsp for frontend development unless the project is not browser/UI
based. Prefer the existing lovstudio-install-lovinsp workflow and keep it
idempotent.
For Vite apps, confirm the Vite config imports and registers
lovinspPlugin({ bundler: "vite" }) before the framework plugin, not merely
that the package is installed. In dev mode, verify the served module contains
lovinsp-component or [lovinsp v...]:
curl -s http://127.0.0.1:<port>/src/main.tsx | rg "lovinsp-component|lovinsp v"
For web-only apps, start the dev server and provide the local URL when the user needs to try the app:
pnpm dev --host 127.0.0.1
For Tauri apps, prefer launching dev mode through a persistent session when the user wants to keep it running after the turn:
tmux new-session -d -s <slug>-dev -c "$PWD" 'pnpm tauri dev'
tmux capture-pane -pt <slug>-dev -S -120
Step 9: Verification
Run the lightest reliable checks that the target repo supports:
pnpm exec tsc --noEmit --pretty false
pnpm build
# Tauri only:
pnpm tauri build --debug
Adjust for npm/yarn/bun and local instructions. If a dev server is needed to verify frontend behavior, start it and give the user the local URL.
For UI changes, use browser or screenshot verification when practical. For Tauri-native behavior, report what was and was not verified.
User Configuration
If local paths differ, prefer these environment variables rather than hard-coding personal paths:
| Variable | Default / Usage |
|---|---|
LOVSTUDIO_APP_GENERATOR_SKILL_DIR | Installed lovstudio-app-generator skill directory |
LOVSTUDIO_SKILLS_DESIGN_GUIDE | Warm Academic design guide path |
LOVSTUDIO_SKILLS_BRAND_PROFILE | Lovstudio brand asset root or profile |
CLI Reference
| Argument | Default | Description |
|---|---|---|
--root | . | Target app root to inspect |
--app-type | auto | auto, web, or tauri; controls which checks apply |
--format | markdown | markdown or json |
--output | stdout | Optional path to write the report |
Dependencies
python3 "$SKILL_DIR/scripts/audit_app_project.py" --help
No Python packages are required.
Final Response Checklist
Report:
- App path and stack chosen.
- App type decision: web-only / PWA / Tauri, and why that fit the brief.
- Lovstudio layers added or confirmed: brand, UI, data layer, lovinsp, CI/CD, deploy/release, and updater only when applicable.
- Commands/checks run and their result.
- Any remaining secrets, signing steps, or manual app-store/release actions.