@uge/payo 0.2.0 → 0.3.1

package/README.md

@@ -2,7 +2,7 @@
 
 <img src="https://raw.githubusercontent.com/uttam-gelot/payo/main/assets/logo.png" alt="Payo" width="200" />
 
-**Generate project-tailored AI assistant rules & skills in under two minutes.**
+**Generate project-tailored AI assistant rules & skills in minutes.**
 
 Payo interviews you about your stack, then writes the guidance files your AI
 coding assistant reads — so Claude, Cursor, Copilot, and friends follow _your_
@@ -33,6 +33,7 @@ project's conventions instead of guessing.
 - [AI vs. template generation](#ai-vs-template-generation)
 - [Bootstrap prompt](#bootstrap-prompt)
 - [Resume anytime](#resume-anytime)
+- [Roadmap](#roadmap)
 - [Requirements](#requirements)
 - [Run locally](#run-locally)
 - [Contributing](#contributing)
@@ -62,7 +63,7 @@ The fix is the guidance files each tool already reads (`CLAUDE.md`,
 by hand is tedious, easy to get wrong, and different for every tool. Most people
 never do it, or do it once and let it rot.
 
-Payo writes them for you in about two minutes — tailored to your actual stack,
+Payo writes them for you in minutes — tailored to your actual stack,
 in each tool's native format — so your assistant follows _your_ conventions from
 the first prompt instead of guessing.
 
@@ -183,6 +184,14 @@ A few environment variables tune AI generation:
 | `PAYO_RETRIES`          | `1`      | Extra attempts after a failed run    |
 | `PAYO_AGENT_TIMEOUT_MS` | `120000` | Wall-clock cap per file (ms)         |
 
+### Your data stays yours
+
+Payo has no backend and no telemetry. Rich generation runs entirely through the
+AI CLI **you** already have installed (`claude`, `cursor-agent`, etc.), so your
+answers go only to that tool under your own account and credentials — exactly as
+if you'd prompted it yourself. Payo itself sends nothing to any server; without a
+CLI present it never leaves your machine at all, falling back to local templates.
+
 ## Bootstrap prompt
 
 An empty repo with great guidance is still an empty repo. After generating, Payo
@@ -197,6 +206,27 @@ Interrupt a run and pick up where you left off. Payo saves your questionnaire
 answers and generation progress under `.payo/`; rerun and it resumes, only
 generating what's missing. Finished runs clean the directory up automatically.
 
+## Roadmap
+
+Payo works today, but it's still early. Here's where it's headed:
+
+- **First-class existing-project support.** Right now Payo shines on a fresh
+  repo. The next big step is making it just as good on an established codebase:
+  **detect** the stack from what's already there (manifests, lockfiles, config,
+  folder layout), **auto-answer** the questionnaire from that evidence, and let
+  you confirm or tweak instead of typing it all out — then the normal generation
+  flow continues.
+- **Broader stack coverage.** More languages, frameworks, ORMs, databases, and
+  AI tools, plus deeper, more opinionated defaults for the ones already
+  supported — so the guidance fits more of the ecosystem out of the box.
+- **A smoother flow.** Faster, clearer prompts; better defaults and grouping;
+  tighter summaries and confirmations; and a generation step that's quicker and
+  more transparent about what it's doing.
+
+Have a stack you want supported or an idea to make the flow better?
+[Open an issue](https://github.com/uttam-gelot/payo/issues) or see
+[Contributing](#contributing).
+
 ## Requirements
 
 **To run Payo:** [Node.js](https://nodejs.org) **>= 18**. That's it — `npx @uge/payo`