frazhd2

blueprint:
  name: Frigate LLM Notification (v0.5-dev)
  author: whag
  description: "Basic requirements:<br /> - Home Assistant with an MQTT broker setup.
    <br /> - Frigate integration with MQTT setup. <br /> Link: https://github.com/blakeblackshear/frigate-hass-integration
    <br /> - LLM Vision integration with provider setup. <br /> Link: https://github.com/valentinfrlch/ha-llmvision
    <br /> - Optional Downloader integration. (Ensure the Use Downloader Input is
    Set Accordingly) <br /> Link: https://www.home-assistant.io/integrations/downloader/<br
    /><br />\nInformation:<br /> - Only suitable for one Frigate camera, use multiple
    instances of this automation for multiple cameras if required. <br /> - LLM Vision

Danm72

Claude Code Custom Agents Setup Instructions

Prompt for LLM Assistant

I need help setting up custom agents for Claude Code. Please help me install the agents from this GitHub gist: https://gist.github.com/Danm72/7cdd172f818505b221988916ebdc9371

Here's what needs to be done:

1. Create the agents directory (if it doesn't exist):

kasuken

description	tools	model
4.1 Do Epic Shit Mode v1	changes codebase editFiles fetch new openSimpleBrowser problems runCommands runTasks search searchResults terminalLastCommand testFailure	GPT-4.1

You are an autonomous agent tasked with fully resolving the user's query before yielding back control. Follow this workflow strictly and do not end your turn until everything is truly complete.

Rules:

• Iterate until fully resolved: Never hand control back until the problem is 100% solved, verified, and all steps are checked off.

burkeholland

Beast Mode

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

Installation Instructions

• Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
• Select "Create new custom chat mode file"

tuliopc23

<div class="container container--mobile">
  <div class="glass-container glass-container--rounded glass-container--large">
    <div class="glass-filter"></div>
    <div class="glass-overlay"></div>
    <div class="glass-specular"></div>
    <div class="glass-content">
      <div class="player">
        <div class="player__thumb">
          <img class="player__img" src="https://images.unsplash.com/photo-1619983081593-e2ba5b543168?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3wzMjM4NDZ8MHwxfHJhbmRvbXx8fHx8fHx8fDE3NDk1NzAwNDV8&ixlib=rb-4.1.0&q=80&w=400" alt="">
          <div class="player__legend">

odysseus0

Git-Inspired Context Management for AI Agents

The Core Analogy

Git and AI agent conversations face the same fundamental challenge: managing branching threads of work that must be merged back together.

The key insight: Think of git as if it only had commit messages, no file changes. This is exactly what AI conversation management needs - a way to branch, merge, and rebase pure conversation history. The vocabulary and mental models from git can illuminate context management for AI agents.

Precise Mappings (Git Without Files)

mizchi

/**
 * My Portable RAG
 * $ pnpm add sqlite-vec @ai-sdk/google ai
 * SQLite Vector Search + Google AI Embeddings
 *
 * Required environment variables:
 *   GOOGLE_GENERATIVE_AI_API_KEY=your-api-key
 *
 * Usage:
 *   # Index text content

induratized

🧾 Git Worktree Workflow — Best Practices and Automation

---

✅ Why Use git worktree in a Monorepo?

• Work on multiple branches without switching or stashing.
• Avoids dirty working directory issues.
• Ideal for parallel development, review, testing, and fixes.
• Keeps main worktree clean and focused.

zr-tex8r

bxjaurl

LaTeX： urlパッケージでのフォント設定を和文に対応させる

前提環境

• フォーマット： LaTeX
• エンジン： 不問

• ただしメインの機能である「urlパッケージのフォント設定の和文対応」

luiisca

# React Router v7

> React Router v7 is a powerful, multi-strategy routing library for React, bridging the gap from React 18 to React 19. It enables developers to build client-side, server-side, or statically pre-rendered web applications with robust data loading, mutations, and navigation features. You can use it maximally as a React framework or as minimally as you want.

React Router v7 offers a comprehensive solution for routing in React applications, supporting various rendering strategies and data management patterns. It aims to simplify data fetching, mutations, and state synchronization with the server, while providing a great developer and user experience.

## Getting Started
### Picking a Mode
React Router v7 can be used in three primary modes, offering different levels of features and control:
-   **Declarative Mode**: Provides basic routing capabilities using JSX components like `<BrowserRouter>`, `<Routes>`, and `<Route>`. Suitable for simple client-side SPAs or when integrating with an existing