Check whether the latest changes were applied to this project.

I expected:
[describe what should have changed]

But I currently see:
[describe what you see]

Please inspect the current app, confirm whether the change exists, and fix it if it was not applied.

Improve this page so it feels polished, useful, and production-ready.

Focus on:
- clearer hero section
- stronger layout
- better spacing
- cards instead of long plain text
- helpful empty states
- clear primary action
- responsive design
- better copy
- realistic sample data if needed

Do not change the core product idea. Improve the user experience and visual structure.

The previous change was too broad. Let’s fix one thing at a time.

Current issue:
[describe one issue]

Expected behavior:
[describe what should happen]

Please only update this specific flow and avoid changing unrelated screens.

Debug the authentication flow.

Check:
- sign-up
- login
- logout
- protected routes
- redirect after login
- user profile creation
- session persistence after refresh
- test credentials

Fix any issue that prevents a user from signing in and reaching the correct dashboard.

Fix the file upload flow.

Users should be able to:
- select a file from their computer
- upload it successfully
- see upload progress or loading state
- see a success state
- see a helpful error if upload fails
- view the uploaded file after refresh

Use Storage for the file.
If the file belongs to a user or record, save the file URL or metadata in the Database.

Make this data persistent.

The app currently loses this data after refresh:
[describe the data]

Create or update the Database tables needed.
Save the data to the Database.
Load the data from the Database when the page opens.
Add loading, empty, and error states.

Debug the Stripe payment flow.

Check:
- pricing page
- checkout button
- checkout redirect
- success page
- cancelled checkout state
- subscription status
- billing settings
- premium feature access
- locked states for free users

Use Stripe for this web app payment flow.
Fix anything that prevents paid users from unlocking the correct features.

Debug the RevenueCat mobile monetisation flow.

Check:
- paywall screen
- monthly and yearly options
- purchase success state
- restore purchases
- entitlement status
- locked premium features
- subscription status in settings
- app behavior after refresh or restart

Use RevenueCat for iOS and Android monetisation.
Fix anything that prevents premium access from unlocking correctly.

Prepare this project for deployment.

Check:
- build errors
- broken pages
- main user journey
- responsive layout
- empty states
- environment or integration issues
- deployment blockers

List anything that must be fixed before deployment.

Help me troubleshoot my custom domain setup.

Domain:
[enter domain]

Check:
- whether the domain is connected to the correct project
- required DNS records
- possible conflicting records
- HTTPS status
- whether anything is still propagating

Explain exactly what I need to change.

Debug the mobile preview.

Check:
- mobile layout
- navigation
- touch targets
- app loading state
- login state
- data persistence
- broken screens
- console or runtime errors

Fix the app so it works smoothly on a real mobile device.

Run a mobile publishing readiness check.

Check:
- selected storefronts
- app name
- bundle ID
- Android package name
- app icon
- store screenshots
- Apple developer access
- Google Play service account access
- release track
- privacy and permissions
- main app flow
- mobile layout
- payment or subscription flow if included

List blockers and fix anything that can be fixed inside the app.

Improve the app store screenshots.

Use the real app screens and create a more polished screenshot set.

Focus on:
- clear benefit per screenshot
- readable headline text
- consistent design
- app-store-ready layout
- no private data
- no broken or unfinished screens
- strong first screenshot

Create variations I can choose from.

Turn this app idea into a stronger LaunchPulse build brief.

Idea:
[paste idea]

Create:
- target user
- problem
- core app flow
- first MVP features
- monetisation angle
- technical requirements
- design direction
- first LaunchPulse build prompt

Keep it focused and buildable.

Help me reduce credit usage for this project.

Suggest a phased build plan that uses smaller focused tasks instead of one large request.
Prioritize the most important features first.

Help me prepare a safe LaunchPulseClaw beta setup.

I want a Clawbot that:
[describe the Clawbot]

Please define:
- role
- target users
- allowed actions
- knowledge it should use
- boundaries
- escalation rules
- testing checklist
- required API key scopes

Turn this repeated workflow into a future LaunchPulse Skill.

Workflow:
[describe workflow]

Create:
- skill name
- purpose
- when to use it
- inputs needed
- expected output
- rules
- boundaries
- examples
- success criteria

Something is not working correctly in this LaunchPulse project.

Issue:
[describe the issue]

Expected behavior:
[what should happen]

Current behavior:
[what happens instead]

Please:
1. Inspect the relevant screen and logic
2. Identify the root cause
3. Fix the issue
4. Add loading, empty, and error states if needed
5. Test the flow after fixing
6. Summarize what changed