eaebf3e101
Add visible FAQ and concepts content, strengthen tool-specific integration guides, and publish a dedicated skills-vs-MCP explainer. Extend homepage SEO metadata and JSON-LD so the GitHub Pages catalog better reflects the repository's real positioning and common user questions.
61 lines
2.5 KiB
Markdown
61 lines
2.5 KiB
Markdown
# Codex CLI Skills
|
|
|
|
If you want **Codex CLI skills** that are easy to install and practical in a local coding loop, this repository is designed for that exact use case.
|
|
|
|
Antigravity Awesome Skills supports Codex CLI through the `.codex/skills/` path and gives you a wide set of reusable task playbooks for planning, implementation, debugging, testing, security review, and delivery.
|
|
|
|
## How to use Antigravity Awesome Skills with Codex CLI
|
|
|
|
Install the library into your Codex path, then invoke focused skills directly in your prompt. The most common pattern is:
|
|
|
|
1. install with `npx antigravity-awesome-skills --codex`
|
|
2. choose one workflow-oriented skill such as `@brainstorming`, `@concise-planning`, or `@test-driven-development`
|
|
3. ask Codex to apply that skill to a concrete file, feature, test, or bugfix
|
|
|
|
## Why use this repo for Codex CLI
|
|
|
|
- It supports Codex CLI with a dedicated install flag and a standard skills layout.
|
|
- It is strong for local repo work where you want to move from planning to implementation to verification without changing libraries.
|
|
- It includes both general-purpose engineering skills and deeper specialist tracks.
|
|
- It gives you docs and bundles, not just raw skill files.
|
|
|
|
## Install Codex CLI Skills
|
|
|
|
```bash
|
|
npx antigravity-awesome-skills --codex
|
|
```
|
|
|
|
### Verify the install
|
|
|
|
```bash
|
|
test -d .codex/skills || test -d ~/.codex/skills
|
|
```
|
|
|
|
## Best starter skills for Codex CLI
|
|
|
|
- [`brainstorming`](../../skills/brainstorming/): clarify requirements before touching code.
|
|
- [`concise-planning`](../../skills/concise-planning/): turn ambiguous work into an atomic execution plan.
|
|
- [`test-driven-development`](../../skills/test-driven-development/): structure changes around red-green-refactor.
|
|
- [`lint-and-validate`](../../skills/lint-and-validate/): keep quality checks close to the implementation loop.
|
|
- [`create-pr`](../../skills/create-pr/): wrap up work cleanly once implementation is done.
|
|
|
|
## Example Codex CLI prompts
|
|
|
|
```text
|
|
Use @concise-planning to break this feature request into an implementation checklist.
|
|
```
|
|
|
|
```text
|
|
Use @test-driven-development to add tests before changing this parser.
|
|
```
|
|
|
|
```text
|
|
Use @create-pr once everything is passing and summarize the user-facing changes.
|
|
```
|
|
|
|
## What to do next
|
|
|
|
- Read [`ai-agent-skills.md`](ai-agent-skills.md) if you want a framework for choosing between broad and curated skill libraries.
|
|
- Use [`workflows.md`](workflows.md) when you want step-by-step execution patterns for common engineering goals.
|
|
- Return to [`README.md`](../../README.md) for the full compatibility matrix.
|