steipete

• Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
• Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
• NEVER edit .env or any environment variable files—only the user may change them.
• Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
• Moving/renaming and restoring files is allowed.
• ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

dgnsrekt

description	argument-hint	allowed-tools	model
Generate a problem-focused summary of the current implementation work	optional_plan_reference	Read(./**), Write(./.strategic-claude-basic/summary/**), Bash(git:*, date:*, grep:*), Glob	claude-opus-4-1

You are tasked with creating implementation summaries that focus on problems, incomplete work, and outstanding issues from the current work session. You should be problem-focused, session-scoped, and work only with uncommitted changes and current context.

Plan reference (optional): $1

stevenrouk

Complete the next task from the plan in docs/start-here.md

Please look at docs/start-here.md and follow the instructions. Your job is to get the next task done. Ultimately, you are the one guiding the work and making sure it meets what it's supposed to do. Chunk the work into small pieces, when it's helpful.

First, review the necessary files, think carefully, review more, and then create a plan to create the next chunk of work. Output your plan for approval by me (the user) before proceeding. Pause after outputting the plan to wait for my input.

Then, after we discuss and the plan is approved, execute the plan to finish the task. Use subagents when helpful. Mark the tasks as "in progress" to let other developers know you are working on them.

When you are done with the next task, say you are done and that we are ready to commit the work.

steipete

{
  "$schema": "https://opencode.ai/config.json",
  "model": "cerebras/qwen-3-coder-480b",
  "provider": {
    "cerebras": {
      "api": "https://api.cerebras.ai/v1",
      "npm": "@ai-sdk/openai-compatible",
      "name": "Cerebras",
      "env": [],
      "options": {

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"

davidfowl

// -----------------------------------------------------------------------------
// Azure RG Janitor - Spectre Edition
// Run with:   dotnet run cleanup-rg.cs
// Targets:    .NET 10 Preview 4+
// -----------------------------------------------------------------------------

#:package Azure.Identity@1.*
#:package Azure.ResourceManager@1.*
#:package Spectre.Console@0.50.0

Aaronontheweb

📚 Agent Memory Protocol

You have a long-term memory service exposed through the MemoryTools MCP interface. Treat it as your personal knowledge base: search it early, extend it often, curate it relentlessly.

1. Retrieve first, think second

• Before you begin any new task (or new sub-task), call
  MemoryTools.Search( query=<a concise natural-language description of the task>, limit=10, minSimilarity=0.70 ).
• For each hit, also call MemoryTools.GetMany( ids=<all relationship IDs> ) so you start with the full context graph.

Pomax

A new home

The script moved! Head on over to https://github.com/pomax/glitch-bulk-downloader for the latest version!

janakiramm

import json
import os  
import requests
import pytz
from datetime import datetime, timedelta
from typing import Any, Callable, Set, Dict, List, Optional
from mcp.server.fastmcp import FastMCP

# Create MCP server
mcp = FastMCP("Flight Server")

jeangatto

{
  "[html]": {
    "editor.defaultFormatter": "vscode.html-language-features"
  },
  "[css]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "[javascript]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },