add git workflow docs, flatten skills, onboard neeraj
- flatten skill dirs (apes/critic → critic, apes/ax → ax) - add Git/Gitea section to CLAUDE.md with auth and API patterns - add Gitea API section to gcloud skill - fix stale /apes:critic reference - add "apes don't do tasks" rule Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
113
.claude/skills/ax/SKILL.md
Normal file
113
.claude/skills/ax/SKILL.md
Normal file
@@ -0,0 +1,113 @@
|
||||
---
|
||||
name: ax
|
||||
description: Audit agent-facing docs, hooks, skills, and config for the apes platform against AX principles. Use when agent behavior is wrong due to missing/unclear docs, poor ergonomics, or misconfigured automation.
|
||||
argument-hint: "[problem description]"
|
||||
disable-model-invocation: true
|
||||
---
|
||||
|
||||
# AX — Agent Experience Audit
|
||||
|
||||
Audit the apes project's Claude Code configuration — CLAUDE.md, hooks, skills, rules, permissions — against AX principles. For each finding, recommend the right mechanism to fix it.
|
||||
|
||||
## Arguments
|
||||
|
||||
- `$ARGUMENTS` — description of the AX problem (e.g., "agents keep deploying to wrong project"). If empty, run a general audit.
|
||||
|
||||
## Workflow
|
||||
|
||||
### Phase 1: AUDIT — Discover and score
|
||||
|
||||
#### 1a. Establish ground truth
|
||||
|
||||
Derive canonical workflows from:
|
||||
- `docker-compose.yml` files on VMs (SSH to check)
|
||||
- Any `Makefile`, `package.json`, `pyproject.toml` in repo
|
||||
- Deployment scripts, CI pipelines
|
||||
- GCP project config (`apes-platform`)
|
||||
|
||||
Ground truth is authoritative. If docs and automation disagree, fix docs.
|
||||
|
||||
#### 1b. Inventory agent-facing surfaces
|
||||
|
||||
Discover all Claude Code configuration:
|
||||
|
||||
**Documentation:** `CLAUDE.md`, `.claude/rules/*.md`, `README.md`
|
||||
**Automation:** `.claude/settings.json`, hooks
|
||||
**Skills:** `.claude/skills/*/SKILL.md`
|
||||
**Commands:** `.claude/commands/*.md`
|
||||
**Agents:** `.claude/agents/*.md`
|
||||
**Memory:** `~/.claude/projects/*/memory/MEMORY.md`
|
||||
|
||||
If `$ARGUMENTS` is provided, focus on relevant surfaces.
|
||||
|
||||
#### 1c. Score against AX principles
|
||||
|
||||
| # | Principle | FAIL when... |
|
||||
|---|-----------|--------------|
|
||||
| 1 | Explicitness over convention | A non-standard workflow isn't called out explicitly |
|
||||
| 2 | Fail fast with clear recovery | Errors lack concrete fix commands |
|
||||
| 3 | Minimize context rot | CLAUDE.md adds tokens that don't earn their keep |
|
||||
| 4 | Structured over unstructured | Important info buried in prose instead of tables/code blocks |
|
||||
| 5 | Consistent patterns | Naming or formatting conventions shift across docs |
|
||||
| 6 | Complete context at point of need | Critical commands missing where they're needed |
|
||||
| 7 | Guard rails over documentation | Says "don't do X" but X would succeed — a hook or permission would be better |
|
||||
| 8 | Single source of truth | Same info maintained in multiple places, or docs diverge from reality |
|
||||
|
||||
**Apes-specific checks:**
|
||||
- GCP project/region/zone correct everywhere?
|
||||
- Docker Compose configs on VMs match what docs describe?
|
||||
- DNS records match what's deployed?
|
||||
- No SaaS dependencies crept in?
|
||||
|
||||
### Phase 2: PROPOSE — Select mechanism and draft fixes
|
||||
|
||||
For each WARN or FAIL, select the right Claude Code mechanism:
|
||||
|
||||
| If the finding is... | Use this mechanism |
|
||||
|---|---|
|
||||
| Block forbidden actions | **PreToolUse hook** |
|
||||
| Dangerous command that should never run | **Permission deny rule** |
|
||||
| Auto-format/lint/test after edits | **PostToolUse hook** |
|
||||
| File-type-specific convention | **`.claude/rules/*.md`** with `paths` frontmatter |
|
||||
| Repeatable workflow or reference | **Skill** |
|
||||
| Complex task needing isolation | **Subagent** |
|
||||
| Critical context surviving compaction | **CLAUDE.md** |
|
||||
| Universal project convention | **CLAUDE.md** (keep <200 lines) |
|
||||
|
||||
Each fix must include:
|
||||
- Which principle it addresses
|
||||
- The selected mechanism and why
|
||||
- Exact implementation (file path + content)
|
||||
|
||||
### Phase 3: REPORT
|
||||
|
||||
```
|
||||
# AX Audit Report — apes
|
||||
|
||||
**Surfaces audited:** <count>
|
||||
|
||||
## Scorecard
|
||||
|
||||
| # | Principle | Rating | Detail |
|
||||
|---|-----------|--------|--------|
|
||||
| 1-8 | ... | PASS/WARN/FAIL | ... |
|
||||
|
||||
## Findings
|
||||
|
||||
| Surface | Issues | Recommended mechanism |
|
||||
|---------|--------|----------------------|
|
||||
| ... | ... | ... |
|
||||
|
||||
## Recommendations
|
||||
|
||||
For each:
|
||||
- Principle addressed
|
||||
- Mechanism type
|
||||
- Exact implementation (file + content)
|
||||
```
|
||||
|
||||
## Constraints
|
||||
|
||||
- This skill is **read-only** — it never modifies files, only reports
|
||||
- Apes-specific: verify no SaaS dependencies in recommendations
|
||||
- Verify GCP infra state via SSH before reporting on deployed services
|
||||
Reference in New Issue
Block a user