How do I install the Project Init skill?

Run npx skillmds@latest add claude-world-director-mode-lite/project-init in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Init safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Init?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Init free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Init?

claude-world (@claude-world-director-mode-lite) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Init by claude-world-director-mode-lite

Name: Project Init
Rating: 4.2 (5 reviews)
Author: claude-world

File contents

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.

---name: project-initdescription: 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.---# Project initializationCreate 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 contextKeep permanent guidance focused on facts useful in most sessions:```markdown# 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 threeCLIs can find `.director-mode/GUIDANCE.md`. Put detailed, conditional proceduresin skills rather than expanding the permanent files.## 3. Verify native assetsCheck the selected CLI surfaces:```textClaude: .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 optionaltool merely to declare setup complete.## 4. Optional integrationsMCP servers, hooks, TDD, autonomous loops, and extra agents are choices, notdefaults. Suggest one only when it materially helps the current repository andexplain its effect. Install or register it only after the user requests it.In particular, never register a Stop hook, deny rule, validator, securityguard, or background tracker as part of ordinary project initialization.## 5. Report the resultSummarize 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.

Frequently asked questions

Project Init