@assistkick/create 1.6.0 → 1.7.0

package/templates/skills/assistkick-code-reviewer/SKILL.md

@@ -119,7 +119,7 @@ npx tsx packages/shared/tools/move_card.ts <feature_id> todo --project-id <proje
 npx tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
 npx tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
 ```
-Returns full .md content plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
+Returns the node content (formatted as markdown) plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
 
 ### search_nodes
 ```
@@ -148,7 +148,7 @@ npx tsx packages/shared/tools/get_status.ts --project-id <project_id>
 2. Never approve without reading the full spec, all connected nodes, and related done features first
 3. Never approve without running tests
 4. Always provide actionable rejection notes — reference specific acceptance criteria, integration issues, or connected node requirements
-5. Never read or write graph.tson, kanban.tson, or node .md files directly — always use the tools
+5. All graph data is stored in SQLite (via Drizzle ORM) — always use the tools above to read and write data
 6. If you find a spec gap during review, add an open question via `update_node` and flag it to the user
 7. All tool commands must be run from the `assistkick-product-system/` directory
 8. Review one feature at a time — complete the verdict before moving to the next

package/templates/skills/assistkick-debugger/SKILL.md

@@ -156,7 +156,7 @@ npx tsx packages/shared/tools/move_card.ts <feature_id> todo --project-id <proje
 npx tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
 npx tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
 ```
-Returns full .md content plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
+Returns the node content (formatted as markdown) plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
 
 ### search_nodes
 ```
@@ -201,7 +201,7 @@ npx tsx packages/shared/tools/get_status.ts --project-id <project_id>
 
 ## Rules
 1. Never write production code — you only read, run tests, add temporary debug logs, and investigate
-2. Never read or write graph.tson, kanban.tson, or node .md files directly — always use the tools
+2. All graph data is stored in SQLite (via Drizzle ORM) — always use the tools above to read and write data
 3. Always call `get_node` on affected features AND their related nodes before investigating
 4. Always create a bugfix feature with detailed findings — the developer should be able to fix it without re-investigating
 5. Include specific file paths, line numbers, root cause analysis, and fix guidance in your bugfix notes

package/templates/skills/assistkick-developer/SKILL.md

@@ -120,7 +120,7 @@ npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --comple
 npx tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
 npx tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
 ```
-Returns full .md content plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
+Returns the node content (formatted as markdown) plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
 
 ### add_node
 ```
@@ -178,9 +178,9 @@ npx tsx packages/shared/tools/rebuild_index.ts --project-id <project_id> --dry-r
 ```
 
 ## Rules
-1. Never read or write graph.tson or node .md files directly — always use the tools
+1. All graph data is stored in SQLite (via Drizzle ORM) — always use the tools above to read and write data
 2. Always call `get_node` on a feature AND its related nodes before implementing — understand the full context
-3. Always use `get_kanban` to check kanban state and `move_card` to transition cards — never edit kanban.tson directly
+3. Always use `get_kanban` to check kanban state and `move_card` to transition cards
 4. Call `move_card <feat_id> in_progress` before starting work, `move_card <feat_id> in_review` when done
 5. Follow all coding standards from `nfr_001` — arrow functions, DI, single responsibility, node:test
 6. Write tests for every feature — test logic and data transformations

package/templates/skills/assistkick-interview/SKILL.md

@@ -94,7 +94,7 @@ npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --comple
 npx tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
 npx tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
 ```
-Returns full .md content plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
+Returns the node content (formatted as markdown) plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
 
 ### add_node
 ```
@@ -219,7 +219,7 @@ The user's time is for product decisions, not answering questions about their
 own codebase that you have full access to.
 
 ## Rules
-1. Never read or write graph.tson or .md files directly — always use the tools
+1. All graph data is stored in SQLite (via Drizzle ORM) — always use the tools above to read and write data
 2. Always call get_node before update_node — never update blind
 3. Always record answers via resolve_question — don't just add a note
 4. Nodes you create should reflect what the user actually said, not your inferences — use assumption node type for inferences