CtrlK
BlogDocsLog inGet started
Tessl Logo

emerge/architecture-patterns

Knowledge base for architecture patterns, trade-offs, and selection criteria. Activates when recommending or evaluating architecture patterns like microservices, monolith, serverless, event-driven, CQRS, or hybrid approaches.

88

1.12x
Quality

82%

Does it follow best practices?

Impact

99%

1.12x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-4/

{
  "context": "Tests whether the agent identifies and flags all known red-flag anti-patterns in a proposed architecture: microservices sharing a database, event sourcing without replay testing, serverless with persistent connections, and CQRS applied to a simple CRUD service.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Distributed monolith flag",
      "description": "review.md flags the microservices-with-shared-database combination as a distributed monolith, or uses equivalent language indicating the services are not truly independent",
      "max_score": 25
    },
    {
      "name": "Event sourcing data loss flag",
      "description": "review.md flags event sourcing without replay testing as a data loss risk",
      "max_score": 20
    },
    {
      "name": "Serverless wrong pattern flag",
      "description": "review.md flags the use of serverless functions for the persistent WebSocket connection as an inappropriate pattern choice for that workload",
      "max_score": 20
    },
    {
      "name": "CQRS over-engineering flag",
      "description": "review.md flags CQRS on the simple CRUD user management service as over-engineered",
      "max_score": 20
    },
    {
      "name": "Does not approve uncritically",
      "description": "review.md does NOT endorse or validate the proposed architecture without raising the above concerns",
      "max_score": 15
    }
  ]
}

evals

SKILL.md

tile.json