Skip to content

feat(docs): add Sanity, Typefully, and GitHub agent templates - #1268

Open
bensabic wants to merge 2 commits into
mainfrom
docs/three-templates
Open

feat(docs): add Sanity, Typefully, and GitHub agent templates#1268
bensabic wants to merge 2 commits into
mainfrom
docs/three-templates

Conversation

@bensabic

Copy link
Copy Markdown
Contributor

Adds three vercel-labs templates to the gallery at /templates.

Template Slug Integrations Source
Sanity sanity-copilot Slack, Sanity, Notion sanity-copilot-eve-template @ f076b80
Typefully typefully Slack, Typefully, Notion typefully-eve-template @ 3627b22
GitHub kody GitHub, Linear, Resend kody-eve-template @ 8427e3c

Each entry mirrors the template's core authored surface — agent.ts, instructions, sandbox, channels, connections, tools, SKILL.md files, subagents, and (where present) schedules. The deep skills/*/references/*.md and rules/*.md docs are excluded: they run to 355 KB on the Sanity template alone, and leaving them out also avoids needing a json variant on TemplateFile["language"] for Typefully's banned-words.json files. Every embedded file was verified byte-for-byte against its upstream clone.

Setup prompts are each template's own "quick start with an AI coding agent" prompt from its README, which points at the hosted setup doc. That differs from the three existing entries, whose prompts describe the copy-and-configure steps inline.

File browser ordering

categoryOrder in file-viewer.tsx renders any unlisted name after everything else, so the new templates surfaced instructions.ts, sandbox.ts, and schedules stranded below lib — and Kody's order differed from the other two because only instructions.md was listed. Standalone files now lead, folders follow, and all three render the same sequence:

agent.ts → instructions.* → sandbox.ts → channels → connections → schedules → skills → tools → subagents → lib

This also moves the Design template's sandbox/ folder from last position into the same slot the other templates' sandbox.ts occupies — the one behavior change to an existing template.

Integrations

Adds Sanity, Typefully, GitHub, and Resend to TemplateIntegration. githubLogo and resendLogo already existed. sanityLogo wraps SiSanity, and typefullyLogo is an inline mark (Typefully isn't in simple-icons). Both inherit currentColor rather than a brand hex, so they match the neighbouring icons and work in dark mode — simple-icons registers Sanity as #0D0E12, which rendered near-black and ignored the grayscale class.

Notes

  • The GitHub template runs on anthropic/claude-fable-5; the other six are claude-sonnet-5.
  • It's also the first entry with no chat-surface tag — its surfaces are GitHub, Linear, and email via Resend.
  • Docs-only, so no changeset.

Mirror the authored surface of three vercel-labs templates into the
gallery, pinned to the revision each was copied from. Each entry uses the
template's own setup prompt.

Fix the file browser's category order along the way: names missing from
the list rendered last, so instructions.ts, sandbox.ts, schedules, and the
design template's sandbox folder were stranded below lib. Standalone files
now lead, folders follow, and every template renders the same sequence.

Signed-off-by: Ben Sabic <bensabic@users.noreply.github.com>
@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
eve-docs Ready Ready Preview, Comment, Open in v0 Jul 28, 2026 2:20pm
eve-docs-1644 Ready Ready Preview, Comment, Open in v0 Jul 28, 2026 2:20pm
eve-docs-4759 Ready Ready Preview, Comment, Open in v0 Jul 28, 2026 2:20pm

@cmpadden cmpadden left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to land this for now - thanks!

@bensabic something I'd like to discuss is how templates and registry items can coexist. Something I could imagine is being able to "build your own" template composing extensions / connections from the registry, then we could scaffold those components into a project for the user.

This would aid in template maintenance, but would add increased complexity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants