@assistkick/create 1.0.1 → 1.3.0

package/templates/skills/{product-bootstrap → assistkick-bootstrap}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: product-bootstrap
+name: assistkick-bootstrap
 description: Bootstrap the product knowledge graph for an existing project by scanning the codebase and interviewing the user. Use when the user wants to onboard a project, bootstrap the graph, initialize the product system, or bring the knowledge graph up to speed for an existing codebase.
 ---
 
@@ -12,7 +12,7 @@ Your goal is to rapidly build a well-connected specification graph by
 priorities, and preferences**. You interact with the graph exclusively
 through the tools below.
 
-All tools live in `product-system/packages/shared/tools/` and
+All tools live in `assistkick-product-system/packages/shared/tools/` and
 are run with `npx tsx`.
 
 ## Bootstrap Philosophy
@@ -181,37 +181,45 @@ from the features they apply to.
 3. Call `end_session` with a summary
 4. Tell the user which phase to resume at next session
 
+## Project ID
+
+All tools require `--project-id <project_id>`. Resolve it at session start:
+- If the user passed a project ID in the invocation arguments → use it directly
+- Otherwise → ask the user: "Which project ID should I use?"
+
+Use the same `<project_id>` on **every** tool call in this session.
+
 ## Tool Reference
 
 ### start_session
 ```
-npx tsx packages/shared/tools/start_session.ts
+npx tsx packages/shared/tools/start_session.ts --project-id <project_id>
 ```
 
 ### end_session
 ```
-npx tsx packages/shared/tools/end_session.ts --summary "..." --nodes-touched "feat_001,dec_001" --questions-resolved 3
+npx tsx packages/shared/tools/end_session.ts --project-id <project_id> --summary "..." --nodes-touched "feat_001,dec_001" --questions-resolved 3
 ```
 
 ### search_nodes
 ```
-npx tsx packages/shared/tools/search_nodes.ts --query "keyword"
-npx tsx packages/shared/tools/search_nodes.ts --type feature
-npx tsx packages/shared/tools/search_nodes.ts --has-open-questions
-npx tsx packages/shared/tools/search_nodes.ts --completeness-below 0.5
+npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --query "keyword"
+npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --type feature
+npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --has-open-questions
+npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --completeness-below 0.5
 ```
 
 ### get_node
 ```
-npx tsx packages/shared/tools/get_node.ts <node_id>
-npx tsx packages/shared/tools/get_node.ts --name "Node Name"
+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.
 
 ### add_node
 ```
-npx tsx packages/shared/tools/add_node.ts --type <type> --name "Name" --description "..."
+npx tsx packages/shared/tools/add_node.ts --project-id <project_id> --type <type> --name "Name" --description "..."
 ```
 Valid types: feature, component, data_entity, decision, tech_choice,
 non_functional_requirement, design_token, design_pattern, user_role,
@@ -219,23 +227,23 @@ flow, assumption, open_question
 
 ### update_node
 ```
-npx tsx packages/shared/tools/update_node.ts <id> --add-acceptance-criteria "..."
-npx tsx packages/shared/tools/update_node.ts <id> --add-open-question "..."
-npx tsx packages/shared/tools/update_node.ts <id> --add-note "Session N: ..."
-npx tsx packages/shared/tools/update_node.ts <id> --set-status <draft|partially_defined|defined>
-npx tsx packages/shared/tools/update_node.ts <id> --set-priority <low|medium|high|blocking>
-npx tsx packages/shared/tools/update_node.ts <id> --set-description "..."
-npx tsx packages/shared/tools/update_node.ts <id> --set-section "SectionName=content"
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-acceptance-criteria "..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-open-question "..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-note "Session N: ..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-status <draft|partially_defined|defined>
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-priority <low|medium|high|blocking>
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-description "..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-section "SectionName=content"
 ```
 
 ### resolve_question
 ```
-npx tsx packages/shared/tools/resolve_question.ts <id> --question "..." --answer "..."
+npx tsx packages/shared/tools/resolve_question.ts <id> --project-id <project_id> --question "..." --answer "..."
 ```
 
 ### add_edge
 ```
-npx tsx packages/shared/tools/add_edge.ts <from_id> <relation> <to_id>
+npx tsx packages/shared/tools/add_edge.ts <from_id> <relation> <to_id> --project-id <project_id>
 ```
 Valid relations: contains, depends_on, governed_by, constrained_by,
 implemented_with, reads_writes, exposes, consumes, performed_by,
@@ -243,25 +251,25 @@ escalates_to, relates_to
 
 ### remove_edge
 ```
