🧩 GITHUB COPILOT MASTER PROMPT — BYWAY ISOLATED PLUGIN SYSTEM

You are coding inside Byway, a modular plugin-based learning platform.

🔒 Core Principles

Plugin Isolation
- Every plugin has its own Prisma schema, generated client, and DB file.
- Never import another plugin’s Prisma client or schema.
- Never perform Prisma joins across plugins.
- Each plugin’s data access stays inside its own
```
/server/db
```
  folder.
Cross-plugin Communication
- Plugins talk to each other strictly through HTTP or GraphQL APIs.
- Example ✅
```
await $fetch('/api/teach/courses/' + courseId)
```
- Example ❌
```
import { PrismaClient } from '../../teach/server/db/generated/client'
```
- All “relations” across plugins are expressed as API requests and verified in the service layer.
Business Logic Integrity
- Enforce production-grade business rules through resolvers, not Prisma foreign keys:
  - If a user is enrolled → they can’t add that course to cart.
  - If an order is paid → create an enrollment automatically.
  - If a teacher isn’t verified → block publishing.
- All these checks happen in GraphQL mutations or REST routes.
Prisma Schema Discipline
- Each plugin models foreign entities by
```
id
```
  only (
```
studentId
```
  ,
```
courseId
```
  , etc.).
- Never add real foreign keys to another plugin’s DB.
- Always include
```
createdAt
```
  ,
```
updatedAt
```
  , and relevant status enums.
GraphQL + API Rules
- Use Nexus
```
objectType
```
  ,
```
mutationField
```
  ,
```
queryField
```
  conventions.
- Don’t leak raw Prisma types — explicitly map fields.
- Fetch related data through API calls or remote resolvers.
- Always validate input and throw clear errors.
Production Mindset
- Each plugin exposes:
  - ```
  /server/graphql/
```
  → GraphQL types & resolvers
- ```
/server/api/
```
    → REST endpoints for other plugins
  - ```
  /nuxt/
```
  → Client pages and components
- Use Ant Design Vue for UI.
- All async operations must be safe, validated, and idempotent.
Global Coordination
- The core orchestrator dynamically loads plugins and registers their GraphQL endpoints.
- Shared entities (User, Auth, Session) live only in
```
authentication
```
  , and are queried over APIs.

🧩 Copilot Instruction Mode

Whenever asked to build, connect, or refactor models:

Keep all Prisma operations scoped to the current plugin.
Express inter-plugin “relations” through API contracts.
Add business rules enforcing common-sense consistency.
Ensure schema fields reflect those logical relations with IDs and status fields.
Generate TypeScript + Nexus GraphQL + REST/Fetch logic in a production-ready style.

🧠 Golden Rule

“Each plugin is its own service. Relations exist only through APIs — not Prisma joins.”

🚀 YOUR NEXT PROMPT BELOW THIS LINE

🔒 Core Principles

Plugin Isolation

Every plugin has its own Prisma schema, generated client, and DB file.
Never import another plugin’s Prisma client or schema.
Never perform Prisma joins across plugins.
Each plugin’s data access stays inside its own
```
/server/db
```
folder.

Cross-plugin Communication

Plugins talk to each other strictly through HTTP or GraphQL APIs.

Example ✅

await $fetch('/api/teach/courses/' + courseId)

Example ❌

import { PrismaClient } from '../../teach/server/db/generated/client'

All “relations” across plugins are expressed as API requests and verified in the service layer.

Business Logic Integrity

Enforce production-grade business rules through resolvers, not Prisma foreign keys:
- If a user is enrolled → they can’t add that course to cart.
- If an order is paid → create an enrollment automatically.
- If a teacher isn’t verified → block publishing.
All these checks happen in GraphQL mutations or REST routes.

Prisma Schema Discipline

Each plugin models foreign entities by
```
id
```
only (
```
studentId
```
,
```
courseId
```
, etc.).
Never add real foreign keys to another plugin’s DB.
Always include
```
createdAt
```
,
```
updatedAt
```
, and relevant status enums.

GraphQL + API Rules

Use Nexus
```
objectType
```
,
```
mutationField
```
,
```
queryField
```
conventions.
Don’t leak raw Prisma types — explicitly map fields.
Fetch related data through API calls or remote resolvers.
Always validate input and throw clear errors.

Production Mindset

Each plugin exposes:
- ```
/server/graphql/
```
  → GraphQL types & resolvers
- ```
/server/api/
```
  → REST endpoints for other plugins
- ```
/nuxt/
```
  → Client pages and components
Use Ant Design Vue for UI.
All async operations must be safe, validated, and idempotent.

Global Coordination

The core orchestrator dynamically loads plugins and registers their GraphQL endpoints.
Shared entities (User, Auth, Session) live only in
```
authentication
```
, and are queried over APIs.

🧩 Copilot Instruction Mode

Whenever asked to build, connect, or refactor models:

Keep all Prisma operations scoped to the current plugin.

Express inter-plugin “relations” through API contracts.

Add business rules enforcing common-sense consistency.

Ensure schema fields reflect those logical relations with IDs and status fields.

Generate TypeScript + Nexus GraphQL + REST/Fetch logic in a production-ready style.

🧩 GITHUB COPILOT MASTER PROMPT — BYWAY ISOLATED PLUGIN SYSTEM

🧩 GITHUB COPILOT MASTER PROMPT — BYWAY ISOLATED PLUGIN SYSTEM

🔒 Core Principles

🧩 Copilot Instruction Mode

🧠 Golden Rule

🚀 YOUR NEXT PROMPT BELOW THIS LINE

Related Skills

Markdown Converter

Nano Banana Pro

1password

🧩 GITHUB COPILOT MASTER PROMPT — BYWAY ISOLATED PLUGIN SYSTEM

🔒 Core Principles

🧩 Copilot Instruction Mode

🧠 Golden Rule

🚀 YOUR NEXT PROMPT BELOW THIS LINE