What PumaForm does

It builds the Apps Script that creates a Google Form, without ever talking to Google. You write the poll here, copy the script out, and run it inside your own Workspace — so a survey about your staff is built by your organisation rather than by a third party you had to trust with the question list.

• Polls are workspaces — one tab per poll, dragged to reorder, double-clicked to rename. The tab name is the form title, so the two cannot drift apart.
• Import a question set from another app — a .pumaform spec exported by PumaSkills arrives as a new poll with its competency ids intact.
• Locked ids survive the round trip — a question carried in from another app keeps the id that app knows it by, shown as an amber pill. Reword the title however you like: the id is held apart from the prose and re-attached on export, so the response column keeps its key.
• Every Forms question type — multiple choice, checkbox, dropdown, short answer, paragraph, linear scale, grids, date and time.
• Branching that tells you when it will not fire — go-to rules are folded away on the question types Google Forms cannot navigate from, and the validator names the ones that would be silently ignored.
• A live preview of how the form will read — the right-hand column, toggled from the topbar.
• Validation before you paste — errors and warnings are counted above the editor, and the script modal repeats the count rather than letting you find out at run time.
• Nothing leaves the page — no network requests, no account, no analytics. The script is a text file you carry to script.google.com yourself.

See the Keyboard tab for every shortcut.