@pylonsync/create-pylon 0.5.3 → 0.5.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -785,7 +785,8 @@ const skillLine = skillInstalled
785
785
  // (Claude Code / Cursor / Codex) auto-reads AGENTS.md, so point the human at it
786
786
  // too. Only the full-stack templates ship one (platform sub-templates don't).
787
787
  const agentsLine = existsSync(join(root, "AGENTS.md"))
788
- ? "AGENTS.md is your coding agent's operating manual for this repo — it reads it first.\n"
788
+ ? "AGENTS.md is your coding agent's operating manual for this repo — it reads it first.\n" +
789
+ "It starts by replacing the placeholder branding (Acme, example.com, demo data) with your product.\n"
789
790
  : "";
790
791
 
791
792
  console.log(`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pylonsync/create-pylon",
3
- "version": "0.5.3",
3
+ "version": "0.5.4",
4
4
  "description": "Scaffold a new Pylon app — realtime backend + web/mobile/expo frontends in one command. Run via `npm create @pylonsync/pylon@latest`.",
5
5
  "publishConfig": {
6
6
  "access": "public"
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**
@@ -2,6 +2,23 @@
2
2
 
3
3
  Pylon serves the API, auth, sync, WebSocket, SSE, and native React 19 SSR from one Rust process on one port. Treat this app as production infrastructure: it supports real auth, SQLite or Postgres, row-level policies, jobs, search, and one-command deploys. Declare entities, policies, and server functions in TypeScript; the binary handles the runtime. Read the full API reference at https://docs.pylonsync.com/llms-full.txt before guessing an API name.
4
4
 
5
+ ## First: replace the placeholders
6
+
7
+ This template ships with placeholder branding, copy, and demo data — the example
8
+ brand **Acme**, `example.com` links, lorem-style text, sample records, and (in the
9
+ marketing templates) fake "Acme vs …" comparisons. Before building features, do
10
+ one pass to make it the real product:
11
+
12
+ - **Brand** — replace every "Acme", its logo, the `example.com` domain, the support
13
+ email, and social links with the real name. Find them: `grep -riE "acme|example\.com" .`
14
+ - **Copy** — rewrite hero, feature, marketing, and comparison text for the actual
15
+ product. Ship no lorem and no "Acme".
16
+ - **Demo data** — replace sample/seed records with the real domain's, or remove them.
17
+
18
+ The manifest name (`buildManifest({ name })`) is already the project name — the
19
+ placeholders live in the CONTENT. A scaffold that still says "Acme" isn't done; make
20
+ this pass before the user has to ask.
21
+
5
22
  ## Directory conventions
6
23
 
7
24
  **Unified SSR app:**