zaid.marzguioui/myeasycms-v2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Claude sub-agents, PRD, MCP improvements (#359)

Browse Source 
1. Added Claude Code sub-agents
2. Added PRD tool to MCP Server
3. Added MCP Server UI to Dev Tools
4. Improved MCP Server Database Tool
5. Updated dependencies
This commit is contained in:
Giancarlo Buomprisco
2025-09-25 12:03:53 +08:00
committed by GitHub
parent 02e2502dcc
commit 2b8572baaa
62 changed files with 5661 additions and 1231 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
apps/web/package.json
View File

@@ -54,14 +54,14 @@
"@makerkit/data-loader-supabase-core": "^0.0.10",
"@makerkit/data-loader-supabase-nextjs": "^1.2.5",
"@marsidev/react-turnstile": "^1.3.1",
"@nosecone/next": "1.0.0-beta.11",
"@nosecone/next": "1.0.0-beta.12",
"@radix-ui/react-icons": "^1.3.2",
"@supabase/supabase-js": "2.57.4",
"@tanstack/react-query": "5.89.0",
"@tanstack/react-query": "5.90.2",
"@tanstack/react-table": "^8.21.3",
"date-fns": "^4.1.0",
"lucide-react": "^0.544.0",
"next": "15.5.3",
"next": "15.5.4",
"next-sitemap": "^4.2.3",
"next-themes": "0.4.6",
"react": "19.1.1",
@@ -76,7 +76,7 @@
"@kit/eslint-config": "workspace:*",
"@kit/prettier-config": "workspace:*",
"@kit/tsconfig": "workspace:*",
"@next/bundle-analyzer": "15.5.3",
"@next/bundle-analyzer": "15.5.4",
"@tailwindcss/postcss": "^4.1.13",
"@types/node": "^24.5.2",
"@types/react": "19.1.13",
@@ -85,7 +85,7 @@
"cssnano": "^7.1.1",
"pino-pretty": "13.0.0",
"prettier": "^3.6.2",
"supabase": "2.40.7",
"supabase": "2.45.5",
"tailwindcss": "4.1.13",
"tailwindcss-animate": "^1.0.7",
"typescript": "^5.9.2"

28
apps/web/supabase/AGENTS.md
View File

@@ -10,25 +10,30 @@ Migrations are generated from schemas. If creating a new schema, the migration c
If modifying an existing migration, use the `diff` command:
### 1. Creating New Schema Files
### 1. Creating new entities
When creating new entities (such as creating a new tabble), we can create a migration as is, just copying its content.
```bash
# Create new schema file
touch apps/web/supabase/schemas/15-my-new-feature.sql
# Apply changes and create migration
pnpm --filter web run supabase:db:diff -f my-new-feature
# Create Migration
pnpm --filter web run supabase migrations new my-new-feature
# Restart Supabase with fresh schema
pnpm supabase:web:reset
# Copy content to migration
cp apps/web/supabase/schemas/15-my-new-feature.sql apps/web/supabase/migrations/$(ls -t apps/web/supabase/migrations/ | head -n1)
# Apply migration
pnpm --filter web supabase migrations up # alternatively reset db with pnpm supabase:web:reset
# Generate TypeScript types
pnpm supabase:web:typegen
```
Verify the diff command generated the same content as the schema; if not, take steps to fix the migration.
### 2. Modifying existing entities
### 2. Modifying Existing Schemas
When modifying existing entities (such ass adding a field to an existing table), we can use the `diff` command to generate a migration following the changes:
```bash
# Edit schema file (e.g., schemas/03-accounts.sql)
@@ -38,7 +43,7 @@ Verify the diff command generated the same content as the schema; if not, take s
pnpm --filter web run supabase:db:diff -f update-accounts
# Apply and test
pnpm supabase:web:reset
pnpm --filter web supabase migrations up # alternatively reset db with pnpm supabase:web:reset
# After resetting
pnpm supabase:web:typegen
@@ -244,7 +249,7 @@ Add triggers if the properties exist and are appropriate:
```bash
# View migration status
pnpm --filter web supabase migration list
pnpm --filter web supabase migrations list
# Reset database completely
pnpm supabase:web:reset
@@ -252,6 +257,9 @@ pnpm supabase:web:reset
# Generate migration from schema diff
pnpm --filter web run supabase:db:diff -f migration-name
## Apply created migration
pnpm --filter web supabase migrations up
# Apply specific migration
pnpm --filter web supabase migration up --include-schemas public
pnpm --filter web supabase migrations up --include-schemas public
```

28
apps/web/supabase/CLAUDE.md
View File

@@ -10,25 +10,30 @@ Migrations are generated from schemas. If creating a new schema, the migration c
If modifying an existing migration, use the `diff` command:
### 1. Creating New Schema Files
### 1. Creating new entities
When creating new entities (such as creating a new tabble), we can create a migration as is, just copying its content.
```bash
# Create new schema file
touch apps/web/supabase/schemas/15-my-new-feature.sql
# Apply changes and create migration
pnpm --filter web run supabase:db:diff -f my-new-feature
# Create Migration
pnpm --filter web supabase migrations new my-new-feature
# Restart Supabase with fresh schema
pnpm supabase:web:reset
# Copy content to migration
cp apps/web/supabase/schemas/15-my-new-feature.sql apps/web/supabase/migrations/$(ls -t apps/web/supabase/migrations/ | head -n1)
# Apply migration
pnpm --filter web supabase migrations up # alternatively reset db with pnpm supabase:web:reset
# Generate TypeScript types
pnpm supabase:web:typegen
```
Verify the diff command generated the same content as the schema; if not, take steps to fix the migration.
### 2. Modifying existing entities
### 2. Modifying Existing Schemas
When modifying existing entities (such ass adding a field to an existing table), we can use the `diff` command to generate a migration following the changes:
```bash
# Edit schema file (e.g., schemas/03-accounts.sql)
@@ -38,7 +43,7 @@ Verify the diff command generated the same content as the schema; if not, take s
pnpm --filter web run supabase:db:diff -f update-accounts
# Apply and test
pnpm supabase:web:reset
pnpm --filter web supabase migrations up # alternatively reset db with pnpm supabase:web:reset
# After resetting
pnpm supabase:web:typegen
@@ -244,7 +249,7 @@ Add triggers if the properties exist and are appropriate:
```bash
# View migration status
pnpm --filter web supabase migration list
pnpm --filter web supabase migrations list
# Reset database completely
pnpm supabase:web:reset
@@ -252,6 +257,9 @@ pnpm supabase:web:reset
# Generate migration from schema diff
pnpm --filter web run supabase:db:diff -f migration-name
## Apply created migration
pnpm --filter web supabase migrations up
# Apply specific migration
pnpm --filter web supabase migration up --include-schemas public
pnpm --filter web supabase migrations up --include-schemas public
```