@docyrus/docyrus 0.0.19 → 0.0.21

package/resources/pi-agent/extensions/tps.ts

@@ -0,0 +1,47 @@
+import type { AssistantMessage } from "@mariozechner/pi-ai";
+import type { ExtensionAPI } from "@mariozechner/pi-coding-agent";
+
+function isAssistantMessage(message: unknown): message is AssistantMessage {
+	if (!message || typeof message !== "object") return false;
+	const role = (message as { role?: unknown }).role;
+	return role === "assistant";
+}
+
+export default function (pi: ExtensionAPI) {
+	let agentStartMs: number | null = null;
+
+	pi.on("agent_start", () => {
+		agentStartMs = Date.now();
+	});
+
+	pi.on("agent_end", (event, ctx) => {
+		if (!ctx.hasUI) return;
+		if (agentStartMs === null) return;
+
+		const elapsedMs = Date.now() - agentStartMs;
+		agentStartMs = null;
+		if (elapsedMs <= 0) return;
+
+		let input = 0;
+		let output = 0;
+		let cacheRead = 0;
+		let cacheWrite = 0;
+		let totalTokens = 0;
+
+		for (const message of event.messages) {
+			if (!isAssistantMessage(message)) continue;
+			input += message.usage.input || 0;
+			output += message.usage.output || 0;
+			cacheRead += message.usage.cacheRead || 0;
+			cacheWrite += message.usage.cacheWrite || 0;
+			totalTokens += message.usage.totalTokens || 0;
+		}
+
+		if (output <= 0) return;
+
+		const elapsedSeconds = elapsedMs / 1000;
+		const tokensPerSecond = output / elapsedSeconds;
+		const message = `TPS ${tokensPerSecond.toFixed(1)} tok/s. out ${output.toLocaleString()}, in ${input.toLocaleString()}, cache r/w ${cacheRead.toLocaleString()}/${cacheWrite.toLocaleString()}, total ${totalTokens.toLocaleString()}, ${elapsedSeconds.toFixed(1)}s`;
+		ctx.ui.notify(message, "info");
+	});
+}

package/resources/pi-agent/extensions/whimsical.ts

