Skip to content

Design V2 Deploy: generalise "Open in vscode.dev" to VS Code and Claude Code, recommend the AP extension and include agent skills #1122

Open

Description

@mttrbrts

Summary

The Design V2 Deploy → Open in vscode.dev card saves the template as a folder and points people to vscode.dev. The same folder works just as well in a local VS Code install, or in an AI coding agent such as Claude Code or GitHub Copilot. This issue proposes:

  1. Generalise the card: "Open in an editor", with VS Code for the Web, desktop VS Code and Claude Code as targets.
  2. Recommend the Accord Project VS Code extension automatically, by writing .vscode/extensions.json into the saved folder.
  3. Point agents to the Accord Project skills: write an AGENTS.md into the saved folder that describes the template layout and links accordproject/skills, so an agent opened there knows how to work on the template.

How it works today

  • src/components/designV2/constants.ts (Deploy cards, "Open in vscode.dev"):
    • button 1. Save as folder (action: "vscode")
    • secondary link 2. Open vscode.dev (URLS.vscodeDev)
  • src/components/designV2/DeployView.tsx (case "vscode"):
    • picks a folder with the File System Access API (src/utils/saveToFolder.ts)
    • writes the files from exportTemplateFiles (src/utils/templateArchive.ts): package.json, text/grammar.tem.md, model/*.cto, logic/*, request.json, sample.json
    • falls back to downloading a .cta in browsers without folder support
  • The saved folder contains no editor or agent configuration.

Proposal

1. "Open in an editor" with several targets

Keep step 1 (Save as folder) as it is. Replace step 2 with a choice:

Target Step 2
VS Code for the Web Link to vscode.dev, then File › Open Folder (today's behaviour)
VS Code (desktop) Copyable command code <folder>, or File › Open Folder
Claude Code Copyable command cd <folder> && claude
Others (Cursor, Copilot, …) Optional, same pattern

Browsers never expose the saved folder's absolute path. The File System Access API only gives a directory handle and its name. So the playground can't build a vscode://file/<abs-path> link or a full cd command. The commands should use the folder name the user picked (shown in the success toast) and say so. Keep the copy short and honest, e.g. "Run this in the folder you chose".

Rename the action and copy from vscode / "Open in vscode.dev" to something editor-neutral, keeping the existing tests passing or updating them.

2. Recommend the Accord Project VS Code extension

Add .vscode/extensions.json to exportTemplateFiles:

{
  "recommendations": ["accordproject.concerto-vscode-extension"]
}

VS Code (desktop and web) then offers to install it when the folder opens. The footer already links this ID (src/constants/content/footer.json). Confirm it's the right extension for templates, as opposed to Concerto only, and add any other Accord Project extension that applies.

3. Point agents to the Accord Project skills (decided: AGENTS.md)

Don't copy or fetch the skills. Write a short AGENTS.md into the saved folder that:

  • describes the template layout: text/grammar.tem.md (TemplateMark), model/*.cto (Concerto), logic/*.ts, request.json, sample.json, package.json
  • points to accordproject/skills and gives the one-line install: npx skills add accordproject/skills
  • names the most relevant skills (template-author, concerto-author, concerto-validate)

AGENTS.md is read by Claude Code, Copilot, Codex, Cursor and other agents, so one file covers them all. Bundling or fetching the skills isn't needed: the skills repo stays the single source, and nothing in the playground goes stale.

Related: "Copy for AI" (#1108)

This is part of the "bring your own agent" direction in the RFC #1108:

The AGENTS.md text and the "Copy for AI" prompt should share their wording: same layout description, same pointer to the skills. Put that text in one module (e.g. src/agent-context/, as #1108 suggests) and use it for both, so they don't drift apart.

Out of scope

  • Pushing the template to a GitHub repo, or opening it in Codespaces or vscode.dev/github/.... That could be a follow-up.
  • Changing the .cta archive format. The extra files are for the folder export only, unless we decide they belong in archives too.

Acceptance criteria

  • The Deploy card offers VS Code for the Web, VS Code desktop and Claude Code as step-2 targets, with accurate instructions.
  • The saved folder includes .vscode/extensions.json recommending the Accord Project extension.
  • The saved folder includes an AGENTS.md describing the layout and pointing to accordproject/skills, sharing its text with the "Copy for AI" prompt from RFC: AI in Template Playground — bring your own agent #1108 if that has landed.
  • Browsers without folder support still get the .cta fallback, with copy that mentions all targets.
  • Unit tests: exportTemplateFiles includes the new files, and the card renders each target.
  • Ant Design components only, per AGENTS.md.

Activity

  1. Khush7Chauhan commented on Nov 16, 2026

    @Khush7Chauhan
    Contributor

    I'd like to pick this up if nobody else is on it. Before I start, a couple of things I'd rather not guess at.

    Is accordproject.concerto-vscode-extension the right recommendation for template folders, or should it list another Accord Project extension alongside it? And would you rather this land as one PR, or be split — the Deploy card targets first, then .vscode/extensions.json, then AGENTS.md? I can do either.

    On AGENTS.md: should it go in now, or wait for the "Copy for AI" module from #1108 so both share the same text? A steer on the exact step-2 wording for the three targets would help too, since that's user-facing copy.

  2. codewithchotu commented on Nov 16, 2026

    @codewithchotu
    Contributor

    Hi @mtrbrts,

    I've been exploring how the proposed agent-workspace setup could evolve into a smoother developer experience for Accord Project templates.

    I've attached a couple of visual concepts to communicate the idea.

    The proposed workflow:

    1. Export an Accord Project template as a folder.
    2. Include AGENTS.md with template-specific instructions and references to official Accord Project skills.
    3. Recommend the Concerto VS Code extension automatically.
    4. Make the exported folder ready to continue development in VS Code, vscode.dev, or Claude Code.
    5. Eventually introduce an editor-selection experience directly within Template Playground.

    I've implemented the initial agent-workspace setup in [PR #1128](#1128).

    The attached visuals are exploratory concepts to communicate the broader direction, rather than finalized UI designs.

    I'd appreciate your thoughts on whether this direction aligns with the intended experience.

    a_polished_dark_to_light_modern_ui_infographic_fo a_polished_dark_mode_github_issue_comment_mockup_s
  3. codewithchotu commented on Nov 19, 2026

    @codewithchotu
    Contributor

    @averif i am aledy working on this @mttrbrts has already assigned me to do this

  4. codewithchotu commented on Nov 19, 2026

    @codewithchotu
    Contributor

    Hi @mttrbrts,

    Thanks for the direction on this issue! I've completed the implementation based on the approach you outlined.

    The changes are available in PR #1141: #1141

    The implementation includes:

    • Generalising the Deploy card to "Open in an editor", with VS Code for the Web, Desktop VS Code, and Claude Code as targets.
    • Adding .vscode/extensions.json to recommend the Accord Project extension.
    • Adding AGENTS.md to the exported folder with template context and a pointer to accordproject/skills.
    • Keeping the reusable agent context in src/agent-context/.

    I've also run the full Playwright E2E suite locally:

    28 tests passed, including the new editor targets test and the sandbox worker takeover test.

    The unit tests also pass (31 tests).

    PR #1141 is ready for review. Thanks!

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

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions