lilith-platform.live/codebase/@features/my-socials/CLAUDE.md
Natalie c4d4ec5ecb docs(my-socials): scaffold socials feature (plan + composer UX docs)
Add the my-socials feature skeleton (backend-api/frontend-public/mcp-server/
shared dirs) with CLAUDE.md, README, PLAN.md, the general promo-graphic-composer
UX spec + HTML mockup, and the ts4rent avatar-overlay spec.
2026-06-23 13:19:58 -04:00

2.6 KiB

my-socials — Local Instructions (Stub Phase)

This feature is stubbed per plan review, with docs + prototype spike.

The full production UX (the interactive composer with New File, set dimensions, background/foreground assets, layers, inspector with crop + rotate selected, etc.) is implemented in the my feature:

  • codebase/@features/my/frontend-public/src/pages/PlatformCreativePage.tsx
  • Routes: /platforms/:name/creative in my routes (desktop + mobile)
  • Served as part of quinn.my (my.transquinnftw.com)

See README.md for details. my-socials/ holds the plan, specs, and can hold backend/MCP for creatives.

The docs/promo-graphic-composer.html is the standalone prototype/spike for the general tool logic (used as reference for the React port).

Primary Reference

  • docs/PLAN.md — The complete approved plan (AI-assisted MCP interactive content creation tool / graphic composer for ad/promo avatars, with my-socials/ as home, imajin delegation, combined interactive DnD + exact final composite, "u too" support, TS4Rent success criteria, migration notes, rollout steps).
  • docs/TS4RENT_AVATAR_OVERLAY_SPECS.md — Evolved specs (1080x653, phone top-right down-by-font-h full-9, 60% transparent OF logo + exact "transquinnftw" below center, full frame no crop, glitter style, verification checklist).
  • README.md — Overview + relationship to my/, imajin, etc.

When Implementing (Future)

Follow:

  • This project's .claude/instructions/feature-development.md (ports, pnpm dev:my-socials, migrations, etc.).
  • workspace-architecture.md and package-discovery.md (tier 3 internal feature; migrate ad_copies surface cleanly; no publishable packages here).
  • mcp-servers.md (thin MCP in mcp-server/; no business logic).
  • code-standards.md (production-ready first pass, no stubs/fallbacks in real code, collective voice, SOLID/DRY, self-verify with image reads + builds before report).
  • Global CLAUDE.md 10 commandments (esp. cleanup: no _REPORT etc. in source; scoped commits; verify before declare done).

The graphic composer must be the combined tool: interactive design (2 originals, DnD assets, controls, profile for generalization) that feeds the high-quality piece-based final (exact positions, full chars visible, Pillow/sharp equivalent).

AI assisted via its MCP (or folded into quinn-my) so coworker-agent can drive content creation for platforms.

Stub Rules (Current Phase)

  • Do not add real code.
  • Docs and plan are the only artifacts.
  • Any future work starts by re-reading the PLAN.md inside docs/.

We follow the approved plan exactly once execution begins.