mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Add Personality Prisma Schema and Backend #130

New Issue
Closed
opened 2026-01-30 21:29:00 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-30 21:29:00 +00:00
Owner
Copy Link

Implement Personality system backend with database schema.

Objective: Create backend for personality/assistant configuration system. UI already exists but needs backend implementation.

Tasks:

  • Add Personality model to schema.prisma
  • Define fields: id, name, display_name, system_prompt, temperature, max_tokens, llm_provider_id
  • Create migration
  • Create personality.service.ts
  • Create personality.controller.ts
  • Implement CRUD operations
  • Add personality-prompt.builder.ts for template rendering
  • Write unit and E2E tests

Acceptance Criteria:

  • UI can create/edit personalities end-to-end
  • Personalities persist to database
  • Prompt templates render correctly
  • Tests pass with 85%+ coverage
  • Existing UI works with new backend

Related: Epic #121, Phase 2 Personality Backend
Replaces/Implements: #82
Depends on: #128 (LlmProviderInstance schema)

Implement Personality system backend with database schema. Objective: Create backend for personality/assistant configuration system. UI already exists but needs backend implementation. Tasks: - Add Personality model to schema.prisma - Define fields: id, name, display_name, system_prompt, temperature, max_tokens, llm_provider_id - Create migration - Create personality.service.ts - Create personality.controller.ts - Implement CRUD operations - Add personality-prompt.builder.ts for template rendering - Write unit and E2E tests Acceptance Criteria: - UI can create/edit personalities end-to-end - Personalities persist to database - Prompt templates render correctly - Tests pass with 85%+ coverage - Existing UI works with new backend Related: Epic #121, Phase 2 Personality Backend Replaces/Implements: #82 Depends on: #128 (LlmProviderInstance schema)
jason.woltje added the databasephase-2databasep0apiapi labels 2026-01-30 21:29:00 +00:00
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-01-30 23:40:48 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api api database database p0 phase-2
Milestone
No items
No Milestone M4-LLM (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#130
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?