Skip to content

Commit fcd296c

Browse files
committed
docs(web): restore skills detail copy
1 parent fee5eeb commit fcd296c

2 files changed

Lines changed: 92 additions & 2 deletions

File tree

packages/web/content/docs/skills.md

Lines changed: 66 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,33 @@ The command pillars stay simple:
1313

1414
Skills add specialist judgment around those pillars. The sections below describe each skill and how it is typically used.
1515

16+
### Skill index
17+
18+
Most skills auto-activate when a request matches their domain, so you do not need to study or manually select every skill before using LazyCodex. When you want to be explicit, put the skill name in the prompt — for example `$visual-qa`, `$git-master`, or `$ulw-research`.
19+
20+
| Skill | Use it for |
21+
| --- | --- |
22+
| `init-deep` | Hierarchical `AGENTS.md` context for large or old repos |
23+
| `ulw-plan` | Explore-first planning before coding |
24+
| `ulw-loop` | Evidence-bound loop until verified completion |
25+
| `start-work` | Execute a plan with durable Boulder progress |
26+
| `review-work` | Five-lane parallel post-implementation review |
27+
| `remove-ai-slops` | Behavior-preserving cleanup of AI-looking code |
28+
| `frontend` | Designed UI work instead of generic layout filling |
29+
| `programming` | Strict TypeScript, Rust, Python, or Go discipline, TDD-first |
30+
| `git-master` | Atomic commits, rebase/squash, push safety, history investigation |
31+
| `visual-qa` | Screenshot/TUI diff plus dual-oracle visual QA |
32+
| `debugging` | Evidence-led root-cause investigation |
33+
| `refactor` | Behavior-preserving restructure of existing code |
34+
| `ulw-research` | Maximum-saturation research with codebase, web, official-docs, and OSS-repo swarms |
35+
| `LSP` | Diagnostics, definitions, references, symbols, and renames |
36+
| `lsp-setup` | Configure language servers for a project |
37+
| `AST-grep` | Structural search and rewrite across code |
38+
| `rules` | Project instructions from AGENTS, rules, and instruction files |
39+
| `comment-checker` | Feedback after edit-like operations |
40+
41+
### Skill highlights
42+
1643
---
1744

1845
### review-work
@@ -176,9 +203,47 @@ Finds code by syntactic shape rather than text — every function call matching
176203

177204
---
178205

206+
### lsp-setup
207+
208+
Language-server installation and workspace wiring.
209+
210+
Configures language servers when a project does not already expose reliable diagnostics, definitions, references, and safe renames. It detects the language stack, installs or points to the right server, and validates that LSP calls work before higher-level coding or refactor skills depend on them.
211+
212+
**When it activates:** When diagnostics are missing, definitions cannot be resolved, or a project needs LSP support before a refactor or programming task.
213+
214+
---
215+
216+
### rules
217+
218+
Project instruction injection from repository and user rule files.
219+
220+
Automatically loads project instructions from sources such as `AGENTS.md`, `CONTEXT.md`, `.omo/rules/`, `.claude/rules/`, `.github/instructions/`, and `.github/copilot-instructions.md`. There is no command to run — the harness treats these rules as active context when the plugin is enabled.
221+
222+
**When it activates:** At session start and prompt submission, so agents inherit project constraints before planning or editing.
223+
224+
---
225+
226+
### comment-checker
227+
228+
Immediate feedback after edit-like operations.
229+
230+
After code changes, `comment-checker` inspects comments near the edited lines. If it flags comment drift — a comment that no longer matches the code below it — the agent must fix or justify the comment before proceeding. This catches stale comments at the moment they are introduced rather than during a later review.
231+
232+
**When it activates:** After write, edit, patch, or other edit-like tool calls when the plugin has the guardrail enabled.
233+
234+
---
235+
179236
### Where skills live
180237

181-
LazyCodex installs skills as part of the OmO plugin. OmO can also load skills from project and user locations such as `.codex/skills`, `~/.codex/skills`, `.agents/skills`, and `~/.agents/skills`.
238+
LazyCodex installs skills as part of the OmO plugin. OmO can also load skills from project and user locations such as `.codex/skills`, `~/.codex/skills`, `.opencode/skills`, `~/.config/opencode/skills`, `.claude/skills`, `.agents/skills`, and `~/.agents/skills`.
239+
240+
LazyCodex installs the Codex Light setup with:
241+
242+
```bash
243+
npx lazycodex-ai install
244+
```
245+
246+
That installer wires the Codex marketplace plugin as `omo@sisyphuslabs` while keeping the public package alias easy to remember.
182247

183248
Each skill carries deep internal references — detailed playbooks, language-specific recipes, and per-phase instructions — but none of that is something you need to read. The harness reads it for you when the skill activates.
184249

0 commit comments

Comments
 (0)