Date: 2026-01-08
CLI Version: 2.1.2
Total Experiments: 29
Raw experiment outputs from testing various claude -p flag combinations.
| #!/usr/bin/env bash | |
| set -euo pipefail | |
| # ─── Convex Deployment Migration ───────────────────────────────────────────── | |
| # Exports data from one Convex deployment and imports into another with | |
| # --replace-all. Handles the .env.local precedence gotcha by swapping it | |
| # temporarily, uses --prod on both export/import, and includes a full | |
| # migration checklist (env vars, deploy). | |
| # | |
| # Usage: |
| description | argument-hint | model | |
|---|---|---|---|
Interview me about the plan |
|
opus |
Read this plan file $1 and interview me in detail using the AskUserQuestionTool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious.
| // Types for the result object with discriminated union | |
| type Success<T> = { | |
| data: T; | |
| error: null; | |
| }; | |
| type Failure<E> = { | |
| data: null; | |
| error: E; | |
| }; |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>My Angular from Scratch</title> | |
| <style> | |
| .my-component { | |
| font-family: Arial, sans-serif; |
| #!/usr/bin/env bash | |
| # Abort sign off on any error | |
| set -e | |
| # Start the benchmark timer | |
| SECONDS=0 | |
| # Repository introspection | |
| OWNER=$(gh repo view --json owner --jq .owner.login) |
| import proxy from 'http2-proxy'; | |
| import type { Plugin, ProxyOptions } from 'vite'; | |
| export const pluginHttp2Proxy = (): Plugin => { | |
| let routes: Record<string, string | ProxyOptions>; | |
| return { | |
| name: 'vite-plugin-http2-proxy', | |
| config: (config) => { | |
| const { server } = config; | |
| routes = server?.proxy ?? {}; |
Made this example to show how to use Next.js router for a 100% SPA (no JS server) app.
You use Next.js router like normally, but don't define getStaticProps and such. Instead you do client-only fetching with swr, react-query, or similar methods.
You can generate HTML fallback for the page if there's something meaningful to show before you "know" the params. (Remember, HTML is static, so it can't respond to dynamic query. But it can be different per route.)
Don't like Next? Here's how to do the same in Gatsby.
| #!/bin/zsh | |
| :<<'ABOUT_THIS_SCRIPT' | |
| ----------------------------------------------------------------------- | |
| Written by:William Smith | |
| Partner Program Manager | |
| Jamf | |
| bill@talkingmoose.net | |
| https://gist.github.com/b6637160b65b751824943ede022daa17 |