Post

1/ The era of manual install scripts for Blessed Frameworks™ is over. New post on `tigris init --agent` and why agent-native onboarding is becoming the baseline.

2/ Your onboarding funnels people into two buckets: users of the framework you picked, and everyone else. Everyone else gets the API reference and good luck. I've been everyone else. I closed the tab.

3/ A portable setup script has to identify the language, the dependency manager, and which dependency manager wins when a project has three. Then be right about every OS and CI environment. Every failure is a support ticket.

4/ The agent needs none of that. Worst case it explores the repo and figures out how you build and deploy. Give it the goal, not the mechanism.

5/ Four things decide whether the prompt works: ask permission before acting, prefer heuristics over mandates, keep credentials out of the context window, phrase everything positively.

7/ Lesson learned the hard way: agents can't install their own config. I shipped skills, the agent installed them, and then behaved like nothing changed. Skills are executable code and the agent can't tell your integration from a crypto miner.

8/ So tigris init has two doors. The wizard for humans in a shell, where installing to an agent is safe because the agent hasn't started. The --agent recipe in plain text, because text is the only thing that works reliably from inside a session.