Drive's Template Library Passes 300 Built-In Templates

Drive's template library has grown to 300 built-in templates — 100 documents, 100 spreadsheets, and 100 slide decks — organized into per-category files rather than one sprawling list. Of those, 31 are fillable: they define real fields and a buildWith function so a template can be populated programmatically, not just opened as a static starting point.

A real templates page

There's now a dedicated /templates page whose filter and search state lives in the URL, backed by a GET /api/templates endpoint supporting kind, category, search query, limit, and cursor-based pagination — so browsing 300 templates doesn't mean loading them all at once.

Templates for AI Agent, too

This release also gives Piskes Agent a drive.template.list capability and a drive.file.create_from_template action that accepts any built-in document ID. In practice, that means an agent can be asked to start a new file from a specific template by name rather than only creating documents from scratch — the same library backing the human-facing /templates page is available to the agent.

Scope of the change

The bulk of this release is the templates themselves, spread across categories including business, contracts (with a Vietnamese-market contracts set), education, HR, marketing and sales, personal, and project operations for documents; finance/budget, HR operations, inventory, personal, sales/CRM, and tracker/planning for spreadsheets; and business reports, education, events, pitch/fundraising decks, sales/marketing, and training/onboarding for slides. The older single-file template library module was removed in favor of this per-category structure, and the generated OpenAPI spec, MCP tool list, and gateway allow-list were all regenerated to include the new agent capability.

This shipped with the full Drive vitest suite passing — 82 files, 1,139 tests — and a clean guardrails run.