robodev 0.23.0 → 0.24.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "robodev",
-  "version": "0.23.0",
+  "version": "0.24.0",
   "description": "CLI for Robodev Starbase — create, auth, link, and deploy hosted apps",
   "type": "module",
   "license": "MIT",

package/src/emit-starter.test.ts

@@ -77,6 +77,42 @@ test("collectFiles for auth-chat starter is Tiny APIs without apps/fe", async ()
   assert.ok(files.length < 200);
 });
 
+test("emitStarter marketplace FE build runs openapi:gen before vite", async () => {
+  const dest = await mkdtemp(join(tmpdir(), "rd-emit-"));
+  try {
+    await emitStarter(join(cliRoot(), "..", "starters", "marketplace"), dest, {
+      name: "Bazaar",
+      packageName: "bazaar-app",
+      title: "Marketplace",
+      versions,
+    });
+    const fePkg = JSON.parse(await readFile(join(dest, "apps/fe/package.json"), "utf8")) as {
+      dependencies?: Record<string, string>;
+      scripts?: { build?: string };
+    };
+    assert.equal(fePkg.dependencies?.["@hookform/resolvers"], "^5.2.2");
+    assert.equal(fePkg.dependencies?.["react-hook-form"], "^7.65.0");
+    assert.match(fePkg.scripts?.build ?? "", /openapi:gen.*vite build/);
+  } finally {
+    await rm(dest, { recursive: true, force: true });
+  }
+});
+
+test("collectFiles for marketplace starter is Tiny APIs without apps/fe", async () => {
+  const files = await collectFiles(join(cliRoot(), "..", "starters", "marketplace"));
+  const paths = new Set(files.map((file) => file.path));
+  assert.ok(paths.has("database.ts"));
+  assert.ok(paths.has("api/listings.ts"));
+  assert.ok(paths.has("api/cart.ts"));
+  assert.ok(paths.has("api/checkout.ts"));
+  assert.ok(paths.has("api/health.ts"));
+  assert.ok(paths.has("api/me.ts"));
+  assert.ok(!paths.has("index.html"));
+  assert.ok(!paths.has("src/main.tsx"));
+  assert.ok([...paths].every((path) => !path.startsWith("apps/")));
+  assert.ok(files.length < 200);
+});
+
 test("collectFiles for space starter is Tiny APIs without apps/fe", async () => {
   const files = await collectFiles(join(cliRoot(), "..", "starters", "space"));
   const paths = new Set(files.map((file) => file.path));

package/templates/auth-chat/package.json

@@ -11,7 +11,7 @@
     "@robodev-ai/sdk": "^0.6.0"
   },
   "devDependencies": {
-    "robodev": "^0.23.0",
+    "robodev": "^0.24.0",
     "rulesync": "^8.18.0",
     "typescript": "^5.9.2"
   }

package/templates/backend/package.json

@@ -10,7 +10,7 @@
     "@robodev-ai/sdk": "^0.6.0"
   },
   "devDependencies": {
-    "robodev": "^0.23.0",
+    "robodev": "^0.24.0",
     "typescript": "^5.9.2"
   }
 }

package/templates/catalog.json

@@ -10,6 +10,11 @@
       "title": "Auth chat",
       "description": "Tiny chat APIs plus a local Povio UI in apps/fe, with invite email"
     },
+    {
+      "id": "marketplace",
+      "title": "Marketplace",
+      "description": "Tiny C2C marketplace APIs plus a local Povio UI in apps/fe"
+    },
     {
       "id": "backend",
       "title": "Backend",

package/templates/empty/package.json

@@ -10,7 +10,7 @@
     "@robodev-ai/sdk": "^0.6.0"
   },
   "devDependencies": {
-    "robodev": "^0.23.0",
+    "robodev": "^0.24.0",
     "typescript": "^5.9.2"
   }
 }

package/templates/marketplace/.config/local.spa.template.yml

