.cursor/skills/lyx-admin-api-expert/SKILL.md
Expert on the Lyx Admin API: Express routes, MongoDB models, auth, storage, draft/publish lifecycle, runtime API. Use when modifying API routes, models, or debugging server-side issues.
npx skillsauth add imenesesl/lyx lyx-admin-api-expertInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
/api/health — public, checks process + MongoDB + S3 storage/api/auth/* — rate-limited (30/15min), JWT for /me and /alias/api/apps/* — JWT required, scoped to req.auth.accountId/api/mfes/* — JWT required, scoped to account/api/layouts/* — GET public, write operations JWT/api/runtime/:accountId/:slug/* — public, reads published configsPOST /api/apps → creates App + draft AppConfig (version "0.0.0", status "draft")PUT /api/apps/:id/config → updates latest draft (assignments, layout)POST /api/apps/:id/publish → sets draft to "published", bumps version, creates new draft cloneaccountId from JWT — never expose other accounts' data._id. Used in all runtime routes.{ mfeId, version } compound unique — rejects duplicate versions.The admin-api uses AWS S3 exclusively for MFE bundle storage. There is no local storage mode.
config.storage.bucket (env: S3_BUCKET){mfeName}/{version}/ with correct MIMEs3:GetObject for */storage/{mfeName}/{version}/remoteEntry.jsconfig.aws.region (env: AWS_REGION)| Variable | Required | Description |
|----------|----------|-------------|
| MONGO_URI | Yes | MongoDB Atlas connection string |
| S3_BUCKET | Yes | S3 bucket name for MFE bundles |
| AWS_REGION | Yes | AWS region (default: us-west-2) |
| JWT_SECRET | Yes | JWT signing secret (fatal if insecure in production) |
| PORT | No | Server port (default: 4000) |
| CORS_ORIGIN | No | CORS origin (default: *) |
| NODE_ENV | No | development or production |
signToken)JWT_SECRET is weak defaultdevelopment
# Lyx Testing Expert ## When to Use Use this skill when: - Writing or modifying Playwright E2E tests - Writing or modifying k6 performance tests - Debugging test failures - Adding test coverage for new features - Running the test suite locally or in CI - Understanding the test architecture ## Test Architecture Overview ### Playwright E2E Tests **Location**: `tests/e2e/` **Configuration**: `playwright.config.ts` at project root **Projects**: - `setup` — Global auth setup (registers/logs in
tools
Expert on the Lyx Shell: layout rendering, Module Federation, SSR streaming, URL parsing, devtools. Use when working with packages/shell, platform/ssr, or debugging MFE loading issues.
development
Expert on the Lyx SDK internals: event bus, shared state, navigation, MFE loading. Use when working with @lyx/sdk code, debugging inter-MFE communication, or implementing new SDK features. Knows all edge cases and internal behaviors.
development
# Lyx QA Regression Tester ## Role You are the QA Regression Tester for the Lyx framework. Your job is to **catch every bug before the user does**. You run after every feature implementation, before any commit or push. You are the last gate — nothing ships without your sign-off. ## When to Activate This skill MUST be invoked: - After implementing any feature (P0, P1, P2, P3) - After fixing any bug - Before every `git commit` that includes code changes - When the user says "regression", "test