Update AGENTS.md file and db schema
This commit is contained in:
@@ -11,6 +11,20 @@ Read `WORKSPACE_MEMORY.md` before making structural changes to page code.
|
|||||||
- **Icons:** `lucide-react`.
|
- **Icons:** `lucide-react`.
|
||||||
- **Validation:** `zod` v4 (`[email protected]`).
|
- **Validation:** `zod` v4 (`[email protected]`).
|
||||||
|
|
||||||
|
## MCP Tool Usage Guidelines
|
||||||
|
|
||||||
|
When building, refactoring, styling, or auditing UI components and layouts, actively invoke these configured MCP servers:
|
||||||
|
|
||||||
|
### 1. `design-mcp` (UI/UX Engineering & Design Standards)
|
||||||
|
|
||||||
|
- **When to call:** Before constructing new page layouts, design systems, empty/loading states, or interactive UI flows.
|
||||||
|
- **Instruction:** Query `design-mcp` to ensure accessibility (a11y), proper layout hierarchy, visual balance, and consistent interaction patterns across application workflows.
|
||||||
|
|
||||||
|
### 2. `design-systems` (Design System Specs & Reference Patterns)
|
||||||
|
|
||||||
|
- **When to call:** When creating or extending reusable component interfaces, verifying design token structures, or inspecting component composition patterns.
|
||||||
|
- **Instruction:** Query `design-systems` to pull canonical UI patterns, atomic component guidelines, and standard prop naming conventions before creating custom components.
|
||||||
|
|
||||||
## Entrypoint
|
## Entrypoint
|
||||||
|
|
||||||
`src/server.ts` — runs `bunextInit()`, initializes a persistent **Piper TTS daemon** (global `PIPER_MANAGER`), starts `Bun.serve` with WebSocket upgrade on `/ws`, then starts cron.
|
`src/server.ts` — runs `bunextInit()`, initializes a persistent **Piper TTS daemon** (global `PIPER_MANAGER`), starts `Bun.serve` with WebSocket upgrade on `/ws`, then starts cron.
|
||||||
|
|||||||
@@ -149,6 +149,19 @@ const schema: BUN_SQLITE_DatabaseSchemaType = {
|
|||||||
},
|
},
|
||||||
],
|
],
|
||||||
},
|
},
|
||||||
|
{
|
||||||
|
tableName: "clients",
|
||||||
|
fields: [
|
||||||
|
{
|
||||||
|
fieldName: "user_id",
|
||||||
|
dataType: "INTEGER",
|
||||||
|
},
|
||||||
|
{
|
||||||
|
fieldName: "ip_address",
|
||||||
|
dataType: "TEXT",
|
||||||
|
},
|
||||||
|
],
|
||||||
|
},
|
||||||
],
|
],
|
||||||
};
|
};
|
||||||
|
|
||||||
|
|||||||
Executable
+11
@@ -0,0 +1,11 @@
|
|||||||
|
#!/bin/bash
|
||||||
|
|
||||||
|
# This script installs wireguard on the host system.
|
||||||
|
# Depending on the OS, whether Debian, or Fedora, or Arch,
|
||||||
|
# this script selects the appropriate package manager and
|
||||||
|
# packages to install to get wireguard working
|
||||||
|
# This script will run as root, to have full access needed
|
||||||
|
# to setup wireguard
|
||||||
|
# This script will also be idempotent, so that it doesn't
|
||||||
|
# have to install repeatedly if the required tools and
|
||||||
|
# packages are alread installed.
|
||||||
Reference in New Issue
Block a user