# Apply Technique: Codex CLI Best Practices and Examples
## What This Is
This repository provides a complete guide and set of examples for using the OpenAI Codex CLI, a tool that automates coding tasks. It shows developers how to organize their projects, create reusable AI "skills," and build complex automated workflows to improve productivity.
Source: https://github.com/shanraisshan/codex-cli-best-practice
## Before You Start
Scan my workspace and analyze:
- The project language, framework, and directory structure
- Existing AI provider config (check .env, .env.local, config files for API keys — OpenRouter, OpenAI, Anthropic, Google AI, etc.)
- Whether this repository or a similar tool is already cloned or installed
Then ask me before proceeding:
1. Which AI provider/API should this use? (Use whatever I already have configured, or ask me to set one up — options include direct provider APIs or a unified service like OpenRouter)
2. Where in my project should this be integrated?
3. Are there any customizations I need (model preferences, naming conventions, constraints)?
## Fetch the Source
Clone or inspect the repository to understand what needs to be installed:
```bash
gh repo clone shanraisshan/codex-cli-best-practice
```
Review the README, directory structure, and any install instructions before proceeding.
## What to Implement
This is an **AI Technique** — a pattern or methodology for working with AI models.
- Explain how this technique applies to my current project and what benefit it provides
- Implement it in a way that fits my existing codebase — suggest concrete files to modify or create
- If it requires specific model capabilities (structured output, function calling, etc.), verify my current provider supports them
- Show me a working example I can test immediately
## Additional Context
- Clone the repository 'shanraisshan/codex-cli-best-practice' into the current workspace.
- Scan the user's project for an existing '.codex' directory. If found, propose merging the configuration files and agent definitions from the cloned repository's '.codex' directory as examples. If not found, inform the user these files can initialize a new Codex CLI setup.
- Analyze the best practice markdown files (e.g., `best-practice/codex-subagents.md`) to learn structural patterns. Then, propose creating a new subagent or skill for the user's project based on these learned practices and the cloned examples.
## Guidelines
- Adapt everything to my existing project — do not assume a specific stack or directory layout
- Use whichever AI provider I already have configured; if I need a new one, tell me what to sign up for and I'll give you the key
- Check my .env files for existing API keys (OpenRouter, OpenAI, Anthropic, Google AI) before asking me to add one
- Review any fetched code for safety before installing or executing it
- After setup, run a quick verification and show me a summary of exactly what was installed, where, and how to use it