@shahmilsaari/memory-core 0.2.8 → 0.2.11

package/dist/db-KU4EEG4Y.js

@@ -0,0 +1,28 @@
+#!/usr/bin/env node
+import {
+  closePool,
+  deleteMemory,
+  getMemory,
+  getPool,
+  hashMemoryContent,
+  listMemories,
+  runMigrations,
+  saveMemory,
+  searchMemories,
+  updateMemory,
+  upsertMemory
+} from "./chunk-73SRPNAL.js";
+import "./chunk-KSLFLWB4.js";
+export {
+  closePool,
+  deleteMemory,
+  getMemory,
+  getPool,
+  hashMemoryContent,
+  listMemories,
+  runMigrations,
+  saveMemory,
+  searchMemories,
+  updateMemory,
+  upsertMemory
+};

package/dist/embedding-PAYD2JYW.js

@@ -0,0 +1,8 @@
+#!/usr/bin/env node
+import {
+  embed
+} from "./chunk-HAGRPKR3.js";
+import "./chunk-KSLFLWB4.js";
+export {
+  embed
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shahmilsaari/memory-core",
-  "version": "0.2.8",
+  "version": "0.2.11",
   "description": "Universal AI memory core — generate AI context files from architecture profiles with RAG support",
   "type": "module",
   "bin": {
@@ -13,8 +13,10 @@
   ],
   "scripts": {
     "build": "tsup",
+    "typecheck": "tsc --noEmit",
     "dev": "tsx src/cli.ts",
-    "start": "node dist/cli.js"
+    "start": "node dist/cli.js",
+    "test": "node --import tsx --test test/**/*.test.ts"
   },
   "dependencies": {
     "@inquirer/prompts": "^5.0.0",

package/profiles/go-api.yml

@@ -0,0 +1,43 @@
+name: go-api
+displayName: Go REST API
+layer: backend
+description: Go REST API with clean package structure, idiomatic error handling, and testability
+
+rules:
+  - Organize code into cmd/, internal/, and pkg/ — cmd/ holds main packages, internal/ holds private packages, pkg/ holds public packages
+  - HTTP handlers are thin — parse request, call service, write response. No business logic.
+  - Services own all business logic — they accept and return domain types, not HTTP types
+  - Always pass context.Context as the first parameter for cancellation and deadline propagation
+  - Return errors explicitly — never panic in library or service code. Reserve panic only for unrecoverable startup failures.
+  - Wrap errors with context using fmt.Errorf("operation: %w", err) to preserve the original error
+  - Define small, single-method interfaces at the point of use, not at the point of implementation
+  - Use struct-based request/response types for all handler inputs and outputs
+  - Validate all incoming request data before passing to the service layer
+  - Configuration comes from environment variables — use a dedicated Config struct loaded at startup with validation
+  - Use structured logging (slog or zerolog) — never log with fmt.Println in production code
+  - Implement graceful shutdown — catch SIGINT/SIGTERM and drain in-flight requests before exiting
+  - Use table-driven tests with t.Run() for all unit tests
+  - Register middleware at the router level — never call middleware logic inside handlers
+  - Database calls live in a repository layer — services never import database drivers directly
+
+folders:
+  - cmd/api/
+  - cmd/api/main.go
+  - internal/handler/
+  - internal/service/
+  - internal/repository/
+  - internal/domain/
+  - internal/middleware/
+  - internal/config/
+  - pkg/
+  - api/
+
+avoid:
+  - Global mutable state outside of the DI wiring in main.go
+  - Business logic inside HTTP handlers
+  - Direct database calls in service layer
+  - Ignoring returned errors (assign to _ only when truly safe)
+  - Naked returns in functions longer than a few lines
+  - Using init() for configuration — use explicit constructors instead
+  - Panicking in non-main code
+  - Mixing HTTP concerns with domain logic

package/profiles/nextjs.yml

@@ -1,32 +0,0 @@
-name: nextjs
-displayName: Next.js App Router
-layer: fullstack
-description: Next.js 13+ App Router with server components, server actions, and colocation
-
-rules:
-  - Use Server Components by default — add 'use client' only when interactivity is required
-  - Data fetching happens in Server Components, not client hooks
-  - Use Server Actions for form mutations and data writes
-  - Keep page.tsx files thin — delegate to feature components
-  - Colocate components, hooks, and utilities near the route that uses them
-  - Shared UI lives in src/components/, shared logic in src/lib/
-  - API routes are for external integrations only — prefer Server Actions for internal mutations
-  - Use Route Groups to organize without affecting URL structure
-  - Environment variables exposed to client must be prefixed NEXT_PUBLIC_
-
-folders:
-  - app/(routes)
-  - app/api
-  - src/components/ui
-  - src/components/features
-  - src/lib/utils
-  - src/lib/actions
-  - src/lib/db
-  - src/types
-
-avoid:
-  - Data fetching in Client Components (use Server Components instead)
-  - useEffect for data loading
-  - Business logic inside page.tsx
-  - Mixing server and client code in the same file
-  - Exposing secrets via NEXT_PUBLIC_ variables