thermondo/tstack (architecture-aura)

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.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/thermondo/tstack

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.