Struere Developer

Struere is an AI-native full-stack agent platform. Define agents, data types, roles, triggers, routers, and tools as TypeScript — then sync to dev and deploy to prod.

Rules

1. Ensure struere dev is running. Before making any changes, verify struere dev is running in the background. If it's not running or not available, use bunx struere sync after each change. Never ask the user whether to sync — just keep changes synced.
2. Fetch docs before writing code. NEVER write or modify Struere code without first fetching the relevant URL from the documentation table below. Every time. No exceptions. Do not work from memory.
3. Use struere chat to test. After creating or modifying an agent, test it with struere chat <slug> to simulate conversations before writing evals. Run multiple test conversations to discover edge cases.
4. Ask before assuming. Before creating an agent, ask what it should do, who it serves, and what tools it needs. Do not guess requirements.
5. One export per file. Each file in agents/, entity-types/, roles/, triggers/, routers/ exports a single default. Only tools/index.ts exports all custom tools.
6. Slugs are identities. Renaming a slug creates a new resource — it does not rename the existing one.
7. Environments are isolated. struere dev syncs to development + eval (eval excludes triggers and routers). struere deploy syncs to production.
8. Roles work for both users and agents. A role's policies/scope rules/field masks apply to whoever is assigned to it. Users get roles via the dashboard; agents declare them in code via defineAgent({ roles: [...] }). Don't conflate agentAccess (dashboard ACL) with agent.roles (permission inheritance). Roles use slug for identity (lowercase, alphanumeric + hyphens); name is a display label. Always declare slug on new roles — it'll be required in a future major version.
9. Keep tools under 5 per agent. Split into specialist agents with agent.chat if you need more.
10. Use bun, never npm. Always bun install, bun run, bunx.
11. Use struere keys for credentials. Get API keys via struere keys create from the CLI — don't direct users to the dashboard for routine key management.
12. Keep CLI updated. Run bun update struere to ensure you're on the latest SDK/CLI version before starting work.