chore(skills): rename all skills to domain-action convention

Adopts the whatsinagame naming pattern where the domain comes
first and the action second (e.g. pr-review, sprint-start,
audio-gen). Updated all cross-references in settings, agents,
docs, and inter-skill references.

12 renames: commit→git-commit, create-skill→skill-create,
gen-audio→audio-gen, gen-image→image-gen, plan-sprint→sprint-plan,
push-pr→pr-push, render-sprite→sprite-gen, review-pr→pr-review,
search-docs→docs-search, start-sprint→sprint-start,
start-workshop→workshop-start.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-19 12:51:56 +01:00
co-authored by Claude Opus 4.6
parent 324caab244
commit f0bab3999d
28 changed files with 43 additions and 43 deletions
+1 -1
View File
@@ -114,7 +114,7 @@ Synthesize findings.
### Qatux (Documenter & Librarian)
- Core team member — participates in discussion rounds as documenter
- Manages document search via `/search-docs` skill
- Manages document search via `/docs-search` skill
- Maintains DECISIONS.md, DISCUSSION.md, briefings, and Qdrant search index
- Answers "did we discuss this?" with citations
+1 -1
View File
@@ -28,7 +28,7 @@ Named after Qatux, the Raiel with perfect memory who helped Paula Myo by recalli
- Provide "state of the project" summaries when asked
### Knowledge management
- Maintain the Qdrant document index via /search-docs skill
- Maintain the Qdrant document index via /docs-search skill
- Update briefing files when decisions change
- Answer retrieval questions: "did we discuss X?", "what did we decide about Y?"
- Catch staleness in briefings and flag for update
+2 -2
View File
@@ -52,9 +52,9 @@
"Bash(tree *)",
"Bash(sed -n *)",
"Skill(commit)",
"Skill(git-commit)",
"Skill(worktree-update)",
"Skill(start-sprint)"
"Skill(sprint-start)"
],
"deny": [
"Bash(git push --force *)",
@@ -1,5 +1,5 @@
---
name: gen-audio
name: audio-gen
description: >
Generate audio assets for The Settled Reach using the Stable Audio Open API
(self-hosted Gradio app at tower-of-joy:11500). Use when generating any game
@@ -1,9 +1,9 @@
---
name: search-docs
name: docs-search
description: >
Search project documents using semantic search (Qdrant + ollama) or grep fallback.
Use when the user asks "did we discuss X?", "find references to Y", "search docs",
or invokes /search-docs. Wraps the qdrant_connector.py for semantic document search.
or invokes /docs-search. Wraps the qdrant_connector.py for semantic document search.
user-invocable: true
allowed-tools: Bash, Read, Grep, Glob
---
@@ -1,8 +1,8 @@
---
name: commit
name: git-commit
description: >
Commit changes with clean, structured messages. Use when the user says
"commit", "save my work", "commit changes", or invokes /commit. Enforces
"commit", "save my work", "commit changes", or invokes /git-commit. Enforces
conventional commit format, groups changes into logical commits, and maintains
CHANGELOG.md. Never squash unrelated changes into one commit.
user-invocable: true
@@ -1,5 +1,5 @@
---
name: gen-image
name: image-gen
description: >
Generate themed visual assets for the Lords of Ash CK3 total conversion mod
using the generate_image MCP tool (Nano Banana / Gemini 2.5 Flash Image).
@@ -1,9 +1,9 @@
---
name: push-pr
name: pr-push
description: >
Push commits and create or update a pull request. Use when the user says
"push pr", "push and create pr", "update pr", "create a pr", "open a pr",
or invokes /push-pr. NOT triggered by plain "push" (that's just git push).
or invokes /pr-push. NOT triggered by plain "push" (that's just git push).
Pushes the current branch, creates a PR if none exists, or confirms the
existing PR was updated. NEVER merges the PR into main — this skill only
pushes to the branch and manages the PR lifecycle.
@@ -41,7 +41,7 @@ git status
```
If there are uncommitted changes (staged or unstaged), run the **commit skill**
first. Use the `/commit` skill to group changes into logical commits with
first. Use the `/git-commit` skill to group changes into logical commits with
proper conventional commit messages. Wait for commit to complete before
proceeding.
@@ -136,5 +136,5 @@ already `done`, `review`, `cancelled`, or `backlog` (only transition
## Arguments
If the user passes arguments (e.g., `/push-pr "my title"`), use them as the
If the user passes arguments (e.g., `/pr-push "my title"`), use them as the
PR title instead of generating one.
@@ -1,9 +1,9 @@
---
name: review-pr
name: pr-review
description: >
Review a branch diff with team-appropriate agents before merge. Use when the
user says "review-pr", "review this PR", "review this branch", or invokes
/review-pr. Spawns reviewers matched to the branch type (code, copy, visual,
/pr-review. Spawns reviewers matched to the branch type (code, copy, visual,
audio) in parallel. Reports approve/reject with inline comments.
user-invocable: true
allowed-tools: Bash, Read, Grep, Glob, Task
@@ -1,5 +1,5 @@
---
name: create-skill
name: skill-create
description: >
Guidance for creating effective Claude Code skills (.skill packages).
Use when the user wants to create, build, design, or iterate on a skill —
@@ -1,9 +1,9 @@
---
name: plan-sprint
name: sprint-plan
description: >
Plan the next sprint and generate team briefing files. Use when the user says
"plan sprint", "prep sprint briefing", "plan next sprint", "sprint planning",
or invokes /plan-sprint. Gathers current sprint status, scans the backlog,
or invokes /sprint-plan. Gathers current sprint status, scans the backlog,
proposes ticket selection, and writes briefing files per team to
docs/sprints/sprint-N/.
user-invocable: true
@@ -19,8 +19,8 @@ When this skill is invoked, spawn SI using the Task tool:
```
Task(
subagent_type: "si",
prompt: "Run /plan-sprint for Sprint N. Read the skill at
.claude/skills/plan-sprint/SKILL.md for the full workflow,
prompt: "Run /sprint-plan for Sprint N. Read the skill at
.claude/skills/sprint-plan/SKILL.md for the full workflow,
then execute it. Use the arguments provided: {args}",
description: "Plan sprint N"
)
@@ -1,9 +1,9 @@
---
name: start-sprint
name: sprint-start
description: >
Manage the sprint lifecycle from main, or start sprint work on a team
branch. Use when the user says "start sprint", "start working on the
server/client/copy", "begin sprint", or invokes /start-sprint. On main:
server/client/copy", "begin sprint", or invokes /sprint-start. On main:
assesses sprint state and does the next right thing (close, activate, or
guide). On a team branch: merges main, loads the briefing, presents the
work plan.
@@ -34,7 +34,7 @@ the team branch workflow (steps 28).
## Main branch workflow (sprint lifecycle management)
When `/start-sprint` is run on `main`, assess the current sprint state
When `/sprint-start` is run on `main`, assess the current sprint state
and do the next right thing. Query the database to determine the state:
```bash
@@ -97,7 +97,7 @@ git push && git push --tags
After closing, re-query the database. If a sprint in `planning` status
exists, continue to **Case B**. Otherwise, report the close and suggest
running `/plan-sprint`.
running `/sprint-plan`.
---
@@ -115,7 +115,7 @@ A sprint is ready to activate. Verify it looks complete:
```
If briefings are missing or the sprint has 0 tickets, report the gap
and suggest running `/plan-sprint` to complete planning.
and suggest running `/sprint-plan` to complete planning.
If everything looks ready, activate the sprint:
@@ -125,14 +125,14 @@ db/connectors/sprint start
Then report:
- Sprint activated (name, ticket count per team)
- Remind the user to switch to a team branch and run `/start-sprint`
- Remind the user to switch to a team branch and run `/sprint-start`
there (or `cd` into the relevant worktree)
---
### Case C: No active sprint and no planned sprint
Nothing is ready. Report the state and suggest running `/plan-sprint`
Nothing is ready. Report the state and suggest running `/sprint-plan`
to plan the next sprint.
---
@@ -167,7 +167,7 @@ If no active sprint is found, report that and stop.
Read the briefing file(s) listed in the `start-work` output
(e.g. `docs/sprints/sprint-6/server.md` and `joint.md`).
If no matching briefing exists for the team, suggest running
`/plan-sprint` to generate one.
`/sprint-plan` to generate one.
### 5. Load ticket details
@@ -1,11 +1,11 @@
---
name: render-sprite
name: sprite-gen
description: >
Render a 3D model to 2D sprites via the Godot render pipeline. Produces
sprites at 3 resolutions (1024, 256, 64) from 4 cardinal directions (north,
east, south, west) with outline applied at working resolution. Use when the
user says "render sprite", "render model", "run the render pipeline",
"test the pipeline", "/render-sprite", or asks to render a specific model
"test the pipeline", "/sprite-gen", or asks to render a specific model
(e.g., "render wall_structural"). Output: 12 PNG files in renderer/output/.
---
@@ -14,7 +14,7 @@ description: >
Run the render script with the model name:
```bash
.claude/skills/render-sprite/scripts/render.sh <model_name>
.claude/skills/sprite-gen/scripts/render.sh <model_name>
```
### Available Models
@@ -52,4 +52,4 @@ ls renderer/models/*.tscn | xargs -I{} basename {} .tscn
1. Create model scene at `renderer/models/<name>.tscn`
2. Apply texture from `renderer/textures/` via StandardMaterial3D
3. Run: `.claude/skills/render-sprite/scripts/render.sh <name>`
3. Run: `.claude/skills/sprite-gen/scripts/render.sh <name>`
@@ -1,8 +1,8 @@
---
name: start-workshop
name: workshop-start
description: >
Start a multi-agent design workshop from a workshop brief. Use when the user says
"start workshop", "run workshop", "let's start the workshop", or invokes /start-workshop.
"start workshop", "run workshop", "let's start the workshop", or invokes /workshop-start.
Parses the workshop brief to extract participants, questions, and round format.
Creates a team, tasks, and spawns agents as teammates via the Task tool.
---
+1 -1
View File
@@ -73,7 +73,7 @@ Cross-reference open PR head branches with the ahead-of-main branches.
Show a summary table of branches ahead of main. For each branch, indicate:
- `[PR]` if it has an open pull request — warn that it should go through
normal review channels (use `/review-pr` instead)
normal review channels (use `/pr-review` instead)
- Commit count and summary
Use `AskUserQuestion` to let the user pick which branches to merge.
+1 -1
View File
@@ -281,7 +281,7 @@ The sync runs automatically as part of `make setup` and via pre-commit hook. Mar
## Commit Conventions
See the `/commit` skill (`.claude/skills/commit/`) for full details. Summary:
See the `/git-commit` skill (`.claude/skills/git-commit/`) for full details. Summary:
- Conventional commits: `type(scope): summary`
- Types: `feat`, `fix`, `refactor`, `chore`, `docs`, `data`, `loc`
+1 -1
View File
@@ -19,7 +19,7 @@ See [palette.md](palette.md) for art direction, "the angle", color relationships
## Pipeline
- **3D render pipeline:** Blender model → Godot Camera3D at -72.5deg → orthographic render → outline pass → resolution downscale
- **Render skill:** `/render-sprite` produces 12 PNGs (4 directions x 3 resolutions)
- **Render skill:** `/sprite-gen` produces 12 PNGs (4 directions x 3 resolutions)
- **Art direction workshop:** `docs/workshops/art-direction-mood-board/`
## Decision References
@@ -575,7 +575,7 @@ The following workshop outputs are ready for formal recording in `decisions/` do
| Velen orbit logistics | Open | Miri | If Sova orbits Velen, freight access to surface needs intra-system wormhole or shuttle service. Flag for next worldbuilding session. |
| 3D render pipeline for 2D sprites | **Resolved** | Tyre, Araminta, Stig | See §10. 3D used only as offline render pipeline — runtime is pure 2D. SubViewport + Camera3D at "the angle" + DirectionalLight3D (neutral). Nano Banana textures UV-mapped onto 3D models, rendered from 4 cardinal directions. |
| Resolution chain | **Resolved** | Tyre, Araminta | 1024x1024 source (archive master) → 256x256 (working, outlines applied at 4-8px) → 64x64 (runtime). Bilinear interpolation both passes. |
| Pipeline test: Era 1 wall texture | **In progress** | Stig, Araminta | Nano Banana texture generated, QA'd (color PASS, flat lighting PASS, tileability PARTIAL — top/bottom seam, acceptable because tiling happens at 3D geometry level). Godot render scene built at `client/tooling/sprite_renderer/`. Render skill created at `.claude/skills/render-sprite/`. Blocked on Godot texture import — needs editor opened once to import the PNG. |
| Pipeline test: Era 1 wall texture | **In progress** | Stig, Araminta | Nano Banana texture generated, QA'd (color PASS, flat lighting PASS, tileability PARTIAL — top/bottom seam, acceptable because tiling happens at 3D geometry level). Godot render scene built at `client/tooling/sprite_renderer/`. Render skill created at `.claude/skills/sprite-gen/`. Blocked on Godot texture import — needs editor opened once to import the PNG. |
| Camera angle: exact value | **Locked** | Lead | "The angle" = ~15-20° from vertical. Rimworld uses orthographic camera with tilt entirely in sprite art. Research confirms no camera projection — the 3D render pipeline Camera3D rotation of -72.5° (from horizontal) produces this. Midpoint of range, tunable by Araminta. |
---
@@ -654,7 +654,7 @@ void fragment() {
| Tileability (3x3 no seams) | **PARTIAL** — Left/right seamless, top/bottom seam visible |
| 64x64 reads as "wall" | **PASS** — Color preserved, reads as surface |
**Render pipeline tooling** built by Stig at `client/tooling/sprite_renderer/`. CLI skill at `.claude/skills/render-sprite/`. First test run blocked on Godot texture import (needs editor opened once to import the PNG into `.godot/imported/`).
**Render pipeline tooling** built by Stig at `client/tooling/sprite_renderer/`. CLI skill at `.claude/skills/sprite-gen/`. First test run blocked on Godot texture import (needs editor opened once to import the PNG into `.godot/imported/`).
**Next step:** Open Godot editor to trigger import, then run render pipeline.
@@ -274,7 +274,7 @@ Safe to create PR.
- Does not run Layer 3 subprocess tests (too slow, nightly-tier)
- Does not run performance benchmarks (machine-dependent, separate target)
- Does not run Gauntlet golden file tests (depends on Gauntlet implementation)
- Does not push or create the PR (that's `make push-pr` or the `/push-pr` skill)
- Does not push or create the PR (that's `make pr-push` or the `/pr-push` skill)
These are separate targets for developers who want deeper verification:
+2 -2
View File
@@ -41,9 +41,9 @@
"Bash(chmod *)",
"Bash(ls *)",
"Skill(commit)",
"Skill(git-commit)",
"Skill(worktree-update)",
"Skill(start-sprint)"
"Skill(sprint-start)"
],
"deny": [
"Bash(git push --force *)",