lytos init

lytos init creates the .lytos/ directory in your project with all 5 pillars pre-configured.

Usage

lyt init                                       # interactive
lyt init --name "Acme API" --tool claude --yes # non-interactive, single tool
lyt init --tool claude,cursor,copilot --yes    # multi-tool: several bridges at once
lyt init --all-tools --yes                     # every shipping adapter

The command is interactive by default. It will ask you:

1. Project name — used in the manifest
2. AI tool(s) — Claude Code, Cursor, Codex (OpenAI), GitHub Copilot, Gemini CLI, Windsurf, Multiple (CSV), All tools, or None. Each choice generates the adapter file that tool reads at session start (CLAUDE.md, .cursor/rules/lytos.mdc, AGENTS.md, .github/copilot-instructions.md, GEMINI.md, or .windsurfrules).

Mixed-team repos

If several developers use different AI tools on the same repo, generate every bridge in one run. Each bridge points at the same .lytos/ directory, so switching tools does not require reconfiguring the project.

lyt init --tool claude,cursor,copilot   # CSV of exactly what the team uses
lyt init --all-tools                    # all six shipping adapters

none can appear in the CSV as a no-op (so scripts can pass "none,claude" without a special case). Unknown values exit with an error before any file is written.

What it creates

.lytos/
├── manifest.md              # Intent — fill in your project identity
├── LYTOS.md                 # Method reference
├── sprint.md                # Current sprint template
├── skills/                  # Design — 9 reusable procedures
│   ├── session-start.md
│   ├── code-structure.md
│   ├── code-review.md
│   ├── testing.md
│   ├── documentation.md
│   ├── git-workflow.md
│   ├── deployment.md
│   ├── security.md
│   └── api-design.md
├── rules/                   # Standards — quality criteria
│   └── default-rules.md
├── issue-board/             # Progress — kanban board
│   ├── BOARD.md
│   ├── 0-icebox/
│   ├── 1-backlog/
│   ├── 2-sprint/
│   ├── 3-in-progress/
│   ├── 4-review/
│   └── 5-done/
└── memory/                  # Memory — accumulated knowledge
    ├── MEMORY.md
    └── cortex/

Options

Flag	Description
--name <name>	Project name (skip the prompt)
--tool <tools>	Single value or CSV: claude, cursor, codex, copilot, gemini, windsurf, none. Example: --tool claude,cursor,copilot
--all-tools	Scaffold bridges for every shipping adapter (claude, cursor, codex, copilot, gemini, windsurf)
--yes	Accept all prompts, use detected defaults
--force	Overwrite an existing .lytos/ directory
--dry-run	Print what would be created without touching the filesystem
--lang <en|fr>	Content language for generated markdown
--profile <vibe-coder|developer|lead>	Briefing profile printed after init

Migrating from legacy .cursorrules

Cursor’s older convention was a flat .cursorrules file at the project root. The modern layout (.cursor/rules/*.mdc with front-matter) is what lyt init --tool cursor ships today. If your project still carries the legacy file, run:

lyt upgrade --migrate-cursor

This moves your existing .cursorrules content into .cursor/rules/lytos.mdc, wrapping it with the modern front-matter. The original content is preserved — it is a format conversion, not a reset. See lyt upgrade for the full behavior.

For teams — enforcing the rule

Cursor’s Team Rules UI (Settings → Rules) has an “Enforce this rule” option that prevents team members from disabling or editing it locally. If your team needs a hard guarantee that every Cursor session loads .lytos/ — for compliance, audit, or onboarding — the person managing the Cursor workspace can mark the Lytos rule as enforced there. This is a Cursor setting, not something lyt init controls; the CLI writes a standard .mdc file that any of the four activation modes can be applied to.

Stack detection

lytos init automatically detects your tech stack by looking at:

• package.json → Node.js / TypeScript
• requirements.txt / pyproject.toml → Python
• go.mod → Go
• Cargo.toml → Rust

The detected stack is pre-filled in the manifest.

After init

Open your AI tool and say: “Help me configure Lytos for this project.”

The AI will read the manifest and help you fill in the project-specific details.