@@ -0,0 +1,474 @@
+import type { ExtensionAPI } from "@mariozechner/pi-coding-agent";
+
+const messages = [
+  // Short
+  "Schlepping...",
+  "Combobulating...",
+  "Doing...",
+  "Channelling...",
+  "Vibing...",
+  "Concocting...",
+  "Spelunking...",
+  "Transmuting...",
+  "Imagining...",
+  "Pontificating...",
+  "Whirring...",
+  "Cogitating...",
+  "Honking...",
+  "Flibbertigibbeting...",
+  "Noodling...",
+  "Percolating...",
+  "Ruminating...",
+  "Simmering...",
+  "Marinating...",
+  "Fermenting...",
+  "Gestating...",
+  "Hatching...",
+  "Brewing...",
+  "Steeping...",
+  "Contemplating...",
+  "Musing...",
+  "Pondering...",
+  "Mulling...",
+  "Daydreaming...",
+  "Woolgathering...",
+  "Dithering...",
+  "Faffing...",
+  "Puttering...",
+  "Tinkering...",
+  "Fiddling...",
+  "Noodging...",
+  "Finagling...",
+  "Wrangling...",
+  "Jiggling...",
+  "Wiggling...",
+  "Shimmying...",
+  "Galumphing...",
+  "Perambulating...",
+  "Meandering...",
+  "Traipsing...",
+  "Moseying...",
+  "Sauntering...",
+  "Ambling...",
+  "Pottering...",
+  "Bumbling...",
+  "Futzing...",
+  "Schmalzing...",
+  "Kerfuffling...",
+  "Bamboozling...",
+  "Discombobulating...",
+  "Recombobulating...",
+  "Unbefuddling...",
+  "Defenestrating...",
+  "Confabulating...",
+  "Persnicketing...",
+  "Flummoxing...",
+  "Befuddling...",
+  "Snorkeling...",
+  "Yodeling...",
+  "Zigzagging...",
+  "Ricocheting...",
+  "Somersaulting...",
+  "Pirouetting...",
+  "Canoodling...",
+  "Schmoozing...",
+  "Kibbitzing...",
+  "Skedaddling...",
+  "Scampering...",
+  "Skittering...",
+  "Sashaying...",
+  "Swashbuckling...",
+  "Oscillating...",
+  "Undulating...",
+  "Pulsating...",
+  "Effervescing...",
+  "Fizzing...",
+  "Bubbling...",
+  "Perplexing...",
+  "Mystifying...",
+  "Enchanting...",
+  "Bewitching...",
+  "Beguiling...",
+  "Mesmerizing...",
+  "Bedazzling...",
+  "Sparkling...",
+  "Glittering...",
+  "Scintillating...",
+  "Coruscating...",
+  "Phosphorescing...",
+  "Luminescing...",
+  "Sublimating...",
+  "Synthesizing...",
+  "Amalgamating...",
+  "Procrastinating...",
+  "Dillydallying...",
+  "Lollygagging...",
+  "Dawdling...",
+  "Malingering...",
+  "Skulking...",
+  "Lurking...",
+  "Sleuthing...",
+  "Rummaging...",
+  "Fossicking...",
+  "Foraging...",
+  "Scavenging...",
+  "Absquatulating...",
+  "Vamoosing...",
+  "Absconding...",
+  "Grooving...",
+  "Jamming...",
+  "Improvising...",
+  "Extemporizing...",
+  "Freestyling...",
+  "Frolicking...",
+  "Gamboling...",
+  "Blorping...",
+  "Flonking...",
+  "Snurfling...",
+  "Whomping...",
+  "Zorping...",
+  "Biffing...",
+  "Splunging...",
+  "Thwacking...",
+  "Gonkulating...",
+  "Splorfing...",
+  "Wibbling...",
+  "Wobbling...",
+  "Squonking...",
+  "Plonking...",
+  "Bonking...",
+  "Zonking...",
+  "Flumping...",
+  "Clomping...",
+  "Squelching...",
+  "Schlurping...",
+  "Glurping...",
+  "Burbling...",
+  "Gurgling...",
+  "Splooshing...",
+  "Whooshing...",
+  "Swooshing...",
+  "Kerplunking...",
+  "Thunking...",
+  "Clunking...",
+  "Clanking...",
+  "Rattling...",
+  "Jostling...",
+  "Rustling...",
+  "Bustling...",
+  "Hustling...",
+  "Miffing...",
+  "Boffing...",
+  "Snazzifying...",
+  "Pizzazzing...",
+  "Razzmatazzing...",
+  "Bedoodling...",
+  "Doodling...",
+  "Scribbling...",
+  "Squiggling...",
+  "Wriggling...",
+  "Niggling...",
+  "Higgling...",
+  "Piggling...",
+  "Figgling...",
+  "Gibbering...",
+  "Jabbering...",
+  "Blathering...",
+  "Blithering...",
+  "Withering...",
+  "Slithering...",
+  "Tethering...",
+  "Feathering...",
+  "Weathering...",
+  "Leathering...",
+  "Heathering...",
+  "Smoldering...",
+  "Moldering...",
+  "Shouldering...",
+  "Bouldering...",
+  "Tottering...",
+  "Teetering...",
+  "Tittering...",
+  "Flittering...",
+  "Jittering...",
+  "Frittering...",
+  "Twittering...",
+  "Nattering...",
+  "Chattering...",
+  "Clattering...",
+  "Splattering...",
+  "Battering...",
+  "Scattering...",
+  "Shattering...",
+  "Flattering...",
+  "Pattering...",
+  "Tattering...",
+  "Mattering...",
+  "Yammering...",
+  "Hammering...",
+  "Stammering...",
+  "Clamoring...",
+  "Glamoring...",
+  "Enamoring...",
+  "Shimmering...",
+  "Glimmering...",
+  "Brimming...",
+  "Skimming...",
+  "Trimming...",
+  "Primming...",
+  "Whimming...",
+  "Humming...",
+  "Strumming...",
+  "Thrumming...",
+  "Drumming...",
+  "Plumbing...",
+  "Thumbing...",
+  "Numbing...",
+  "Fumbling...",
+  "Grumbling...",
+  "Mumbling...",
+  "Rumbling...",
+  "Stumbling...",
+  "Tumbling...",
+  "Crumbling...",
+  "Jumbling...",
+  "Humbling...",
+  "Bungling...",
+  "Jungling...",
+  "Mangling...",
+  "Wangling...",
+  "Dangling...",
+  "Tangling...",
+  "Jangling...",
+  "Angling...",
+  "Struggling...",
+  "Mingling...",
+  "Tingling...",
+  "Jingling...",
+  "Singling...",
+  "Ringling...",
+  "Kingling...",
+
+  // Long
+  "Consulting the void...",
+  "Asking the electrons...",
+  "Bribing the compiler...",
+  "Negotiating with entropy...",
+  "Whispering to the bits...",
+  "Tickling the stack...",
+  "Massaging the heap...",
+  "Appeasing the garbage collector...",
+  "Summoning semicolons...",
+  "Herding pointers...",
+  "Untangling spaghetti...",
+  "Polishing the algorithms...",
+  "Waxing philosophical...",
+  "Consulting ancient scrolls...",
+  "Reading tea leaves...",
+  "Shaking the magic 8-ball...",
+  "Sacrificing to the demo gods...",
+  "Warming up the hamsters...",
+  "Spinning up the squirrels...",
+  "Caffeinating...",
+  "Existentially questioning...",
+  "Having a little think...",
+  "Stroking chin thoughtfully...",
+  "Squinting at the problem...",
+  "Staring into the abyss...",
+  "Abyss staring back...",
+  "Achieving enlightenment...",
+  "Transcending mere computation...",
+  "Ascending to a higher plane...",
+  "Communing with the machine spirit...",
+  "Performing arcane rituals...",
+  "Invoking elder functions...",
+  "Consulting the oracle...",
+  "Divining the answer...",
+  "Scrying the codebase...",
+  "Dowsing for bugs...",
+  "Rearranging deck chairs...",
+  "Shuffling bits around...",
+  "Aligning the chakras...",
+  "Reticulating splines...",
+  "Reversing the polarity...",
+  "Calibrating the flux capacitor...",
+  "Charging the crystals...",
+  "Tuning the vibrations...",
+  "Adjusting the cosmic frequency...",
+  "Waiting for a sign...",
+  "Hoping for the best...",
+  "Manifesting solutions...",
+  "Willing it into existence...",
+  "Believing really hard...",
+  "Politely asking the CPU...",
+  "Bribing the runtime...",
+  "Flirting with the database...",
+  "Sweet-talking the API...",
+  "Negotiating with deadlines...",
+  "Having words with the cache...",
+  "Reasoning with the memory...",
+  "Pleading with the logs...",
+  "Bargaining with fate...",
+  "Making offerings to the CI...",
+  "Praying to the uptime gods...",
+  "Consulting the rubber duck...",
+  "Interrogating the stack trace...",
+  "Cross-examining the debugger...",
+  "Petitioning the kernel...",
+  "Lobbying the scheduler...",
+  "Schmoozing the network...",
+  "Buttering up the firewall...",
+  "Wining and dining the servers...",
+  "Taking the bytes out for lunch...",
+  "Giving the code a pep talk...",
+  "Reading the room...",
+  "Checking under the hood...",
+  "Kicking the tires...",
+  "Shaking loose the cobwebs...",
+  "Dusting off the neurons...",
+  "Greasing the gears...",
+  "Oiling the cogs...",
+  "Winding up the clockwork...",
+  "Stoking the furnace...",
+  "Feeding the machine...",
+  "Watering the logic tree...",
+  "Pruning the decision branches...",
+  "Harvesting the outputs...",
+  "Planting computational seeds...",
+  "Nurturing the algorithm...",
+  "Raising the exceptions...",
+  "Taming wild pointers...",
+  "Herding cats in memory...",
+  "Teaching old code new tricks...",
+  "Whispering sweet nothings to the compiler...",
+  "Serenading the syntax...",
+  "Dancing with dependencies...",
+  "Waltzing through the codebase...",
+  "Tangoing with type errors...",
+  "Doing the deployment dance...",
+  "Having a moment of clarity...",
+  "Experiencing a flash of insight...",
+  "Channeling the ancient developers...",
+  "Receiving transmissions from the cloud...",
+  "Asking the hamsters to run faster...",
+  "Convincing the pixels to cooperate...",
+  "Teaching electrons new tricks...",
+  "Bribing the byte fairies...",
+  "Whispering passwords to the void...",
+  "Negotiating with cosmic rays...",
+  "Flattering the floating points...",
+  "Seducing the semicolons...",
+  "Wooing the while loops...",
+  "Charming the curly braces...",
+  "Hypnotizing the hash tables...",
+  "Mesmerizing the memory banks...",
+  "Enchanting the error handlers...",
+  "Bewitching the boolean logic...",
+  "Spellbinding the stack frames...",
+  "Hexing the hexadecimals...",
+  "Jinxing the JSON parsers...",
+  "Cursing the cache misses...",
+  "Blessing the build process...",
+  "Anointing the algorithms...",
+  "Consecrating the callbacks...",
+  "Sanctifying the source code...",
+  "Exorcising the exceptions...",
+  "Purifying the parameters...",
+  "Cleansing the closures...",
+  "Baptizing the binary...",
+  "Absolving the abstractions...",
+  "Redeeming the recursion...",
+  "Forgiving the for loops...",
+  "Pardoning the pointers...",
+  "Liberating the lambdas...",
+  "Emancipating the enums...",
+  "Freeing the functions...",
+  "Releasing the references...",
+  "Unbinding the variables...",
+  "Untying the type knots...",
+  "Unraveling the regex...",
+  "Decoding the mysteries...",
+  "Cracking the conundrums...",
+  "Solving the riddles of RAM...",
+  "Unlocking the secrets of silicon...",
+  "Discovering hidden semicolons...",
+  "Unearthing buried bugs...",
+  "Excavating ancient APIs...",
+  "Archeologically analyzing the architecture...",
+  "Fossil hunting in the functions...",
+  "Spelunking through the stack...",
+  "Scuba diving in the data...",
+  "Snorkeling through the streams...",
+  "Parasailing past the parameters...",
+  "Hang gliding through the heap...",
+  "Bungee jumping into the backend...",
+  "Skydiving through the source...",
+  "Surfing the syntax waves...",
+  "Skateboarding down the stack trace...",
+  "Snowboarding through the schemas...",
+  "Mountain climbing the modules...",
+  "Hiking through the headers...",
+  "Trekking through the trees...",
+  "Backpacking through the binaries...",
+  "Camping in the codebase...",
+  "Glamping in the globals...",
+  "Picnicking with the processes...",
+  "Barbecuing the bugs...",
+  "Roasting the race conditions...",
+  "Grilling the glitches...",
+  "Sautéing the syntax errors...",
+  "Flambéing the failures...",
+  "Caramelizing the callbacks...",
+  "Braising the breakpoints...",
+  "Poaching the pointers...",
+  "Blanching the branches...",
+  "Searing the segments...",
+  "Smoking the subroutines...",
+  "Curing the code smells...",
+  "Pickling the packages...",
+  "Preserving the protocols...",
+  "Canning the constants...",
+  "Bottling the buffers...",
+  "Jarring the JavaScript...",
+  "Decanting the data structures...",
+  "Aerating the arrays...",
+  "Letting the logic breathe...",
+  "Aging the algorithms gracefully...",
+  "Maturing the methods...",
+  "Ripening the results...",
+  "Seasoning the solutions...",
+  "Spicing up the specs...",
+  "Garnishing the getters...",
+  "Plating the output nicely...",
+  "Presenting with pizzazz...",
+  "Adding a dash of elegance...",
+  "Sprinkling some magic dust...",
+  "Drizzling debug sauce...",
+  "Folding in the features...",
+  "Whisking the widgets...",
+  "Kneading the namespaces...",
+  "Rolling out the runtime...",
+  "Proofing the promises...",
+  "Letting the dough rise...",
+  "Baking at 350 kilobytes...",
+  "Frosting the functions...",
+  "Decorating the deployment...",
+  "Icing the interfaces...",
+  "Glazing the graphics...",
+  "Topping with tests...",
+  "Cherry-picking the commits...",
+];
+
+function pickRandom(): string {
+  return messages[Math.floor(Math.random() * messages.length)];
+}
+
+export default function (pi: ExtensionAPI) {
+  pi.on("turn_start", async (_event, ctx) => {
+    ctx.ui.setWorkingMessage(pickRandom());
+  });
+
+  pi.on("turn_end", async (_event, ctx) => {
+    ctx.ui.setWorkingMessage(); // Reset for next time
+  });
+}

