💜

Symmony Skin

ร้านค้าออนไลน์สกินแคร์

E-commerce

Access URLs

💬Discord#web-symmonyskin

ข้อมูลทางเทคนิค

Directory

apps/symmonyskin

Schema

app_symmonyskin

Dev Port

3204

Type

E-commerce

Agent Rules (CLAUDE.md)

Symmony Skin — AI Agent Scope Rules

This file defines the strict boundaries for any AI agent working on this app. Violations of these rules may break other websites in the monorepo.

Identity

  • App: Symmony Skin (ร้านค้าออนไลน์ Symmony Skin)
  • Directory: apps/symmonyskin/
  • Database Schema: app_symmonyskin
  • CMS Admin: /cms
  • Dev Port: 3204
  • Type: E-commerce (ใช้ @platform/cms-ecommerce)

Allowed Scope

You may ONLY modify files inside apps/symmonyskin/. Specifically:

apps/symmonyskin/src/app/          — Pages, layouts, routes
apps/symmonyskin/src/components/   — UI components
apps/symmonyskin/src/lib/          — Utilities, queries, types
apps/symmonyskin/src/payload/      — CMS collections and globals
apps/symmonyskin/public/           — Static assets (images, icons)
apps/symmonyskin/src/styles/       — CSS/Tailwind styles

Forbidden Actions

NEVER do any of the following:

  1. Modify files outside apps/symmonyskin/ — especially:

    • apps/bhwc/, apps/pollaphat/, apps/horhomeplus/
    • packages/cms-core/, packages/cms-theme/, packages/cms-ecommerce/
    • Root config files (pnpm-lock.yaml, turbo.json, tsconfig.json)
  2. Modify database configuration — never change:

    • schemaName in payload.config.ts
    • DATABASE_URI in .env.local
    • Any migration files that affect other schemas
  3. Modify payment processing logic — never change:

    • Payment gateway credentials or config
    • Order calculation logic (pricing, tax, shipping)
    • Payment callback/webhook handlers
    • ถ้าต้องแก้ pricing → แก้ผ่าน CMS Admin เท่านั้น
  4. Install/remove packages at root level — never run:

    • pnpm add at workspace root
    • pnpm remove at workspace root
  5. Push directly to main or develop — always use feature branches

  6. Delete data — never run destructive database operations

  7. Modify shared package types — never change anything in packages/

E-commerce Specific Rules

  • Product prices → change via CMS Admin (/cms), never in code
  • Order status → change via CMS Admin, never via scripts
  • Inventory → manage via CMS Admin
  • Payment settings → only admin can change, never via agent
  • Coupon/discount logic → comes from shared package, do not override

Safe Package Installation

# Correct — scoped to symmonyskin
pnpm --filter symmonyskin add <package-name>

# WRONG — affects entire monorepo
pnpm add <package-name>

Branch & Commit Convention

  • Branch: feat/symmonyskin-<topic> or fix/symmonyskin-<topic>
  • Commit: feat(symmonyskin): <summary> or fix(symmonyskin): <summary>
  • PR title: [symmonyskin] <summary>

Before Submitting a PR

  1. Run pnpm --filter symmonyskin build — must pass
  2. Verify no files outside apps/symmonyskin/ were modified
  3. Extra for e-commerce: Test checkout flow end-to-end if UI was changed
  4. Provide tunnel URL for team review
  5. List all changed files in PR description

CMS Data Management

  • Content/product changes → do through CMS Admin at /cms, not code
  • Schema changes → modify files in apps/symmonyskin/src/payload/
  • After schema changes → restart dev server to apply migrations

Cross-Site Change Request

If a task legitimately requires changes to shared packages:

  1. STOP — do not proceed
  2. Report to the team: "This task requires changes to shared code that affects all websites"
  3. Wait for explicit approval with cross-site-change: approved
  4. Only then proceed, with extra caution and testing of ALL affected apps