Brief NitroGAS Co-Pilot so you get working Apps Script

Co-Pilot is optional. The NitroGAS extension stays free forever for snippets and the editor workflow. When you do use Co-Pilot, the quality of the Apps Script you get tracks the quality of the brief — not the vibes in the prompt. Here's how we brief it on real bootstrapper jobs: paste headers, say what "done" looks like, list constraints, ask for one function, then verify in the editor before you trust it on live data.

TL;DR

• Paste sheet headers and a one-line outcome ("append unique leads by email").
• Constraints beat adjectives: batch writes, no custom functions, dry-run flag, lock.
• Ask for one function (or a tiny set) — not an entire product.
• Verify: run on a copy tab, check quotas assumptions, read the code before authorize-all.
• Free NitroGAS forever; Co-Pilot when you're stuck — pay when you need it.

What is NitroGAS Co-Pilot for (and not for)?

For: drafting helpers you already understand — header maps, upserts, trigger installers, try/catch alerts — faster than typing from memory.

Not for: inventing your business logic, guessing undocumented APIs, or replacing a code review. If you couldn't explain the function to a junior after reading it, don't ship it.

Snippets cover the 80% patterns. Co-Pilot helps with the awkward 20% where your sheet names and constraints are weird.

What should you paste into the brief?

Minimum packet:

1. Headers — exact strings from row 1 (email, name, status, syncedAt)
2. Sheet names — Leads, Log, Archive
3. Done looks like — "Upsert by email; set syncedAt; log counts"
4. Constraints — bullet list (below)
5. Out of scope — "Don't build a sidebar; don't use custom functions"

Example brief:

Sheet: Leads Headers: email | name | status | syncedAt Write a function syncLeads_(rows) that: - upserts by email using batch getValues/setValues - sets syncedAt to now on writes - returns { written, skipped } Constraints: - no cell-by-cell I/O - no custom functions (=myFn) - honor a Script Property DRY_RUN=true (log only) - use withDocumentLock around the write section

Which constraints actually improve the output?

These pay rent every time:

Constraint	Why
Batch getValues / setValues	Stops quota-burning loops
No custom functions	Custom fns recalculate and thrash
Dry-run Script Property	Safe rehearsal on prod sheets
Lock (withDocumentLock)	Stops overlapping triggers
Header map by name	Survives inserted columns
One entry function + _ helpers	Readable review

Avoid vague asks like "make it production ready" or "use best practices" — model them as bullets instead.

How do you ask for one function instead of a system?

Bad: "Build my client onboarding system with menus, APIs, and dashboards."

Better: "Write copyTemplateSheet(ss, templateName, newName) that copies a tab, clears data rows, stamps Created."

Then a second turn: "Add menuNewClientSheet that prompts for a name and calls it."

Small surfaces are reviewable. Giant pastes hide the footgun on line 180.

How do you verify before live data?

1. Read the code — unknown services? surprise UrlFetch? delete or justify.
2. Copy the tab — run against Leads_TEST with three rows.
3. Dry run on — confirm zero writes when DRY_RUN=true.
4. Dry run off — three-row success, then a duplicate-key case.
5. Trigger last — install time-driven only after menu runs are boring.

Authorize scopes deliberately. If Co-Pilot suggests Drive + Gmail + Spreadsheets for a sheet-only upsert, push back.

What does a good follow-up look like?

When the first draft is close:

Keep syncLeads_. Change only: - key column is "Email" (capital E) - skip rows where status === "closed" - log to sheet Log with level INFO/ERROR Do not add a sidebar.

Surgical follow-ups beat re-rolling the whole prompt. Paste the current function if the thread lost context.

Why do vague prompts produce confident wrong code?

Models fill gaps with popular tutorials: custom functions, getValue in loops, SpreadsheetApp.flush() sprinkled like confetti, OAuth for APIs you don't need. Your constraints are the diff between "looks like Apps Script" and "fits this workbook."

If you can't list constraints, you're not ready to generate — sketch the bullet list first on paper.

Example: bad brief vs good brief

Bad

Make a script that syncs my leads from the API and keeps the sheet updated nicely.

Good

Sheet Leads headers: email | name | status | syncedAt API: GET https://api.example.com/leads returns JSON array [{email,name,status}] Function importLeads(): - UrlFetch once, parse JSON - upsert by email (batch read/write) - set syncedAt on change - return { fetched, written, skipped } Constraints: muteHttpExceptions, retry on 429/5xx max 4, DRY_RUN property, no custom functions

Same job, vastly less cleanup.

How do snippets and Co-Pilot work together?

Typical flow:

1. Install / open NitroGAS; pull a snippet close to the problem (upsertRowByKey, buildHeaderMap, emailErrorAlert).
2. If the snippet needs shaping for your headers/API, brief Co-Pilot with the snippet name + your constraints.
3. Paste the result under a _ helper; keep the snippet's mental model.

You're not choosing "snippets XOR AI." Snippets are the catalog; Co-Pilot is the adapter.

What should you refuse in generated code?

Delete or rewrite if you see:

• Custom functions for heavy I/O
• Per-cell reads/writes in loops
• Hard-coded column letters for business fields
• Secrets in source (apiKey = '…') — use Script Properties
• eval / runaway UrlFetch without quotas thinking
• UI alerts inside time-driven entry points

Minimal rehearsal checklist

1. Brief with headers + constraints → one function returned.
2. Rename one header in the brief → follow-up fixes map only.
3. Ask for dry-run → no writes when property true.
4. Run on three-row copy tab → counts match.
5. Only then point at the live tab / install trigger.

Soft product note (no hype)

NitroGAS is free to keep using for snippets and everyday Apps Script work. Co-Pilot is optional — there when a brief like the ones above would save you an hour, and you can pay when you need it. No need to rename your workflow around AI; treat it like a fast junior who needs a crisp ticket.

Closing checklist

• Headers + sheet names pasted exactly
• One-sentence definition of done
• Explicit constraints (batch I/O, dry-run, locks, no custom fns)
• Asked for one function (or a tiny pair)
• Reviewed code; tested on a copy tab
• Trigger installed only after menu path is boring

Happy Coding!