AI SummaryThese three steps are REQUIRED after every change, no exception: 1. Changelog — Add entry to . NEVER skip, even for small fixes. 2. serial.txt — If ANY file under , , or any module imported at API startup was changed: increment by 1.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "pbgui — Copilot Instructions" prompt rules to my project. Repository: https://github.com/msei99/pbgui Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Copilot Instructions for pbgui
⛔ MANDATORY — Before finishing ANY task
These three steps are REQUIRED after every change, no exception: • Changelog — Add entry to releases/unreleased.md. NEVER skip, even for small fixes. • serial.txt — If ANY file under api/, PBApiServer.py, or any module imported at API startup was changed: increment api/serial.txt by 1. • Commit/push — ALWAYS ask user before committing or pushing. Failure to do steps 1–2 is a bug, not an oversight. ---
Release workflow
• Release steps are in RELEASING.md. • For each release vX.YY: • pbgui_purefunc.py: bump PBGUI_VERSION. • Move releases/unreleased.md notes into releases/vX.YY.md and update CHANGELOG.md. • api/serial.txt: increment so running clients show the restart requirement. • Commit: Release vX.YY, tag vX.YY, push branch + tags.
Project conventions
• FastAPI UI routes live under api/; pure helpers live in pbgui_purefunc.py. • Exchange operations (CCXT, market fetch, symbol info) belong in Exchange.py. • Database operations belong in Database.py. • Use :material/...: icon buttons for compact inline navigation (e.g. :material/arrow_left: / :material/arrow_right: for month navigation). Prefer material icons for concise controls consistent with existing UI. • When showing/exporting configs as JSON, use real JSON serialization (json.dumps) so null/true/false are preserved (avoid Python None/True/False formatting).
Chat trigger phrases
• If the user writes Bitte in Todo festhalten:, store the content in docs/roadmap/TODO.md (do not store it in repository root files). • If the user writes Merke Dir:, store the content as a persistent instruction in this file (.github/copilot-instructions.md) under ## Persistent Notes.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts