alvinsng

name	no-use-effect
description	Enforce the no-useEffect rule when writing or reviewing React code. ACTIVATE when writing React components, refactoring existing useEffect calls, reviewing PRs with useEffect, or when an agent adds useEffect "just in case." Provides the five replacement patterns and the useMountEffect escape hatch.

No useEffect

Archetapp

Polymarket BTC 5-Minute Up/Down Trading Bot — Build Guide

What This Bot Does

This bot trades Polymarket's "BTC Up or Down" 5-minute binary markets. Every 5 minutes, Polymarket opens a market asking: "Will BTC be higher or lower than the opening price when this 5-minute window closes?" You buy "Up" or "Down" tokens at some price (e.g. $0.50–$0.95), and if you're right, each token pays out $1.00. If you're wrong, you lose your bet.

The bot uses technical analysis on real-time Binance BTC price data to predict the outcome, then places the trade on Polymarket right before the window closes — when we have the most information but (ideally) before the token price has fully priced in the outcome.

---

spenceriam

0 · About the User and Your Role

• The person you are assisting is User.
• Assume User is an experienced senior backend/database engineer, familiar with mainstream languages and their ecosystems such as Rust, Go, and Python.
• User values "Slow is Fast", focusing on: reasoning quality, abstraction and architecture, long-term maintainability, rather than short-term speed.
• Your core objectives:
  • As a strong reasoning, strong planning coding assistant, provide high-quality solutions and implementations in as few interactions as possible;
  • Prioritize getting it right the first time, avoiding superficial answers and unnecessary clarifications.

---

regenrek

GPT Codex Sound Notification

hooks/notify.sh

#!/usr/bin/env bash
payload="${1:-$(cat)}"

DEFAULT_CODEX_SOUND="<your_sound_here.wav>"
# Set CODEX_CUSTOM_SOUND in your shell config (e.g. ~/.zshrc;~/.bashrc;...) to override the alert path.
CODEX_CUSTOM_SOUND="${CODEX_CUSTOM_SOUND:-$DEFAULT_CODEX_SOUND}"

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