← Solutions to problemsImporting knowledge

There’s no simple way to bring knowledge into your codebase.

Standards, context, and process live in people’s heads or scattered docs — not where the work actually happens.

Problem

There’s no simple way to bring knowledge into your codebase.

Shift

Install knowledge and process into your repo.

Effect

Move knowledge and guidance into the repo where humans and AI already work.

Signal view

Visible in the work

Raw input

Usable output

Knowledge
Patterns
Process

How we help

Install knowledge and process into your repo.

We ship installable packs you drop into your repository. Knowledge, standards, and workflows then live alongside the code your team and AI already use — no separate wiki or hidden tribal knowledge. Packs are versioned, tool-agnostic, and designed to run with Cursor, Claude, MCP, or a manual fallback.

What changes

01

The source of truth moves closer to the work.

02

Humans and AI stop depending on fresh explanation every time.

03

Standards become reusable operating context instead of scattered notes.

Who this helps most

Primary fit

  • Vibe coders & AI-first developers. You want expert practices and structure without spending months building them — install instead of invent.

Also strong for

Secondary fit

  • New teams & new hires. You need to align on standards and context fast; one install gets everyone on the same page.

Next step

If this problem feels familiar, the next move is usually either to install a pack or review the service path that helps make the operating model real.

Use this page to

  • Recognize whether the problem is genuinely present in your team.
  • See the product logic behind the pack and service routes.
  • Decide whether to move into installation, enquiry, or further exploration.