Learn Peak by making something

Open Basecamp and choose Crew. Make a bot from a persona or write one in a sentence: "You make the music for our videos and keep the playlists." Give it a model, turn on the skills it needs, pick its look and voice, and ask it something by name.

In Basecamp’s Everyone thread, write "@all What is everyone doing for launch day?" Then follow up with "@Research check the date against the holidays" and see the answer come back to the table.

Press the mountain on the start page, go to the Lodge and say what you want. Interrupt it mid-answer to steer. Then in Routine → Wake-ups, have a bot wake daily at eight to check something and tell you what it found.

Open Peak with ^1. In the landing input, type a question and leave the mode on Search. Now switch the mode to Note and type the same words — you get a block note titled with them instead of a results page. Then paste a URL into Search and watch it open the site instead of searching for it.

Right-click a tab you are not on → Show Beside → Left or Right. Put a long video on one side and your notes on the other side, then quit Peak and reopen it — the split returns on the same sides. Click the other pane’s tab to move the address bar and toolbar across.

Make one profile per context. Save the tabs from a research session as a session, close them all, and reopen the session next week. Then open an incognito tab and confirm it never appears in your history.

In Safari, select a paragraph, right-click and choose Ask Peak AI. Then send a page to Peak from the share sheet, and add the Agenda widget.

Capture this page. Then: "Turn it into a block note: three headings, the key claims as bullets under each, a table of the numbers with a source column, a to-do block per next action, and a divider before the sources. Link the original page at the top."

Read three sources on one question, then: "Make a task board called <topic>. Lanes: To read, In progress, Shipped. One card per source with the claim it makes, and a separate card for each thing I should do next. Put anything I cannot verify yet in To read."

Create a project called <name>. Instructions: "Write for a technical reader, British spelling, never invent a source, and keep prose under three sentences per paragraph." Add the two PDFs I am working from as reference files. Then ask a question without re-explaining any of it.

Open Finance and choose Try with a sample year. Then open Budget and let it suggest amounts from the last three months, open Recurring to see the subscriptions it found, and look at Reports for where the money went.

Open a whiteboard. Put the central idea in the middle as a card, then four consequences around it. Wire each one to the centre with its own line, then drag the outer cards about and watch the connectors follow instead of breaking.

Add the country map of <country> to the board. Then a sticky note for each city in this list, sitting on the city, and an arrow from each note to a card that says what happens there. Use one Lucide icon per kind of event so the board reads without a key.

Open my <deck> on a whiteboard, laid out page by page with the edges drawn. Then pull out the slides that cover <theme> into a separate row and put a heading card above them. Show me any two slides that are saying the same thing.

Build me a site about <subject>. Dark ground, one accent colour, generous spacing, a hero with a real headline, three sections and a footer. Use no external fonts or CDNs — everything must work offline. Make it multi-page: /, /about and /work, sharing one layout.

Build a PeakUI app with three tabs: Home, Library, Settings. Name every view for its screen. Use .formStyle(.grouped) on the Settings form. Use TabView for the sections and NavigationLink for pushes. Screenshot it at desktop and phone size, drive to every screen, then export it as an Xcode project.

Trace this logo into vector artwork, then animate the trace being drawn on: opacity 0 to 1 while trim goes 0 to 1 over 1.4 seconds, easeOut. Then export it as a GIF that ping-pongs so the loop has no visible restart. Separately, build me a flying game over a ridge with twenty collectables along a trail and a timer.

Make me a 12-slide deck on <subject> for <audience>. 16:9. One idea per slide, at most five bullets, a title plus one supporting line. Include one infographic for the process and one chart. Then render it, check the geometry, and look at the tiled picture of every slide before you describe it to me.

Make App Store screenshots for <app>: six slides at iPhone portrait size, each with a short headline above a framed device shot, and one palette and one type hierarchy across all six. Then the same six at iPad size and again at Mac size. Export each set as PNG.

Turn on the Slide Design skill. Before you describe the deck to me, render it, read the geometry report, then look at the tiled picture of every slide and fix what fails: an unpainted ground, a palette that drifts, a title that is not in the same place twice, or a shape holding nothing. Then tell me what you changed.

Start from the announcement structure. Add my clips to the bottom row, trim the first two, put a title card over the opening shot on a row above, and a music bed under both rows. Fade the title in, fade the ending out, and export the film.

Look at the edit as a grid of frames. Take the last frame of the cut, generate a clip that starts from exactly there, add it to the bottom row after the first, then join the clips into a single file. Repeat until the move is as long as I want.

Switch to the mixer. Voice on row 1 at full, music on row 2 around 0.3 and ducked below the voice. Set the project tempo so the ruler counts bars instead of seconds, and snap the music clips to the grid. Bounce the sound on its own to .m4a.