@@ -0,0 +1,27 @@
+STAGE: "local"
+OUTPUT: "export"
+
+ANALYZE: "false"
+NEXT_TELEMETRY_DISABLED: "1"
+
+VITE_PUBLIC_RELEASE: ${env:RELEASE}
+VITE_PUBLIC_STAGE: ${func:stage}
+
+APP_PUBLIC_API_URL: &APP_PUBLIC_API_URL "http://localhost:4000"
+APP_PUBLIC_API_MODE: &APP_PUBLIC_API_MODE "real"
+VITE_PUBLIC_API_URL: *APP_PUBLIC_API_URL
+VITE_PUBLIC_API_MODE: *APP_PUBLIC_API_MODE
+
+VITE_PUBLIC_LOG_LEVEL: "trace"
+
+VITE_PUBLIC_SENTRY_DSN: ""
+VITE_PUBLIC_SENTRY_ENVIRONMENT: ${func:stage}
+VITE_PUBLIC_SENTRY_TRACES_SAMPLE_RATE: "0"
+VITE_PUBLIC_SENTRY_REPLAYS_SESSION_SAMPLE_RATE: "0"
+VITE_PUBLIC_SENTRY_REPLAYS_ON_ERROR_SAMPLE_RATE: "0"
+
+VITE_PUBLIC_AUTH_CUSTOM_JWT_ENABLE_MAGIC_LINK: "true"
+
+VITE_PUBLIC_GOOGLE_ANALYTICS_MEASUREMENT_ID: ""
+
+VITE_DEV_PORT: "3000"

package/templates/marketplace/.oxlint-base.json

@@ -0,0 +1,29 @@
+{
+  "$schema": "apps/fe/node_modules/oxlint/configuration_schema.json",
+  "plugins": ["eslint", "typescript", "unicorn", "import", "oxc", "promise", "vitest"],
+  "categories": {
+    "correctness": "error",
+    "perf": "error",
+    "pedantic": "off",
+    "style": "off",
+    "restriction": "off",
+    "suspicious": "off",
+    "nursery": "off"
+  },
+  "env": {
+    "builtin": true,
+    "node": true,
+    "shared-node-browser": true
+  },
+  "rules": {
+    "eslint/eqeqeq": [
+      "error",
+      "always",
+      {
+        "null": "ignore"
+      }
+    ],
+    "typescript/no-floating-promises": "off",
+    "eslint/capitalized-comments": "off"
+  }
+}

package/templates/marketplace/.oxlintrc.json

@@ -0,0 +1,78 @@
+{
+  "$schema": "apps/fe/node_modules/oxlint/configuration_schema.json",
+  "extends": [".oxlint-base.json"],
+  "plugins": [
+    "eslint",
+    "typescript",
+    "unicorn",
+    "import",
+    "vitest",
+    "react",
+    "react-perf",
+    "jsx-a11y"
+  ],
+  "categories": {
+    "style": "error"
+  },
+  "ignorePatterns": [
+    "openapi-codegen.config.ts",
+    "postcss.config.js",
+    "out",
+    "dist",
+    "public",
+    "scripts",
+    ".vscode",
+    ".turbo",
+    "node_modules",
+    "apps/fe/src/routeTree.gen.ts",
+    "apps/fe/src/openapi",
+    "apps/fe/public"
+  ],
+  "overrides": [
+    {
+      "files": ["vite-plugin-*.ts", "apps/fe/vite-plugin-*.ts"],
+      "rules": {
+        "import/no-nodejs-modules": "off"
+      }
+    }
+  ],
+  "rules": {
+    "eslint/no-implicit-coercion": "off",
+    "no-map-spread": "off",
+    "eslint/sort-keys": "off",
+    "eslint/sort-imports": "off",
+    "eslint/no-ternary": "off",
+    "eslint/id-length": "off",
+    "eslint/no-magic-numbers": "off",
+    "eslint/arrow-body-style": "off",
+    "eslint/max-params": "off",
+    "eslint/func-style": "off",
+    "eslint/new-cap": "off",
+    "eslint/no-continue": "off",
+    "eslint/max-statements": "off",
+    "eslint/no-duplicate-imports": [
+      "error",
+      {
+        "allowSeparateTypeImports": true
+      }
+    ],
+    "react/exhaustive-deps": "off",
+    "react/jsx-props-no-spreading": "off",
+    "react/jsx-max-depth": "off",
+    "react-perf/jsx-no-new-object-as-prop": "off",
+    "react-perf/jsx-no-new-function-as-prop": "off",
+    "react-perf/jsx-no-new-array-as-prop": "off",
+    "react-perf/jsx-no-jsx-as-prop": "off",
+    "typescript/no-empty-interface": "off",
+    "import/no-named-export": "off",
+    "import/group-exports": "off",
+    "import/prefer-default-export": "off",
+    "import/exports-last": "off",
+    "import/consistent-type-specifier-style": "off",
+    "jest/require-hook": "off",
+    "unicorn/filename-case": "off",
+    "unicorn/prefer-global-this": "off",
+    "unicorn/no-await-expression-member": "off",
+    "unicorn/no-null": "off"
+  }
+}