-npx tsx packages/shared/tools/remove_edge.ts <from_id> <relation> <to_id>
+npx tsx packages/shared/tools/remove_edge.ts <from_id> <relation> <to_id> --project-id <project_id>
 ```
 
 ### get_gaps
 ```
-npx tsx packages/shared/tools/get_gaps.ts
-npx tsx packages/shared/tools/get_gaps.ts --blocking-only
-npx tsx packages/shared/tools/get_gaps.ts --type feature
+npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id>
+npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id> --blocking-only
+npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id> --type feature
 ```
 
 ### get_status
 ```
-npx tsx packages/shared/tools/get_status.ts
+npx tsx packages/shared/tools/get_status.ts --project-id <project_id>
 ```
 
 ### rebuild_index
 ```
-npx tsx packages/shared/tools/rebuild_index.ts
-npx tsx packages/shared/tools/rebuild_index.ts --dry-run
+npx tsx packages/shared/tools/rebuild_index.ts --project-id <project_id>
+npx tsx packages/shared/tools/rebuild_index.ts --project-id <project_id> --dry-run
 ```
 
 ## Search Strategy
@@ -300,7 +308,7 @@ The `search_nodes --query` tool returns graph-aware relevance-ranked results.
 4. Nodes should reflect reality (codebase + user statements), not inferences —
    use `assumption` node type for inferences
 5. If the user contradicts something in the graph, update it and add a note
-6. All tool commands must be run from the `product-system/`
+6. All tool commands must be run from the `assistkick-product-system/`
    directory
 7. Set status to `defined` for features clearly implemented in the codebase;
    use `draft` for planned/future work

package/templates/skills/{product-code-reviewer → assistkick-code-reviewer}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: product-code-reviewer
+name: assistkick-code-reviewer
 description: Review implemented features against their specification, coding standards, and test coverage. Use when the user wants to review code, check implementation quality, or validate features before QA.
 ---
 
@@ -11,7 +11,7 @@ in the feature spec has actually been implemented. You pick up features from
 the `in_review` column, validate them, and either approve or reject with
 actionable feedback.
 
-All tools live in `product-system/packages/shared/tools/` and are run with `npx tsx`.
+All tools live in `assistkick-product-system/packages/shared/tools/` and are run with `npx tsx`.
 
 ## Session Start Protocol
 1. Call `get_kanban --column in_review` — identify features awaiting review
@@ -72,14 +72,14 @@ After reviewing, you MUST take exactly one action:
 ### Approve
 If the feature delivers what was requested and passes all checks:
 ```
-npx tsx packages/shared/tools/move_card.ts <feat_id> qa
+npx tsx packages/shared/tools/move_card.ts <feat_id> qa --project-id <project_id>
 ```
 Report to the user: what was reviewed, how it integrates with existing features, and that it passed.
 
 ### Reject
 If any check fails — especially if the feature does not deliver what was requested:
 ```
-npx tsx packages/shared/tools/move_card.ts <feat_id> todo --note "Clear description of what needs fixing"
+npx tsx packages/shared/tools/move_card.ts <feat_id> todo --project-id <project_id> --note "Clear description of what needs fixing"
 ```
 The note MUST be actionable — reference specific acceptance criteria that are not met,
 specific integration issues with existing features, or specific connected node requirements
@@ -91,48 +91,56 @@ Your transitions:
 - **In Review → QA**: Feature passes review (approve)
 - **In Review → Todo**: Feature fails review (reject with notes)
 
+## Project ID
+
+All tools require `--project-id <project_id>`. Resolve it at session start:
+- If the user passed a project ID in the invocation arguments → use it directly
+- Otherwise → ask the user: "Which project ID should I use?"
+
+Use the same `<project_id>` on **every** tool call in this session.
+
 ## Tool Reference
 
 ### get_kanban
 ```
-npx tsx packages/shared/tools/get_kanban.ts                    # show all columns
-npx tsx packages/shared/tools/get_kanban.ts --column in_review # features awaiting review
-npx tsx packages/shared/tools/get_kanban.ts --column done      # already shipped features
+npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id>                    # show all columns
+npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column in_review # features awaiting review
+npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column done      # already shipped features
 ```
 
 ### move_card
 ```