Write the narration as it should be heard — numbers and abbreviations spelled out. Generate it. Generate a short instrumental bed that sits under a voice. Cut the dead air out of my raw talking recording first, then merge narration and score onto the film with a two-second fade out.

Record fifteen seconds of me reading the passage on screen, say it is my own voice, and call it “Me”. Then speak “Welcome to the show” in it, and convert this recording into the same voice.

Make an audiobook from these three notes, one chapter each, read by the ready-made voice Charles, with a two-second pause after each title. Then make a story from my script in which Maya and Tom each get their own voice.

Dub this interview into Spanish: find the two speakers, translate every line on the device, give each a different voice, and tell me how far the dub drifts from the picture.

Split this song into stems and keep the backing track in my Library.

Research <question>. For every claim, give me the page it came from and mark whether you read it in full or only saw it as a search result. If a sentence cannot be tied back to a page you actually fetched, drop it and tell me you dropped it.

Build a search index over my bookmarks and notes, using an on-device embedding model so nothing leaves the machine. Then find what I saved about state machines, describing it rather than naming it.

Open this article in reader mode. Turn it into clean Markdown and save it. Then transcribe my voice memo about it, strip the silence out of the recording, and put the transcript in the same note under the article with the link at the top.

Take this logo. Remove its background. Give me the actual palette as hex — measure it from the image, do not guess. Trace it into an SVG path I can animate. Then extrude it with a depth of 12 and a bevel of 1, and tell me which letters come out solid.

Choose Deadnet from the search engine list and search for something. Follow a link, then follow one from that page. Compare the Invented mode against Grounded, which looks up what is true first and invents the sources around it.

Track my app and its two closest competitors. For the search “budget planner”, tell me how popular and how contested it is, and show which stores sell each of them.

Crawl my site up to 250 pages, show me the errors first, and write titles and descriptions that fit for the pages that are missing them.

Learn my brand from peakbrowser.app, then draft four posts for LinkedIn and Instagram about the new release, each with a picture, and plan them across the next two weeks.

Open Settings → API. Add one key — OpenRouter is the broadest, and it is the only route to image, video, music and speech. Press Test beside it: Peak asks the provider for its model list, which is a real request, because a revoked key looks exactly like a valid one until something is sent.

Settings → MLX. Turn the engine on and download a model Peak suggests for your device. Pick it in any chat and ask it about the page you are on — nothing leaves the machine.

On the Mac holding the weights, switch on Let Peers Use My Models under Settings › MLX. On the phone, open the model menu and look under Nearby Mac — the machine’s models are listed, named after the machine they live on. Pick one and ask.

On a Mac or iPhone running the latest system with Apple Intelligence switched on, open the model menu. Apple’s model is already there. Ask it a question — then ask it to search the web, and watch it decline rather than pretend.

Turn the engine on. From the Mac menu bar, copy the address and the token. Point any OpenAI-compatible client at http://127.0.0.1:52424/v1 with that token as its bearer.

Open Settings → Tools and read a skill’s full instruction text before enabling it. Turn on Minimal for a small model, or Deep Research for a question worth several sources. Then set a different skill beside the persona in one conversation’s own settings.

Leave Require approval before actions on. Ask for something that writes files, and watch the requested changes queue in the AI inspector until you accept them.

Set the model for each kind under Session Settings → Generation Models — those are shared across every chat, unlike the conversation model. Ask for an image, then attach a source image and ask for an edit rather than a new picture.

Show why the sum of the first n odd numbers is n squared, with the steps typeset. Then draw how a pull request gets reviewed as a flowchart, chart these four numbers as a bar chart — 12, 19, 7, 24 — and plot y = sin(x) and y = x/3.

Write Python that works out the monthly payment on a 25-year loan of 3,200,000 at 5.2% and plots the remaining balance over time. Let me read it before it runs.

(In Claude Code, once connected) What is on my calendar this week, and which of my notes mention the launch? Then make a task board for the launch from those notes.

Make a flying game over a ridge. Heightfield terrain with fog that leaves the far ridges just visible, and ninety conifers in the valleys as scenery. Put a trail of twenty collectables along the route — reachable in about three minutes — plus a minimap, a timer and a speed readout. Crashing into the ground above 18 m/s ends the run.

Open the Arcade Hub. Play one round of a short local game, then set up a focus space for the next block of work. Keep it in the same window as the work — the point is not switching apps.

Set a room passphrase. Share tabs, notes and a whiteboard with the other device, and turn everything else off. Then on the phone, borrow the model from the Mac in the room and ask it two questions.