Skip to content

Conversation

@chrisradek
Copy link
Member

This updates the copilot instructions to better support 2 scenarios:

  1. Initializing a new TypeSpec project. I already saw the init typespec tool called when using a prompt like "Help me create a new Azure service using TypeSpec named Radek Trinkets". Including the structure guidelines helps copilot choose better directory names for the typespec project.
  2. Provides a link to the common typespec-docs.instructions.md file. With this, the agent actually uses our published TypeSpec/TypeSpec azure llms.txt files to pinpoint which docs to load

@github-actions
Copy link

github-actions bot commented Sep 11, 2025

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ The required check named Protected Files has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide


Comment generated by summarize-checks workflow run.

@chrisradek
Copy link
Member Author

Updated the docs to use the v2 spec for folder structure.

Here's a test run showing the agent asking for the info needed to create the folder:
image


Before creating or initializing a TypeSpec project, you must know your org name, service name, and the type of service: data-plane or control-plane (ARM).

Then create a new project directory under the `specification/<orgName>/resource-manager/<RPNamespace>/<ServiceName>` or `specification/<orgName>/data-plane/<ServiceName>` path, following the guidelines below.
Copy link
Member

Choose a reason for hiding this comment

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

@qiaozha FYI as you are working on the V2 conversion
CC: @josefree

@chrisradek chrisradek merged commit 04d520c into Azure:main Sep 15, 2025
44 of 46 checks passed
markcowl pushed a commit to markcowl/azure-rest-api-specs that referenced this pull request Sep 18, 2025
…zure#37361)

* update copilot instructions for tsp init and typespec doc retrieval

* update typespec structure guidelines

* missed unstaged change

* fix formatting

---------

Co-authored-by: Christopher Radek <[email protected]>
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.

3 participants