package/templates/marketplace/.rulesync/rules/frontend-api-boundary.md

@@ -0,0 +1,36 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Frontend must consume generated OpenAPI queries and models, not backend internals."
+globs: ["apps/fe/src/**/*.{ts,tsx}"]
+cursor:
+  alwaysApply: false
+  description: "Apply when editing frontend components, hooks, providers, pages, or clients that call the API."
+  globs: ["apps/fe/src/**/*.{ts,tsx}"]
+---
+
+# Frontend API Boundary
+
+Frontend application code must consume the API through generated files in `apps/fe/src/openapi`.
+
+Use generated modules such as:
+
+- `@/openapi/<domain>/<domain>.queries`
+- `@/openapi/<domain>/<domain>.models`
+- `@/openapi/queryModules`
+
+For generated mutations, pass invalidation through the mutation options instead of importing `queryClient` or calling `invalidateQueries` with generated query keys. The current module is invalidated by default through `invalidateCurrentModule: true`; invalidate dependent modules explicitly with `invalidateModules: [QueryModule.someModule]`.
+
+After mutations, derive follow-up UI state from canonical API response or query state instead of leaving action controls unchanged. Disable duplicate submissions when the API state already represents a pending or completed action, and surface mutation errors through the default generated-client error handler or a feature-specific message.
+
+Do not import `@robodev-ai/sdk`, `database.ts`, Drizzle tables, or API helper modules into frontend features.
+
+`apps/fe/src/openapi` is generated by `@povio/openapi-codegen-cli` from root `openapi.json` (or a live project `/openapi.json` when `OPENAPI_LIVE=true`). Do not hand-edit generated OpenAPI client files.
+
+When API contracts change:
+
+1. Update `api/` handlers and `openapi.json` if the documented contract changed.
+2. Run `bun openapi:gen` from `apps/fe`.
+3. Update frontend code to use the regenerated queries and models.
+
+Point `VITE_PUBLIC_API_URL` at the Starbase project host origin only. Do not append `/api`.

package/templates/marketplace/.rulesync/rules/frontend-component-structure.md

