Add portable Codex ops kit

This commit is contained in:
slaguru666
2026-04-12 14:00:55 +01:00
commit aa907983db
19 changed files with 679 additions and 0 deletions
+22
View File
@@ -0,0 +1,22 @@
# Portable Memory
These markdown files are the durable layer you can sync across machines.
## What Belongs Here
- user preferences that stay true across projects
- stable workflow conventions
- active project summaries
- important decisions worth remembering later
## What Does Not Belong Here
- secrets
- API keys
- giant transcript dumps
- temporary debugging notes
- anything that is likely to be stale within a day or two
## Operating Principle
Short, curated memory beats large raw history.
+7
View File
@@ -0,0 +1,7 @@
# Active Projects
## Codex Ops Kit
- Purpose: make Codex cheaper to run, easier to resume, and easier to share across machines.
- Core components: profile-based config, short global instructions, portable memory markdown, and maintenance scripts.
- Important constraint: portable assets should exclude secrets and large transient databases.
+15
View File
@@ -0,0 +1,15 @@
# Architecture Decisions
## Separate Durable Memory From Transcript History
Durable preferences and project summaries live in curated markdown files.
Large session JSONL files are treated as archival evidence that can be summarized or archived, not as the primary continuity layer.
## Prefer Profiles Over One Global Setting
There is no single best cost/performance configuration for every task. This kit uses `economy`, `balanced`, and `deep` profiles so the user can pick the right tradeoff quickly.
## Keep Instruction Files Lean
Small, targeted `AGENTS.md` files improve efficiency more reliably than giant all-purpose prompt files.
+6
View File
@@ -0,0 +1,6 @@
# User Profile
- Prefers Codex setups that are portable and Git-friendly.
- Wants lower token and credit usage by default without losing the option to do deeper work when needed.
- Wants Codex to retain durable context so recurring setup explanations are minimized.
- Prefers practical systems that can be shared with other Codex instances on other machines.
+8
View File
@@ -0,0 +1,8 @@
# Workflow Preferences
- Default to a balanced cost/performance profile for everyday work.
- Use cheaper profiles for small edits, reviews, and narrow tasks.
- Reserve higher reasoning settings for architecture, hard debugging, or multi-file refactors.
- Keep always-loaded instructions short.
- Distill reusable knowledge into markdown memory notes after substantial work.
- Periodically audit local Codex storage and archive old session transcripts instead of relying on them as memory.