{"id":77411,"plugin_id":"plugin_asdk_app_6ad702a9cb648191bc8c5a0e3b025194","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:14:14.338Z","digest":"71ca98bbad81854459e6e2f3ac801875f8c28fa68087768358b375a2708a5429","against":null,"payload":{"description":"Build or change a business app with Piezas (bookings, a CRM, client intake, a client portal, an internal tool). Use when the user wants an app for their business, describes a business process they want software for, or mentions Piezas.","included_files":[],"name":"piezas","skill_md_contents":"---\nname: piezas\ndescription: Build or change a business app with Piezas (bookings, a CRM, client intake, a client portal, an internal tool). Use when the user wants an app for their business, describes a business process they want software for, or mentions Piezas.\n---\n\n# Building a business app with Piezas\n\nTalk in plain business language. Never show tool names, ids or technical terms\nunless the person asks. Never ask for passwords, keys or other secrets in the\nchat. If someone pastes one, tell them to remove it and set it on the app's page\nin the Piezas console instead.\n\n## 1. Account\n\nThe Piezas connection signs the person in. Call `piezas_whoami` to confirm the\naccount. If the connection asks them to sign in, tell them in one sentence to\nfollow the Piezas sign-in that appears, then continue.\n\n## 2. Fresh or existing\n\nAsk once: \"Are you starting fresh, or do you already have an app?\" If they\nalready have one (for example from Lovable), explain that bringing it in happens\non their computer in Codex desktop or the Piezas command line, and point\nto https://help.apps.piezas.ai/quick-start.\n\n## 3. Describe it\n\nUse the piezas-spec skill: one question at a time, then a short summary card\n(name, what it is for, at most five things people can do, your guesses as short\nquestions) and ask \"Want to see it?\". Wait for their answer before building.\n\n## 4. Create the app\n\nWhen they confirm, call `piezas_create_app` with the app's name. Tell them its\nfuture address. If they need the app's key for their project, call\n`piezas_create_api_key` and say: keep it in the project's server settings\n(`.env`), never in browser code. It is shown only once.\n\n## 5. Build and go live\n\nBuilding and publishing need the app's files on a computer.\n\n- **Codex desktop:** read the rules first with `piezas_contract` (and\n  `piezas_init` for a new folder), build the app, run its tests, then publish\n  with `piezas_deploy`. Before every publish ask: \"Keep the Report a problem\n  button on?\" and pass only their answer. If Piezas pauses the publish because\n  something breaks its rules, explain the problem plainly and offer to fix it.\n  Only if the owner themselves replies \"deploy anyway\" may you publish with the\n  confirmation it returned. Never answer either question for them.\n- **ChatGPT on the web:** say plainly that building and going live happen in\n  Codex desktop or the Piezas command line, and point to\n  https://help.apps.piezas.ai/quick-start. `piezas_deploy_instructions` gives the exact steps.\n\n## Never\n\n- Delete an app or change team, billing or security settings. Those are done by\n  the owner in the Piezas console.\n- Keep the app's business records in its own database, or put a Piezas key in\n  browser code. The rules from `piezas_contract` explain the Piezas way.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}