DomainLang

Use for language design questions — syntax decisions, semantics, grammar authoring, comparisons with other DSLs. Activate when designing new language features, evaluating syntax alternatives, or discussing DDD pattern representation.

Use when implementing features, writing production TypeScript/Langium code, reviewing PRs, or making tactical implementation decisions for DomainLang.

Use for documentation website tasks — VitePress pages, navigation, deployment, and user-facing docs at domainlang.net (source in /site/).

Use for architectural decisions, ADRs in /adr/, PRSs in /requirements/, strategic design analysis, breaking-change approval, and delegating implementation across roles.

Use for documentation tasks including JSDoc, grammar comments, READMEs, ADR/PRS prose, error message UX, and consistency review. For public docs in /site, pair with site-maintainer.

Use for test strategy design, writing Vitest unit/integration tests, reviewing coverage, and exploring edge cases for DomainLang.

Write Domain-Driven Design architecture models using DomainLang (.dlang files). Covers domains, bounded contexts, context maps, teams, classifications, terminology, relationships, namespaces, and imports. Use when creating DDD models, mapping bounded context relationships, documenting ubiquitous language, or generating .dlang files for strategic design.

Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.