@uge/payo 0.3.1 → 0.3.3

package/README.md

@@ -122,9 +122,10 @@ guidance files straight into your repo.
    and you get Next.js-specific follow-ups; choose Postgres and you're asked
    about migrations and naming. Most prompts ship a **recommended default**, so
    you can blast through with <kbd>Enter</kbd>.
-3. **Review your stack.** Before writing anything, Payo shows a summary of every
-   answer and asks you to confirm. Say no and your answers are kept — rerun to
-   edit them.
+3. **Review your stack — and edit inline.** Before writing anything, Payo shows a
+   summary of every answer. Choose **Edit an answer** to change any response — or
+   re-open a section you skipped — right from the review; dependent questions are
+   re-asked automatically. Pick **Generate** when it looks right.
 4. **Payo generates the guidance.** It writes each tool's files in their native
    format and location (see the table below). With the tool's CLI installed,
    files are generated in parallel by the AI; otherwise solid templates are used.
@@ -153,11 +154,11 @@ Each tool gets files in its own native format and location:
 
 ## What it asks about
 
-Payo understands **25 frameworks, 24 ORMs, and 4 databases** across
+Payo understands **25 frameworks, 24 ORMs, and 16 databases** across
 **TypeScript/JavaScript, Python, Go, and Rust** — and tailors its follow-up
 questions to whatever you pick. Dimensions covered:
 
-- **Project** — type (frontend / backend / full-stack) and a short description
+- **Project** — type (frontend / backend / full-stack / CLI / script) and a short description
 - **Language & framework** — plus framework-specific conventions
 - **API** — REST, GraphQL, gRPC, tRPC
 - **Frontend** — styling and state management