
Tracks Architecture Decision Records (ADRs) in docs/adrs/. Creates, lists, and updates ADRs following project conventions. TRIGGER when: user wants to record, review, or update an architectural decision.
Review code changes (PRs, diffs, branches) against the opinionated TypeScript architecture rules. Checks whether changes align with the architecture — layer dependencies, module boundaries, event patterns, domain purity, and structural conventions. Triggers on phrases like "review this PR", "arch review", "check if this change follows the architecture", "review these changes", "does this PR align with the architecture", or "architecture review". Also invocable via the /tseng:arch-review slash command.
Bootstrap a new greenfield TypeScript client-server project with an opinionated monorepo architecture. Use when the user asks to bootstrap, scaffold, or initialize a new project. Triggers on phrases like "bootstrap my project", "scaffold a new project", "start a new typescript project", "set up my project", or "create a new app". Also invocable via the /tseng:bootstrap slash command.
Pick and implement the next user story from a PRD GitHub issue. Analyzes merged PRs for prior work and findings, proposes a plan, implements it, and creates a PR linking back to the PRD. Use when user says "ralph it", "ralph-it", or wants to work through PRD user stories.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Upgrade a previously bootstrapped or adopted project when the architecture evolves. Diffs the current architecture rules against the project's last locked review, identifies new or changed rules, and proposes incremental changes. Triggers on phrases like "upgrade my project", "sync with latest architecture", "update to new rules", "upgrade tseng", or "architecture changed, update my project". Also invocable via the /tseng:upgrade slash command.
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue after user approval. Use when user wants to write a PRD, create a product requirements document, or plan a new feature. Always present the PRD for user approval before submitting.
Implement an architectural specification as working code. Takes the output of the spec skill (from a GitHub issue, conversation context, or pasted text) and produces working TypeScript code following the project's established conventions and the architecture rules. Triggers on phrases like "build this spec", "implement this spec", "build it", "implement the feature", "code this up", or "turn this spec into code". Also invocable via the /tseng:build-it slash command.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Spec out a feature or change with full knowledge of the opinionated TypeScript architecture and the project's adoption state. Conducts a thorough discovery interview to understand domain concerns, bounded contexts, and application services, then produces a high-level architectural specification — never concrete implementation details. Triggers on phrases like "spec this feature", "design this change", "architect this", "help me spec", "what modules do I need", or "think through this feature". Also invocable via the /tseng:spec slash command.
Check and align a repo's .claude/settings.json and CLAUDE.md with team conventions. Use when the user wants to standardize a repo, align conventions, check settings, or bootstrap Claude Code config in a new project.
Adopt the opinionated TypeScript architecture in an existing project. Runs a review first, then proposes incremental changes the user can accept or discard. Remembers discarded proposals so they aren't re-suggested. Triggers on phrases like "adopt the architecture", "migrate my project", "align my project with the rules", "adopt tseng", or "make my project conform". Also invocable via the /tseng:adopt slash command.
Review an existing TypeScript project against the opinionated architecture rules. Use when the user asks to review, audit, check, or validate their project's architecture. Triggers on phrases like "review my project", "check the architecture", "audit my code structure", "validate my project", or "does my project follow the rules". Also invocable via the /tseng:review slash command.