Cyriaque

Le créateur de Claude Code @bcherny, vient de lâcher un ÉNORME thread sur les features qu'il utilise. Y a des bangers que j'vais adopter des maintenant J'vous résume TOUT en un tweet ⬇️ >app mobile : Claude Code tourne sur l'app iOS/Android. Onglet "Code" à gauche. Boris écrit une grosse partie de son code depuis son téléphone, sans ouvrir son laptop >/teleport : tu bosses justement sur l'app mobile dans le train, t'arrives chez toi, /teleport et tu reprends ta session exactement là où t'en étais sur ton PC. Ça marche dans tous les sens : mobile, desktop, web, terminal, tu peux bouger de l'un a l'autre. >/remote-control : ton build plante pendant que t'es dehors ? Tu contrôles ta session PC depuis ton téléphone. 💡Son astuce : dans /config, il active "Enable Remote Control for all sessions" pour que ce soit toujours dispo quelque soit ta session >/branch : GAME CHANGER que j'utilisais pas encore. En gros, tu veux tester une idée risquée sans casser ta session ? /branch la duplique. Si ça foire, t'as rien perdu. Depuis le terminal : claude --resume --fork-session >/loop et /schedule : programme Claude pour tourner en boucle tout seul, jusqu'à une semaine. Boris s'en sert comme ça : - /loop 5m /babysit : review ses PR, rebase, et les pousse en prod toutes les 5 min - /loop 30m /slack-feedback : crée des PR à partir du feedback Slack toutes les 30 min - /loop /post-merge-sweeper : rattrape les commentaires de review qu'il a ratés - /loop 1h /pr-pruner : ferme les vieilles PR qui servent plus Le game changer c'est de transformer tes workflows en skills, puis de les mettre en boucle 🔁 >hooks : branche des automatismes à chaque étape de Claude. Exemples : - SessionStart : charger du contexte à chaque lancement - PreToolUse : logger chaque commande que Claude exécute - PermissionRequest : valider les actions de Claude depuis WhatsApp - Stop : relancer Claude automatiquement quand il s'arrête >Dispatch : contrôle l'app Desktop à distance. Pour gérer tes mails, Slack, fichiers, navigateur.. même quand t'es pas devant ton ordi. Boris l'utilise tous les jours, même quand il code pas >l'extension Chrome : Claude VOIT ton site dans le navigateur et corrige en boucle jusqu'à ce que ça soit propre. En vrai c'est logique : si tu demandes à quelqu'un de construire un site sans qu'il puisse le voir, le résultat sera moyen. Là il code, regarde, corrige, répète. Ça marche sur Chrome et Edge >Desktop app : l'app Desktop lance et teste tes serveurs web automatiquement dans un navigateur intégré. Tu codes ton site, Claude le démarre et le vérifie pour toi, sans que tu touches à rien >/btw : l'agent est en plein boulot sur un truc long et t'as une question rapide ? /btw te laisse lui parler à côté sans interrompre ce qu'il fait >claude -w (worktrees) : lance plusieurs Claude en parallèle sur le même repo, chacun dans son espace isolé. Ils se marchent pas dessus. Boris en a des dizaines qui tournent en même temps. Sur le Desktop app, c'est juste une checkbox "worktree" à cocher J'utilisais pas encore ça, ça va changer 🤯 >/batch : Ça c'est quand t'as un ENORME chantier devant toi. Migration de 200 fichiers, refacto massif ? /batch va te poser des questions puis envoie des dizaines, des centaines, voire des milliers d'agents bosser en parallèle. Tu dors, et eux font le taff >--bare : accélère le lancement jusqu'à 10x. Par défaut Claude charge tes configs, CLAUDE.md, MCPs.. --bare skip tout ça. Utile quand tu fais des appels rapides. >--add-dir : ton projet dépend d'un autre dossier ? Donne accès aux deux en même temps. Il dit qu'on peut aussi mettre "additionalDirectories" dans le "settings. json" pour que ce soit automatique à chaque lancement >--agent : fabrique tes propres agents dans .claude/agents/. Chaque agent a ses propres instructions et outils. Un pour le front, un pour les tests, un pour la doc.. Tu lances avec claude --agent=mon-agent >/voice : parle au lieu de taper. Maintiens la barre espace dans le terminal, ou le bouton micro sur Desktop. Boris fait la MAJORITÉ de son dev comme ça En vrai je taffe beaucoup au bureau donc pas évident, mais je vais tester quand je serai dehors. ____ Voilà, vous avez TOUT, Je vais envoyer a Claude Code tout ce qui me parle et que j'utilisais pas encore. Hâte de voir ce que ça peut changer dans mon quotidien.

