Create various settings file I have one file for each provider, all in ~/.claude
- KIMI K2.5: kimi_settings.json
{
"env": {
"ANTHROPIC_BASE_URL": "https://api.moonshot.ai/anthropic",
| You are the council, a group representing everyone who interacts with or influences the system being developed. | |
| You speak for those who use, build, and maintain the product, platform, or environment. | |
| Your purpose is to help [insert name, role, and purpose of the main creator, stakeholder, or audience here]. | |
| Explain what they want to achieve and why the council’s perspective matters. | |
| Speak with honesty and practicality to reflect what is most important to users, creators, and stakeholders. | |
| ## Who You Are Talking To | |
| [Insert description of the primary recipient or audience the council addresses.] | |
| [Explain their mindset, goals, and working style so replies can fit their needs and context.] |
| import ARKit | |
| import CoreHaptics | |
| import GameController | |
| import RealityKit | |
| import SwiftUI | |
| struct ImmersiveLaserPenMeasurementView: View { | |
| @State private var stylusManager = StylusLaserPenManager() | |
| var body: some View { |
| #!/bin/bash | |
| # Script to update a firewall rule in a Hetzner Firewall with your current IP address. | |
| # Good if you would like to restrict SSH access only for your current IP address (secure). | |
| ################# | |
| # WARNING: This script will overwrite all rules in the firewall rules, so make sure you | |
| # added all the required rules. | |
| # I use a separate firewall rule just for SSH access. | |
| ################# |
| import { PropsWithChildren, useEffect, useState } from "react"; | |
| import { Container } from "~/components/container"; | |
| import { ArrowLeft, ArrowRight } from "lucide-react"; | |
| import { range } from "~/utils/range"; | |
| const IMAGES = [ | |
| { | |
| id: 1, | |
| url: "https://images.pexels.com/photos/1366919/pexels-photo-1366919.jpeg", | |
| }, |
| // app > api > webhook > stripe > js route.js --> | |
| import { NextResponse } from 'next/server'; | |
| import { headers } from 'next/headers'; | |
| import Stripe from 'stripe'; | |
| import connectMongo from '@/libs/mongoose'; | |
| import User from '@models/User'; | |
| const stripe = new Stripe(process.env.STRIPE_SECRET_KEY); | |
| const webhookSecret = process.env.STRIPE_WEBHOOK_SECRET; |
| // ==UserScript== | |
| // @name Hide Links From Mainstream Media | |
| // @namespace http://tampermonkey.net/ | |
| // @version 0.1 | |
| // @description Hides all links from mainstream media websites on news.ycombinator | |
| // @match https://news.ycombinator.com/* | |
| // @grant none | |
| // ==/UserScript== | |
| (function() { |
| // ==UserScript== | |
| // @name Youtube SkipAd | |
| // @namespace keesiemeijer | |
| // @version 0.1 | |
| // @description Automatically skips ads after 5 seconds | |
| // @author keesiemeijer | |
| // @match https://www.youtube.com/* | |
| // @grant none | |
| // ==/UserScript== |
I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.