Sunrise

SunriseAug 7, 2026

You can now load a 400-page book as one Claude skill. You read a technical book once and forget most of it within months. Highlights pile up and notes go unopened. Searching the PDF returns pages, not answers. Asking a chatbot risks hallucinated chapters and made-up quotes. Book-to-skill turns any technical book into a structured reference that loads on demand inside Claude Code. The open-source pipeline picks an extraction tool based on content type: > Docling for tables and code > pdftotext for prose-heavy text > ebooklib for EPUB files It then generates per-chapter summaries, a glossary, and a cheatsheet of named frameworks pulled from the actual source. Calling /your-book-slug replication loads only the relevant chapter into context. A 400-page volume normally costs around 200K tokens upfront. This approach grounds every answer in your copy, sidestepping training drift entirely. The author effectively sits beside you while you work. 🔗 https://lnkd.in/eniKYBZM

SunriseAug 10, 2026

Your AI demo works. That's exactly why it's about to fail. The image below shows why. First, two terms. → Vibe coding is when you let AI generate code from a rough idea, accept what looks right, and ship it. Fast, loose, demo-ready. → Vibe engineering is the same speed, but you build the foundation underneath it. The parts that hold weight when real users show up. Now look at the picture. On the left, the track looks finished because the train is on it. On the right, same train, same speed, but the supports go all the way to bedrock. Here's what most people miss. The collapse on the left isn't a coding failure. The code ran. The demo worked. The train moved. It's a foundation failure that looked like working software right up until the moment it didn't. AI made the generating easy. It did nothing for the part that holds weight. So here's how you go from one side to the other. Five pillars that turn a demo into a system. 1. Tests before trust If AI wrote it, write a test that proves it works. No test, no ship. 2. Handle the failure, not just the happy path Ask what breaks when the input is wrong, empty, or huge. Build for that. 3. Name an owner Every AI feature needs one person accountable when it breaks at 2am. No owner means no one is watching. 4. Watch it in the wild Add logging and alerts before launch, not after the first outage. You cannot fix what you cannot see. 5. Review what AI generated like you would a new hire's first week Fast, but checked. Trust the speed, verify the weight. Run those five and the train still moves. It just doesn't fall. What I call the AI Execution Gap is the distance between something that moves and something that holds. These five pillars are how you close it. Fast is easy now. Standing is the hard part. It always was. 🔖 Save this for your next build review. ♻️ Repost to put it in front of someone shipping AI right now.

SunriseAug 8, 2026

17 official Claude plugins (almost) nobody uses. 141 skills you can hire in 60 seconds (links below): ✦ The Engineer (10) Reviews your code, hunts the bug, and owns the deploy checklist so you don't → https://lnkd.in/e_gezrGH ✦ The Analyst (10) Takes a messy spreadsheet and hands back a clean dashboard → https://lnkd.in/eMbiMjQA ✦ The PM (8) Turns a vague idea into specs, a roadmap and a sprint plan → https://lnkd.in/ejQgipaj Grow your biz ✦ The Closer (9) Researches the account, preps the call, and keeps the pipeline moving → https://lnkd.in/eNWQT8Na ✦ The Marketer (8) Plans the campaign, writes it, and tells you what actually worked → https://lnkd.in/eTGkUzpz ✦ The Support Rep (5) Triages the ticket, drafts the reply, and escalates the ones that matter → https://lnkd.in/e3-5EhCf Sort your ops ✦ The Operator (9) Writes the runbook, tracks compliance, and vets the vendor → https://lnkd.in/eQC7rx68 ✦ The Money Team (8) Closes the books, reconciles the accounts, and files the report → https://lnkd.in/eH72dsY4 ✦ The Counsel (9) Reads the contract, flags the risk, and redlines the NDA → https://lnkd.in/eQ7wxMdc Hire your crew ✦ The People Team (9) Writes the offer, preps the interview, and runs onboarding → https://lnkd.in/eWYqHHF6 ✦ The Designer (7) Critiques the mockup, builds the design system, and hands it to code → https://lnkd.in/e2ffk6vK ✦ The Researcher (6) Reads the papers and runs the analysis pipeline → https://lnkd.in/eqZqB3kp Run your world ✦ The Business Owner (31) Six jobs in one: money, customers, admin and briefs → https://lnkd.in/ew_pPdWF ✦ The Finder (5) Searches every tool you own from one prompt → https://lnkd.in/eh8Au662 ✦ Your Assistant (4) Remembers everything and runs your week → https://lnkd.in/ehcQ72xB ✦ The Plugin Manager (2) Builds you a plugin that isn't on this list → https://lnkd.in/eRFAbmcg ✦ The Reader (1) Reads and signs a PDF so you never open Acrobat again → https://lnkd.in/eKVVQJZ5 Secure it ✦ The Guardian Scans your codebase, filters the false alarms, and explains every real risk → https://lnkd.in/eMxb3Ami How to install any of them: In Cowork, open claude.com/plugins. In Claude Code, run claude plugin marketplace add anthropics/knowledge-work-plugins Don't install 17 at once. Pick two or three that match your job. Repost ♻️ to help someone build their own team. P.S. Which one are you (actually) hiring first?