-npx tsx packages/shared/tools/move_card.ts <feature_id> qa                            # approve
-npx tsx packages/shared/tools/move_card.ts <feature_id> todo --note "What to fix"     # reject
+npx tsx packages/shared/tools/move_card.ts <feature_id> qa --project-id <project_id>                            # approve
+npx tsx packages/shared/tools/move_card.ts <feature_id> todo --project-id <project_id> --note "What to fix"     # reject
 ```
 
 ### get_node
 ```
-npx tsx packages/shared/tools/get_node.ts <node_id>
-npx tsx packages/shared/tools/get_node.ts --name "Node Name"
+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.
 
 ### search_nodes
 ```
-npx tsx packages/shared/tools/search_nodes.ts --query "keyword"
-npx tsx packages/shared/tools/search_nodes.ts --type feature
+npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --query "keyword"
+npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --type feature
 ```
 
 ### update_node
 ```
-npx tsx packages/shared/tools/update_node.ts <id> --add-note "Review: ..."
-npx tsx packages/shared/tools/update_node.ts <id> --add-open-question "..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-note "Review: ..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-open-question "..."
 ```
 
 ### get_gaps
 ```
-npx tsx packages/shared/tools/get_gaps.ts
+npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id>
 ```
 
 ### get_status
 ```
-npx tsx packages/shared/tools/get_status.ts
+npx tsx packages/shared/tools/get_status.ts --project-id <project_id>
 ```
 
 ## Rules
@@ -142,6 +150,6 @@ npx tsx packages/shared/tools/get_status.ts
 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
 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 `product-system/` directory
+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
 9. The `move_card` tool validates transitions — trust the error if a move is rejected

package/templates/skills/assistkick-db-explorer/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: assistkick-db-explorer
+description: Explore and inspect the database with read-only access. Use when the user wants to check database contents, inspect table schemas, count rows, sample data, or run read-only SQL queries to understand the current state of the data.
+---
+
+# Database Explorer Skill
+
+## Your Role
+You are a database inspector. You use the `db_explorer` tool to help the user
+understand the current state of the database — table structures, row counts,
+data samples, and custom read-only queries. You have absolutely NO write
+capabilities. You can only read and inspect.
+
+All commands are run from the `assistkick-product-system/` directory.
+
+## Tool Reference
+
+### List all tables
+```
+npx tsx packages/shared/tools/db_explorer.ts tables
+```
+Shows all tables with row counts.
+
+### Describe a table schema
+```
+npx tsx packages/shared/tools/db_explorer.ts describe <table_name>
+```
+Shows columns, types, nullability, defaults, primary keys, indexes, and foreign keys.
+
+### Count rows
+```
+npx tsx packages/shared/tools/db_explorer.ts count <table_name>
+npx tsx packages/shared/tools/db_explorer.ts count <table_name> --where "status = 'draft'"
+npx tsx packages/shared/tools/db_explorer.ts count <table_name> --where "project_id = 'proj_001'"
+```
+
+### Sample rows
+```
+npx tsx packages/shared/tools/db_explorer.ts sample <table_name>
+npx tsx packages/shared/tools/db_explorer.ts sample <table_name> --limit 5
+npx tsx packages/shared/tools/db_explorer.ts sample <table_name> --where "type = 'feature'" --limit 3
+npx tsx packages/shared/tools/db_explorer.ts sample <table_name> --order-by "created_at DESC" --limit 5
+```
+
+### Run a read-only SQL query
+```
+npx tsx packages/shared/tools/db_explorer.ts query "SELECT id, name, type, status FROM nodes WHERE type = 'feature'"
+npx tsx packages/shared/tools/db_explorer.ts query "SELECT n.id, n.name, k.column_name FROM nodes n JOIN kanban k ON n.id = k.node_id"
+npx tsx packages/shared/tools/db_explorer.ts query "SELECT type, COUNT(*) as cnt FROM nodes GROUP BY type ORDER BY cnt DESC"
+npx tsx packages/shared/tools/db_explorer.ts query "PRAGMA table_info('nodes')"
+```
+Only SELECT, PRAGMA, and EXPLAIN queries are allowed. Write operations are blocked.
+A safety LIMIT of 100 is auto-appended to SELECT queries without an explicit LIMIT.
+
+## Available Tables
+
+| Table | Description |
+|-------|-------------|
+| `nodes` | Knowledge graph nodes (features, components, decisions, etc.) |
+| `edges` | Relationships between nodes |
+| `kanban` | Feature kanban board state |
+| `sessions` | Interview session history |
+| `coherence_reviews` | Graph change proposals |
+| `review_meta` | Kanban metadata and review state |
+| `users` | User accounts |
+| `refresh_tokens` | JWT refresh tokens |
+| `password_reset_tokens` | Password reset flow |
+| `invitations` | User invitations |
+| `projects` | Project contexts |
+| `pipeline_state` | Pipeline execution state |
+
+## Security
+
+- Only SELECT, PRAGMA, and EXPLAIN queries are allowed
+- Write keywords (INSERT, UPDATE, DELETE, DROP, ALTER, CREATE, etc.) are blocked
+- Multiple statements (semicolons) are blocked
+- Sensitive columns (`password_hash`, `token_hash`) are automatically redacted as `[REDACTED]`
+- SQL comments are stripped before validation
+
+## Rules
+1. Never attempt write operations — the tool will reject them
+2. Use `--where` to filter results rather than dumping entire tables
+3. Use `--limit` to keep output manageable
+4. The `--project-id` flag is optional — use `--where "project_id = '...'"` to filter by project
+5. All tool commands must be run from the `assistkick-product-system/` directory
+6. Start with `tables` to understand what's available, then `describe` to understand structure, then `sample` or `query` to inspect data

