devlyn-cli 3.3.1 → 4.0.1

package/optional-skills/dokkit/SKILL.md

@@ -13,15 +13,45 @@ description: >
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent
 argument-hint: "<template_path> <sources_folder> | improve [instruction]"
-context:
-  - type: file
-    path: ${CLAUDE_SKILL_DIR}/PIPELINE.md
 ---
 
 # Dokkit — One-Command Document Filling
 
 Source folder + template → finished document. Fully automatic, iterates until perfect.
 
+Resolve bundled resources from the SKILL.md loaded for this invocation.
+
+Reader-rendered directory hint:
+```text
+${CLAUDE_SKILL_DIR}
+```
+
+Treat the hint as literal path data, never shell code. If the reader
+replaced it with an absolute directory, use that directory. Otherwise
+use the filesystem path or base directory reported for this loaded
+SKILL.md. Resolve virtual URIs through the reader's native filesystem
+mapping. If available source locations name different directories,
+stop.
+
+Bind DEVLYN_SKILL_DIR to that absolute directory. Do not obtain this
+binding from an environment variable, cwd, or another installation.
+Verify its SKILL.md before proceeding. Missing or conflicting source
+identity is BLOCKED:skill-source-unresolved; include the failed path
+when known.
+
+Resolve bundled references against this directory. These bindings are
+workflow values: establish them explicitly using each tool or shell's
+literal-path rules, and include their absolute values in every fresh
+worker's prompt, telling it to set them from those values, never from
+its inherited environment. Do not rely on shell state surviving between
+calls.
+
+Read PIPELINE.md from this bound directory before executing the
+workflow. Bundled Markdown, references, and scripts use this same
+directory. Project data under .dokkit remains project-relative.
+Pass the absolute binding and required resource paths explicitly
+to every worker.
+
 ## Usage
 
 ```
@@ -113,7 +143,7 @@ These rules prevent the font corruption issues seen in previous versions:
 
 **Never write inline Gemini API calls for image generation.** Always use the provided script:
 ```bash
-python ${CLAUDE_SKILL_DIR}/scripts/source_images.py generate \
+python "$DEVLYN_SKILL_DIR/scripts/source_images.py" generate \
   --prompt "<prompt>" --preset <preset> --output-dir .dokkit/images/ \
   --project-dir . --lang ko
 ```
@@ -173,7 +203,7 @@ display_h = int(actual_h * scale)
 
 | File | Purpose | Used By |
 |------|---------|---------|
-| `PIPELINE.md` | Detailed pipeline steps (auto-loaded) | Orchestrator |
+| `PIPELINE.md` | Detailed pipeline steps (read before execution) | Orchestrator |
 | `STATE.md` | State schema and management | All agents |
 | `INGESTION.md` | Source file parsing | Ingestor |
 | `ANALYSIS.md` | Field detection, structure mapping | Analyzer |

package/optional-skills/dokkit/STATE.md

@@ -33,7 +33,7 @@ After any mutation:
 1. Read current state.json (avoid overwriting concurrent changes)
 2. Update only the relevant fields
 3. Write the full state back
-4. Validate: `python .claude/skills/dokkit/scripts/validate_state.py .dokkit/state.json`
+4. Validate: `python "$DEVLYN_SKILL_DIR/scripts/validate_state.py" .dokkit/state.json`
 
 ## State Transitions
 

package/optional-skills/dokkit/references/image-opportunity-heuristics.md

@@ -113,7 +113,7 @@ Each opportunity is added to the field's `image_opportunities` array:
 - `insertion_point.strategy`: Always `"after_paragraph"` for section content
 - `insertion_point.anchor_text`: Distinctive Korean phrase from the paragraph (used by filler to locate insertion point)
 - `generation_prompt`: English prompt for AI image generation
-- `preset`: Maps to `.claude/skills/dokkit/scripts/source_images.py` preset parameter
+- `preset`: Maps to the bundled `scripts/source_images.py` preset parameter
 - `content_type`: One of `flowchart`, `diagram`, `data`, `concept`, `infographic`
 - `rationale`: Brief explanation of why an image helps here
 - `dimensions`: Default size — filler may adjust based on content_type

package/optional-skills/generate-skill/REFERENCE.md

@@ -46,7 +46,6 @@ Complete catalog of YAML frontmatter fields for Claude Code skill files (`SKILL.
 | `argument-hint` | string | none | Placeholder shown to user (e.g., `"[file path]"`) |
 | `user-invocable` | boolean | `true` | Whether users can trigger via `/skill-name` |
 | `disable-model-invocation` | boolean | `false` | If `true`, Claude cannot proactively trigger the skill |
-| `context` | list | none | Files to inject into context when skill activates |
 | `agent` | object | none | Run skill as a subagent with its own context |
 | `model` | string | inherited | Override model (`opus`, `sonnet`, `haiku`) |
 | `hooks` | object | none | Shell commands to run on skill lifecycle events |
