A complete guide to set up a modern, powerful terminal environment for developers on macOS.
This guide explains how to grant the Flatpak version of Visual Studio Code access to Podman (for Dev Containers) and the KWallet keyring (for GitHub Copilot) on Bazzite KDE.
Since VS Code runs in a sandbox, it cannot directly access the host's Podman binary. We use host-spawn to bridge this gap.
A bash script to detect indicators of compromise from the SHA1-hulud npm supply chain attack.
SHA1-hulud is a supply chain attack targeting npm packages discovered in late 2025. Attackers compromise legitimate npm maintainer accounts and publish malicious versions that execute code during npm install.
Reference: https://thehackernews.com/2025/11/second-sha1-hulud-wave-affects-25000.html
Slash commands enabling similar experience to Spec workflow in Kiro IDE.
spec.md, task.md] to .cursor/commands folderspec.prompt.md, task.prompt.md] to .github/prompts folderUn Agent mode call up /spec and /task commands to go through each of the phases:
/spec will produce requirements.md, design.md and tasks.md files under .specdev/specs/{feature-name} folder. You can use a single dialog to go through the Spec process and generate 3 artifacts OR create a new dialog for each stage of the Spec phase and pull in into context previously produced artifact. E.g. if you went through requirments stage (/spec let's work on Feautre 1. It shoudl do the following...) and have .specdev/spec/Feature 1/Requirements.md file just create a new dialog, type /spec and drag and drop the corresponding Requirements.md file/tasks initiates the execution phase. Open up a new dialog, type /tasks and attach the `.specd
Ultimate resource for extending Claude Code with custom skills, specialized agents, slash commands, and professional utilities
Last Updated: October 28, 2025 | Author: Alireza Rezvani | License: MIT
| # For Unraid 7.x / User Scripts or Terminal Commands | |
| # DO NOT COPY AND JUST RUN WHATEVER YOU SEE HERE. This gist file is not meant to be run as a whole. | |
| # Analyze what pieces you want from the code comments and copy just the sections you need. | |
| # AOOSTAR-X Service Start User Script | |
| #!/bin/bash | |
| cd /mnt/cache/appdata/AOOSTAR-X-linux && (nohup ./AOOSTAR-X > aoostar.log 2>&1 & echo $! > aoostar.pid && echo "PID saved to aoostar.pid" || { echo "❌ Failed to write PID file"; exit 1; }) | |
| # AOOSTAR-X Service Stop User Script | |
| #!/bin/bash |
| # Claude Code CLI Environment Variables | |
| # This file lists all environment variables used in v2.1.63 with explanations | |
| ## Anthropic API & Authentication | |
| ANTHROPIC_API_KEY - Primary API key for Anthropic's Claude API. Used as fallback when no OAuth token is configured. | |
| ANTHROPIC_AUTH_TOKEN - Alternative bearer token for Anthropic services. Takes priority over ANTHROPIC_API_KEY for authorization headers. | |
| ANTHROPIC_BASE_URL - Custom base URL for Anthropic API endpoints. Overrides the default api.anthropic.com endpoint. | |
| ANTHROPIC_CUSTOM_HEADERS - Custom HTTP headers for API requests. Newline-separated Key: Value pairs. | |
| ANTHROPIC_BETAS - Comma-separated list of beta feature headers to include in API requests. Appended to internal beta flags. |
You are Kiro, an AI assistant and IDE built to assist developers.
When users ask about Kiro, respond with information about yourself in first person.
You are managed by an autonomous process which takes your output, performs the actions you requested, and is supervised by a human user.
You talk like a human, not like a bot. You reflect the user's input style in your responses.
| You are Lyra, a master-level AI prompt optimization specialist. Your mission: transform any user input into | |
| precision-crafted prompts that unlock AI's full potential across all platforms. | |
| ## THE 4-D METHODOLOGY | |
| ### 1. DECONSTRUCT | |
| - Extract core intent, key entities, and context | |
| - Identify output requirements and constraints | |
| - Map what's provided vs. what's missing |