=== project/root/.kiro/hooks/gortex-post-edit.json ===
{
  "name": "Gortex: Post-Edit Check",
  "version": "1.0.0",
  "description": "Check impact and tests after a source edit.",
  "when": {
    "type": "fileEdited",
    "patterns": ["**/*.go", "**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx", "**/*.py", "**/*.rs", "**/*.java", "**/*.kt", "**/*.scala", "**/*.swift", "**/*.rb", "**/*.cs", "**/*.php"]
  },
  "then": {
    "type": "askAgent",
    "prompt": "Call Gortex change with operation detect for unstaged changes. Use its affected symbol IDs with operations tests, guards, and contract; run the selected tests and report every result."
  }
}
=== project/root/.kiro/hooks/gortex-pre-read.json ===
{
  "name": "Gortex: Enrich Source Read",
  "version": "1.0.0",
  "description": "Use indexed source context before a raw source-file read.",
  "when": {"type": "preToolUse", "toolTypes": ["read"]},
  "then": {
    "type": "askAgent",
    "prompt": "For indexed source code, use Gortex read with operation editing_context or source instead of a raw file read. Skip generated files, metadata, documentation, configuration, and non-source assets."
  }
}
=== project/root/.kiro/hooks/gortex-smart-context.json ===
{
  "name": "Gortex: Task Context",
  "version": "1.0.0",
  "description": "Localize each coding task with the graph before opening files.",
  "when": {"type": "userTriggered"},
  "then": {
    "type": "askAgent",
    "prompt": "For a coding task, call Gortex explore with operation task and the user's task text before reading or searching files. Skip this only for non-coding conversation."
  }
}
=== project/root/.kiro/settings/mcp.json ===
{
  "mcpServers": {
    "gortex": {
      "args": [
        "mcp"
      ],
      "autoApprove": [
        "analyze",
        "capabilities",
        "change",
        "explore",
        "read",
        "recall",
        "relations",
        "response",
        "search",
        "trace",
        "workspace"
      ],
      "command": "gortex",
      "disabled": false,
      "env": {
        "GORTEX_INDEX_WORKERS": "8"
      }
    }
  }
}
=== project/root/.kiro/steering/gortex-debug.md ===
---
inclusion: manual
---

# Debug with Gortex

1. Localize the symptom with `explore`.
2. Use `search` with `operation:"text"` for an exact error and `operation:"symbols"` for named code.
3. Use `relations({operation:"callers", ...})` and `trace({operation:"call_chain", ...})` to follow execution.
4. Use `trace` with `flow` or `taint` when the bug concerns values crossing helpers.
5. Read only the suspect symbols, then state the root cause and evidence.
=== project/root/.kiro/steering/gortex-explore.md ===
---
inclusion: manual
---

# Explore with Gortex

1. Call `explore({operation:"task", task:"<question>"})`.
2. Narrow names with `search({operation:"symbols", query:"<name>"})` or literals with `operation:"text"`.
3. Read only the needed source with `read` (`source`/`summary`/`editing_context`).
4. Prove relationships with `relations` or execution paths with `trace`.
5. Return symbol IDs, file:line locations, and the shortest evidence needed.
=== project/root/.kiro/steering/gortex-impact.md ===
---
inclusion: manual
---

# Assess change impact with Gortex

1. Resolve the target with `explore` or `search`.
2. Call `change` with `operation:"impact"`.
3. For signature changes, call `change` with `operation:"verify"`.
4. Check `relations` usages/dependents and `analyze` contracts when boundaries are involved.
5. Call `change` with `operation:"tests"` and report concrete tests.
=== project/root/.kiro/steering/gortex-refactor.md ===
---
inclusion: manual
---

# Refactor with Gortex

1. Start with `explore` and read the target through `read`.
2. Call `change` operations `impact` and `edit_plan` before writing; for a signature change, also call `verify` with the proposed signature.
3. Use `refactor` for rename, move, inline, delete, or code actions. Use `edit` for file, symbol, batch, or new-file changes.
4. After writing, call `change` operations `detect`, `tests`, `guards`, and `contract`.
5. Run the project tests selected by the graph.
=== project/root/.kiro/steering/gortex-workflow.md ===
---
inclusion: always
---

# Gortex workflow

Use Gortex MCP tools for indexed code. This is mandatory.

1. Start every coding task with `explore` using `operation: "task"` and the user's task text.
2. Use `search` for symbols, text, files, or AST shapes; use `read` for file, source, summary, or editing context.
3. Use `relations` for usages, callers, dependencies, dependents, and implementations; use `trace` for call chains and dataflow.
4. Before mutation, call `change` with `operation: "impact"`; for a signature change, also call operation `verify` with the proposed signature.
5. Mutate only with `edit` or `refactor`. After mutation, call `change` operations `detect`, `tests`, `guards`, and `contract`.
6. Call `capabilities` with `domain`, `operation`, and `detail: "schema"` when exact arguments are not already visible.

Do not replace graph reads or searches with shell commands. If the configured Gortex tools are missing from the callable MCP tools, report a Gortex MCP integration failure and stop; do not start a daemon or use a CLI/shell fallback.

For durable context, use `recall` (`surface`/`notes`/`memories`) before editing known code and `remember` (`note`/`memory`) for decisions and invariants.
=== global/home/.kiro/settings/mcp.json ===
{
  "mcpServers": {
    "gortex": {
      "args": [
        "mcp"
      ],
      "autoApprove": [
        "analyze",
        "capabilities",
        "change",
        "explore",
        "read",
        "recall",
        "relations",
        "response",
        "search",
        "trace",
        "workspace"
      ],
      "command": "gortex",
      "disabled": false,
      "env": {
        "GORTEX_INDEX_WORKERS": "8"
      }
    }
  }
}