@@ -62,20 +61,15 @@ allowed-tools: Read, Bash(npm test *), Bash(npx *)
 
 Wildcard `*` matches any arguments. Without a glob, Bash runs any command.
 
-### `context` Field
+### Supporting files
 
-Inject files into the skill's context automatically:
+Read supporting files explicitly from the skill body:
 
-```yaml
-context:
-  - type: file
-    path: ${CLAUDE_SKILL_DIR}/PATTERNS.md
-  - type: file
-    path: ./CLAUDE.md
+```text
+Before proceeding, read PATTERNS.md relative to the directory
+containing this loaded SKILL.md.
 ```
 
-Use `${CLAUDE_SKILL_DIR}` for paths relative to the skill directory.
-
 ### `agent` Field
 
 Run the skill as an isolated subagent:
@@ -102,7 +96,10 @@ hooks:
 
 ## String Substitutions
 
-These placeholders are replaced at runtime:
+Claude Code replaces these placeholders when rendering a skill.
+They are reader substitutions, not portable shell environment
+variables. Portable resource references use the selected skill
+directory and relative paths.
 
 | Placeholder | Replaced With |
 |---|---|
@@ -116,7 +113,7 @@ These placeholders are replaced at runtime:
 ```markdown
 Parse `$ARGUMENTS` for the file path.
 If `$1` is empty, ask the user for a target file.
-Read the config from `${CLAUDE_SKILL_DIR}/config.yaml`.
+Read config.yaml relative to this loaded skill's directory.
 ```
 
 ---

package/optional-skills/generate-skill/SKILL.md

@@ -15,6 +15,13 @@ argument-hint: "[skill description or name]"
 Create production-quality Claude Code skills with correct frontmatter, structured workflows, and Claude 4.6 prompt patterns.
 
 Reference files in this skill directory:
+
+Resolve the bundled reference paths below against the directory
+containing the SKILL.md loaded for this invocation, using its opened
+path, reader-reported base directory, or native URI mapping. Never
+resolve them against cwd or another installation. Missing source
+identity is BLOCKED:skill-source-unresolved.
+
 - `REFERENCE.md` — Complete frontmatter field catalog and validation rules
 - `PROMPT-PATTERNS.md` — Claude 4.6 prompt engineering patterns for skill bodies
 - `CHECKLIST.md` — Quality verification checklist
@@ -50,11 +57,13 @@ Estimate the total line count for the skill content:
 Rules for reference files:
 - One level deep only (no nested references)
 - Add a table of contents if a reference file exceeds 100 lines
-- Reference files use `${CLAUDE_SKILL_DIR}/FILENAME.md` for paths
+- Reference files use paths relative to the generated SKILL.md, with
+  an explicit instruction to resolve them against the loaded skill
+  directory.
 
 ### Step 3: Write Frontmatter
 
-Read `${CLAUDE_SKILL_DIR}/REFERENCE.md` for the complete field catalog.
+Read `REFERENCE.md` for the complete field catalog.
 
 Apply these rules:
 - `name`: lowercase, hyphens only, max 64 chars, no "anthropic" or "claude"
@@ -64,7 +73,7 @@ Apply these rules:
 
 ### Step 4: Write Skill Body
 
-Read `${CLAUDE_SKILL_DIR}/PROMPT-PATTERNS.md` for Claude 4.6 patterns.
+Read `PROMPT-PATTERNS.md` for Claude 4.6 patterns.
 
 Structure the body in this order:
 1. **Title and purpose** — One-line summary of what the skill does and why
@@ -111,7 +120,7 @@ For multi-file skills, create reference files:
 
 ### Step 7: Validate
 
-Read `${CLAUDE_SKILL_DIR}/CHECKLIST.md` and verify the generated skill against every item.
+Read `CHECKLIST.md` and verify the generated skill against every item.
 
 Fix any issues before presenting the final output.
 
@@ -124,7 +133,6 @@ After generating the skill, present:
 3. **Test invocation** — Example command to test the skill
 
 Offer to:
-- Run `/devlyn:review` on the generated skill for quality assurance
 - Run `pyx-scan` if the skill will be published
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devlyn-cli",
-  "version": "3.3.1",
+  "version": "4.0.1",
   "description": "Loop & harness engineering for AI coding agents (Claude Code, Codex, and any AGENTS.md-driven agent) — take intent to shipped, engineer-quality software hands-free with phase-gated pipelines and agent orchestration",
   "homepage": "https://github.com/fysoul17/devlyn-cli#readme",
   "bin": {
@@ -13,6 +13,8 @@
     "!config/skills/preflight-workspace/**",
     "!config/skills/devlyn:ideate-workspace",
     "!config/skills/devlyn:ideate-workspace/**",
+    "!config/skills/devlyn-ideate-workspace",
+    "!config/skills/devlyn-ideate-workspace/**",
     "!config/skills/devlyn:auto-resolve-workspace",
     "!config/skills/devlyn:auto-resolve-workspace/**",
     "!config/skills/roadmap-archival-workspace",