@@ -0,0 +1,38 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Frontend component extraction and feature subcomponent structure conventions."
+globs: ["apps/fe/src/**/*.{ts,tsx}"]
+cursor:
+  alwaysApply: false
+  description: "Apply when organizing frontend feature components, page sections, mapped items, or reusable UI."
+  globs: ["apps/fe/src/**/*.{ts,tsx}"]
+---
+
+# Frontend Component Structure
+
+Extract repeatable UI into subcomponents. Every named React component should live in its own file, even when it is currently used only once. Keep the component file near the feature, layout, page, or shared UI area that owns it.
+
+Extract large or complex sections of pages into named components so route and page components stay readable. Anything mapped from an array should usually be a component, such as cards, table row actions, repeated sections, or list items.
+
+The planets feature is the reference example while the template is still a prototype:
+
+- `PlanetCard` for mapped grid cards.
+- `PlanetsFilters` for shared filter controls.
+- `PlanetsTableActions` for repeated row actions.
+- `PlanetsTable` and `PlanetsTableInfinite` for table wrappers.
+- `PlanetDetailsPage` and `PlanetEditPage` for large route-owned views.
+
+When implementing a real app, remove the planets and aliens links from app navigation such as `apps/fe/src/components/layout/AppHeader.tsx` so these examples are not directly accessible in the product UI, but keep the example implementation available as a reference unless the team intentionally deletes the demo layer.
+
+Route files should own routing, document metadata, and route data boundaries. Feature components should own the page UI and interaction details.
+
+Exception: route-local wrappers such as `PageComponent` or layout guard components may stay in route files when they only connect routing primitives to feature components.
+
+## Shared Utilities
+
+Keep generic formatting, parsing, calculation, and data-shaping helpers in `apps/fe/src/utils/*.utils.ts` files instead of defining them inside component files. Export helpers through namespaces such as `DateUtils.formatDate(...)` or `NumberUtils.formatInteger(...)` so call sites stay explicit and related helpers stay grouped.
+
+Component files may keep UI-local glue helpers only when the logic is tightly coupled to that component's JSX, such as adapting one component's prop shape or handling a local event. If the helper describes dates, numbers, arrays, strings, IDs, or other domain-neutral data, move it into a shared utility file.
+
+For apps with multiple user roles that require distinct UI or business workflows, also apply the role-based app structure rule.

package/templates/marketplace/.rulesync/rules/frontend-forms.md

@@ -0,0 +1,32 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Frontend form patterns with Povio UI useForm, generated schemas, and formControl wiring."
+globs: ["apps/fe/src/**/*.{ts,tsx}"]
+cursor:
+  alwaysApply: false
+  description: "Apply when building or changing frontend forms, modals, edit pages, or input components."
+  globs: ["apps/fe/src/**/*.{ts,tsx}"]
+---
+
+# Frontend Forms
+
+Use `useForm` and form-aware inputs from `@povio/ui/tanstack` with generated OpenAPI Zod schemas for API-backed forms. The planets feature is the reference example while the template is still a prototype:
+
+- Create form: `apps/fe/src/components/features/planets/list/PlanetCreateModal.tsx`
+- Edit form: `apps/fe/src/components/features/planets/details/PlanetEditPage.tsx`
+
+Prefer this shape:
+
+```tsx
+const form = useForm({
+  zodSchema: PlanetsModels.PlanetsCreateInputSchema,
+  defaultValues: { name: "" },
+});
+```
+
+Pass form state into Povio UI inputs with `field={{ form, name: "fieldName" }}`. Use `form.handleSubmit`, `form.reset`, and `form.setFieldValue` for form actions, and `useFormValue(form, selector)` for reactive field reads.
+
+Avoid local `useState`, custom `value`, and custom `onChange` plumbing for fields that belong to the form. Use TanStack Form's `form.Field` adapter only when a component cannot accept the Povio UI `field` binding.
+
+Use generated OpenAPI queries and mutations for submit handlers. Keep toast feedback and navigation close to the feature interaction that owns them.

package/templates/marketplace/.rulesync/rules/frontend-notifications.md

