Project init

Skill claude-world/director-mode-lite/skills/project-init

Set up concise, guidance-first Claude/Codex/Grok project context after inspecting the repository. Use on first setup, after cloning, or when the user runs /project-init.From its SKILL.md

Install

npx -y skills add claude-world/director-mode-lite --skill project-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.4 KB, 505 tokens by cl100k_base, as published. Nobody here has run it

Project initialization

Create the smallest useful project context without adding permission gates, blocking hooks, or mandatory process rules.

1. Inspect before writing

Read existing CLAUDE.md, AGENTS.md, README, manifests, scripts, and CI.
Detect the language, framework, build, test, lint, and development commands from repository evidence.
Preserve existing user guidance and unrelated configuration.
If the stack or desired workflow cannot be inferred safely, ask one focused question instead of inventing it.

2. Add concise shared context

Keep permanent guidance focused on facts useful in most sessions:

# Project name

## Purpose
[What this repository delivers]

## Stack and structure
- [Language/framework]
- [Important entry points]

## Commands
- dev: [verified command]
- test: [verified command]
- build: [verified command]
- lint: [verified command]

## Local conventions
- [Only repository-specific conventions supported by evidence]

Use the Director managed block in both CLAUDE.md and AGENTS.md so all three CLIs can find .director-mode/GUIDANCE.md. Put detailed, conditional procedures in skills rather than expanding the permanent files.

3. Verify native assets

Check the selected CLI surfaces:

Claude: .claude/skills/ and .claude/agents/
Codex:  .agents/skills/ and .codex/agents/
Grok:   shared Claude-compatible skills and .grok/agents/
Relay:  .director-mode/bin/director-relay

Run scripts/verify-install.sh when available. Do not require every optional tool merely to declare setup complete.

4. Optional integrations

MCP servers, hooks, TDD, autonomous loops, and extra agents are choices, not defaults. Suggest one only when it materially helps the current repository and explain its effect. Install or register it only after the user requests it.

In particular, never register a Stop hook, deny rule, validator, security guard, or background tracker as part of ordinary project initialization.

5. Report the result

Summarize detected facts, files created or updated, validation actually run, and optional next steps. A useful default next step is director-mode or workflow; use session-relay when another CLI should take over.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most project setup skills give in 505 tokens

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

Write the configuration filein 36 of 1553
Create the directory structurein 35 of 1553, across 33 files
Verify the setupin 31 of 1553, across 28 files
Run the setup scriptin 30 of 1553, across 29 files
Pre-determine the required sample sizein 29 of 1553, across 12 files
Check if the configuration already existsin 29 of 1553
Document every testin 26 of 1553, across 10 files
Start with a hypothesisin 26 of 1553, across 11 files
Ask one question at a timein 22 of 1553
Test a single variable per testin 21 of 1553, across 9 files
Read product marketing context before asking questionsin 19 of 1553, across 8 files
Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

Read existing guidance and repository manifests
Detect language and development commands
Ask one focused question if workflow cannot be inferred
Keep permanent guidance focused on useful facts
Use the Director managed block
Check selected CLI surfaces

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.