name: tufte-viz description: | Ideate and critique data visualizations using Edward Tufte's principles from "The Visual Display of Quantitative Information." Use this skill when: (1) Designing new data visualizations or charts (2) Critiquing or improving existing visualizations (3) Reviewing dashboards or reports for graphical integrity (4) Deciding between visualization approaches (5) Reducing chartjunk or improving data-ink ratio (6) Planning small multiples or high-density displays
| #!/usr/bin/env python3 | |
| """ | |
| Claude Code token usage analyzer. | |
| Analyzes ~/.claude/projects/ JSONL files for token usage patterns. | |
| """ | |
| import json | |
| import os | |
| import sys | |
| from pathlib import Path |
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| # Repo Audit — Planned Scope + Readiness | |
| Use this when there is a credible plan: PRD, spec, beads, contracts, backlog, design docs, or another trustworthy artifact that defines intended scope. | |
| ## Objective | |
| Perform a ground-truth audit that answers **two separate questions**: | |
| 1. **What functionality exists and is proven end to end?** | |
| 2. **Compared with the explicit plan, what is missing, partial, conflicted, dead, or risky?** |
| #!/usr/bin/env pwsh | |
| #Requires -Version 5.1 | |
| #Requires -RunAsAdministrator | |
| <# | |
| .SYNOPSIS | |
| AIO WSL Arch Linux Setup Script - Revised & Hardened Version | |
| .DESCRIPTION | |
| Configura automaticamente uma distro Arch Linux no WSL com ambiente de desenvolvimento completo. |
This guide defines when to declare an incident, who is responsible for communication, and how to communicate externally during an incident.
It also defines how to act technically during an incident, emphasizing mitigation over fixes to reduce risk and downtime.
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.
Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.
Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1
- Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
- Select "Create new custom chat mode file"
| description | 4.1 Beast Mode | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| tools |
|
Beast Mode v3 is out now: 👉 https://gist.github.com/burkeholland/88af0249c4b6aff3820bf37898c8bacf
You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.
