holycodex 0.3.2 → 0.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "holycodex",
-  "version": "0.3.2",
+  "version": "0.4.0",
   "description": "Lean Codex-only agent toolkit for ChatGPT Plus",
   "keywords": [
     "agents",

package/plugin/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "holycodex",
-  "version": "0.3.2",
+  "version": "0.4.0",
   "description": "Lean Codex-only agents, skills, hooks, and MCP defaults.",
   "author": {
     "name": "David Basile Filho",

package/plugin/agents/explorer.toml

@@ -1,6 +1,6 @@
-description = "Read-only internal repository explorer. Use for a narrow unfamiliar codebase question needing exact files, symbols, history, or diagnostics before implementation."
+description = "Use for read-only repo research: exact files, symbols, history, or diagnostics."
 model = "gpt-5.6-luna"
 model_reasoning_effort = "low"
 developer_instructions = """
-Start: "I detect investigation intent — [reason]. [action]." Inspect assigned internal area only. Use git_bash MCP for every shell command. Read-only: search, read, diagnostics, history. No edit, install, external write, or subagent. Do not broaden scope. Return concise findings with exact paths, symbols, evidence, uncertainty. Stop when assigned question answered.
+Start: "I detect investigation intent — [reason]. [action]." Inspect only assigned repo scope. Use git_bash MCP for every shell command. Search, read, diagnose, and inspect history; never edit, install, write externally, delegate, or broaden scope. Return exact paths, symbols, evidence, and uncertainty. Stop when question is answered.
 """

package/plugin/agents/librarian.toml

@@ -1,6 +1,6 @@
-description = "Read-only external-source researcher. Use when current primary documentation, standards, versions, or cited evidence must be verified outside the repository."
+description = "Use for read-only external research from current primary sources."
 model = "gpt-5.6-luna"
 model_reasoning_effort = "low"
 developer_instructions = """
-Start: "I detect research intent — [reason]. [action]." Research assigned external sources only. Use git_bash MCP for every shell command. Read-only. Prefer primary current sources. No implementation, external write, or subagent. Do not broaden query. Return concise claim, citation, version/date, conflict, uncertainty. Stop when assigned question answered.
+Start: "I detect research intent — [reason]. [action]." Research only assigned external scope. Use git_bash MCP for every shell command. Prefer current primary sources; never implement, write externally, delegate, or broaden scope. Return claims with citations, versions or dates, conflicts, and uncertainty. Stop when question is answered.
 """

package/plugin/agents/worker.toml

@@ -1,6 +1,6 @@
-description = "Isolated implementation worker. Use only for a bounded independent change with explicit files and acceptance criteria when delegation materially helps."
+description = "Use for isolated, bounded implementation with explicit acceptance criteria."
 model = "gpt-5.6-luna"
 model_reasoning_effort = "medium"
 developer_instructions = """
-Start: "I detect implementation intent — [reason]. [action]." Implement only explicit files, scope, acceptance criteria. Use git_bash MCP for every shell command. Prompt, skill, or instruction task: load caveman skill first; write terse without losing constraints. Preserve architecture, API, behavior, naming, style. Smallest correct change. No speculative cleanup, abstraction, dependency, docs, or subagent. Respect user work. Run smallest targeted proof. Return changed paths, checks, blocker.
+Start: "I detect implementation intent — [reason]. [action]." Change only assigned files and scope; meet stated criteria. Use git_bash MCP for every shell command. Prompt, skill, or instruction task: load caveman skill first; write terse without losing constraints. Preserve architecture, API, behavior, naming, style, and user work. Make smallest correct change; add no speculative cleanup, abstraction, dependency, docs, or subagent. Run smallest proof. Return changed paths, checks, and blockers.
 """

package/plugin/runtime/bootstrap.js

@@ -1,4 +1,4 @@
-import { t as CORE_INSTRUCTIONS } from "./core-instructions-CKS8xwZK.js";
+import { t as CORE_INSTRUCTIONS } from "./core-instructions-D4kR5ZFv.js";
 import { access } from "node:fs/promises";
 import { join } from "node:path";
 //#region src/bootstrap.ts

package/plugin/runtime/cli.js

@@ -120,7 +120,7 @@ function paths(home = process.env.CODEX_HOME ?? join(homedir(), ".codex")) {
 		home,
 		config: join(home, "config.toml"),
 		cacheRoot,
-		cache: join(cacheRoot, "0.3.2"),
+		cache: join(cacheRoot, "0.4.0"),
 		agents: join(home, "holycodex", "agents"),
 		legacy: [
 			join(home, "plugins", "cache", "sisyphuslabs", "omo"),
@@ -208,7 +208,7 @@ async function cleanup(_options) {
 }
 //#endregion
 //#region src/cli.ts
-var VERSION = "0.3.2";
+var VERSION = "0.4.0";
 var HELP = `HolyCodex ${VERSION}\n\nUsage: holycodex <install|cleanup> [options]\n\nOptions:\n  --help              Show help\n  --version           Show version\n  --no-tui            Accepted; commands are noninteractive\n  --codex-autonomous  Set autonomous Codex permissions\n  --json              Print machine-readable result\n`;
 async function main() {
 	const args = process$1.argv.slice(2);

package/plugin/runtime/core-instructions-D4kR5ZFv.js

@@ -0,0 +1,4 @@
+//#region src/core-instructions.ts
+var CORE_INSTRUCTIONS = "HolyCodex: Start first user-facing update: \"I detect [fix/implementation/investigation/question] intent — [reason]. [action].\" Act. Shell: git_bash MCP; exec_command only if unavailable or nonshell. Prompt, skill, or instruction edit: load caveman; preserve constraints. Primary owns decisions, integration, verification. Delegate only bounded independent work that saves cost/time: explorer=repo facts; librarian=current external facts; worker=isolated implementation. Never delegate responsibility, trivial, or tightly coupled work. Subagents cut cost, not form organization. Match reasoning effort to complexity. Use GPT 5.6 Luna for most subagents at low or medium reasoning; GPT 5.6 Terra only for complex subagent work, at low reasoning.";
+//#endregion
+export { CORE_INSTRUCTIONS as t };

package/plugin/runtime/git-bash.js

@@ -166,7 +166,7 @@ async function handleGitBashMcpRequest(input, options = {}) {
 		capabilities: { tools: { listChanged: false } },
 		serverInfo: {
 			name: "git_bash",
-			version: "0.3.2"
+			version: "0.4.0"
 		},
 		protocolVersion: protocolVersionFromInput(input) ?? "2024-11-05"
 	});
@@ -222,7 +222,7 @@ async function runToolResponse(id, args, options) {
 function toolsForOptions(options) {
 	const sharedTools = [{
 		name: "which_bash",
-		description: "Use before Windows shell work when the Git Bash executable path must be confirmed.",
+		description: "Use to find Git Bash on Windows.",
 		inputSchema: {
 			type: "object",
 			properties: {},
@@ -230,7 +230,7 @@ function toolsForOptions(options) {
 		}
 	}, {
 		name: "diagnose",
-		description: "Use when git_bash cannot run or Windows shell readiness needs diagnosis.",
+		description: "Use to diagnose Git Bash readiness.",
 		inputSchema: {
 			type: "object",
 			properties: {},
@@ -240,27 +240,27 @@ function toolsForOptions(options) {
 	if (!canRunGitBash(options)) return sharedTools;
 	return [{
 		name: "run",
-		description: "Use on native Windows for Bash commands, POSIX behavior, Git tooling, or Unix utilities; use exec_command only when git_bash is unavailable or the operation is not shell work.",
+		description: "Use to run Bash, Git, POSIX, or Unix commands on Windows; use exec_command only if unavailable or nonshell.",
 		inputSchema: {
 			type: "object",
 			properties: {
 				command: {
 					type: "string",
-					description: "The command to execute."
+					description: "Command to run."
 				},
 				timeout: {
 					type: "integer",
 					minimum: 1,
 					maximum: MAX_TIMEOUT_MS,
-					description: `Optional timeout in milliseconds. If omitted, uses the inherited exec_command timeout when configured; otherwise ${defaultTimeoutMs(options)}ms.`
+					description: `Timeout in milliseconds; defaults to inherited exec_command timeout or ${defaultTimeoutMs(options)}ms.`
 				},
 				workdir: {
 					type: "string",
-					description: "The working directory to run the command in. Defaults to the current directory. Use this instead of 'cd' commands."
+					description: "Working directory. Use this instead of 'cd'. Defaults to current directory."
 				},
 				description: {
 					type: "string",
-					description: "Clear, concise description of what this command does in 5-10 words."
+					description: "Command purpose in 5-10 words."
 				}
 			},
 			required: ["command"],

package/plugin/runtime/lsp.js

@@ -2877,7 +2877,7 @@ var LSP_MCP_TOOLS = [
 		name: "status",
 		aliases: ["lsp_status"],
 		title: "LSP Status",
-		description: "Use to inspect configured and active LSP servers without starting one.",
+		description: "Use to list LSP servers without starting them.",
 		inputSchema: objectSchema({}),
 		execute: executeLspStatus
 	},
@@ -2885,7 +2885,7 @@ var LSP_MCP_TOOLS = [
 		name: "diagnostics",
 		aliases: ["lsp_diagnostics"],
 		title: "LSP Diagnostics",
-		description: "Use after code edits or during diagnosis to get errors, warnings, and hints for a file or directory.",
+		description: "Use to get file or directory diagnostics.",
 		inputSchema: objectSchema({
 			filePath: {
 				type: "string",
@@ -2909,7 +2909,7 @@ var LSP_MCP_TOOLS = [
 		name: "goto_definition",
 		aliases: ["lsp_goto_definition"],
 		title: "LSP Goto Definition",
-		description: "Use to find the exact definition of a symbol before changing or explaining it.",
+		description: "Use to find a symbol's definition.",
 		inputSchema: objectSchema({
 			filePath: {
 				type: "string",
@@ -2934,7 +2934,7 @@ var LSP_MCP_TOOLS = [
 		name: "find_references",
 		aliases: ["lsp_find_references"],
 		title: "LSP Find References",
-		description: "Use to find every workspace reference before refactoring, renaming, or assessing impact.",
+		description: "Use to find all workspace references to a symbol.",
 		inputSchema: objectSchema({
 			filePath: {
 				type: "string",
@@ -2963,7 +2963,7 @@ var LSP_MCP_TOOLS = [
 		name: "symbols",
 		aliases: ["lsp_symbols"],
 		title: "LSP Symbols",
-		description: "Use to outline one file or locate named symbols across the workspace.",
+		description: "Use to outline a file or search workspace symbols.",
 		inputSchema: objectSchema({
 			filePath: {
 				type: "string",
@@ -2972,7 +2972,7 @@ var LSP_MCP_TOOLS = [
 			scope: {
 				type: "string",
 				enum: ["document", "workspace"],
-				description: "Use document for file outline or workspace for project-wide search."
+				description: "document outlines a file; workspace searches the project."
 			},
 			query: {
 				type: "string",
@@ -2989,7 +2989,7 @@ var LSP_MCP_TOOLS = [
 		name: "prepare_rename",
 		aliases: ["lsp_prepare_rename"],
 		title: "LSP Prepare Rename",
-		description: "Use before rename to verify the symbol and position support a semantic rename.",
+		description: "Use to check whether a symbol supports semantic rename.",
 		inputSchema: objectSchema({
 			filePath: {
 				type: "string",
@@ -3014,7 +3014,7 @@ var LSP_MCP_TOOLS = [
 		name: "rename",
 		aliases: ["lsp_rename"],
 		title: "LSP Rename",
-		description: "Use for a semantic workspace-wide symbol rename after prepare_rename succeeds.",
+		description: "Use to rename a symbol workspace-wide after prepare_rename succeeds.",
 		inputSchema: objectSchema({
 			filePath: {
 				type: "string",
@@ -3044,16 +3044,16 @@ var LSP_MCP_TOOLS = [
 		name: "install_decision",
 		aliases: ["lsp_install_decision"],
 		title: "LSP Install Decision",
-		description: "Use after a missing-server prompt to record explicit install permission or a decline; decline when permission was not explicit.",
+		description: "Use to record explicit LSP install permission or decline.",
 		inputSchema: objectSchema({
 			server_id: {
 				type: "string",
-				description: "The LSP server id from the not-installed message (e.g. 'rust')."
+				description: "Server id from the not-installed message, e.g. rust."
 			},
 			decision: {
 				type: "string",
 				enum: ["declined", "allowed"],
-				description: "'declined' silences future prompts; 'allowed' pre-authorizes installation."
+				description: "declined silences prompts; allowed authorizes installation."
 			}
 		}, ["server_id", "decision"]),
 		execute: executeLspInstallDecision
@@ -3072,7 +3072,7 @@ function coerceToolArguments(value) {
 //#endregion
 //#region packages/lsp-core/src/mcp.ts
 var SERVER_NAME = "lsp";
-var SERVER_VERSION = "0.3.2";
+var SERVER_VERSION = "0.4.0";
 async function handleLspMcpRequest(input) {
 	if (!isPlainRecord(input)) return errorResponse(null, -32600, "Invalid Request");
 	const id = jsonRpcId(input["id"]);

package/plugin/runtime/rules.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { t as CORE_INSTRUCTIONS } from "./core-instructions-CKS8xwZK.js";
+import { t as CORE_INSTRUCTIONS } from "./core-instructions-D4kR5ZFv.js";
 import { mkdir, readFile, readdir, rm, writeFile } from "node:fs/promises";
 import { dirname, isAbsolute, join, relative, resolve } from "node:path";
 import { stdin, stdout } from "node:process";

package/plugin/skills/ast-grep/SKILL.md

@@ -1,20 +1,20 @@
 ---
 name: ast-grep
-description: AST-aware search and deterministic rewrite. Use when a code pattern depends on syntax shape or needs a safe repeatable codemod.
+description: Search or rewrite code by syntax shape; use for safe repeatable codemods.
 ---
 
 # ast-grep
 
-Use `sg` when target is syntax shape: function, call, class, import, missing `await`, empty catch, unsafe assertion, or codemod. Use `rg` for plain text.
+Use `sg` for syntax shapes; use `rg` for text.
 
 ## Flow
 
 1. Name language and exact syntax shape.
 2. Start search-only. Use smallest pattern with metavariables.
-3. Inspect every match class. Add `inside`, `has`, `not`, or relational rule only when needed.
+3. Inspect match classes; constrain only as needed.
 4. Test rewrite on narrow path. Review diff.
 5. Apply deterministic rewrite. Run formatter, diagnostics, targeted tests.
 
-Use `sg run -p '<pattern>' -l <language> <path>` for simple search. Use YAML rule for constraints, relational matching, or reusable codemod. Never run write mode before match review. Never use regex replacement for syntax-bearing code.
+Simple search: `sg run -p '<pattern>' -l <language> <path>`. Use YAML for constraints, relations, or reusable codemods. Review matches before writes. Never regex-replace syntax-bearing code.
 
 Load only needed reference: `patterns.md`, `yaml-rules.md`, `recipes.md`, `pitfalls.md`, `sgconfig.md`, `cli.md`, or `install.md`.

package/plugin/skills/caveman/SKILL.md

@@ -1,84 +1,31 @@
 ---
 name: caveman
-description: >
-  Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman
-  while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra,
-  wenyan-lite, wenyan-full, wenyan-ultra.
-  Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens",
-  "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
+description: Terse, technically exact replies in lite, full, ultra, or Wenyan variants. Use for caveman mode, brief replies, fewer tokens, or `/caveman`.
 ---
 
-Respond terse like smart caveman. All technical substance stay. Only fluff die.
+# Caveman
 
-## Persistence
+Write terse. Keep all technical meaning; remove filler.
 
-ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift. Still active if unsure. Off only: "stop caveman" / "normal mode".
-
-Default: **full**. Switch: `/caveman lite|full|ultra`.
+Active every reply until user says `stop caveman` or `normal mode`. Default `full`; switch with `/caveman lite|full|ultra` or Wenyan equivalent.
 
 ## Rules
 
-Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). No tool-call narration, no decorative tables/emoji, no dumping long raw error logs unless asked — quote shortest decisive line. Standard well-known tech acronyms OK (DB/API/HTTP); never invent new abbreviations (cfg/impl/req/res/fn) — tokenizer split them same as full word: zero token saved, reader still decode. Full word cheaper AND clearer. No causal arrows (→) either — own token, save nothing. Technical terms exact. Code blocks unchanged. Errors quoted exact.
-
-Preserve user's dominant language. User write Portuguese → reply Portuguese caveman. User write Spanish → reply Spanish caveman. Compress the style, not the language. No forced English openings or status phrases. ALWAYS keep technical terms, code, API names, CLI commands, commit-type keywords (feat/fix/...), and exact error strings verbatim — unless user explicitly ask for translation.
-
-No self-reference. Never name or announce the style. No "caveman mode on", "me caveman think", no third-person caveman tags. Output caveman-only — never normal answer plus "Caveman:" recap. Exception: user explicitly ask what the mode is.
+- Match user's language.
+- Preserve exact technical terms, code, APIs, commands, paths, error text, and commit keywords unless translation requested.
+- Remove articles when clear, filler, pleasantries, hedging, repetition, and decorative formatting. Fragments allowed.
+- Use short familiar words. Keep standard acronyms; invent none. No causal arrows.
+- No self-reference, style announcement, tool narration, or duplicate normal-language recap.
+- Quote only decisive error lines unless more requested.
+- Code, commits, and PR text stay grammatical.
 
 Pattern: `[thing] [action] [reason]. [next step].`
 
-Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
-Yes: "Bug in auth middleware. Token expiry check use `<` not `<=`. Fix:"
-
-## Intensity
-
-| Level            | What change                                                                                                                                                                                                                                                                                                                  |
-| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **lite**         | No filler/hedging. Keep articles + full sentences. Professional but tight                                                                                                                                                                                                                                                    |
-| **full**         | Drop articles, fragments OK, short synonyms. Classic caveman. No tool-call narration, no decorative tables/emoji, no long raw error-log dumps unless asked. Standard acronyms OK; no invented abbreviations                                                                                                                  |
-| **ultra**        | Strip conjunctions when cause-then-effect stay unambiguous. One word when one word enough. State each fact once. NO prose abbreviations (cfg/impl/req/res/fn/auth), NO arrows (X → Y) — measured zero token saving under tokenizer, cost decode clarity. Code symbols, function names, API names, error strings: never touch |
-| **wenyan-lite**  | Semi-classical. Drop filler/hedging but keep grammar structure, classical register                                                                                                                                                                                                                                           |
-| **wenyan-full**  | Maximum classical terseness. Fully 文言文. 80-90% character reduction. Classical sentence patterns, verbs precede objects, subjects often omitted, classical particles (之/乃/為/其)                                                                                                                                         |
-| **wenyan-ultra** | Extreme abbreviation while keeping classical Chinese feel. Maximum compression, ultra terse                                                                                                                                                                                                                                  |
-
-Example — "Why React component re-render?"
-
-- lite: "Your component re-renders because you create a new object reference each render. Wrap it in `useMemo`."
-- full: "New object ref each render. Inline object prop = new ref = re-render. Wrap in `useMemo`."
-- ultra: "Inline obj prop, new ref, re-render. `useMemo`."
-- wenyan-lite: "組件頻重繪，以每繪新生對象參照故。以 useMemo 包之。"
-- wenyan-full: "每繪新生對象參照，故重繪；以 useMemo 包之則免。"
-- wenyan-ultra: "新參照則重繪。useMemo 包之。"
-
-Example — "Explain database connection pooling."
-
-- lite: "Connection pooling reuses open connections instead of creating new ones per request. Avoids repeated handshake overhead."
-- full: "Pool reuse open DB connections. No new connection per request. Skip handshake overhead."
-- ultra: "Pool reuse open DB connections. No per-request handshake."
-- wenyan-full: "池蓄已開之連，不逐請而新開，省握手之費。"
-- wenyan-ultra: "池蓄連，免逐請新開，省握手。"
-
-## Auto-Clarity
-
-Drop caveman when:
-
-- Security warnings
-- Irreversible action confirmations
-- Multi-step sequences where fragment order or omitted conjunctions risk misread
-- Compression itself creates technical ambiguity (e.g., `"migrate table drop column backup first"` — order unclear without articles/conjunctions)
-- User asks to clarify or repeats question
-
-Resume caveman after clear part done.
-
-Example — destructive op:
-
-> **Warning:** This will permanently delete all rows in the `users` table and cannot be undone.
->
-> ```sql
-> DROP TABLE users;
-> ```
->
-> Caveman resume. Verify backup exist first.
+## Levels
 
-## Boundaries
+- `lite`: grammatical sentences; no filler or hedging.
+- `full`: drop clear articles; fragments and short words allowed.
+- `ultra`: state each fact once; remove safe conjunctions; never shorten technical text.
+- `wenyan-lite|full|ultra`: same levels in semi-classical to fully classical Chinese.
 
-Code/commits/PRs: write normal. "stop caveman" or "normal mode": revert. Level persist until changed or session end.
+Use full grammar for security warnings, irreversible confirmations, ordered steps, ambiguity, or clarification. Resume terse style afterward.

package/plugin/skills/comment-checker/SKILL.md

@@ -1,16 +1,8 @@
 ---
 name: comment-checker
-description: Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
+description: Use to handle comment-checker warnings after edits.
 ---
 
-# Codex Comment Checker
+# Comment Checker
 
-The plugin registers a `PostToolUse` hook for successful `apply_patch`, `write`, `edit`, `multi_edit`, and `multiedit` calls.
-
-When comment-checker reports a warning after a patch, Codex receives blocking feedback and should fix or explain the flagged comment before moving on.
-
-## Scope
-
-- No MCP tool is exposed.
-- Non-edit tools are ignored by this plugin.
-- Missing checker binaries emit no hook output so normal Codex work can continue.
+After successful `apply_patch`, `write`, `edit`, `multi_edit`, or `multiedit`, fix or explain any blocking warning before continuing. Non-edit tools are ignored. No MCP tool exists. Missing checker binaries produce no output.

package/plugin/skills/compress/SKILL.md

@@ -1,26 +1,18 @@
 ---
 name: compress
-description: Rewrite any text, skill, prompt, documentation, instructions, prose, notes, or structured content to use fewer words and tokens while preserving meaning, facts, constraints, safety, tone, and required structure. Use when asked to compress, condense, tighten, shorten, de-duplicate, optimize token usage, or rewrite using caveman principles.
+description: Use to shorten text without losing meaning, constraints, tone, safety, structure, or exact technical content.
 ---
 
 # Compress
 
-Rewrite with caveman principles: all substance stays; filler dies. Do not automatically adopt caveman voice unless user requests it. Default output remains clear, grammatical, and natural.
+1. Identify purpose, audience, format, facts, exact strings, constraints, gates, warnings, links, and tone.
+2. Remove repetition, filler, redundant headings, obvious explanation, decorative wording, and weak transitions.
+3. Merge related rules. Use direct verbs, familiar words, compact lists, and one statement per fact.
+4. Preserve names, code, commands, paths, APIs, errors, numbers, citations, legal terms, user terminology, and order where it matters.
+5. Compare result with source: no lost rule, changed meaning, weaker prohibition, invented claim, broken reference, or scope change.
 
-## Workflow
+Keep grammar when terseness risks ambiguity, especially for safety, irreversible actions, legal or medical text, and ordered work. Do not adopt caveman voice unless requested.
 
-1. Identify purpose, audience, format, required facts, exact strings, constraints, decision gates, safety warnings, examples, links, and tone.
-2. Remove repetition, throat-clearing, filler, redundant headings, obvious explanation, decorative adjectives, and verbose transitions.
-3. Merge related rules. Prefer direct verbs, short familiar words, compact lists, and one statement per fact.
-4. Preserve technical names, code, commands, paths, APIs, error strings, numbers, citations, legal terms, and user-defined terminology exactly unless correction is requested.
-5. Preserve ordering when sequence matters. Keep full grammar where compression could create ambiguity, especially safety, irreversible actions, legal/medical guidance, or multi-step operations.
-6. Check compressed output against source: no lost requirement, changed meaning, weakened prohibition, invented claim, broken reference, or altered scope.
+For skills and prompts, preserve frontmatter, triggers, tool and resource routing, permissions, stop conditions, and validation. For code or config, change prose only unless refactoring was requested. Keep evidence and nuance in prose; keep tables only when they improve scanning.
 
-## Content Rules
-
-- **Skills/prompts:** preserve YAML frontmatter, trigger coverage, imperative instructions, tool/resource references, permissions, stop conditions, and validation. Remove duplicated “when to use” prose from body when frontmatter already carries it.
-- **Code/config:** never compress syntax or identifiers unless explicitly asked to refactor. Compress surrounding explanation only.
-- **Prose/docs:** preserve thesis, evidence, nuance, attribution, and intended tone. Remove repeated framing and examples that add no distinct value.
-- **Lists/tables:** merge duplicates; keep mappings and comparisons when format improves scan speed.
-
-If user sets length/ratio/style, follow it. Otherwise aim for largest safe reduction, not shortest possible output. Report before/after size only when useful or requested.
+Honor requested size or style; otherwise maximize safe reduction. Report size only when useful or requested.

package/plugin/skills/debugging/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: debugging
-description: Reproduce, isolate, prove, and minimally fix runtime bugs. Use for crashes, wrong behavior, hangs, races, leaks, or unexplained performance.
+description: Use to prove and minimally fix crashes, wrong behavior, hangs, races, leaks, or slowness.
 ---
 
 # Debugging
@@ -9,15 +9,14 @@ No guess-fix loop.
 
 1. Reproduce exact symptom with smallest command.
 2. Minimize input, environment, and path.
-3. Write at least three plausible causes from distinct layers.
-4. Rank by evidence and cheap falsifier.
-5. Instrument narrow boundary. Capture values, ordering, ownership, timing, process state.
-6. Disprove causes. After two failed rounds, change angle; do not add reviewer or oracle agent.
-7. Confirm root cause with evidence that predicts symptom.
-8. Add failing public-behavior regression test.
-9. Make minimum root fix.
-10. Run targeted test, then proportional suite. Remove temporary instrumentation.
+3. List three plausible cross-layer causes; rank by evidence and cheapest falsifier.
+4. Instrument narrow boundary. Capture values, ordering, ownership, timing, process state.
+5. Disprove causes. Change angle after two failed rounds; add no reviewer or oracle agent.
+6. Confirm root cause with evidence that predicts symptom.
+7. Add failing public-behavior regression test.
+8. Make minimum root fix.
+9. Run targeted test, then proportional suite. Remove temporary instrumentation.
 
-No sleeps for async proof. Use event, signal, fake clock, trace, debugger, profiler, sanitizer, or deterministic fixture. No implementation before root cause unless user explicitly asks for mitigation.
+No sleeps for async proof; use deterministic events, clocks, traces, debuggers, profilers, sanitizers, or fixtures. Do not implement before proving cause unless user requests mitigation.
 
 Load only relevant runtime/tool reference under `references/`. Report reproduction, hypotheses rejected, root cause, proof, fix, checks, residual uncertainty.

package/plugin/skills/define-goal/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: define-goal
-description: Define or refine one measurable goal before work. Use only when explicitly asked to set, create, quantify, or clarify a goal.
+description: Use to define one measurable goal when explicitly asked to set or refine one.
 ---
 
 # Define Goal
@@ -9,12 +9,12 @@ On activation, first user-visible line must be:
 
 **GOAL MODE ACTIVATED**
 
-Turn intent into one bounded, verifiable objective. No plan, log, snapshot, ledger, or handoff.
+Create one bounded, verifiable objective; no plan, log, snapshot, ledger, or handoff.
 
 ## Flow
 
 1. State outcome, target, proof, scope, exclusions, stop condition.
-2. Add meaningful thresholds: exact checks, paths, environments, counts, limits. No fake precision.
+2. Add useful checks, paths, environments, counts, or limits; no fake precision.
 3. Replace activity goals like “improve” with observable state.
 4. Ask one short question only if missing scope or validator changes intent.
 5. Call `get_goal`.

package/plugin/skills/frontend/SKILL.md

@@ -1,18 +1,18 @@
 ---
 name: frontend
-description: Build, style, debug, audit, or polish web UI. Use for frontend components, pages, visual QA, accessibility, performance, or premium editorial design.
+description: Use to build, debug, audit, or polish web UI, accessibility, performance, or editorial design.
 ---
 
 # Frontend
 
-Preserve stack, behavior, design tokens, component patterns, and supplied screenshot/URL contract. Small request stays small. No forced `DESIGN.md`, research lane, new dependency, GSAP, or heavyweight QA.
+Preserve stack, behavior, tokens, patterns, and supplied visual contract. Keep scope small. Do not force `DESIGN.md`, research, dependencies, GSAP, or heavy QA.
 
 ## Route
 
-- Build/redesign: inspect app shell, tokens, target component, responsive contract.
-- Visual reference: use supplied screenshot/URL first. Measure layout, type, color, spacing, surface, motion.
+- Build/redesign: inspect shell, tokens, target component, responsive contract.
+- Visual reference: use it first; measure layout, type, color, spacing, surface, and motion.
 - Performance: load `references/perfection/README.md` only for real audit or regression.
-- Palette/type/style lookup: load only relevant `references/ui-ux-db` data.
+- Palette/type/style: load only relevant `references/ui-ux-db` data.
 - Premium editorial: use rules below.
 
 ## Premium editorial mode

package/plugin/skills/handoff/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: handoff
-description: Compact conversation state into a safe resumable handoff. Use when asked to hand off, save context, or prepare another agent/session to continue.
+description: Use to save compact, safe context for another agent or session.
 ---
 
 # Handoff

package/plugin/skills/lsp/SKILL.md

@@ -1,21 +1,21 @@
 ---
 name: lsp
-description: Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.
+description: Use LSP diagnostics, definitions, references, symbols, or safe rename.
 ---
 
-# Codex LSP
+# LSP
 
-Call `lsp` MCP tools through the tool interface; `lsp.*`/`mcp__lsp__*` are tool-call names, not shell commands.
+Call `lsp` MCP tools, never their names as shell commands.
 
 ## Tools
 
-- `lsp.status`: list configured, installed, missing, disabled, and active language servers.
-- `lsp.diagnostics`: check one file or directory for LSP diagnostics. Prefer `severity: "error"` after edits.
-- `lsp.goto_definition`: locate a symbol definition from file, line, and character.
-- `lsp.find_references`: find usages of a symbol across the workspace.
-- `lsp.symbols`: inspect document symbols or search workspace symbols.
-- `lsp.prepare_rename`: check whether a rename is valid at a position.
-- `lsp.rename`: apply a language-server workspace edit for a rename.
+- `lsp.status`: server state.
+- `lsp.diagnostics`: file or directory diagnostics; prefer `severity: "error"` after edits.
+- `lsp.goto_definition`: symbol definition.
+- `lsp.find_references`: workspace usages.
+- `lsp.symbols`: document outline or workspace symbol search.
+- `lsp.prepare_rename`: rename validity.
+- `lsp.rename`: workspace rename edit.
 
 ## Config
 

package/plugin/skills/lsp-setup/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lsp-setup
-description: Configure and verify one language server. Use when semantic tooling is missing, unconfigured, or reports that its server is not installed.
+description: Use to configure and verify one missing or unconfigured language server.
 ---
 
 # LSP Setup

package/plugin/skills/plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plan
-description: Write a concise executable plan. Use only when the user explicitly asks for a plan before implementation.
+description: Use to write an executable plan only when explicitly requested before implementation.
 ---
 
 # Plan

package/plugin/skills/plan-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plan-review
-description: Review and repair an existing plan once. Use only when the user explicitly asks to review, critique, validate, or improve a plan.
+description: Use to review and repair a plan once when explicitly requested.
 ---
 
 # Plan Review

package/plugin/skills/programming/SKILL.md

@@ -1,13 +1,11 @@
 ---
 name: programming
-description: Strict Python, Rust, TypeScript, and Go implementation. Use whenever creating or changing .py, .pyi, .rs, .ts, .tsx, .mts, .cts, or .go files.
+description: Use strict Python, Rust, TypeScript, and Go rules for matching source files.
 ---
 
 # Programming
 
-Use for `.py`, `.pyi`, `.rs`, `.ts`, `.tsx`, `.mts`, `.cts`, `.go`, or matching project manifest.
-
-Before code, read language `references/<language>/README.md`; load only linked topic needed. Read `references/logging.md` only when touching logs. Rust unsafe/FFI also loads all `references/rust-ub/`.
+Before editing `.py`, `.pyi`, `.rs`, `.ts`, `.tsx`, `.mts`, `.cts`, `.go`, or matching manifests, read `references/<language>/README.md`. Load `references/logging.md` only for logs and all `references/rust-ub/` for Rust unsafe or FFI.
 
 ## Core
 

package/plugin/skills/refactor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: refactor
-description: Behavior-preserving structural change with tests and semantic navigation. Use when asked to refactor, restructure, extract, simplify, or modernize code.
+description: Use to refactor, restructure, extract, simplify, or modernize code without behavior changes.
 ---
 
 # Refactor

package/plugin/skills/remove-ai-slops/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: remove-ai-slops
-description: Remove AI-authored code smells while preserving behavior. Use when asked to clean generated code, remove AI slop, or simplify branch changes without feature work.
+description: Use to remove AI-generated code smells without behavior or feature changes.
 ---
 
 # Remove AI Slops

package/plugin/skills/rules/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: rules
-description: Explain or inspect HolyCodex scoped rule loading and cache. Use for rule locations, matching, injection, deduplication, limits, or cache behavior.
+description: Use to inspect HolyCodex rule discovery, matching, injection, deduplication, limits, or cache.
 ---
 
 # Rules

package/plugin/skills/security-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: security-research
-description: Exploitability-led security audit with optional narrow research. Use for repository security reviews, threat analysis, vulnerability validation, or attack paths.
+description: Use for exploitability-led repo security review, threat analysis, validation, or attack paths.
 ---
 
 # Security Research

package/plugin/skills/tdd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: tdd
-description: Public-seam vertical red-green-refactor development. Use when the user requests test-first work, TDD, regression tests, or integration tests.
+description: Use public-seam red-green-refactor for requested TDD, regression, or integration tests.
 ---
 
 # TDD

package/plugin/skills/tdd/mocking.md

@@ -1,60 +1,5 @@
-# When to Mock
+# Mocking
 
-Mock at **system boundaries** only:
+Prefer real objects, test databases, or fakes. Mock only system boundaries: external APIs, time, randomness, and sometimes databases or filesystems. Never mock owned classes or internal collaborators.
 
-- External APIs (payment, email, etc.)
-- Databases (sometimes - prefer test DB)
-- Time/randomness
-- File system (sometimes)
-
-Don't mock:
-
-- Your own classes/modules
-- Internal collaborators
-- Anything you control
-
-## Designing for Mockability
-
-At system boundaries, design interfaces that are easy to mock:
-
-**1. Use dependency injection**
-
-Pass external dependencies in rather than creating them internally:
-
-```typescript
-// Easy to mock
-function processPayment(order, paymentClient) {
-  return paymentClient.charge(order.total);
-}
-
-// Hard to mock
-function processPayment(order) {
-  const client = new StripeClient(process.env.STRIPE_KEY);
-  return client.charge(order.total);
-}
-```
-
-**2. Prefer SDK-style interfaces over generic fetchers**
-
-Create specific functions for each external operation instead of one generic function with conditional logic:
-
-```typescript
-// GOOD: Each function is independently mockable
-const api = {
-  getUser: (id) => fetch(`/users/${id}`),
-  getOrders: (userId) => fetch(`/users/${userId}/orders`),
-  createOrder: (data) => fetch("/orders", { method: "POST", body: data }),
-};
-
-// BAD: Mocking requires conditional logic inside the mock
-const api = {
-  fetch: (endpoint, options) => fetch(endpoint, options),
-};
-```
-
-The SDK approach means:
-
-- Each mock returns one specific shape
-- No conditional logic in test setup
-- Easier to see which endpoints a test exercises
-- Type safety per endpoint
+Inject boundary dependencies. Expose one typed operation per external action instead of a generic conditional fetcher; each mock then has one input and result shape.

package/plugin/skills/tdd/tests.md

@@ -1,77 +1,7 @@
-# Good and Bad Tests
+# Tests
 
-## Good Tests
+Test caller-visible behavior through public interfaces. Good tests survive refactors, use known literal expectations, perform one action, and assert its observable result.
 
-**Integration-style**: Test through real interfaces, not mocks of internal parts.
+Reject tests of private methods, internal calls, call counts, storage inspected behind the public interface, snapshots without a stable contract, or expected values recomputed by production logic. These test implementation, not behavior.
 
-```typescript
-// GOOD: Tests observable behavior
-test("user can checkout with valid cart", async () => {
-  const cart = createCart();
-  cart.add(product);
-  const result = await checkout(cart, paymentMethod);
-  expect(result.status).toBe("confirmed");
-});
-```
-
-Characteristics:
-
-- Tests behavior users/callers care about
-- Uses public API only
-- Survives internal refactors
-- Describes WHAT, not HOW
-- One logical assertion per test
-
-## Bad Tests
-
-**Implementation-detail tests**: Coupled to internal structure.
-
-```typescript
-// BAD: Tests implementation details
-test("checkout calls paymentService.process", async () => {
-  const mockPayment = jest.mock(paymentService);
-  await checkout(cart, payment);
-  expect(mockPayment.process).toHaveBeenCalledWith(cart.total);
-});
-```
-
-Red flags:
-
-- Mocking internal collaborators
-- Testing private methods
-- Asserting on call counts/order
-- Test breaks when refactoring without behavior change
-- Test name describes HOW not WHAT
-- Verifying through external means instead of interface
-
-```typescript
-// BAD: Bypasses interface to verify
-test("createUser saves to database", async () => {
-  await createUser({ name: "Alice" });
-  const row = await db.query("SELECT * FROM users WHERE name = ?", ["Alice"]);
-  expect(row).toBeDefined();
-});
-
-// GOOD: Verifies through interface
-test("createUser makes user retrievable", async () => {
-  const user = await createUser({ name: "Alice" });
-  const retrieved = await getUser(user.id);
-  expect(retrieved.name).toBe("Alice");
-});
-```
-
-**Tautological tests**: Expected value restates the implementation, so the test passes by construction.
-
-```typescript
-// BAD: Expected value is recomputed the way the code computes it
-test("calculateTotal sums line items", () => {
-  const items = [{ price: 10 }, { price: 5 }];
-  const expected = items.reduce((sum, i) => sum + i.price, 0);
-  expect(calculateTotal(items)).toBe(expected);
-});
-
-// GOOD: Expected value is an independent, known literal
-test("calculateTotal sums line items", () => {
-  expect(calculateTotal([{ price: 10 }, { price: 5 }])).toBe(15);
-});
-```
+Example: after `createUser`, verify `getUser(id)` returns the user; do not query the database directly.

package/plugin/runtime/core-instructions-CKS8xwZK.js

@@ -1,4 +0,0 @@
-//#region src/core-instructions.ts
-var CORE_INSTRUCTIONS = "HolyCodex core: Start first user-facing update: \"I detect [fix/implementation/investigation/pure question] intent — [reason]. [action].\" Then act. Use git_bash MCP for every shell command. Use exec_command only when git_bash is unavailable or work is not a shell command. Prompt, skill, or instruction task: load caveman skill first; write terse without losing constraints. Primary agent keeps control. Subagents reduce cost, never simulate an organization. Delegate bounded labor, never responsibility. Spend intelligence only where complexity requires it.";
-//#endregion
-export { CORE_INSTRUCTIONS as t };