@@ -0,0 +1,24 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Frontend notification inbox, preferences, push permission, service worker, and token registration boundaries."
+globs: ["apps/fe/src/**/*.{ts,tsx}", "apps/fe/public/**/*.{js,ts}"]
+cursor:
+  alwaysApply: false
+  description: "Apply when frontend work handles notifications, push permission, service workers, push tokens, unread counts, or notification preferences."
+  globs: ["apps/fe/src/**/*.{ts,tsx}", "apps/fe/public/**/*.{js,ts}"]
+---
+
+# Frontend Notifications
+
+Use generated `@/openapi` queries, mutations, and models for notification history, preferences, and push-token registration. Do not import `@robodev-ai/sdk` or `database.ts` into frontend feature code.
+
+Request push permission only after an explanatory UI and explicit user gesture. Never request it automatically during initial application load. Handle unsupported, default, denied, granted, registered, expired, and failed-registration states.
+
+Register the service worker and provider subscription through a small browser integration, then persist the token/subscription through the generated authenticated user API. Clean up or detach the current device registration on logout when required by the security model.
+
+Keep push payloads minimal and privacy-safe. Validate internal deep links before navigation. Never depend on push as the only record of an important event; provide a paginated in-app notification list and unread state.
+
+Use generated mutation invalidation options for unread counts, mark-read actions, preferences, and token changes. Do not access the query client directly for generated API state.
+
+Use `@povio/ui` for permission prompts, notification lists, menus/popovers, tags, forms, confirmations, and toasts. Use `povio-ui-styling` for styling-layer decisions.

package/templates/marketplace/.rulesync/rules/frontend-povio-components.md

@@ -0,0 +1,42 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Frontend interactive controls and typography must use Povio UI primitives instead of native replacements."
+globs: ["apps/fe/src/**/*.{ts,tsx}"]
+cursor:
+  alwaysApply: false
+  description: "Apply when creating or editing React components, controls, forms, tables, overlays, or user-facing text."
+  globs: ["apps/fe/src/**/*.{ts,tsx}"]
+---
+
+# Use Povio UI Components
+
+Use a component from `@povio/ui` whenever it provides the required primitive. Do not recreate an available Povio component with a native element plus Tailwind or custom CSS.
+
+Required replacements include:
+
+- `Button`, `TextButton`, or the appropriate Povio action component instead of a styled `<button>`.
+- `TextInput`, `PasswordInput`, `TextArea`, checkbox, radio, select, autocomplete, and other Povio form controls instead of native form controls.
+- `Typography` instead of directly styling user-facing headings, paragraphs, labels, or spans.
+- `Table` or `InfiniteTable` instead of a hand-built native data table.
+- `Modal`, `Confirmation`, `Drawer`, `BottomSheet`, `Menu`, `Tooltip`, or `ResponsivePopover` instead of custom overlay primitives.
+- `FileUpload` instead of a directly exposed file input.
+- Povio hooks such as `useForm` and `useToast` instead of parallel custom infrastructure.
+
+Before creating a control:
+
+1. Search `@povio/ui` usage in the repository.
+2. Inspect existing feature components for the same primitive.
+3. Use the existing Povio props and variants.
+4. Apply the `povio-ui-styling` skill when choosing between local Tailwind, `UIConfig`, `UIOverrides`, a shared wrapper, or scoped CSS.
+
+Native semantic and structural elements such as `<main>`, `<section>`, `<article>`, `<nav>`, `<form>`, `<div>`, and list elements remain appropriate for document structure and layout. Use TanStack Router navigation primitives for routing. This rule prohibits native replacements for available Povio UI behavior; it does not prohibit semantic HTML.
+
+If Povio UI has no suitable primitive:
+
+- Compose existing Povio components first.
+- Put a reusable project-specific primitive under `apps/fe/src/components/shared/ui`.
+- Preserve keyboard behavior, focus visibility, accessible names, disabled state, validation state, and loading state.
+- Keep the exception narrow; do not introduce another general-purpose UI library.
+
+When touching an existing native control that has a Povio equivalent, migrate it when the change is safely within scope. Do not expand a narrowly requested fix into a broad unrelated rewrite.

package/templates/marketplace/.rulesync/rules/frontend-povio-ui.md

