Turn years of experience into knowledge you can actually reuse.

The most valuable professional knowledge is often the part you know so well that you stopped writing it down.

The problem

Patterns, heuristics and judgment accumulate over a career but remain fragmented across projects or simply in memory.

What goes in the repository

Patterns
Heuristics
Frameworks
Checklists
Lessons learned
Examples
Anti-patterns
References

craft/
├── index.md
├── patterns/
├── playbooks/
├── lessons/
└── references/

Why an open repository helps

Written judgment can be reused on the next engagement. Remembered judgment has to be reconstructed every time.

How Okide helps

Okide makes that craft easy to add to as you work, with history for the lessons that change.

Humans and agents, same files

Give an agent your accumulated judgment, not only the current task prompt.

OPEN BY DEFAULT

Keep the repository. Change the tools around it.

Experience compounds when it lives in files you can hand to the next project or the next agent. Okide helps you work with the repository without turning it into an Okide-only format.

Learn about Open Knowledge Format → Download Okide — free

Related use cases

ROLES

Domain expertise

Capture the knowledge that makes an expert expert.

domain/concepts/

Explore →

PERSONAL

Consulting

Structure client knowledge while keeping your method reusable.

clients/acme/index.md

Explore →

PERSONAL

Personal knowledge

Keep durable knowledge outside any single app.

knowledge/index.md

Explore →