Goal: Replace the brainstorm server's vendored nodemodules with a single zero-dependency server.js using Node built-ins. Architecture: Single file with WebSocket protocol (RFC 6455 text frames), HTTP server (http module), and file watching (fs.watch).
Goal: Add spec and plan document review loops to the brainstorming and writing-plans skills. Architecture: Create reviewer prompt templates in each skill directory.
--- name: writing-plans description: Use when you have a spec or requirements for a multi-step task, before touching code --- Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it.
NEVER: INSTEAD: Example: your human partner's rule: "External feedback - be skeptical, but check carefully" your human partner's rule: "You and reviewer both report to me. If we don't need this feature, don't add it." Push back when: How to push back: If you're uncomfortable pushing back out loud: Name that tension, then tell your partner about the issue you've seen.
Load this reference when: writing or changing tests, adding mocks, or adding cleanup/helper methods for tests. Two principles govern everything here: Strict TDD produces both naturally: a test written first and watched failing against real code has already proven it can fail, and only earns a mock when the real dependency proves slow or external.
LLMs respond to the same persuasion principles as humans. Understanding this psychology helps you design more effective skills - not to manipulate, but to ensure critical practices are followed even under pressure.
--- name: finishing-a-development-branch description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work --- Core principle: Verify tests → Detect environment → Present options → Execute choice → Clean up. Announce at start: "I'm using the finishing-a-development-branch skill to complete this work." Run the project's full test suite (npm test / cargo test / pytest / go test ./...).
Goal: Refactor visual brainstorming from blocking TUI feedback model to non-blocking "Browser Displays, Terminal Commands" architecture. Architecture: Browser becomes an interactive display; terminal stays the conversation channel.
--- name: using-git-worktrees description: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback --- Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools.
Goal: Make using-git-worktrees, finishing-a-development-branch, and related skills work in the Codex App's sandboxed worktree environment without breaking existing behavior. Architecture: Read-only environment detection (git-dir vs git-common-dir) at the start of two skills.
Goal: Replace the brainstorm server's vendored nodemodules with a single zero-dependency server.js using Node built-ins. Architecture: Single file with WebSocket protocol (RFC 6455 text frames), HTTP server (http module), and file watching (fs.watch).
Goal: Add spec and plan document review loops to the brainstorming and writing-plans skills. Architecture: Create reviewer prompt templates in each skill directory.
--- name: writing-plans description: Use when you have a spec or requirements for a multi-step task, before touching code --- Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it.
NEVER: INSTEAD: Example: your human partner's rule: "External feedback - be skeptical, but check carefully" your human partner's rule: "You and reviewer both report to me. If we don't need this feature, don't add it." Push back when: How to push back: If you're uncomfortable pushing back out loud: Name that tension, then tell your partner about the issue you've seen.
Load this reference when: writing or changing tests, adding mocks, or adding cleanup/helper methods for tests. Two principles govern everything here: Strict TDD produces both naturally: a test written first and watched failing against real code has already proven it can fail, and only earns a mock when the real dependency proves slow or external.
LLMs respond to the same persuasion principles as humans. Understanding this psychology helps you design more effective skills - not to manipulate, but to ensure critical practices are followed even under pressure.
--- name: finishing-a-development-branch description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work --- Core principle: Verify tests → Detect environment → Present options → Execute choice → Clean up. Announce at start: "I'm using the finishing-a-development-branch skill to complete this work." Run the project's full test suite (npm test / cargo test / pytest / go test ./...).
Goal: Refactor visual brainstorming from blocking TUI feedback model to non-blocking "Browser Displays, Terminal Commands" architecture. Architecture: Browser becomes an interactive display; terminal stays the conversation channel.
--- name: using-git-worktrees description: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback --- Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools.
Goal: Make using-git-worktrees, finishing-a-development-branch, and related skills work in the Codex App's sandboxed worktree environment without breaking existing behavior. Architecture: Read-only environment detection (git-dir vs git-common-dir) at the start of two skills.