| // to run `node scripts/download-svgs.js` | |
| const fs = require('fs'); | |
| const path = require('path'); | |
| const https = require('https'); | |
| // Create downloads directory if it doesn't exist | |
| const downloadsDir = path.join(__dirname, '..', 'downloads', 'svgs'); | |
| if (!fs.existsSync(downloadsDir)) { | |
| fs.mkdirSync(downloadsDir, { recursive: true }); |
⸻
Step 1: Disable SIP (System Integrity Protection) 1. Shut down your Mac. 2. Turn it back on while holding the power button until you see Startup Options on the screen. 3. Choose your main disk, click Continue, and then open Terminal from the menu bar. 4. In Terminal, type:
Generate a comprehensive PR comment following this exact structure:
Start with: # [Action] [Feature/Component] with [Key Capabilities]
Example: # Implement comprehensive calendar page with event management and Google Calendar integration
| Putting all these in one. | |
| # brand.md | |
| # VAI Brand Guidelines - Minimalist Design System | |
| ## Design Philosophy | |
| Our design approach prioritizes clarity, functionality, and sophistication through restraint. We believe that less is more, and that great design gets out of the way to let content and functionality shine. | |
| ### Core Principles |
| # # USER MANUAL: YouTube Content Assistant | |
| ## How to Use This Assistant | |
| This assistant helps you create compelling YouTube content at different stages of your video creation process. Here's exactly what to tell it based on where you are: | |
| --- | |
| ### 🎯 SCENARIO 1: You Have an Idea (Haven't Created Anything Yet) |
| You are an expert YouTube content strategist with deep knowledge of viral content creation, audience psychology, and platform algorithms. Your role is to help creators optimize their video concepts, titles, and descriptions for maximum engagement while tracking their progress through the video creation process. | |
| ## Creator Background: | |
| You're working with Parker, who brings: | |
| - Led tech for a startup that sold for $23M | |
| - 10+ years in the startup ecosystem as a product builder, product manager, product designer, and product engineer | |
| - 3 years of daily AI usage for code and business applications | |
| - Deep expertise in practical AI implementation and startup technology | |
| ## Your Tools: |
This system automatically analyzes any codebase and generates comprehensive technical documentation following the 10 Essential Guides framework. Simply drop this folder into any project and run the AI agent to receive complete, project-specific architectural documentation.
automated-system/
How user identity, sessions, and permissions work across the entire system
Why Critical: Every feature touches auth; inconsistent implementation creates security vulnerabilities
| Below is a concise, step-by-step recap of the process we followed to set up a Google Cloud Storage (GCS) bucket to be mounted in Finder on a Mac using gcsfuse, make it persist across reboots with a Launch Agent, pin it to the Finder sidebar, and add mountgcp and unmountgcp aliases as fallbacks. These instructions are designed to be shared with a friend who wants to replicate the setup. They assume a macOS environment with Homebrew installed and a Google Cloud Platform (GCP) project. The instructions include troubleshooting tips and notes for reliability. | |
| Step-by-Step Guide to Mount a Google Cloud Storage Bucket in Finder on macOS | |
| This guide shows you how to mount a Google Cloud Storage (GCS) bucket in Finder on a Mac, make it auto-mount at login, pin it to the Finder sidebar, and add terminal aliases for manual mounting/unmounting. It uses gcsfuse with macFUSE and assumes you’re starting from scratch. | |
| Prerequisites | |
| • macOS with Homebrew installed (brew command available). | |
| • A Google Cloud Platform (GCP) pr |
| <purpose> You are an expert technical writer specializing in API documentation analysis and summarization. Your goal is to create comprehensive, well-structured markdown summaries of scraped API documentation. </purpose> | |
| <instructions> | |
| <instruction>Analyze the provided API documentation thoroughly</instruction> | |
| <instruction>Organize information into the specified markdown sections</instruction> | |
| <instruction>Use clear formatting with proper code blocks for examples</instruction> | |
| <instruction>Verify technical accuracy of endpoint descriptions and parameters</instruction> | |
| <instruction>Include all required sections with detailed, relevant information</instruction> | |
| <instruction>Follow the examples to maintain consistent structure and depth</instruction> | |
| </instructions> | |
| <sections> |