This guide outlines a best-practice, modern local machine setup for frontend development on a MacBook M4. It focuses on maximizing productivity, performance, and developer experience.
Homebrew is the essential package manager for macOS. It simplifies the installation of almost all the tools we will use.
Terminal app and run the following command. This will also install the Xcode Command Line Tools (including Git).| { | |
| "customModes": [ | |
| { | |
| "name": "🧑✈️ Commander", | |
| "slug": "commander", | |
| "roleDefinition": "You are the Commander of the Content Army. You act as the central coordinator for content creation pipelines. Your responsibilities include interacting with the user (for initial requests and mid-pipeline reviews/selections), dynamically planning the workflow based on the briefing output and project context (like style guides and project language), delegating tasks to specialist modes, and managing the state for each content piece by creating and updating task definition files.", | |
| "customInstructions": "As the Commander:\n\n**Core Directives:**\n\n- **Interact with the user in the language they are currently using.** Adapt your responses accordingly.\n- **Internal logic, task definitions, and status reporting should remain in English** for system consistency.\n- **You MUST meticulously track your own token usage and cost.** Before initiating any action that involves significant processing or int |
| { | |
| "customModes": [ | |
| { | |
| "slug": "sparc", | |
| "name": "⚡️ SPARC Orchestrator", | |
| "roleDefinition": "You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology. You ensure secure, modular, testable, and maintainable delivery using the appropriate specialist modes.", | |
| "customInstructions": "Follow SPARC:\n\n1. Specification: Clarify objectives and scope. Never allow hard-coded env vars.\n2. Pseudocode: Request high-level logic with TDD anchors.\n3. Architecture: Ensure extensible system diagrams and service boundaries.\n4. Refinement: Use TDD, debugging, security, and optimization flows.\n5. Completion: Integrate, document, and monitor for continuous improvement.\n\nUse `new_task` to assign:\n- spec-pseudocode\n- architect\n- code\n- tdd\n- debug\n- security-review\n- docs-writer\n- integration\n- post-deployment-monitoring-mode\n- refinement-optimization-mode\n\nValidate:\n✅ Files < 500 lines\n✅ No hard-coded |
Some notes, tools, and techniques for reverse engineering macOS binaries.
My random collection of notes on AI voice cloning services/models/techniques/etc. Just because something is listed here, doesn't necessarily mean I have tried it, nor endorse it. Use this as a starting point for doing your own further research.
| import praw | |
| import json | |
| import tweepy | |
| import time | |
| import os | |
| import csv | |
| import configparser | |
| import urllib.parse | |
| import sys | |
| from imgurpython import ImgurClient |
To start using the Jellyfin API, authorization is probably the first thing you'll need to do. Jellyfin's authorization options can be a bit confusing because there are a lot of deprecated options.
Generally there are three ways to authenticate: no authorization, user authorization with an access token or authorization with an API key. The first way is easy, just do nothing. But most often you'll need to use either the access token or API key.
There are multiple methods for transmitting authorization values, however, some are outdated and scheduled to be removed.
It's recommend to use the Authorization header. If header auth isn't an option, the token may be sent through the ApiKey query parameter. Sending secure data in a query parameter is unsafe as the changes of it leaking (via logs, copy-paste actions or by other means) are high. Only use this method as a last resort.
| #!/usr/bin/env bash | |
| # Builds mpv & mpv.app on Apple silicon Macs. | |
| # Run this script from the root directory of the mpv repo. | |
| # if anything fails, gtfo | |
| set -ex | |
| meson setup build | |
| meson compile -C build |
Current static binaries do not target https://bitbucket.org/multicoreware/x265_git/issues/563/patch-neon-arm64-improvements which can be identified
Before
x265 [info]: using cpu capabilities: none!
[libx264 @ 0xaaab0a5fc000] using cpu capabilities: ARMv8 NEON