ertzu-project-architect

name	ertzu-project-architect
description	Use when planning, reviewing, or changing ERTZU architecture, route structure, service boundaries, deployment readiness, or repository instructions.

ERTZU Project Architect

When To Use

Use this skill before changing app structure, route organization, data boundaries, deployment setup, shared helpers, project instructions, or any cross-cutting marketplace workflow.

ERTZU-Specific Instructions

• Preserve ERTZU as a product-centered verified luxury perfume marketplace.
• Keep canonical marketplace browsing on /listings and /listings/[id].
• Do not convert products back into individual seller listing pages.
• Read AGENTS.md, docs/ai/PROJECT_CONTEXT.md, docs/ai/ARCHITECTURE.md, and relevant Next.js docs in node_modules/next/dist/docs/ before editing.
• Prefer the existing App Router, Supabase, Tailwind token, and helper patterns.
• Keep changes scoped. Separate docs, schema, route, and UI changes unless a task explicitly requires a combined release.

Files And Areas To Inspect

• package.json
• next.config.ts
• tsconfig.json
• eslint.config.mjs
• src/app/layout.tsx
• src/app/page.tsx
• src/app/listings/page.tsx
• src/app/listings/[id]/page.tsx
• src/lib/supabase.ts
• src/lib/supabase-server.ts
• src/lib/market.ts
• src/lib/matching.ts
• supabase/*.sql
• supabase/migrations/*.sql
• .github/workflows/supabase-migrations.yml
• docs/ai/*.md

Concrete Checks

• Confirm whether a change affects product pages, asks, bids, orders, admin, payments, email, or profile data.
• Confirm the latest relevant SQL file before relying on a table, RPC, policy, or view definition.
• Check whether a route is a Client Component and whether server-only secrets could leak through imports.
• Check that new behavior has a migration, RLS/RPC authorization, and UI copy aligned with ERTZU verification.
• Check that docs reflect command, architecture, security, or marketplace changes.
• Run npm run lint and npm run build after code changes when feasible.

Mistakes To Avoid

• Do not rebuild the project from scratch.
• Do not add a broad data layer just to tidy existing Supabase queries.
• Do not introduce a new design system while src/app/globals.css already contains tokens and primitives.
• Do not change database behavior without checking RLS, RPC grants, and migration order.
• Do not treat frontend auth checks as sufficient authorization.
• Do not install new packages without explicit approval.