package/templates/skills/{product-debugger → assistkick-debugger}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: product-debugger
+name: assistkick-debugger
 description: Debug and investigate bugs reported by the user, find root causes, and create bugfix features with findings. Use when the user reports a bug, wants to investigate an issue, or needs help finding the root cause of a problem.
 ---
 
@@ -12,7 +12,7 @@ the root cause, and create a bugfix feature in the graph with your findings so
 the developer knows exactly what to fix. You never write production code — you
 only read code, run tests, and trace issues.
 
-All tools live in `product-system/packages/shared/tools/` and are run with `npx tsx`.
+All tools live in `assistkick-product-system/packages/shared/tools/` and are run with `npx tsx`.
 
 ## Session Start Protocol
 1. Call `get_status` — understand current project state
@@ -52,7 +52,7 @@ When static code reading isn't enough to identify the root cause, **add temporar
 - Never leave debug logs in the codebase
 
 ### 5. Use Browser Automation to Reproduce and Observe
-Use `agent-browser` (already installed) to interact with the running application in a headless browser. See `.claude/skills/product-debugger/references/agent-browser.md` for the full command reference.
+Use `agent-browser` (already installed) to interact with the running application in a headless browser. See `.claude/skills/assistkick-debugger/references/agent-browser.md` for the full command reference.
 
 **Core workflow:**
 ```bash
@@ -104,17 +104,17 @@ Once you've found the root cause, create a bugfix feature:
 
 1. **Create the bugfix feature** with a clear description of the problem and root cause:
 ```
-npx tsx packages/shared/tools/add_node.ts --type feature --kind bugfix --name "Fix: <short description>" --description "Root cause description..."
+npx tsx packages/shared/tools/add_node.ts --project-id <project_id> --type feature --kind bugfix --name "Fix: <short description>" --description "Root cause description..."
 ```
 
 2. **Add acceptance criteria** that describe the correct behavior:
 ```
-npx tsx packages/shared/tools/update_node.ts <new_feat_id> --add-acceptance-criteria "..."
+npx tsx packages/shared/tools/update_node.ts <new_feat_id> --project-id <project_id> --add-acceptance-criteria "..."
 ```
 
 3. **Add investigation notes** with root cause details, code locations, and fix guidance:
 ```
-npx tsx packages/shared/tools/update_node.ts <new_feat_id> --add-note "Investigation: ..."
+npx tsx packages/shared/tools/update_node.ts <new_feat_id> --project-id <project_id> --add-note "Investigation: ..."
 ```
 The note should include:
 - Reproduction steps
@@ -124,71 +124,79 @@ The note should include:
 
 4. **Link the bugfix** to the affected feature(s):
 ```
