Octo home

Inked Context
Linked Nodes

Create a framework-native app or production-minded monorepo with shared guidance already built in.

Start a project
pnpm dlx @markromolecule/octo@latest

Ready to copy.

Read the docs View source

One clean start.
Fewer decisions later.

Octo handles the seams that usually appear after the scaffold is already in use.

Choose the right shape

Create a focused app or a coordinated pnpm monorepo from one guided flow.

Stay framework-native

Start with familiar React, Next.js, Astro, Hono, or Express conventions.

Skip fine-tuning

Give coding agents the exact rules and workflows they need without custom model training.

Own every file

Generate readable TypeScript without a hidden runtime or proprietary wrapper.

Start production-ready

Include validation, CI seams, dependency updates, and deployment guidance.

Keep context flexible

Use the bundled snapshot, a Git submodule, or your own standalone copy.

From prompt to project

The Octo flow.

Four focused steps take you from an empty directory to a validated, context-ready codebase.

  1. 01

    Scope the workspace

    Choose one focused app or a coordinated pnpm workspace.

    Project shape
    ? Choose project shape:
❯ Standard (Single App)
  Monorepo (Shared workspaces)
  2. 02

    Integrate frameworks

    Use native generators and keep familiar framework conventions.

    Framework-native output
    Next.jsAstroHonoReactExpress
  3. 03

    Seed agent context

    Add project rules and workflows that assistants can follow from the first task.

    Generated context
    .agents/
├── rules/
│   └── web-components.md
└── workflows/
    └── feature-delivery.md
  4. 04

    Validate and ship

    Confirm the generated context is synchronized before you build.

    Context check
    $ pnpm context:validate
✓ Context is ready

Frequently asked questions

Everything else lives in the documentation.

Explore the docs
Does Octo replace the framework CLI?

No. Standard web projects use the official Vite, Next.js, or Astro generators. Octo coordinates setup and adds the shared engineering context around them.

When should I choose a monorepo?

Choose it when applications and shared packages need to evolve together. For one focused application, Standard mode keeps the framework’s familiar structure.

Does the bundled context require Git?

No. Bundled Snapshot copies the context-factory included with the package and needs no Git connection during generation.

Can I use my own context-factory?

Yes. Pass --context-repo or set CONTEXT_FACTORY_REPO to use a repository your team owns.

What do I need before I start?

Use Node.js 20 or newer and pnpm. The generated project includes the commands needed to validate its context.