# TRIZ agent setup

Set up the user's chosen project. This guide alone does not authorize live model spend, commits, pushes, or destructive changes. Requires Node 24+, npm, and Git. Windows uses Ubuntu WSL for the Bash installer. Preserve working installations and existing provider configuration.

## Install

Check triz --help first. If installation is needed, download and inspect https://trizit.dev/install.sh, then run it. For local preview substitute the preview origin. The script installs reviewed source revision 358abed38978499d9da85f65885b70716ae952a1 from GitHub and builds locked JavaScript dependencies. No Rust is needed. If access, network, or permissions fail, report the prerequisite; do not use sudo or bypass access controls. The site URL works after deployment; do not claim npm registry availability.

## Skill and instructions

Download /skills/triz/SKILL.md from this site's origin into the project's .agents/skills/triz/SKILL.md. For Claude Code also install into .claude/skills/triz/SKILL.md when selected. Preserve customized existing skills: report conflicts before overwriting. Read the installed skill and resolve the actual triz command path.

Add exactly one block to the project AGENTS.md:

<triz>
For conflicting coding requirements, read .agents/skills/triz/SKILL.md. Analyze evidence with TRIZ, persist result JSON, and hand candidate strategies and uncertainty to the manager before implementation. Never treat a strategy as verified or accept it without independent checks.
</triz>

Append on first setup; replace the existing block in place on reruns; unchanged content is a no-op. Preserve every byte outside the block. Stop for duplicated, nested, or unbalanced tags. Any TRIZ prose added to other shared instruction files must also use one triz block.

Codex and Cursor can use AGENTS.md. Confirm instruction discovery for the actual client. Claude Code uses its skill or a tagged CLAUDE.md pointer; Gemini CLI uses GEMINI.md; Copilot IDE clients may use .github/copilot-instructions.md. Other clients such as Windsurf, Cline, Roo Code, Aider, and Continue should use their current supported context/rules mechanism with a small pointer to AGENTS.md and the skill. Configure only selected clients; verify terminal and file access. Do not insert XML tags into JSON configuration.

## Verify

Run triz catalog and inspect triz --help. Use a valid documented request and offline response fixture to exercise analyze --offline ... --out ... followed by inspect. Do not fabricate a live result or weaken uncertainty checks. For live analysis, verify the optional Pi SDK and provider configuration with the user; authentication stays with the human, never collect keys in chat.

Return a compact setup receipt: CLI location/version, installed skill paths, managed instruction files, offline checks, and unresolved dependencies. Installing TRIZ does not automatically configure a global MCP client or a hosted service.