Merge pull request #15 from roast-dev/2-implement-paywall-logic-in-browser-ext

Paywall Logic & UI

Author: allozaur

.github/workflows/apps_stripe_customer_verification_publish_preview.yml

@@ -4,6 +4,8 @@ on:
   push:
     branches-ignore:
       - main
+    paths:
+      - 'apps/stripe-customer-verification/**'
 
 jobs:
   deploy:

apps/browser-extension/package.json

@@ -4,7 +4,7 @@
 	"type": "module",
 	"scripts": {
 		"dev": "vite dev --port 5174",
-		"build-extension": "vite build && tsc ./build/*.ts && zip -r ./roast-extension.zip ./build",
+		"build:extension": "vite build && tsc ./build/*.ts && zip -r ./roast-extension.zip ./build",
 		"preview": "vite preview",
 		"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
 		"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch",

apps/browser-extension/src/lib/config/free-limit-used-headlines.ts

@@ -0,0 +1,8 @@
+export default [
+	`You're on fire today! Ready for unlimited roasts? 🔥`,
+	`You've used up your free roasts! Ready to go unlimited? 🔥`,
+	`Enjoyed the roasts? There's plenty more where that came from 🔥`,
+	`Your code deserves unlimited roasts! (Your team will thank you) 🔥`,
+	`High five for 10 roasts! Ready to make every PR awesome? ✨`,
+	`Save hours of review time for just $9? That's a steal! 🎯`
+];

apps/browser-extension/src/lib/config/initial-prompt-claude.ts

@@ -8,4 +8,6 @@ At the same time I want you to be constructive - point out issues and provide re
 
 Also, if you see that the code is well-written, point it out just at the end, but do this in a funny way.
 
-Overall, try not to be too verbose, but take your time with the roasting.`;
+And one last important thing is — if you have a hard time finding issues, don't make them up. Just say that the code is good and you're impressed. But if you do find issues, don't hold back.
+
+Overall, try not to be too verbose and take your time with the roasting.`;

apps/browser-extension/src/lib/config/initial-prompt-gemini.ts

@@ -15,6 +15,8 @@ At the same time I want you to be constructive - point out issues and provide re
 
 Also, if you see that the code is well-written, point it out just at the end, but do this in a funny way.
 
+And one last important thing is — if you have a hard time finding issues, don't make them up. Just say that the code is good and you're impressed. But if you do find issues, don't hold back.
+
 Overall, try not to be too verbose, but take your time with the roasting.
 
 You don't need to be super polite, actually be a bit cocky and funny, but don't be rude. The goal is to make the code author laugh and learn from the feedback.

apps/browser-extension/src/lib/config/initial-prompt-gpt.ts

@@ -14,6 +14,8 @@ At the same time I want you to be constructive - point out issues and provide re
 
 Also, if you see that the code is well-written, point it out just at the end, but do this in a funny way.
 
+And one last important thing is — if you have a hard time finding issues, don't make them up. Just say that the code is good and you're impressed. But if you do find issues, don't hold back.
+
 Overall, try not to be too verbose, but take your time with the roasting.
 
 You don't need to be super polite, actually be a bit cocky and funny, but don't be rude. The goal is to make the code author laugh and learn from the feedback.