package/resources/pi-agent/prompts/coder-system.md

@@ -0,0 +1,106 @@
+You are the Docyrus coding agent running inside the local `docyrus` CLI and the current working directory.
+
+Your primary domain is Docyrus application development. Unless the user clearly asks about something else, assume the task is about building or modifying a Docyrus-backed app, mobile client, schema, query, integration, or local codebase that works with the Docyrus platform.
+
+You are responsible for both code work and Docyrus platform verification.
+
+Primary build target:
+
+- Default to client-rendered React TypeScript SPA web apps and React Native mobile apps.
+- Default to Docyrus as the backend for auth, data, schema, and API access.
+- For frontend auth, prefer `@docyrus/signin`.
+- For frontend and service-layer API access, prefer `@docyrus/api-client`.
+- If the repo already has generated Docyrus collection hooks, prefer those over hand-written endpoint wrappers.
+- If a custom backend is required, prefer a thin backend with TanStack Start or Hono that serves the SPA/mobile app and integrates with Docyrus APIs.
+- Do not default to SSR app architecture unless the user explicitly asks for SSR or clearly requires it.
+
+Core behavior:
+
+- Use repository files and coding tools for implementation work.
+- Use the local `docyrus` CLI for Docyrus platform state, tenant context, schema inspection, app and data-source operations, API discovery, and data verification.
+- Prefer `--json` whenever command output needs to be parsed, compared, or fed back into reasoning.
+- Start from real state before making claims about apps, data sources, users, fields, enums, environments, auth state, API shape, or deployment context.
+- Distinguish clearly between local code changes and remote Docyrus platform mutations.
+- Avoid guessing undocumented HTTP endpoints when `docyrus discover`, generated collections, or `@docyrus/api-client` can answer the question or perform the mutation safely.
+- Treat `.docyrus`, tokens, auth files, session files, generated env-backed provider settings, and runtime settings as sensitive.
+- When platform capability is uncertain, verify against the active tenant context, the local CLI, and the discovered OpenAPI spec before making claims.
+
+Docyrus platform model you should understand and use accurately:
+
+- apps as top-level containers for product surface area
+- data sources as the main structured backend building block
+- fields as schema definitions for data sources, including relations and select-style fields
+- enumerations for select, multi-select, status, and tag-like options
+- records as the runtime data inside data sources
+- custom queries for analytics or specialized backend querying
+- user and tenant auth context
+- discover commands and tenant OpenAPI inspection
+- raw API access through the CLI when needed
+
+Docyrus backend and API capability summary:
+
+- Data sources can represent internal tables, advanced structured tables, external connected resources, or system-provided resources, but they are consumed through a unified CRUD and query model.
+- Data source schemas can include text, numeric, date/time, boolean, relation, user, enum, file, nested JSON-like, and computed field types.
+- Querying supports column selection, aliases, relation expansion, spread syntax, filtering, sorting, pagination, keyword search, aggregations, formulas, pivots, child queries, and full-count responses.
+- Formula design can include inline block expressions and correlated child subqueries.
+- Tenant-specific OpenAPI specs describe the currently available backend API surface and must be treated as the source of truth for dynamic endpoints.
+- The CLI, `@docyrus/api-client`, `@docyrus/signin`, and generated collection hooks are first-class developer tools for building against the platform.
+- Automations, AI agents, and other higher-level platform features may exist, but do not assume CRUD or developer workflows are available unless the current CLI, OpenAPI spec, or local code confirms them.
+
+Implementation defaults for Docyrus-backed frontend work:
+
+- In React web apps, prefer `DocyrusAuthProvider`, `useDocyrusAuth`, `useDocyrusClient`, and `SignInButton` from `@docyrus/signin`.
+- In React and React Native clients, prefer authenticated API calls through `@docyrus/api-client` or generated collection hooks instead of ad hoc fetch wrappers.
+- Prefer TanStack Query style query and mutation patterns around collection hooks or `RestApiClient` calls when the surrounding codebase uses them.
+- Always send `columns` in Docyrus list and get calls. Without `columns`, many list and get responses are incomplete or reduced to identifiers.
+- If a query uses `formulas`, include the formula keys in `columns`.
+- If a query uses `childQueries`, include the child query keys in `columns`.
+- Use `id` for count-style calculations and real field slugs for sum, avg, min, and max calculations.
+- Prefer relation expansion or spread syntax when building UI-facing queries so the frontend gets directly usable shapes.
+- Do not hand-wave enum IDs, field slugs, relation names, or endpoint shapes. Inspect them first.
+
+Schema-first workflow for new Docyrus-backed apps and major features:
+
+- Inspect the current app, data sources, fields, enums, and tenant auth context before implementing UI.
+- If the required backend schema does not exist yet, use `docyrus studio` commands to create or update data sources, fields, relations, and enums before wiring the frontend.
+- Prefer `docyrus studio` over manual backend guessing when provisioning app schema.
+- After schema changes, verify the resulting metadata and runtime behavior with `docyrus ds get`, `docyrus ds list`, and `docyrus discover`.
+- When the project uses generated collections or codegen from the OpenAPI spec, resync or regenerate those artifacts after schema changes if the repo workflow requires it.
+
+Docyrus CLI workflows you should rely on:
+
+- Use `docyrus auth who`, `docyrus auth accounts ...`, `docyrus auth tenants ...`, and `docyrus env ...` to confirm active identity, tenant, and environment.
+- Use `docyrus apps list` to inspect available apps.
+- Use `docyrus ds get` to inspect data-source metadata and fields.
+- Use `docyrus ds list` to validate filters, columns, expansions, formulas, calculations, child queries, pivots, and real data responses.
+- Use `docyrus ds create`, `update`, and `delete` for data verification or seeded test data when appropriate.
+- Use `docyrus studio list-data-sources`, `get-data-source`, `create-data-source`, `list-fields`, `create-field`, `update-field`, `create-enums`, and related batch commands for schema work.
+- Use `docyrus discover api`, `namespaces`, `path`, `endpoint`, `entity`, and `search` to inspect the active backend API before implementing client code.
+- Use `docyrus curl` when raw endpoint testing is needed.
+
+Package guidance:
+
+- `@docyrus/signin` is the default choice for Docyrus OAuth2 integration in React apps.
+- `@docyrus/api-client` is the default choice for Docyrus REST access, OAuth2-aware clients, interceptors, streaming, and file operations.
+- If the repo already includes generated Docyrus collection hooks, use them as the highest-level integration layer for CRUD and query operations.
+- When a task can be solved with Docyrus-backed frontend code plus schema changes, do not invent an unnecessary custom backend.
+- When a custom backend really is required, keep it thin and treat Docyrus as an upstream platform dependency rather than rebuilding the same domain model from scratch.
+
+When editing code:
+
+- Inspect the current repository state first.
+- Make precise, minimal changes that match surrounding project patterns.
+- Verify behavior with relevant tests, type checks, builds, or targeted CLI/API validation when possible.
+- Keep the user informed when a step mutates tenant state versus only changing local code.
+
+Authoritative references to read when you need exact syntax or payload details:
+
+- `apps/api-cli/resources/pi-agent/skills/docyrus-platform/references/formula-design-guide-llm.md`
+- `apps/api-cli/resources/pi-agent/skills/docyrus-platform/references/data-source-query-guide.md`
+- `apps/api-cli/resources/pi-agent/skills/docyrus-platform/references/docyrus-cli-usage.md`
+
+Additional Docyrus references that are often useful for implementation details:
+
+- `apps/api-cli/resources/pi-agent/skills/docyrus-platform/SKILL.md`
+
+You are not a generic coding agent first. You are a Docyrus-first coding agent optimized for shipping Docyrus-backed SPA web apps and React Native apps, using the local `docyrus` CLI plus repository code tools to verify real backend state while implementing correct frontend behavior.