-npx tsx packages/shared/tools/add_edge.ts <new_feat_id> relates_to <affected_feat_id>
+npx tsx packages/shared/tools/add_edge.ts <new_feat_id> relates_to <affected_feat_id> --project-id <project_id>
 ```
 
 5. **Report findings** to the user with a summary of the root cause and the bugfix feature ID
 
+## Project ID
+
+All tools require `--project-id <project_id>`. Resolve it at session start:
+- If the user passed a project ID in the invocation arguments → use it directly
+- Otherwise → ask the user: "Which project ID should I use?"
+
+Use the same `<project_id>` on **every** tool call in this session.
+
 ## Tool Reference
 
 ### get_kanban
 ```
-npx tsx packages/shared/tools/get_kanban.ts                    # show all columns
-npx tsx packages/shared/tools/get_kanban.ts --column qa        # features in QA
-npx tsx packages/shared/tools/get_kanban.ts --column done      # shipped features
+npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id>                    # show all columns
+npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column qa        # features in QA
+npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column done      # shipped features
 ```
 
 ### move_card
 ```
-npx tsx packages/shared/tools/move_card.ts <feature_id> todo --note "Bug found — see feat_NNN for details"
+npx tsx packages/shared/tools/move_card.ts <feature_id> todo --project-id <project_id> --note "Bug found — see feat_NNN for details"
 ```
 
 ### get_node
 ```
-npx tsx packages/shared/tools/get_node.ts <node_id>
-npx tsx packages/shared/tools/get_node.ts --name "Node Name"
+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.
 
 ### search_nodes
 ```
-npx tsx packages/shared/tools/search_nodes.ts --query "keyword"
-npx tsx packages/shared/tools/search_nodes.ts --type feature
-npx tsx packages/shared/tools/search_nodes.ts --has-open-questions
+npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --query "keyword"
+npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --type feature
+npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --has-open-questions
 ```
 
 ### add_node
 ```
-npx tsx packages/shared/tools/add_node.ts --type feature --kind bugfix --name "Fix: ..." --description "..."
+npx tsx packages/shared/tools/add_node.ts --project-id <project_id> --type feature --kind bugfix --name "Fix: ..." --description "..."
 ```
 Use `--kind bugfix` when creating bug features.
 
 ### update_node
 ```
-npx tsx packages/shared/tools/update_node.ts <id> --add-acceptance-criteria "..."
-npx tsx packages/shared/tools/update_node.ts <id> --add-open-question "..."
-npx tsx packages/shared/tools/update_node.ts <id> --add-note "Investigation: ..."
-npx tsx packages/shared/tools/update_node.ts <id> --set-description "..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-acceptance-criteria "..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-open-question "..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-note "Investigation: ..."
+npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-description "..."
 ```
 
 ### add_edge
 ```
-npx tsx packages/shared/tools/add_edge.ts <from_id> <relation> <to_id>
+npx tsx packages/shared/tools/add_edge.ts <from_id> <relation> <to_id> --project-id <project_id>
 ```
 
 ### resolve_question
 ```
-npx tsx packages/shared/tools/resolve_question.ts <id> --question "..." --answer "..."
+npx tsx packages/shared/tools/resolve_question.ts <id> --project-id <project_id> --question "..." --answer "..."
 ```
 
 ### get_gaps
 ```
-npx tsx packages/shared/tools/get_gaps.ts
+npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id>
 ```
 
 ### get_status
 ```
-npx tsx packages/shared/tools/get_status.ts
+npx tsx packages/shared/tools/get_status.ts --project-id <project_id>
 ```
 
 ## Rules
@@ -198,9 +206,9 @@ npx tsx packages/shared/tools/get_status.ts
 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
 6. Always link bugfix features to the affected feature(s) via `add_edge`
-7. All tool commands must be run from the `product-system/` directory
+7. All tool commands must be run from the `assistkick-product-system/` directory
 8. The `move_card` tool validates transitions — trust the error if a move is rejected
 9. If the bug reveals a spec gap, add an open question via `update_node` on the affected feature and flag it to the user
 10. Investigate one bug at a time — complete the investigation before moving to the next
 11. Always remove any temporary debug logs you added before filing the bugfix feature — never leave debug code in the codebase
-12. Use `agent-browser` for browser-based investigation — see `.claude/skills/product-debugger/references/agent-browser.md` for the full command reference, our app is available at http://localhost:5173
+12. Use `agent-browser` for browser-based investigation — see `.claude/skills/assistkick-debugger/references/agent-browser.md` for the full command reference, our app is available at http://localhost:5173