Instructions file CodexOpenCode
Instructions for JerryLookupU/klein-harness, a project described as: Klein-Harness is a repo-local closed-loop .harness runtime for Codex-first agent work.
11 5mo ago A 221 tokens
original MIT
Skill Claude CodeCodex
A planning guide that turns an unclear software request into a concrete blueprint for implementation. It covers new features, extensions, refactoring, design reviews, and comparing solutions.
11 5mo ago A 77 tokens
original MIT
Skill Claude CodeCodex
A skill that studies a codebase to document its real development conventions and maintainer preferences. It can produce a contributor guide or a shorter set of repository rules.
11 5mo ago A 56 tokens
original MIT
Skill Claude CodeCodex
A skill for searching Klein-Harness handoff and runtime logs. Klein-Harness is a system that coordinates coding workers and records their progress and results.
11 5mo ago A 50 tokens
original MIT
Skill Claude CodeCodex
An orchestration guide for turning a complex request into a shared plan, a dependency graph, and separate worker tasks. A dependency graph shows which tasks must finish before others can start.
11 5mo ago A 66 tokens
original MIT
Skill Claude CodeCodex
A setup and maintenance guide for a .harness folder: a shared set of rules that tells coding agents how to enter a project, claim work, recover from mistakes, and hand tasks to one another.
11 5mo ago A 59 tokens
original MIT
Skill Claude CodeCodex
A tool guide for turning web pages, documentation, and URLs into clean Markdown text. Markdown is a plain-text format that is easier for a coding assistant to read, search, and save.
11 5mo ago A 62 tokens
original MIT
Skill Claude CodeCodex
A working method for completing complex coding tasks through investigation, focused execution, verification, and review. It is designed for Klein-Harness workflows, which route tasks to workers and verify their results.
11 5mo ago A 86 tokens
original MIT
Skill Claude CodeCodex
A disciplined method for debugging software problems and finding their root cause. It requires collecting evidence, reproducing the failure, testing one explanation at a time, and verifying the fix.
11 5mo ago A 49 tokens
original MIT