tstack

Surfaces relevant team architecture guidance whenever the user is doing — or about to do — code-time work that may touch architectural decisions. Activate on user intent, not just slash commands. Fire when the user is designing or scaffolding a new service, module, component, or feature; choosing a technology, framework, or library for a non-trivial decision; refactoring across service or module boundaries; planning a change that spans multiple files or systems; deciding whether to extend an existing service vs build a new one; or asking about how something should be structured. Conversational shapes that should trigger include "help me design X", "I want to build a new Y", "should I use Z for this", "let me add a feature that does W", "where should this live", "is this the right place for Y", and similar. Also fires on slash invocations like /review, /ship, /plan, /refactor when the change is architecture-shaped. Reads the team's ARCHITECTURE.md and interjects only when there's a specific principle to flag for the current context. Stays silent if tstack isn't configured, ARCHITECTURE.md is missing, or no relevant guidance applies.

Surfaces business and product domain context whenever the user is — or is about to be — working in a product area or initiative whose "why", customer, or scope they may not have. Activate on user intent, not just slash commands. Fire when the user is starting work in an unfamiliar product domain; asking "why are we building X", "what's [domain] for", "who's the customer of Y", "what problem does Z solve"; making product or scope decisions that benefit from business context; touching code or process attached to a specific business initiative; mentioning a customer-facing feature without describing the customer. Conversational shapes that should trigger include "why does X exist", "what does [team/product] do", "who uses Y", "what problem does Z solve", "I'm working on the [domain]", "help me understand the [system] business case", "what's the goal of [project]", "what's [product] about". Reads the team's DOMAINS.md and surfaces the relevant initiative, customer, or business rationale. Stays silent if tstack isn't configured, DOMAINS.md is missing, or no relevant domain entry exists.

Surfaces team conventions for shipping code whenever the user is — or is about to be — writing, testing, reviewing, deploying, or operating production code. Activate on user intent, not just slash commands. Fire when the user is writing new code in an existing repo (style, lint, conventions apply); adding or updating tests; preparing a pull request (review process, required checks, branch rules); modifying CI/CD workflows or GitHub Actions; editing Terraform / Pulumi / other IaC; configuring deploys (Heroku, Cloud Run, GCP, staging, prod); touching repo settings managed centrally (branch protection, rulesets, collaborators, autolinks); configuring DNS (DNSimple) or CDN (Fastly); running or debugging tests; releasing or rolling back; configuring observability or alerting; setting up secrets or environment configuration. Conversational shapes that should trigger include "let me add tests for X", "is this ready to merge", "how do we deploy Y", "set up CI for this service", "add a github actions workflow", "configure branch protection", "should I use [tool] for tests", "what's our convention for [code pattern]", "how do we handle migrations", "where does this terraform go", "create a state bucket", "should I deploy to Heroku", "add a fastly rule", "what's our lint config", "how do we name PRs". Also fires on slash invocations like /review, /ship, /plan, /test, /refactor when the work is shipping-shaped. Reads the team's SHIPPING.md and interjects only when there's a specific convention or process to flag for the current context. Stays silent if tstack isn't configured, SHIPPING.md is missing, or no relevant guidance applies.

Captures conclusions, decisions, and identifications from the user's conversation with the agent and offers to write them into the relevant tstack kb file. Activate when the user makes a decision, identifies an owner or vendor, picks a tool, describes a customer or domain, names a service-and-its-maintainer, corrects a stale fact, or otherwise states a fact that one of the other auras (architecture, paved-path, how-we-ship, people, domain) would want in its knowledge base — and that fact isn't already there. Conversational shapes that should trigger include "we decided to use X", "Y owns this", "we're going with Z for [category]", "let's standardize on W", "the [system] is owned by [person/team]", "our customer for [domain] is [profile]", "we don't use [tool] anymore", "from now on we always do X", "the answer is [X]", "[person] is now the [role] for [domain]", "actually it's [correction]", and similar declarative resolutions. Also fires after another aura interjects and the user resolves the question with a substantive answer. Reads the relevant kb file from $TSTACK_KB_DIR/, checks whether the new information is already captured, and if not, drafts an addition. Offers the user the appropriate write workflow — local edit, git commit, push, or pull request via the gh CLI — based on how the kb source is configured. Never writes silently; every step requires explicit confirmation via AskUserQuestion. Stays silent if tstack isn't configured, no kb file matches the statement, the information is already documented, or the discussion is exploratory rather than concluded.

Surfaces team-approved technology choices, vendors, and common recipes whenever the user is — or is about to be — picking a library, framework, vendor, hosting target, or runtime; or starting a how-to task that has a sanctioned recipe. Activate on user intent, not just slash commands. Fire when the user is choosing a library or framework for a non-trivial task; selecting a vendor (auth, payments, email, analytics, CMS, observability, error reporting, etc.); picking a hosting target or runtime (Heroku, GCP, Cloud Run, Vercel, etc.); scaffolding a new project or service; adding a dependency to package.json / requirements.txt / go.mod / pyproject.toml; asking "what do we use for X", "should I use Y or Z", "is W approved here", "what's our default for [category]"; starting a task that has a documented cookbook (e.g., "add a new service", "wire up auth", "set up event bus", "add a webhook handler"). Conversational shapes that should trigger include "I'm going to use [tool]", "let's add [library]", "what's our default for [category]", "should I use [vendor]", "where should I host this", "how do we usually [verb]", "is X approved here", "what tool do we use for Y", "let me install [package]". Also fires on slash invocations like /scaffold, /plan, /new when the choice is technology-shaped. Reads the team's PAVED_PATH.md and interjects only when the team has a specific position on the current choice. Stays silent if tstack isn't configured, PAVED_PATH.md is missing, or no relevant position exists.