palskills 1.0.2 → 1.0.3

package/bin/palskills.js

@@ -111,19 +111,19 @@ ALL code, comments, docstrings, variable names, and commit messages MUST be in E
 
 ## Palbox Knowledge Graph (CRITICAL)
 ### Before you start ANY task
-1. **Check if `.palbox/` exists.** If not, the project hasn't been bootstrapped yet.
+1. **Check if .palbox/ exists.** If not, the project has not been bootstrapped yet.
 2. **Read the core nodes:**
-   - `.palbox/README.md` — project identity, tech stack, goals
-   - `.palbox/architecture.md` — folder structure, design patterns, key modules
-   - `.palbox/methods.md` — coding conventions, testing strategy, git workflow
+   - .palbox/README.md — project identity, tech stack, goals
+   - .palbox/architecture.md — folder structure, design patterns, key modules
+   - .palbox/methods.md — coding conventions, testing strategy, git workflow
 3. **Search for related past work:**
-   - Search for keywords in `.palbox/flows/` and `.palbox/history/`
-   - Follow `[[wikilinks]]` to discover connected context
-4. **Read relevant flows** in `.palbox/flows/` — they document how features work end-to-end
-5. **Read relevant history** in `.palbox/history/` — past plans, executions, lessons learned
+   - Search for keywords in .palbox/flows/ and .palbox/history/
+   - Follow wikilinks to discover connected context
+4. **Read relevant flows** in .palbox/flows/ — they document how features work end-to-end
+5. **Read relevant history** in .palbox/history/ — past plans, executions, lessons learned
 
 ### After you complete a task
-- Record what you did. The Palskills system (Panthalus) will create a `.palbox/history/YYYY-MM-DD-feature.md` node with `[[wikilinks]]` to related entries.
+- Record what you did. The Palskills system (Panthalus) will create a .palbox/history/YYYY-MM-DD-feature.md node with wikilinks to related entries.
 - If you discovered new patterns, conventions, or pitfalls, note them — they enrich the graph.
 `;
 }
@@ -159,15 +159,15 @@ ALL code, comments, docs, variable names, and commit messages MUST be in English
 
 ### Project Context — Palbox Knowledge Graph
 Before you start ANY task:
-1. **Check if `.palbox/` exists.** Read the core nodes:
-   - `.palbox/README.md` — project identity, stack, goals
-   - `.palbox/architecture.md` — folder structure, patterns, key modules
-   - `.palbox/methods.md` — conventions, testing, git workflow
-2. **Search `.palbox/flows/` and `.palbox/history/`** for related past work.
-3. **Follow `[[wikilinks]]`** — they connect related nodes in the knowledge graph.
+1. **Check if .palbox/ exists.** Read the core nodes:
+   - .palbox/README.md — project identity, stack, goals
+   - .palbox/architecture.md — folder structure, patterns, key modules
+   - .palbox/methods.md — conventions, testing, git workflow
+2. **Search .palbox/flows/ and .palbox/history/** for related past work.
+3. **Follow wikilinks** — they connect related nodes in the knowledge graph.
 
 After completing work:
-- The Palskills system (Panthalus) records to `.palbox/history/` with bi-directional links.
+- The Palskills system (Panthalus) records to .palbox/history/ with bi-directional links.
 
 ### Code Quality
 - No file exceeds 200 lines without strong justification.
@@ -219,15 +219,15 @@ ALL code, comments, docstrings, variable names, function names, and commit messa
 
 ## Project Context — Palbox Knowledge Graph
 Before starting any task:
-1. Check if `.palbox/` exists. Read the core nodes:
-   - `.palbox/README.md` — project identity, stack, goals
-   - `.palbox/architecture.md` — folder structure, patterns, key modules
-   - `.palbox/methods.md` — conventions, testing, git workflow
-2. Search `.palbox/flows/` and `.palbox/history/` for related past work.
-3. Follow `[[wikilinks]]` — they connect related nodes in the knowledge graph.
+1. Check if .palbox/ exists. Read the core nodes:
+   - .palbox/README.md — project identity, stack, goals
+   - .palbox/architecture.md — folder structure, patterns, key modules
+   - .palbox/methods.md — conventions, testing, git workflow
+2. Search .palbox/flows/ and .palbox/history/ for related past work.
+3. Follow wikilinks — they connect related nodes in the knowledge graph.
 
 After completing work:
-- The Palskills system (Panthalus) records your session to `.palbox/history/` with bi-directional `[[wikilinks]]`.
+- The Palskills system (Panthalus) records your session to .palbox/history/ with bi-directional wikilinks.
 - If you discovered patterns, pitfalls, or conventions worth preserving, note them.
 `;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "palskills",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "AI-powered development pipeline — 5 Hermes Agent skills orchestrated as a knowledge graph",
   "keywords": [
     "hermes-agent",