BETAekkOS is currently in beta. Please report all bugs to support@ekkos.dev
ekkOS_docs
Core Concepts

Patterns

Save solutions. Retrieve them when you need them.

What is a Pattern?

A pattern is a problem-solution pair that you can save and retrieve later. When you solve a problem, save it. When you face a similar problem, search for it.

Solutions

Approaches that worked — save these for future reference.

Anti-Patterns

What NOT to do — save these to avoid repeating mistakes.

Example Pattern

Use Supabase Auth for Next.jsWorks well

Problem

Need to add authentication to a Next.js application with social logins and email/password.

Solution

Use @supabase/auth-helpers-nextjs with the App Router. Configure providers in Supabase dashboard. Use middleware for route protection.

Works When

  • • Next.js 13+ with App Router
  • • Need social auth (Google, GitHub, etc.)
  • • Using Supabase for database

Avoid

  • Don't roll custom JWT handling
  • Don't store tokens in localStorage

Saving Patterns

Tell your AI to save something when you've solved a problem:

"Remember this for next time"
"Save this pattern: always validate user input before database queries"
"Forge this as an anti-pattern — we should never do this again"

Using Patterns

Patterns are automatically retrieved when relevant. You can also search explicitly:

"Search my memory for authentication patterns"
"What patterns do we have for error handling?"
"How did we solve this before?"

Related