Reusable Skills and Open Knowledge Format (OKF) templates for Codex, Claude Code, and agent-assisted software projects.
Agent coding tools work best when they have both project knowledge and clear working procedures. Most repositories mix those concerns into ad hoc prompts, stale wiki pages, or long instructions that are hard to maintain.
This repository provides a small, portable starter kit:
- OKF templates for project knowledge that humans and agents can read.
- Skills for repeatable engineering workflows such as feature work, bug investigation, tests, refactoring, and OKF updates.
AGENTS.mdguidance for Codex.CLAUDE.mdguidance for Claude Code.- A minimal example you can copy into your own repository.
OKF, or Open Knowledge Format, is the project knowledge layer. In this repo, OKF means a directory of Markdown files with lightweight YAML frontmatter where useful. It captures architecture, domain concepts, data structures, features, playbooks, and update history.
OKF answers: "What is true about this project?"
A Skill is an agent-readable workflow. Each Skill has a SKILL.md file with trigger conditions, required context, steps, guardrails, and a completion checklist.
Skills answer: "How should the agent do this kind of work?"
AGENTS.md is the Codex-facing instruction file. It tells Codex how to use this repository, when to read README/docs/OKF, and how to keep Skills and docs synchronized.
CLAUDE.md is the Claude Code-facing instruction file. It mirrors the same repository rules, but is written for Claude Code users and workflows.
flowchart LR
Library["Reusable source library<br/>skills/"]
Codex["Codex project<br/>.agents/skills/"]
Claude["Claude Code project<br/>.claude/skills/"]
OKF["Project knowledge<br/>okf/"]
Agents["Codex guidance<br/>AGENTS.md"]
ClaudeMd["Claude Code guidance<br/>CLAUDE.md"]
Library --> Codex
Library --> Claude
OKF --> Codex
OKF --> Claude
Agents --> Codex
ClaudeMd --> Claude
.
├── README.md
├── LICENSE
├── CONTRIBUTING.md
├── CHANGELOG.md
├── AGENTS.md
├── CLAUDE.md
├── docs/
│ ├── getting-started.md
│ ├── codex.md
│ ├── claude-code.md
│ ├── okf.md
│ ├── customization.md
│ └── usage-matrix.md
├── examples/
│ ├── minimal/
│ │ ├── AGENTS.md
│ │ ├── CLAUDE.md
│ │ ├── okf/
│ │ └── skills/
│ ├── codex-project/
│ │ └── .agents/skills/
│ └── claude-code-project/
│ └── .claude/skills/
├── okf/
│ ├── index.md
│ ├── log.md
│ ├── architecture/
│ ├── domain/
│ ├── data/
│ ├── features/
│ └── playbooks/
└── skills/
├── implement-feature/
├── investigate-bug/
├── add-test/
├── refactor-safely/
└── update-okf/
-
Copy the minimal template into your project:
cp -R examples/minimal/. /path/to/your-repo/
-
Edit
/path/to/your-repo/okf/index.mdto describe your project. -
Add one or two project-specific OKF documents under
okf/architecture/,okf/domain/,okf/data/,okf/features/, orokf/playbooks/. -
Ask Codex or Claude Code to use the relevant Skill:
Use the implement-feature skill to add user profile editing. Read OKF first and update OKF after the implementation if behavior changes.
For a slower walkthrough, see Getting Started.
Codex should read AGENTS.md for repository-level instructions. The top-level skills/ directory is the canonical reusable source library in this repo. In a Codex project, place auto-discovered project Skills under .agents/skills/.
Typical request:
Use the implement-feature skill to add a CSV export button.
Read README.md, docs/codex.md, and relevant OKF files before editing.
See examples/codex-project/ for the Codex auto-discovery layout.
See docs/codex.md for setup and usage details.
Claude Code should read CLAUDE.md for repository-level instructions. The top-level skills/ directory is the canonical reusable source library in this repo. In a Claude Code project, place auto-discovered project Skills under .claude/skills/.
Typical request:
Use the investigate-bug skill.
Reproduce the issue first, summarize likely causes, then propose the smallest fix.
See examples/claude-code-project/ for the Claude Code auto-discovery layout.
See docs/claude-code.md for setup and usage details.
| Skill | Use when | Do not use when |
|---|---|---|
implement-feature |
Adding a new feature or changing existing behavior. | The task is only research or triage. |
investigate-bug |
Investigating a defect, regression, or unclear failure. | The root cause and exact fix are already known. |
add-test |
Adding or improving tests for existing behavior. | The behavior is still undefined. |
refactor-safely |
Improving structure without behavior changes. | Public APIs, schemas, or product behavior must change. |
update-okf |
Updating OKF after implementation or design changes. | There is no user-visible, architectural, domain, data, or playbook change. |
Use OKF for stable project knowledge, not task instructions. A useful OKF document should usually include:
- YAML frontmatter with at least
type. - A clear
titleanddescription. - Links to related OKF documents when relevant.
- Concrete details that help an agent avoid guessing.
- Citations or source links for claims that came from external material.
Example:
---
type: Feature
title: CSV Export
description: Lets users export filtered table rows as a CSV file.
tags: [export, reporting]
---
# Behavior
The export includes the same rows currently visible after filters are applied.
# Related
- Reporting overview: `okf/domain/reporting.md`See docs/okf.md.
- Copy
AGENTS.md,CLAUDE.md, andokf/into your repository. - Copy selected Skills from top-level
skills/into.agents/skills/for Codex or.claude/skills/for Claude Code. - Rewrite
okf/index.mdfor your project. - Add project-specific knowledge under the OKF directories.
- Update
AGENTS.mdandCLAUDE.mdwith your test commands, coding conventions, and release rules. - Keep reusable Skill source files generic enough to reuse, and keep project facts in OKF.
- Add a
review-prSkill for pull request review workflows. - Add
okf/data/warehouse.mdto document analytics tables or data contracts. - Add
okf/playbooks/release.mdfor release steps. - Narrow
refactor-safelywith project-specific public API rules. - Add test commands to
AGENTS.mdandCLAUDE.md.
- Start a feature: use
implement-feature, thenupdate-okf. - Debug a regression: use
investigate-bug, then optionallyadd-test. - Improve coverage: use
add-testwith a target file, feature, or bug. - Clean up code: use
refactor-safelyand keep the diff small. - Refresh project knowledge: use
update-okfafter a meaningful implementation change.
See docs/usage-matrix.md for a compact Codex, Claude Code, and generic template comparison.
Contributions should improve reuse, clarity, or correctness without turning this repository into a project-specific prompt dump.
Before opening a pull request:
- Read CONTRIBUTING.md.
- Keep Skills and docs synchronized.
- Verify links from README,
AGENTS.md, andCLAUDE.md. - Avoid secrets, credentials, private URLs, and personal data.
This project is released under the MIT License.
This repository provides templates and operating guidance for coding agents. It does not guarantee correctness, security, legal compliance, or production readiness. Review generated changes, adapt the templates to your organization, and choose appropriate validation before public or production use.