@@ -0,0 +1,45 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Frontend UI uses Povio UI primitives first and semantic Tailwind tokens."
+globs: ["apps/fe/src/**/*.{ts,tsx,css}"]
+cursor:
+  alwaysApply: false
+  description: "Apply when editing frontend UI, styling, layout, components, or CSS."
+  globs: ["apps/fe/src/**/*.{ts,tsx,css}"]
+---
+
+# Frontend UI
+
+## Use `@povio/ui` First
+
+Always use components and hooks from `@povio/ui` when a suitable primitive exists, including `Button`, `Typography`, `Table`, `Modal`, `Confirmation`, `TextButton`, `TextInput`, `TextArea`, `PasswordInput`, `FileUpload`, `useForm`, `useToast`, and `Tag`.
+
+Create project-specific UI only when `@povio/ui` does not provide the needed primitive. Shared custom primitives live under `apps/fe/src/components/shared/ui`.
+
+Feature components should compose existing layout and shared primitives such as `PageHeader`, `BackHeader`, `LoadingState`, `ErrorText`, and `Card` before introducing new wrappers.
+
+When implementing a real app, remove the demo planets and aliens links from app navigation such as `apps/fe/src/components/layout/app-header/AppHeader.tsx` so they are not directly accessible in the product UI, but keep the example code available as a reference unless the team intentionally deletes the demo layer.
+
+## Tailwind Tokens
+
+The default Tailwind color palette is removed in `apps/fe/src/styles/base.css`. Do not use default color utilities such as:
+
+- `text-red-500`
+- `bg-blue-600`
+- `border-gray-200`
+- `ring-emerald-400`
+
+Use semantic tokens exported from Figma in `apps/fe/src/styles/theme.css` and exposed through Tailwind, for example:
+
+- Surface, fill, and outline: `bg-elevation-fill-default-1`, `border-elevation-outline-default-1`
+- Text: `text-text-default-1`, `text-text-default-2`, `text-text-error-1`
+- Interactive: `bg-interactive-contained-primary-idle`, `hover:bg-interactive-contained-primary-hover`
+
+Do not manually edit `apps/fe/src/styles/theme.css`; it is exported from Figma. If a hand-written semantic token or Tailwind theme mapping is needed, add it only in `apps/fe/src/styles/base.css` before referencing it from JSX or CSS.
+
+## Forms And API Data
+
+For forms backed by API requests, prefer generated OpenAPI model schemas with `@povio/ui` `useForm`, for example `useForm({ zodSchema: UserModels.UpdateProfileBodySchema })`.
+
+Use generated OpenAPI queries and mutations for all API state. Keep API side effects, toast feedback, loading states, and query invalidation close to the feature that owns the interaction. For mutation invalidation, pass generated mutation options such as `invalidateModules`; do not import `queryClient` into feature code for generated API queries.

package/templates/marketplace/.rulesync/rules/frontend-query-autocomplete.md

@@ -0,0 +1,29 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Frontend QueryAutocomplete usage for database-entity dropdowns with generated label queries and queryParams."
+globs: ["apps/fe/src/**/*.{ts,tsx}"]
+cursor:
+  alwaysApply: false
+  description: "Apply when a frontend form or filter needs a dropdown/search picker of database entities."
+  globs: ["apps/fe/src/**/*.{ts,tsx}"]
+---
+
+# Frontend QueryAutocomplete
+
+Use this pattern whenever the UI needs a dropdown/search picker of entities from the database, such as selecting a alien, company, project, user, category, or any other related row in a form or filter.
+
+Use `QueryAutocomplete` for these database-entity dropdowns. It should call a generated labels endpoint such as `AliensQueries.useListLabels`, not load full related records into the form.
+
+Reference examples:
+
+- Create form: `apps/fe/src/components/features/planets/list/PlanetCreateModal.tsx`
+- Edit form: `apps/fe/src/components/features/planets/details/PlanetEditPage.tsx`
+- Filter control: `apps/fe/src/components/features/planets/list/PlanetsFilters.tsx`
+  The matching labels endpoint input schema must define `search`, usually as `search: z.string().optional()`, because `QueryAutocomplete` passes search text through that parameter.
+
+If a labels endpoint needs extra context, pass it through `QueryAutocomplete` with `queryParams`. The matching labels endpoint input schema can include optional parameters beyond `search`, such as extra filters or flags that control how rows map into `{ id, label }`.
+
+When the autocomplete belongs to a form, import it from `@povio/ui/tanstack` and prefer `field={{ form, name }}`. When it belongs to filters, read and write through the `useFilters` store.
+
+Real app features should use generated labels queries from `@/openapi`.

