# Mo Setup

> Inspect and bring a project and its environment up to the Meta-O contract, including substantive knowledge, instructions, tooling, backend companions, and unsandboxed Codex, Claude Code, and OpenCode posture.

- Skill: `shkarupa-alex/mo-setup` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx skillmds@latest add shkarupa-alex/mo-setup`
- Raw SKILL.md: https://api.skillmd.com/api/skills/shkarupa-alex/mo-setup/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: shkarupa-alex (https://skillmd.com/u/shkarupa-alex)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/shkarupa-alex/mo-setup

---


# Set up a project for Meta-O

Read [Project setup contract](references/project-setup.md),
[Backend contract](references/backend-contract.md), and
[Purpose and architecture contract](references/purpose-and-architecture.md)
completely. For a Python project also read
[Python QC profile](references/qc-python.md) completely; for a TypeScript or
JavaScript project also read
[TypeScript QC profile](references/qc-typescript.md). Read both for a mixed
Python/TypeScript project. Read only the applicable language profiles completely.

Detect Orca through its native environment and status surface; report unsupported
or ambiguous environments. Check `orca`/`orca-cli` separately from the upstream
`orchestration` companion skill.

When watchdog readiness is in scope, check mature `jq` and `flock` dependencies
separately from backend controls.

Use Orca's version-matched `orca skills` guide. Report the exact source
separately from control discovery; an unrelated personal copy is not evidence.

Inspect knowledge, entry instructions, README, architecture reasons, backlog
quality, E2E and acceptance mapping, language/build config, mature complexity
and size linting, significant-code purpose, deterministic non-mutating QC, and
unsandboxed Codex/Claude Code/OpenCode posture. Do not create a backend fixture
document in ordinary projects.

If tracked repair is required, explain it and use a separate
`feature/meta-o-setup` branch based on up-to-date `develop`; never mix setup
repair into the current feature branch. Personal configuration changes require
explicit confirmation.