This guide will help you set up Claude Code for your development environment.
- Node.js 18 or higher
- npm 8 or higher
- AWS credentials with access to Bedrock
--- | |
description: "Use shadcn/ui components as needed for any UI code" | |
patterns: "*.tsx" | |
--- | |
# Shadcn UI Components | |
This project uses @shadcn/ui for UI components. These are beautifully designed, accessible components that you can copy and paste into your apps. | |
## Finding and Using Components |
import { serve } from "https://deno.land/[email protected]/http/server.ts"; | |
import { crypto } from "https://deno.land/[email protected]/crypto/mod.ts"; | |
import { | |
ImageMagick, | |
initialize, | |
MagickFormat, | |
} from "https://deno.land/x/[email protected]/mod.ts"; | |
import { Tinify } from "https://deno.land/x/[email protected]/mod.ts"; | |
import { createClient } from "https://esm.sh/@supabase/[email protected]"; |
These snippets provide a foundation for starting and stopping supervision trees at runtime using feature flags (e.g. Launch Darkly).
Some things to note when adapting these snippets:
ld_key
) specified.FeatureFlags
module to be available that implements is_on?/2
. Adjust as needed to accomodate your own feature flag setup.#!/usr/bin/env sh | |
:: default : yabai -m config active_window_opacity 1; yabai -m config normal_window_opacity 1; | |
# Focus | |
shift + alt - home : yabai -m window --focus north | |
shift + alt - j : yabai -m window --focus north | |
shift + alt - end : yabai -m window --focus south | |
shift + alt - k : yabai -m window --focus south | |
shift + alt - delete : yabai -m window --focus west |
Macro hygiene is the concept of macros that work in all contexts; they don't affect and aren't affected by anything around them. Ideally all macros would be fully hygienic, but there are lots of pitfalls and traps that make it all too easy to accidentally write unhygienic macros. This guide attempts to provide a comprehensive resource for writing the most hygienic macros.
First, a little aside on the details of Rust's module system, and specifically paths; it is
# Take Hasura migrations from staging and apply them to prod | |
# Usage: ./migrate.sh "<staging-endpoint>" "<staging-secret>" "<prod-endpoint>" "<prod-secret>" "<migration-name>" | |
STAGING_ENDPOINT="$1" | |
STAGING_SECRET="$2" | |
PROD_ENDPOINT="$3" | |
PROD_SECRET="$4" | |
MIGRATION_NAME="$5" |