@recipeclubwithj: Love sushi? Try these Sweet Chilli Sushi Cups 🍣 For the crispy rice cups: 1 cup cooked rice (cold works best) 1 tsp Olive oil For the filling: 100g salmon (or tuna / prawns / chicken) For the sauce 1 tbsp mayo (or Kewpie) 1 tbsp Mingle Sweet Chilli sauce 1 tsp soy sauce 1 tsp rice vinegar 1–2 tsp furikake seasoning To finish: - 1 spring onion, sliced - Extra furikake seasoning Method 1. Preheat the oven to 200c fan (or air fryer to 190c). 2. Press the cooked rice tightly into a mini muffin tray to form cups. 3. Spray lightly with oil, then bake for 10-15 minutes if using airfryer (oven will take 20-30 minutes) until golden and crisp. 4. In a bowl, mix the mayo, sweet chilli sauce, soy sauce and rice vinegar. 5. Add your chosen protein and furikake, then mix until combined. 6. Remove the crispy rice cups from the oven and let cool for 2–3 minutes to firm up. 7. Spoon the filling into each cup. 8. Finish with spring onion + extra furikake. #salmon #sushi #ricecups

recipeclubwithj
recipeclubwithj
Open In TikTok:
Region: AU
Sunday 27 September 2026 23:58:01 GMT
8621
63
1
20

Music

Download

Comments

lilianatrejos1
Lili :
[Cara muy sonriente][Cara muy sonriente][Cara muy sonriente]
2026-09-28 02:50:03
0
To see more videos from user @recipeclubwithj, please go to the Tikwm homepage.

Other Videos

How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say
How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say "paid". The text reminder plugs in the same way with Twilio. Every outside service connects like this: account, key, drawer, sentence. Go live: push to GitHub, import into Vercel, paste the same keys into its settings, deploy. Buy your domain, add it in Vercel, copy two DNS lines into your domain company, and it's live on your own name with the padlock. Before real customers: point the webhook at the new address and swap test keys for live keys. After that, adding more is one sentence: Google Calendar sync, a loyalty card, review requests, or an automation that drops every new booking into your CRM. Your job becomes the owner who tests every button like a customer would. #buildwithai #claudecode #aiagent

About