3/ Two of the most powerful features in Claude Code: /loop and /schedule Use these to schedule Claude to run automatically at a set interval, for up to a week at a time. I have a bunch of loops running locally: - /loop 5m /babysit, to auto-address code review, auto-rebase, and shepherd my PRs to production - /loop 30m /slack-feedback, to automatically put up PRs for Slack feedback every 30 mins - /loop /post-merge-sweeper to put up PRs to address code review comments I missed - /loop 1h /pr-pruner to close out stale and no longer necessary PRs - lots more!.. Experiment with turning workflows into skills + loops. It's powerful. code.claude.com/docs/en/schedu…

2/ Move sessions back and forth between mobile/web/desktop and terminal Run "claude --teleport" or /teleport to continue a cloud session on your machine. Or run /remote-control to control a locally running session from your phone/web. Personally, I have "Enable Remote Control for all sessions" set in my /config. code.claude.com/docs/en/remote…

Profile Settings Screen Got Redesign ✨ Before → After 👏@Abmankendrick

Bon bah nouvelle créa

How to grow your app from 0 to 100k users (PLAYBOOK): by the end, you'll know how to: - get your first 10 paying customers without a funnel - build organic growth that compounds monthly - know exactly when to spend money and when not to - turn your users into your best acquisition channel here's the full 7-stage roadmap: Stage 1 (0-10): find your niche and sell one person at a time the biggest mistake is building for "everyone" you don't need a market. you need 10 people who feel the pain so badly they'd pay you today how to find them: > pick one specific audience (who can potentially buy the solution) > go where they already complain: X, Reddit, Slack communities, Discord servers > read their exact words. the language they use to describe the pain = your marketing copy > DM 50 people. not pitching. just asking "what's the most frustrating part of [problem]?" your first 10 customers should feel like you read their mind with my own product, I went to a conference and just talked about the problem I was solving 5 people wanted to buy before I had anything to sell, 50 are ready to test (at 2x price from basic costs) metric to watch: conversion from conversation to "shut up and take my money" mistake to avoid: building features before talking to humans -------- Stage 2 (10-100): do things that don't scale forget funnels. forget ads. forget automation this stage is manual and it's supposed to be how to get to 100: > send 20-30 personalized DMs daily on X, Reddit, LinkedIn (not cold outreach!) > post daily in communities where your audience already lives > jump in free onboarding calls, watch how people use your product > when someone leaves, always ask why (it happens often lol) what this gives you: 1: real feedback that shapes your product into something people actually need 2: language and objections you'll use in marketing for the next 2 years 3: early advocates who tell their friends the first 100 users will teach you more than any analytics dashboard ever will don't scale until you've fixed everything these 100 people found broken metric to watch: how many users come back after week 1 mistake to avoid: automating too early and losing the human feedback loop -------- Stage 3 (100-500): fix retention before chasing growth this is where most apps die silently they keep acquiring users while losing them out the back door before you spend a single minute on growth, answer these: 1: what % of users are still active after 7 days? 30 days? 2: where exactly do people drop off in onboarding? 3: what does your "WOW moment" look like and how fast do users reach it? how to fix retention: > cut time to value. 10 steps to feel the product? make it 3 > one email sequence that gets users to their first win in 24hrs > remove features that confuse more than they help > talk to churned users. after 10 calls the pattern is obvious your target: get churn below 5% monthly before moving to stage 4 because growing with 15% churn is like filling a bucket with a hole in it metric to watch: monthly churn rate and day-1 retention mistake to avoid: adding features instead of fixing the experience -------- Stage 4 (500-1k): build your organic engine and referral system now you've got the right to scale two engines to build simultaneously: content engine: - pick 2 platforms max (X + LinkedIn, or YouTube + TikTok depending on your audience) - post 5x/week minimum. document your building process, share insights, show results - every post should teach one thing or prove one result - repurpose: one idea = 1 long post + 3 short posts + 1 thread across platforms referral engine: - trigger "invite a friend" right when users feel the most value - reward both sides: extended trial, premium feature, or credit - make sharing one click with a pre-written message - track top referrers and treat them like VIPs this is where growth starts compounding. content brings strangers. referrals bring warm leads. both are free metric to watch: viral coefficient (how many new users each existing user brings) mistake to avoid: spreading across 5 platforms and doing all of them poorly -------- Stage 5 (1k-10k): partnerships, affiliates, and first paid experiments organic alone hits a ceiling. now you layer partnerships: > find products with the same audience but no competition > propose co-marketing: joint webinars, shared newsletters, bundles > one right partnership can bring 500+ users overnight affiliates and BDs: > launch an affiliate program with 20-30% recurring commission > recruit creators who already talk to your audience > find 2-3 BDs to sell your product on commission base first paid channels: > only test ads when you know your CAC and LTV cold > start with retargeting (cheapest and highest intent) > test one cold channel: Meta for B2C, LinkedIn/Google for B2B > $500-1k/mo to test. scale only what's profitable in 30 days metric to watch: CAC to LTV ratio (aim for 1:3 minimum) mistake to avoid: spending on ads before your funnel converts organically -------- Stage 6 (10k-50k): scale what works, kill what doesn't at this stage you already know your channels. now it's about efficiency what to do: 1: double down on your top 2 channels. kill the rest 2: make your first growth hire 3: automate onboarding, emails, and referral tracking 4: build a community around the product: Discord, Slack, or Circle the community is your moat: > users help each other (reduces support costs) > feature requests come directly from power users > community members have 2-3x higher retention than non-members > it creates switching costs that competitors can't copy metric to watch: revenue per employee and growth rate month over month mistake to avoid: hiring too fast and burning cash before the model is proven -------- Stage 7 (50k-100k): brand, moat, and paid scale you're no longer just an app. you're a brand how to think about this stage: > brand is why someone picks you over 10 alternatives without comparing features > invest in design, storytelling, positioning, make the product feel inevitable > go bigger: conferences, podcasts, media, Product Hunt at scale paid acquisition at scale: - increase ad budget on proven channels - test new channels (influencer marketing, sponsorships, programmatic) - build lookalike audiences from your best customers - keep CAC under control as you scale, it will try to climb protect the moat: 1: deepen community engagement 2: build integrations and partnerships that make leaving painful 3: create content flywheel that compounds (SEO, YouTube library, newsletter archive) metric to watch: brand search volume and organic vs paid ratio mistake to avoid: letting paid acquisition become your only growth channel -------- CONCLUSION most apps die between 100 and 1,000 users because founders skip retention and jump straight to ads the truth is: the first 3 stages are ugly, manual, and slow but they build the foundation that makes stages 4-7 feel like gravity start narrow. fix retention. then scale Growth is a system, make it effective ♥️ P.S. since this day, I will start showing what I build in public to show you how I grow revenue in my apps make the products and do an immediate ship for less than 1 week and how you can repeat this system.

