Results for “normen”

Establish team norms for collaboration and communication. TRIGGERS - Use when user needs help with team-norms related tasks.

Establish team norms for collaboration and communication. TRIGGERS - Use when user needs help with team-norms related tasks.

Standard reviewer for correctness and reproducibility. Use when the user asks to talk to Omen, requests a code review, or needs reproducibility verification.

Enforce idiomatic Rust patterns for ownership, error handling, enums, traits, concurrency, and best practices to build safe, performant applications.

Enumerating failure modes via pre-mortem analysis. Systematically identifies failure scenarios for plans, designs, and features, scoring them with RPN/AP. Does not write code.

Nocaps: Novel Object Captioning at Scale

Strip a problem to its irreducible fundamental truths and rebuild the solution from the ground up — free from analogy, convention, and inherited assumptions. Load when the user feels constrained by how something has always been done, when existing solutions feel expensive or inefficient for no good reason, when the user asks to think from first principles, challenge the fundamentals, or rebuild this from scratch. Also triggers on "why does it have to work this way", "what are the actual constraints here", "ignore what everyone else does", or when deep-thinking diagnoses a convention-break frame. Based on Aristotle's first principles method, popularised by Musk and Feynman. Produces genuinely novel solutions by eliminating convention.

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.

Build a bilingual terminology glossary and style guide that enforces consistency across a translation project.

Establishes baseline coding conventions for naming, readability, immutability, and code-quality review across projects.

Establish clear naming conventions for design assets, components, and tokens to make design systems predictable and maintainable.

Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs.

Architects, reviews, and scales backend systems with structured blueprints, trade-off analysis, and audit reports.

Defines structural schemas, data ontologies, and interaction boundaries for autonomous entities and synthetic data architectures.

.NET backend conventions, patterns, and test infrastructure. Use when working with C# files, .csproj projects, ASP.NET APIs, xUnit tests, FluentAssertions, Entity Framework, WebApplicationFactory, dotnet CLI, NuGet packages, .NET dependency injection, middleware, or controller patterns.

Token Standards

Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs.

Apply core PHP language standards and modern 8.x features. Use when working with PHP 8.x features like enums, fibers, readonly properties, or named arguments.