jester/zlh-grind
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity
The daily GPT grind
33 Commits 1 Branch 0 Tags 143 KiB
Markdown 100%
5ba386b1c8
Go to file
jester 5ba386b1c8 Replace CONSTRAINTS.md with frontend-specific constraints - Next.js, SSR boundaries, UI philosophy, forbidden patterns
2025-12-27 23:33:19 +00:00
SCRATCH Create quick reference for DNS fix needed in next session 2025-12-20 23:10:20 +00:00
ANTI_DRIFT_GUARDRAIL.md Create ANTI_DRIFT_GUARDRAIL.md - Protect working pipelines from helpful but harmful changes 2025-12-20 23:20:06 +00:00
ANTI_DRIFT.md Add explicit anti-drift guardrail document 2025-12-13 18:43:30 +00:00
CONSTRAINTS.md Replace CONSTRAINTS.md with frontend-specific constraints - Next.js, SSR boundaries, UI philosophy, forbidden patterns 2025-12-27 23:33:19 +00:00
OPEN_THREADS.md Update OPEN_THREADS.md - Reflect devcontainer provisioning resolution, artifact naming fix, and new open items 2025-12-21 23:01:45 +00:00
README.md Add explicit execution continuity statement to README 2025-12-14 00:29:38 +00:00
SESSION_LOG.md Replace SESSION_LOG.md with correct Dec 20-21 chronology (devcontainer provisioning work only) 2025-12-21 23:00:48 +00:00
SESSION_START.md Update session start checklist to include ANTI_DRIFT.md 2025-12-13 18:45:33 +00:00
UPSTREAMS.md Register zlh-api upstream repo 2025-12-13 22:16:47 +00:00

README.md

zlh-grind

GPT Execution Workspace for ZeroLagHub

This repository is dedicated exclusively to GPT-driven implementation work. It exists to capture execution context, day-to-day grind notes, and concrete changes made during development.

This repository exists to preserve execution continuity across long-running development work.

Assistant Prompt

You are údar. In this repo you act as the execution assistant: implement, verify, and log work. Keep continuity by reading SESSION_LOG.md, OPEN_THREADS.md, and UPSTREAMS.md. Do not make architecture decisions here; defer to canonical docs in jester/knowledge-base.

What This Repo Is For

  • Daily GPT work logs
  • Session handovers
  • Implementation notes and scratchpads
  • Tracking what was changed, when, and why

What This Repo Is NOT

  • ❌ Architecture decisions
  • ❌ Cross-project source of truth
  • ❌ Product or strategy documentation

All canonical architecture, decisions, and references live in: jester/knowledge-base

Working Rules

  • This repo may be messy, iterative, and practical
  • Prefer clarity over polish
  • Reference canonical docs instead of duplicating them

If it happened during hands-on GPT execution, it belongs here.