package/templates/marketplace/.rulesync/rules/frontend-tables-and-lists.md

@@ -0,0 +1,34 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Frontend list and table patterns for grids, Table, InfiniteTable, filters, and sorting."
+globs: ["apps/fe/src/**/*.{ts,tsx}"]
+cursor:
+  alwaysApply: false
+  description: "Apply when building or changing list pages, grids, tables, filters, sorting, pagination, or row actions."
+  globs: ["apps/fe/src/**/*.{ts,tsx}"]
+---
+
+# Frontend Tables And Lists
+
+The planets feature intentionally shows multiple list patterns while the template is still a prototype:
+
+- Demo switcher: `apps/fe/src/components/features/planets/list/PlanetsPage.tsx`
+- Grid list: `apps/fe/src/components/features/planets/list/PlanetsGridPage.tsx`
+- Table list: `apps/fe/src/components/features/planets/list/PlanetsTablePage.tsx`
+- Infinite table list: `apps/fe/src/components/features/planets/list/PlanetsInfiniteTablePage.tsx`
+- Table wrappers and actions: `apps/fe/src/components/features/planets/list/table/*`
+
+The `Segment` in `PlanetsPage` is demo-only. Real feature pages should usually choose one list pattern and use it consistently.
+
+Prefer paginated API queries for database-backed collections. Use regular generated list queries only for data that is guaranteed to stay short, such as enums, compact option lists, or label-style endpoints.
+
+Use `Table` from `@povio/ui` for small bounded table lists and `InfiniteTable` when incremental loading is useful for the feature. Infinite tables require a paginated backend endpoint and generated `use<Endpoint>Infinite` query. Even non-infinite collection views should normally be backed by a paginated endpoint unless the collection is intentionally bounded.
+
+When a feature needs filters, define a filter schema on the API model, expose it through OpenAPI when useful, and use `useFilters` on the frontend. Put filter controls in a focused component such as `PlanetsFilters`. Use `as="filter"` on Povio UI filter controls.
+
+When a feature needs sorting, expose an enum of sortable keys from the API layer and pass the generated enum schema into `dynamicColumns({ options: { sortable } })`. Use `useSorting` on the frontend and pass its `order` string to the generated query.
+
+Use wrapper components around table primitives. A table wrapper should accept `TableWrapperProps<T>` or `InfiniteTableWrapperProps<T>` from `@povio/ui` and spread props into `Table` or `InfiniteTable`, while defining columns locally with a `getColumns` helper above the component.
+
+Keep per-row actions in a small action component, such as `PlanetsTableActions`, and use a shared row-action wrapper when available so clicks do not accidentally trigger row navigation.

package/templates/marketplace/.rulesync/rules/frontend-translations.md

@@ -0,0 +1,26 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Frontend translation key structure and no-hardcoded-text conventions."
+globs: ["apps/fe/src/**/*.{ts,tsx,json}"]
+cursor:
+  alwaysApply: false
+  description: "Apply when adding or changing frontend user-facing text, locale files, or translation keys."
+  globs: ["apps/fe/src/**/*.{ts,tsx,json}"]
+---
+
+# Frontend Translations
+
+Do not hardcode user-facing frontend text. Add copy to locale files and access it through `useTranslation`.
+
+Translation key structure should generally follow the feature/component tree. The planets feature is the current reference example:
+
+- `planets.page.*`
+- `planets.views.*`
+- `planets.filters.*`
+- `planets.createModal.*`
+- `planets.editModal.*`
+- `planets.table.*`
+- `planets.detail.*`
+
+When Slovenian translations are required, preserve real Slovenian characters with carons, especially Unicode `U+0161`, `U+010D`, and `U+017E`. Do not leave mojibake or replacement-character artifacts in locale files.

