dirigence/reliquary
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

📝 Update UV detection goals and workpad SKILL docs

Browse Source
This commit is contained in:
Gabor Körber
2026-05-19 18:45:57 +02:00
parent e562b53cc3
commit 840e79fde4
2 changed files with 31 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/g4b_ai/skills/workpad/SKILL.md
+7 -7
View File
@@ -1,6 +1,6 @@
---
name: workpad
description: Decides WHERE and WHEN to put working documents — reports, plans, goals, brainstorms, designs, journals, research, specs, tickets, bug notes. Use this skill whenever the user asks you to write a "report", "plan", "goal", "brainstorm", "design", "journal", "research note", "spec", or anything "in the workpad" — and also when another skill is about to drop a markdown file somewhere ad-hoc (e.g. a `superpowers/` subdirectory, the repo root, `/tmp`, or alongside source code). If a workpad exists, the workpad wins. This skill steers other skills toward a single, predictable place for thinking-in-markdown so the user can always find what was written and when.
description: Decides WHERE and WHEN to put working documents — reports, plans, goals, brainstorms, designs, journals, research, specs, tickets, bug notes. Use this skill whenever the user asks you to write a "report", "plan", "goal", "brainstorm", "design", "journal", "research note", "spec", or anything "in the workpad" — and also when another skill is about to drop a markdown file somewhere ad-hoc (e.g. a `superpowers/` subdirectory, the repo root, `/tmp`, or alongside source code). If a workpad exists, the workpad wins. This skill steers other skills toward a single, predictable place for markdown documents. Can be used together with any superpowers.
---
# Workpad
@@ -14,14 +14,14 @@ Treat this skill as authoritative for placement. If another skill suggests writi
Resolve the workpad base directory in this order — stop at the first hit:
1. **Explicit user instruction in the current conversation.** If they said "put it in `~/notes/foo`", that wins.
2. **`WORKPAD_FOLDER` environment variable.** Reading it reliably is fiddly because Claude Code runs commands in subshells that may not inherit the user's interactive env, and the value may live in a project-local `.env` file rather than the actual environment. Try, in order:
- `uv run --quiet --with python-dotenv python -c "from dotenv import load_dotenv; import os; load_dotenv(); print(os.environ.get('WORKPAD_FOLDER',''))"` if `uv` is available. This loads `.env` from the current working directory before reading the variable, which catches the common case where `WORKPAD_FOLDER` is set per-project in a `.env`.
- `just workpad-folder` (or any equivalent recipe) if a `.justfile` / `justfile` is present and defines one — `just` loads `.env` automatically.
- `printenv WORKPAD_FOLDER` as a last resort. This will only see values exported into the actual process environment, not values in `.env` files.
2. **`WORKPAD_FOLDER` environment variable.** Reading it reliably is fiddly because Agents run commands in subshells that may not inherit the user's interactive env, and the value may be injected on purpose not available to the agent:
- `just workpad-folder` (or any equivalent recipe) if a `.justfile` / `Justfile` is present and defines one — `just` loads `.env` automatically.
- `printenv WORKPAD_FOLDER` as a last resort. This will only see values exported into the actual process environment.
If any of these prints a non-empty path, treat it as the workpad base.
3. **Project-local ticket folder.** Some projects keep a sibling folder *outside* the main repo for per-ticket scratch (e.g. `../<repo>-tickets/` or a path the user has mentioned before). If such a folder is configured for this project, prefer placing the workpad inside it (e.g. `<ticket-folder>/workpad/`). When in doubt whether one exists, ask.
4. **`/docs/workpad`** at the project root, if a `/docs` folder already exists.
5. **Otherwise: ask.** If there is no `/docs` folder and no other signal, do not silently create `/docs/workpad/`. Ask the user where the workpad should live, and confirm before creating any folders.
5. **`/.workpad`** at the project root.
6. **Otherwise: ask.** If there is no `/docs` folder and no other signal, do not silently create `/docs/workpad/`. Ask the user where the workpad should live, and confirm before creating any folders.
## Folder structure
@@ -42,7 +42,7 @@ It may also contain any of these, created on demand:
- `specs/` — frozen, unchanging specifications
- `tickets/` — per-ticket scratch space
If one of these optional folders is needed and doesn't exist yet, create it. Don't create folders speculatively.
If one of these optional folders is needed and doesn't exist yet, create it. Don't create folders speculatively. Treat unknown folders as owned by the user and ignore them.
## File naming