|
| 1 | +<!-- Use this file to provide workspace-specific custom instructions to Copilot. For more details, visit https://code.visualstudio.com/docs/copilot/copilot-customization#_use-a-githubcopilotinstructionsmd-file --> |
| 2 | +- [ ] Verify that the copilot-instructions.md file in the .github directory is created. |
| 3 | + |
| 4 | +- [ ] Clarify Project Requirements |
| 5 | + <!-- Ask for project type, language, and frameworks if not specified. Skip if already provided. --> |
| 6 | + |
| 7 | +- [ ] Scaffold the Project |
| 8 | + <!-- |
| 9 | + Ensure that the previous step has been marked as completed. |
| 10 | + Call project setup tool with projectType parameter. |
| 11 | + Run scaffolding command to create project files and folders. |
| 12 | + Use '.' as the working directory. |
| 13 | + If no appropriate projectType is available, search documentation using available tools. |
| 14 | + Otherwise, create the project structure manually using available file creation tools. |
| 15 | + --> |
| 16 | + |
| 17 | +- [ ] Customize the Project |
| 18 | + <!-- |
| 19 | + Verify that all previous steps have been completed successfully and you have marked the step as completed. |
| 20 | + Develop a plan to modify codebase according to user requirements. |
| 21 | + Apply modifications using appropriate tools and user-provided references. |
| 22 | + Skip this step for "Hello World" projects. |
| 23 | + --> |
| 24 | + |
| 25 | +- [ ] Install Required Extensions |
| 26 | + <!-- ONLY install extensions provided mentioned in the get_project_setup_info. Skip this step otherwise and mark as completed. --> |
| 27 | + |
| 28 | +- [ ] Compile the Project |
| 29 | + <!-- |
| 30 | + Verify that all previous steps have been completed. |
| 31 | + Install any missing dependencies. |
| 32 | + Run diagnostics and resolve any issues. |
| 33 | + Check for markdown files in project folder for relevant instructions on how to do this. |
| 34 | + --> |
| 35 | + |
| 36 | +- [ ] Create and Run Task |
| 37 | + <!-- |
| 38 | + Verify that all previous steps have been completed. |
| 39 | + Check https://code.visualstudio.com/docs/debugtest/tasks to determine if the project needs a task. If so, use the create_and_run_task to create and launch a task based on package.json, README.md, and project structure. |
| 40 | + Skip this step otherwise. |
| 41 | + --> |
| 42 | + |
| 43 | +- [ ] Launch the Project |
| 44 | + <!-- |
| 45 | + Verify that all previous steps have been completed. |
| 46 | + Prompt user for debug mode, launch only if confirmed. |
| 47 | + --> |
| 48 | + |
| 49 | +- [ ] Ensure Documentation is Complete |
| 50 | + <!-- |
| 51 | + Verify that all previous steps have been completed. |
| 52 | + Verify that README.md and the copilot-instructions.md file in the .github directory exists and contains current project information. |
| 53 | + Clean up the copilot-instructions.md file in the .github directory by removing all HTML comments. |
| 54 | + --> |
| 55 | + |
| 56 | +<!-- |
| 57 | +## Execution Guidelines |
| 58 | +PROGRESS TRACKING: |
| 59 | +- If any tools are available to manage the above todo list, use it to track progress through this checklist. |
| 60 | +- After completing each step, mark it complete and add a summary. |
| 61 | +- Read current todo list status before starting each new step. |
| 62 | +
|
| 63 | +COMMUNICATION RULES: |
| 64 | +- Avoid verbose explanations or printing full command outputs. |
| 65 | +- If a step is skipped, state that briefly (e.g. "No extensions needed"). |
| 66 | +- Do not explain project structure unless asked. |
| 67 | +- Keep explanations concise and focused. |
| 68 | +
|
| 69 | +DEVELOPMENT RULES: |
| 70 | +- Use '.' as the working directory unless user specifies otherwise. |
| 71 | +- Avoid adding media or external links unless explicitly requested. |
| 72 | +- Use placeholders only with a note that they should be replaced. |
| 73 | +- Use VS Code API tool only for VS Code extension projects. |
| 74 | +- Once the project is created, it is already opened in Visual Studio Code—do not suggest commands to open this project in Visual Studio again. |
| 75 | +- If the project setup information has additional rules, follow them strictly. |
| 76 | +
|
| 77 | +FOLDER CREATION RULES: |
| 78 | +- Always use the current directory as the project root. |
| 79 | +- If you are running any terminal commands, use the '.' argument to ensure that the current working directory is used ALWAYS. |
| 80 | +- Do not create a new folder unless the user explicitly requests it besides a .vscode folder for a tasks.json file. |
| 81 | +- If any of the scaffolding commands mention that the folder name is not correct, let the user know to create a new folder with the correct name and then reopen it again in vscode. |
| 82 | +
|
| 83 | +EXTENSION INSTALLATION RULES: |
| 84 | +- Only install extension specified by the get_project_setup_info tool. DO NOT INSTALL any other extensions. |
| 85 | +
|
| 86 | +PROJECT CONTENT RULES: |
| 87 | +- If the user has not specified project details, assume they want a "Hello World" project as a starting point. |
| 88 | +- Avoid adding links of any type (URLs, files, folders, etc.) or integrations that are not explicitly required. |
| 89 | +- Avoid generating images, videos, or any other media files unless explicitly requested. |
| 90 | +- If you need to use any media assets as placeholders, let the user know that these are placeholders and should be replaced with the actual assets later. |
| 91 | +- Ensure all generated components serve a clear purpose within the user's requested workflow. |
| 92 | +- If a feature is assumed but not confirmed, prompt the user for clarification before including it. |
| 93 | +- If you are working on a VS Code extension, use the VS Code API tool with a query to find relevant VS Code API references and samples related to that query. |
| 94 | +
|
| 95 | +TASK COMPLETION RULES: |
| 96 | +- Your task is complete when: |
| 97 | + - Project is successfully scaffolded and compiled without errors |
| 98 | + - copilot-instructions.md file in the .github directory exists in the project |
| 99 | + - README.md file exists and is up to date |
| 100 | + - User is provided with clear instructions to debug/launch the project |
| 101 | +
|
| 102 | +Before starting a new task in the above plan, update progress in the plan. |
| 103 | +--> |
| 104 | +- Work through each checklist item systematically. |
| 105 | +- Keep communication concise and focused. |
| 106 | +- Follow development best practices. |
0 commit comments