I’m mad I didn’t think of this first 😭 this is so fun and creative

Today we're introducing TRIBE v2 (Trimodal Brain Encoder), a foundation model trained to predict how the human brain responds to almost any sight or sound. Building on our Algonauts 2025 award-winning architecture, TRIBE v2 draws on 500+ hours of fMRI recordings from 700+ people to create a digital twin of neural activity and enable zero-shot predictions for new subjects, languages, and tasks. Try the demo and learn more here: go.meta.me/tribe2

Un SaaS bootstrappé s’est fait vider sa base de données mardi matin. Cause : un token JWT sans expiration volé 3 semaines avant. Ton SaaS est peut être déjà dans le même cas. Tu le sauras quand tes users te le diront. 5 failles que 90% des SaaS bootstrappés ont en ce moment : 1.Pas de rate limiting sur tes endpoints. Un bot teste 10 000 mots de passe et ton serveur il est en détente. 2.Des clés API dans ton repo GitHub. 3.Panel admin sans 2FA. Un mot de passe leak ailleurs = accès total à ton infra. 4.Tokens JWT sans expiration. Suffit de le voler une fois et il est valide pour toujours. 5.Zéro système d’alerte. Tu découvres la brèche après tes users. Et non dire à Claude ou Lovable “fix ça et fais pas d’erreur” change rien. La bonne nouvelle c’est que chaque point se règle en moins d’une journée. Si tu sais quoi chercher ou par qui passer.

5 minutes to build, looks way more expensive. @AdityaSur11

run more native ads 💰

omg you have to scroll this site 😮 oryzo.ai

Scroll-based 3d landing page. and anyone can achieve the same results. Here's the prompt

Seedance 2.0 nails any animation style 🔥 Perfect consistency. Frame by frame. Tutorial below👇

iOS 26 vibe, liquid glass effect.

Claude watching me write code manually after I hit the daily limit

🔥Viral Website Idea: A website to give ideas on "what to Build n Ship" this weekend (based on niche, trend, etc.)

Some sites I use for picking colors or gradients for a new design. 1. coolors.co 2. grabient.com 3. colorhub.app 4. colorhunt.co 5. gradients.colorion.co 6. colorkit.co 7. kigen.design/color

@charaf_ecomwize @EcomWize Drop

Biggest drop ever! I'm giving away 16 landing page templates you can plug into your Shopify store INSTANTLY - just add your content, or let @ecomwize generate it for you in 15 minutes The pack includes: 3x landing pages 1x long-form landing page 4x product pages 4x listicles 4x advertorials Like + comment "Drop" and I'll send it to you (must be following to receive the DM)

Introducing Rork Max Publishing Rork Max can now fill your entire App Store page without you ever touching it. It fills in all the fields, generates beautiful icons & screenshots, makes a mock review so you don't get rejected, and submits for you. Yes, iPad screenshots too.