package/templates/marketplace/.rulesync/rules/project-overview.md

@@ -0,0 +1,32 @@
+---
+root: true
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Project overview and Rulesync source-of-truth guidance."
+globs: ["**/*"]
+cursor:
+  alwaysApply: true
+  description: "Project overview and Rulesync source-of-truth guidance."
+  globs: ["**/*"]
+---
+
+# Marketplace starter AI rules
+
+This project is a Vite React frontend in `apps/fe` plus a Robodev backend at the **repository root** (`database.ts` + `api/**/*.ts` using `@robodev-ai/sdk`). There is no Expo / mobile app in this starter. End-user auth is reserved on the project host at `/api/user/*`. There is no in-browser fake backend.
+
+`robodev deploy` from this root uploads schema and APIs. It does not host the Povio SPA. Run the UI with bun in `apps/fe`.
+
+Shared AI rules and skills are authored in `.rulesync/`. Generated files for Codex, Claude Code, and Cursor are local outputs and should be regenerated with `bun rules:gen`.
+
+This starter is a signed-in C2C Buy-It-Now goods marketplace. Listings, cart, checkout, orders, watches, and reviews live in `api/` and `apps/fe/src/components/features`.
+
+When an app has multiple user roles with distinct UI or business workflows, use the conditional role-based app structure rule. Do not apply role splitting to simple single-role apps or small permission differences.
+
+Use the more specific generated rules for:
+
+- Robodev `defineDatabase` tables in `database.ts`.
+- Robodev `defineApi` routes in `api/`.
+- Reserved `/api/user/*` auth contracts (do not implement `api/user/**` in the project).
+- Frontend API boundaries around generated `@/openapi` queries and models.
+- Povio UI and semantic Tailwind token usage.
+- Frontend forms, tables/lists, `QueryAutocomplete`, translations, and component structure.
+- Role-based frontend structure when an app has multiple distinct user roles.

package/templates/marketplace/.rulesync/rules/robodev-api.md

@@ -0,0 +1,30 @@
+---
+root: false
+targets: ["claudecode", "codexcli", "cursor"]
+description: "Robodev defineApi file routes and handler conventions."
+globs: ["api/**/*.ts"]
+cursor:
+  alwaysApply: false
+  description: "Apply when editing Starbase API routes."
+  globs: ["api/**/*.ts"]
+---
+
+# Robodev API
+
+Project APIs live in `api/`. `api/planets.ts` is served at `/planets` and `/api/planets`. Prefer the `/api/...` path in OpenAPI and frontend clients.
+
+## File layout
+
+- `api/foo.ts` → `/api/foo`
+- `api/foo/[id].ts` → `/api/foo/:id`
+- Export `get` / `post` / `put` / `patch` / `delete` as `defineApi(...)`.
+- Shared helpers belong in `api/_lib.ts`. Do not export `defineApi` from `_lib.ts`.
+- Do not add `api/user/**`. Those paths are reserved for Robodev Auth.
+
+## Handlers
+
+- Use `auth: "required"` on routes that Tiny marked authenticated.
+- Handler context includes `db`, `user`, `email`, `storage`, `params`, `query`, `body`.
+- Return JSON for 200, or `{ status, body }` for errors (404/403/400).
+- Keep request/response shapes compatible with `openapi.json` so OpenAPI codegen stays stable.
+- After changing public contracts, update `openapi.json` if needed and run `bun openapi:gen` from `apps/fe`.