shmakk 1.1.0 → 1.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (450) hide show
  1. package/README.md +16 -1
  2. package/package.json +6 -3
  3. package/scripts/import-skills.js +536 -0
  4. package/scripts/install-skills.js +64 -0
  5. package/skills/ai-elements.md +482 -0
  6. package/skills/architecture.md +151 -0
  7. package/skills/backend-adapter-aws-lambda.md +204 -0
  8. package/skills/backend-adapter-express.md +177 -0
  9. package/skills/backend-adapter-fastify.md +222 -0
  10. package/skills/backend-adapter-fetch.md +200 -0
  11. package/skills/backend-api-docs.md +22 -0
  12. package/skills/backend-aspire.md +232 -0
  13. package/skills/backend-aspnet-core.md +62 -0
  14. package/skills/backend-build-chatgpt-app.md +321 -0
  15. package/skills/backend-build-mcp-app.md +393 -0
  16. package/skills/backend-build-mcp-server.md +222 -0
  17. package/skills/backend-build-mcpb.md +200 -0
  18. package/skills/backend-building-ai-agent-on-cloudflare.md +401 -0
  19. package/skills/backend-caching.md +206 -0
  20. package/skills/backend-chatgpt-app-submission.md +157 -0
  21. package/skills/backend-chatgpt-apps.md +321 -0
  22. package/skills/backend-client-setup.md +318 -0
  23. package/skills/backend-containerize-aspnet-framework.md +455 -0
  24. package/skills/backend-create-spring-boot-java-project.md +164 -0
  25. package/skills/backend-create-spring-boot-kotlin-project.md +148 -0
  26. package/skills/backend-csharp-async.md +50 -0
  27. package/skills/backend-csharp-docs.md +63 -0
  28. package/skills/backend-csharp-mcp-server-generator.md +60 -0
  29. package/skills/backend-dotenv.md +201 -0
  30. package/skills/backend-dotenvx.md +119 -0
  31. package/skills/backend-env-vars.md +259 -0
  32. package/skills/backend-error-handling.md +254 -0
  33. package/skills/backend-fastapi.md +437 -0
  34. package/skills/backend-go-mcp-server-generator.md +335 -0
  35. package/skills/backend-java-mcp-server-generator.md +757 -0
  36. package/skills/backend-kotlin-mcp-server-generator.md +450 -0
  37. package/skills/backend-middlewares.md +243 -0
  38. package/skills/backend-multi-stage-dockerfile.md +47 -0
  39. package/skills/backend-nestjs.md +192 -0
  40. package/skills/backend-next-forge.md +375 -0
  41. package/skills/backend-nextjs.md +746 -0
  42. package/skills/backend-openapi-to-application-code.md +113 -0
  43. package/skills/backend-php-mcp-server-generator.md +523 -0
  44. package/skills/backend-python-mcp-server-generator.md +106 -0
  45. package/skills/backend-routing-middleware.md +251 -0
  46. package/skills/backend-ruby-mcp-server-generator.md +661 -0
  47. package/skills/backend-rust-mcp-server-generator.md +578 -0
  48. package/skills/backend-semantic-kernel.md +57 -0
  49. package/skills/backend-server-setup.md +379 -0
  50. package/skills/backend-server-side-calls.md +250 -0
  51. package/skills/backend-subscriptions.md +407 -0
  52. package/skills/backend-swift-mcp-server-generator.md +670 -0
  53. package/skills/backend-trpc-router.md +152 -0
  54. package/skills/backend-typescript-mcp-server-generator.md +91 -0
  55. package/skills/backend-validators.md +229 -0
  56. package/skills/backend.md +76 -0
  57. package/skills/backup.md +165 -0
  58. package/skills/budget.md +140 -0
  59. package/skills/business-gtm-0-to-1-launch.md +322 -0
  60. package/skills/business-gtm-operating-cadence.md +421 -0
  61. package/skills/business-gtm-positioning-strategy.md +439 -0
  62. package/skills/business-gtm-product-led-growth.md +340 -0
  63. package/skills/calendar.md +95 -0
  64. package/skills/code-review.md +130 -0
  65. package/skills/compliance.md +168 -0
  66. package/skills/contracts.md +130 -0
  67. package/skills/daily-job-run.md +46 -0
  68. package/skills/daily-webdesign.md +187 -0
  69. package/skills/database-bigquery-pipeline-audit.md +130 -0
  70. package/skills/database-cosmosdb-datamodeling.md +1046 -0
  71. package/skills/database-durable-objects.md +187 -0
  72. package/skills/database-ef-core.md +76 -0
  73. package/skills/database-fabric-lakehouse.md +107 -0
  74. package/skills/database-neon-postgres-egress-optimizer.md +213 -0
  75. package/skills/database-neon-postgres.md +218 -0
  76. package/skills/database-postgresql-code-review.md +213 -0
  77. package/skills/database-postgresql-optimization.md +405 -0
  78. package/skills/database-sql-code-review.md +302 -0
  79. package/skills/database-sql-optimization.md +297 -0
  80. package/skills/dependency-audit.md +165 -0
  81. package/skills/design-kami-landing.md +234 -0
  82. package/skills/design.md +221 -0
  83. package/skills/dev-acquire-codebase-knowledge.md +175 -0
  84. package/skills/dev-add-educational-comments.md +129 -0
  85. package/skills/dev-add-model-descriptions.md +74 -0
  86. package/skills/dev-adr-review.md +56 -0
  87. package/skills/dev-boost-prompt.md +26 -0
  88. package/skills/dev-build-run-debug.md +130 -0
  89. package/skills/dev-chunk.md +49 -0
  90. package/skills/dev-claude-md-improver.md +180 -0
  91. package/skills/dev-code-exemplars-blueprint-generator.md +127 -0
  92. package/skills/dev-code-tour.md +434 -0
  93. package/skills/dev-comment-code-generate-a-tutorial.md +27 -0
  94. package/skills/dev-commit.md +81 -0
  95. package/skills/dev-context-map.md +53 -0
  96. package/skills/dev-conventional-commit.md +73 -0
  97. package/skills/dev-create-architectural-decision-record.md +98 -0
  98. package/skills/dev-create-draft-pr.md +17 -0
  99. package/skills/dev-create-pr.md +17 -0
  100. package/skills/dev-create-readme.md +22 -0
  101. package/skills/dev-csharp-mstest.md +479 -0
  102. package/skills/dev-csharp-nunit.md +72 -0
  103. package/skills/dev-csharp-tunit.md +101 -0
  104. package/skills/dev-csharp-xunit.md +69 -0
  105. package/skills/dev-debug-failing-test.md +90 -0
  106. package/skills/dev-diff-analyze.md +32 -0
  107. package/skills/dev-diffs.md +24 -0
  108. package/skills/dev-dotnet-best-practices.md +86 -0
  109. package/skills/dev-dotnet-design-pattern-review.md +43 -0
  110. package/skills/dev-dotnet-timezone.md +110 -0
  111. package/skills/dev-dotnet-upgrade.md +117 -0
  112. package/skills/dev-doublecheck.md +278 -0
  113. package/skills/dev-explain-error.md +15 -0
  114. package/skills/dev-finding-discovery.md +164 -0
  115. package/skills/dev-fix-finding.md +111 -0
  116. package/skills/dev-full-file-edit.md +25 -0
  117. package/skills/dev-git-commit.md +125 -0
  118. package/skills/dev-git-flow-branch-creator.md +293 -0
  119. package/skills/dev-git-workflow.md +46 -0
  120. package/skills/dev-github-automation.md +64 -0
  121. package/skills/dev-github-code-review.md +1140 -0
  122. package/skills/dev-github-issues.md +202 -0
  123. package/skills/dev-gpt-5-4-prompting.md +55 -0
  124. package/skills/dev-investigation-mode.md +277 -0
  125. package/skills/dev-java-add-graalvm-native-image-support.md +450 -0
  126. package/skills/dev-java-docs.md +24 -0
  127. package/skills/dev-java-refactoring-extract-method.md +105 -0
  128. package/skills/dev-java-refactoring-remove-parameter.md +85 -0
  129. package/skills/dev-merge.md +73 -0
  130. package/skills/dev-migrate-create.md +36 -0
  131. package/skills/dev-migrate-validate.md +36 -0
  132. package/skills/dev-my-issues.md +9 -0
  133. package/skills/dev-my-pull-requests.md +15 -0
  134. package/skills/dev-planning-oracle-to-postgres-migration-integration-testing.md +45 -0
  135. package/skills/dev-playwright-generate-test.md +18 -0
  136. package/skills/dev-playwright.md +148 -0
  137. package/skills/dev-prompt-builder.md +142 -0
  138. package/skills/dev-pytest-coverage.md +29 -0
  139. package/skills/dev-python-manager-discovery.md +330 -0
  140. package/skills/dev-python-pypi-package-builder.md +445 -0
  141. package/skills/dev-readme-blueprint-generator.md +79 -0
  142. package/skills/dev-refactor-method-complexity-reduce.md +99 -0
  143. package/skills/dev-refactor-plan.md +66 -0
  144. package/skills/dev-refactor.md +646 -0
  145. package/skills/dev-review-and-refactor.md +16 -0
  146. package/skills/dev-reviewing-oracle-to-postgres-migration.md +68 -0
  147. package/skills/dev-ruff-recursive-fix.md +201 -0
  148. package/skills/dev-run-e2e-tests.md +126 -0
  149. package/skills/dev-run-pre-commit-checks.md +133 -0
  150. package/skills/dev-run-smoke-tests.md +127 -0
  151. package/skills/dev-scaffolding-oracle-to-postgres-migration-test-project.md +55 -0
  152. package/skills/dev-spring-boot-testing.md +190 -0
  153. package/skills/dev-sync-upstream.md +32 -0
  154. package/skills/dev-sync.md +74 -0
  155. package/skills/dev-tdd-workflow.md +23 -0
  156. package/skills/dev-terraform-azurerm-set-diff-analyzer.md +49 -0
  157. package/skills/dev-test-driven-development.md +372 -0
  158. package/skills/dev-test-gaps.md +18 -0
  159. package/skills/dev-test-triage.md +55 -0
  160. package/skills/dev-typer.md +267 -0
  161. package/skills/dev-typescript-setup.md +25 -0
  162. package/skills/dev-unified-diff-edit.md +16 -0
  163. package/skills/dev-unit-test-vue-pinia.md +198 -0
  164. package/skills/dev-using-git-worktrees.md +216 -0
  165. package/skills/dev-validation.md +99 -0
  166. package/skills/dev-verification.md +168 -0
  167. package/skills/dev-webapp-testing.md +134 -0
  168. package/skills/dev-write-coding-standards-from-file.md +317 -0
  169. package/skills/dev-write-tests.md +16 -0
  170. package/skills/devops-appinsights-instrumentation.md +49 -0
  171. package/skills/devops-az-cost-optimize.md +306 -0
  172. package/skills/devops-chronicle.md +154 -0
  173. package/skills/devops-deployments-cicd.md +331 -0
  174. package/skills/devops-devops-rollout-plan.md +118 -0
  175. package/skills/devops-geistdocs.md +276 -0
  176. package/skills/devops-observability.md +774 -0
  177. package/skills/devops-observe-metrics.md +35 -0
  178. package/skills/devops-observe-trace.md +30 -0
  179. package/skills/devops-phoenix-cli.md +163 -0
  180. package/skills/devops-phoenix-tracing.md +140 -0
  181. package/skills/devops-publish-to-pages.md +108 -0
  182. package/skills/devops-telemetry.md +87 -0
  183. package/skills/devops-update-avm-modules-in-bicep.md +61 -0
  184. package/skills/devops.md +81 -0
  185. package/skills/diagrams-canvas.md +204 -0
  186. package/skills/diagrams-draw-io-diagram-generator.md +463 -0
  187. package/skills/diagrams-excalidraw-diagram-generator.md +614 -0
  188. package/skills/diagrams-graphify.md +1277 -0
  189. package/skills/docs-bear-notes.md +108 -0
  190. package/skills/docs-create-llms.md +211 -0
  191. package/skills/docs-doc-gen.md +20 -0
  192. package/skills/docs-documentation-writer.md +46 -0
  193. package/skills/docs-llm-config.md +33 -0
  194. package/skills/docs-mkdocs-translations.md +109 -0
  195. package/skills/docs-obsidian-vault-maintainer.md +14 -0
  196. package/skills/docs-obsidian.md +82 -0
  197. package/skills/docs-prose.md +324 -0
  198. package/skills/docs-update-llms.md +217 -0
  199. package/skills/docs-update-markdown-file-index.md +77 -0
  200. package/skills/docs-wiki-maintainer.md +20 -0
  201. package/skills/documents.md +120 -0
  202. package/skills/email.md +113 -0
  203. package/skills/expenses.md +140 -0
  204. package/skills/file-ops.md +149 -0
  205. package/skills/files-convert-plaintext-to-md.md +363 -0
  206. package/skills/files-doc.md +81 -0
  207. package/skills/files-docx.md +594 -0
  208. package/skills/files-markdown-to-html.md +917 -0
  209. package/skills/files-nano-pdf.md +39 -0
  210. package/skills/files-pdf.md +315 -0
  211. package/skills/files-pdftk-server.md +163 -0
  212. package/skills/files-pptx-html-fidelity-audit.md +255 -0
  213. package/skills/files-pptx.md +231 -0
  214. package/skills/files-xlsx.md +301 -0
  215. package/skills/find-jobs.md +78 -0
  216. package/skills/format-conversion.md +157 -0
  217. package/skills/frontend-ai-elements.md +483 -0
  218. package/skills/frontend-ai-gateway.md +563 -0
  219. package/skills/frontend-ai-generation-persistence.md +242 -0
  220. package/skills/frontend-ai-sdk.md +799 -0
  221. package/skills/frontend-ai-visibility.md +127 -0
  222. package/skills/frontend-angular-developer.md +130 -0
  223. package/skills/frontend-aspnet-minimal-api-openapi.md +42 -0
  224. package/skills/frontend-bencium-innovative-ux-designer.md +719 -0
  225. package/skills/frontend-chat-sdk.md +666 -0
  226. package/skills/frontend-chrome-devtools.md +98 -0
  227. package/skills/frontend-frontend-app-builder.md +186 -0
  228. package/skills/frontend-frontend-design.md +43 -0
  229. package/skills/frontend-frontend-testing-debugging.md +143 -0
  230. package/skills/frontend-gsap-framer-scroll-animation.md +152 -0
  231. package/skills/frontend-internal-linking.md +109 -0
  232. package/skills/frontend-json-render.md +335 -0
  233. package/skills/frontend-keyword-clustering.md +118 -0
  234. package/skills/frontend-next-intl-add-language.md +20 -0
  235. package/skills/frontend-on-page-seo.md +112 -0
  236. package/skills/frontend-premium-frontend-ui.md +114 -0
  237. package/skills/frontend-react-best-practices.md +143 -0
  238. package/skills/frontend-schema-markup.md +160 -0
  239. package/skills/frontend-seo-audit.md +110 -0
  240. package/skills/frontend-swr.md +215 -0
  241. package/skills/frontend-technical-seo.md +162 -0
  242. package/skills/frontend-use-dom.md +418 -0
  243. package/skills/frontend-web-coder.md +564 -0
  244. package/skills/frontend-web-design-reviewer.md +369 -0
  245. package/skills/frontend-web-perf.md +202 -0
  246. package/skills/frontend.md +125 -0
  247. package/skills/general-adapter-standalone.md +199 -0
  248. package/skills/general-auth.md +356 -0
  249. package/skills/general-containerize-aspnetcore.md +393 -0
  250. package/skills/general-create-technical-spike.md +231 -0
  251. package/skills/general-cron-jobs.md +72 -0
  252. package/skills/general-ddd-aggregate.md +52 -0
  253. package/skills/general-ddd-context.md +46 -0
  254. package/skills/general-ddd-validate.md +51 -0
  255. package/skills/general-dependency-check.md +26 -0
  256. package/skills/general-email-marketing.md +86 -0
  257. package/skills/general-healthcheck.md +246 -0
  258. package/skills/general-import-infrastructure-as-code.md +368 -0
  259. package/skills/general-init.md +49 -0
  260. package/skills/general-java-junit.md +64 -0
  261. package/skills/general-java-springboot.md +66 -0
  262. package/skills/general-javascript-typescript-jest.md +45 -0
  263. package/skills/general-kotlin-springboot.md +71 -0
  264. package/skills/general-make-repo-contribution.md +91 -0
  265. package/skills/general-market-research.md +78 -0
  266. package/skills/general-marketplace.md +468 -0
  267. package/skills/general-model-recommendation.md +673 -0
  268. package/skills/general-payments.md +352 -0
  269. package/skills/general-quality-playbook.md +480 -0
  270. package/skills/general-run-integration-tests.md +113 -0
  271. package/skills/general-superjson.md +274 -0
  272. package/skills/general-swiftpm-macos.md +51 -0
  273. package/skills/general-threat-model.md +61 -0
  274. package/skills/invoices.md +167 -0
  275. package/skills/licenses.md +159 -0
  276. package/skills/logs.md +156 -0
  277. package/skills/marketing.md +139 -0
  278. package/skills/media-image-manipulation-image-magick.md +253 -0
  279. package/skills/media-imagegen.md +357 -0
  280. package/skills/media-openai-whisper-api.md +63 -0
  281. package/skills/media-openai-whisper.md +39 -0
  282. package/skills/media-peekaboo.md +191 -0
  283. package/skills/media-screenshot.md +268 -0
  284. package/skills/media-speech.md +145 -0
  285. package/skills/media-transcribe.md +82 -0
  286. package/skills/media-video-frames.md +47 -0
  287. package/skills/mobile-android-emulator-qa.md +81 -0
  288. package/skills/mobile-android-performance.md +280 -0
  289. package/skills/mobile-building-mcp-server-on-cloudflare.md +267 -0
  290. package/skills/mobile-building-native-ui.md +322 -0
  291. package/skills/mobile-expo-api-routes.md +369 -0
  292. package/skills/mobile-expo-cicd-workflows.md +92 -0
  293. package/skills/mobile-expo-deployment.md +191 -0
  294. package/skills/mobile-expo-dev-client.md +165 -0
  295. package/skills/mobile-expo-module.md +177 -0
  296. package/skills/mobile-expo-tailwind-setup.md +481 -0
  297. package/skills/mobile-expo-ui-jetpack-compose.md +41 -0
  298. package/skills/mobile-expo-ui-swift-ui.md +40 -0
  299. package/skills/mobile-ios-app-intents.md +78 -0
  300. package/skills/mobile-ios-debugger-agent.md +52 -0
  301. package/skills/mobile-ios-ettrace-performance.md +198 -0
  302. package/skills/mobile-ios-memgraph-leaks.md +77 -0
  303. package/skills/mobile-native-data-fetching.md +508 -0
  304. package/skills/mobile-packaging-notarization.md +48 -0
  305. package/skills/mobile-react-native-architecture.md +672 -0
  306. package/skills/mobile-react-native-mobile-design.md +438 -0
  307. package/skills/mobile-signing-entitlements.md +59 -0
  308. package/skills/mobile-swiftui-liquid-glass.md +91 -0
  309. package/skills/mobile-swiftui-patterns.md +210 -0
  310. package/skills/mobile-swiftui-performance-audit.md +108 -0
  311. package/skills/mobile-swiftui-ui-patterns.md +97 -0
  312. package/skills/mobile-swiftui-view-refactor.md +204 -0
  313. package/skills/mobile-upgrading-expo.md +134 -0
  314. package/skills/mobile.md +183 -0
  315. package/skills/notes.md +106 -0
  316. package/skills/planning-adr-create.md +62 -0
  317. package/skills/planning-adr-index.md +67 -0
  318. package/skills/planning-architecture-blueprint-generator.md +323 -0
  319. package/skills/planning-brainstorming.md +165 -0
  320. package/skills/planning-breakdown-epic-arch.md +67 -0
  321. package/skills/planning-breakdown-epic-pm.md +59 -0
  322. package/skills/planning-breakdown-feature-implementation.md +129 -0
  323. package/skills/planning-breakdown-feature-prd.md +62 -0
  324. package/skills/planning-breakdown-plan.md +510 -0
  325. package/skills/planning-breakdown-test.md +366 -0
  326. package/skills/planning-cloud-design-patterns.md +63 -0
  327. package/skills/planning-content-brief.md +128 -0
  328. package/skills/planning-content-strategy.md +138 -0
  329. package/skills/planning-content-translation.md +143 -0
  330. package/skills/planning-create-github-action-workflow-specification.md +277 -0
  331. package/skills/planning-create-github-issues-feature-from-implementation-plan.md +29 -0
  332. package/skills/planning-create-github-issues-for-unmet-specification-requirements.md +36 -0
  333. package/skills/planning-create-github-pull-request-from-specification.md +25 -0
  334. package/skills/planning-create-implementation-plan.md +158 -0
  335. package/skills/planning-create-specification.md +128 -0
  336. package/skills/planning-first-ask.md +31 -0
  337. package/skills/planning-folder-structure-blueprint-generator.md +406 -0
  338. package/skills/planning-gen-specs-as-issues.md +166 -0
  339. package/skills/planning-generate-snapshot.md +144 -0
  340. package/skills/planning-generate-status-report.md +336 -0
  341. package/skills/planning-metric-pack-designer.md +27 -0
  342. package/skills/planning-pm-spec.md +53 -0
  343. package/skills/planning-prd.md +144 -0
  344. package/skills/planning-project-assessment.md +182 -0
  345. package/skills/planning-project-setup-info-local.md +128 -0
  346. package/skills/planning-project-workflow-analysis-blueprint-generator.md +294 -0
  347. package/skills/planning-service-oriented-architecture.md +248 -0
  348. package/skills/planning-spec-to-backlog.md +544 -0
  349. package/skills/planning-technology-stack-blueprint-generator.md +243 -0
  350. package/skills/planning-update-implementation-plan.md +158 -0
  351. package/skills/planning-update-specification.md +128 -0
  352. package/skills/planning-what-context-needed.md +40 -0
  353. package/skills/planning-writing-plans.md +153 -0
  354. package/skills/prepare-application.md +81 -0
  355. package/skills/productivity-apple-notes.md +78 -0
  356. package/skills/productivity-apple-reminders.md +119 -0
  357. package/skills/productivity-capture-tasks-from-meeting-notes.md +680 -0
  358. package/skills/productivity-daily-prep.md +156 -0
  359. package/skills/productivity-email-drafter.md +101 -0
  360. package/skills/productivity-hr-onboarding.md +53 -0
  361. package/skills/productivity-things-mac.md +87 -0
  362. package/skills/productivity-update.md +169 -0
  363. package/skills/reminders.md +109 -0
  364. package/skills/research-dossier-collect.md +71 -0
  365. package/skills/research-kg-extract.md +37 -0
  366. package/skills/research-openai-docs.md +89 -0
  367. package/skills/research-research-add-items.md +31 -0
  368. package/skills/research-research-report.md +94 -0
  369. package/skills/research-research-synthesize.md +63 -0
  370. package/skills/research-summarize.md +88 -0
  371. package/skills/research-transformers-js.md +635 -0
  372. package/skills/research.md +119 -0
  373. package/skills/security-ai-prompt-engineering-safety-review.md +231 -0
  374. package/skills/security-attack-path-analysis.md +182 -0
  375. package/skills/security-gdpr-compliant.md +284 -0
  376. package/skills/security-mcp-security-audit.md +279 -0
  377. package/skills/security-pii-detect.md +31 -0
  378. package/skills/security-secret-scanning.md +243 -0
  379. package/skills/security-security-best-practices.md +87 -0
  380. package/skills/security-security-ownership-map.md +207 -0
  381. package/skills/security-security-review.md +169 -0
  382. package/skills/security-security-scan.md +138 -0
  383. package/skills/security-security-threat-model.md +82 -0
  384. package/skills/security-threat-model-analyst.md +76 -0
  385. package/skills/sysmon.md +181 -0
  386. package/skills/system-arch-linux-triage.md +32 -0
  387. package/skills/system-centos-linux-triage.md +32 -0
  388. package/skills/system-debian-linux-triage.md +32 -0
  389. package/skills/system-fedora-linux-triage.md +32 -0
  390. package/skills/system-geofeed-tuner.md +865 -0
  391. package/skills/system-iot-anomalies.md +15 -0
  392. package/skills/system-iot-firmware.md +16 -0
  393. package/skills/system-iot-fleet.md +14 -0
  394. package/skills/system-iot-register.md +19 -0
  395. package/skills/system-iot-witness-verify.md +15 -0
  396. package/skills/system-tmux.md +171 -0
  397. package/skills/system-window-management.md +228 -0
  398. package/skills/task-management.md +90 -0
  399. package/skills/tasks.md +102 -0
  400. package/skills/test-coverage.md +188 -0
  401. package/skills/ux-ui.md +128 -0
  402. package/skills/web.md +186 -0
  403. package/skills/workflow-act-on-feedback.md +15 -0
  404. package/skills/workflow-automate-this.md +245 -0
  405. package/skills/workflow-autoresearch.md +276 -0
  406. package/skills/workflow-coding-agent.md +317 -0
  407. package/skills/workflow-deep-research.md +44 -0
  408. package/skills/workflow-dispatching-parallel-agents.md +183 -0
  409. package/skills/workflow-eval-driven-dev.md +148 -0
  410. package/skills/workflow-executing-plans.md +71 -0
  411. package/skills/workflow-mentoring-juniors.md +311 -0
  412. package/skills/workflow-receiving-code-review.md +214 -0
  413. package/skills/workflow-repo-story-time.md +155 -0
  414. package/skills/workflow-requesting-code-review.md +104 -0
  415. package/skills/workflow-session-report.md +43 -0
  416. package/skills/workflow-structured-autonomy-generate.md +126 -0
  417. package/skills/workflow-subagent-driven-development.md +280 -0
  418. package/skills/writing.md +106 -0
  419. package/src/agent.js +0 -0
  420. package/src/browser.js +297 -0
  421. package/src/cli.js +25 -4
  422. package/src/code-reviewer.js +119 -0
  423. package/src/completions.js +1 -1
  424. package/src/control.js +222 -30
  425. package/src/coordinator.js +303 -0
  426. package/src/correction.js +29 -8
  427. package/src/edit-tracker.js +21 -0
  428. package/src/edit-viewer.js +414 -0
  429. package/src/endpoints.js +64 -15
  430. package/src/index.js +45 -11
  431. package/src/llm.js +86 -2
  432. package/src/mcp-client.js +416 -0
  433. package/src/memory.js +182 -0
  434. package/src/planner.js +216 -0
  435. package/src/rules.js +90 -0
  436. package/src/self-commands.js +757 -0
  437. package/src/services/voice.js +10 -7
  438. package/src/session-search.js +427 -0
  439. package/src/session.js +487 -99
  440. package/src/shmakk-server.js +91 -0
  441. package/src/skills.js +410 -3
  442. package/src/subagent.js +4 -1
  443. package/src/system-prompt.js +13 -5
  444. package/src/task-file.js +114 -0
  445. package/src/taskClassifier.js +246 -0
  446. package/src/team.js +752 -0
  447. package/src/tools.js +142 -21
  448. package/src/web.js +35 -5
  449. package/src/workflows.js +261 -0
  450. package/src/workspace-index.js +25 -6
package/skills/planning-pm-spec.md ADDED
@@ -0,0 +1,53 @@
1
+ ---
2
+ name: pm-spec
3
+ description: |
4
+ Product spec / PRD as a single page — problem, success metrics, scope,
5
+ user stories, design notes, rollout plan, open questions. Use when the
6
+ brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".
7
+ triggers:
8
+ - "prd"
9
+ - "spec"
10
+ - "product spec"
11
+ - "feature brief"
12
+ - "feature doc"
13
+ - "需求文档"
14
+ od:
15
+ mode: prototype
16
+ platform: desktop
17
+ scenario: product
18
+ preview:
19
+ type: html
20
+ entry: index.html
21
+ design_system:
22
+ requires: true
23
+ sections: [color, typography, layout, components]
24
+ example_prompt: "Write me a PRD for adding two-factor auth to our SaaS app — problem, scope, milestones, open questions."
25
+ category: planning
26
+ ---
27
+
28
+ # Product Spec Skill
29
+
30
+ Produce a one-page product spec / PRD.
31
+
32
+ ## Workflow
33
+
34
+ 1. Read the active DESIGN.md.
35
+ 2. Identify the feature + audience from the brief.
36
+ 3. Layout:
37
+ - Header strip: title, status pill (Draft / Review / Approved), date, owner.
38
+ - Three-line summary at the top — what, who, why now.
39
+ - "Problem" panel with one paragraph and a quote from a customer or
40
+ internal partner.
41
+ - "Goals & non-goals" two-column block.
42
+ - "Success metrics" table with metric / target / measurement.
43
+ - "User stories" list with as-a / I-want / so-that format.
44
+ - "Scope" milestone tracker (3–4 phases).
45
+ - "Open questions" with assignee chips.
46
+ 4. One inline `<style>`, semantic HTML, accent used twice max.
47
+
48
+ ## Output contract
49
+
50
+ ```
51
+ <artifact identifier="spec-name" type="text/html" title="Spec Title">
52
+ <!doctype html>...</artifact>
53
+ ```
package/skills/planning-prd.md ADDED
@@ -0,0 +1,144 @@
1
+ ---
2
+ name: prd
3
+ description: 'Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.'
4
+ license: MIT
5
+ category: planning
6
+ ---
7
+
8
+ # Product Requirements Document (PRD)
9
+
10
+ ## Overview
11
+
12
+ Design comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.
13
+
14
+ ## When to Use
15
+
16
+ Use this skill when:
17
+
18
+ - Starting a new product or feature development cycle
19
+ - Translating a vague idea into a concrete technical specification
20
+ - Defining requirements for AI-powered features
21
+ - Stakeholders need a unified "source of truth" for project scope
22
+ - User asks to "write a PRD", "document requirements", or "plan a feature"
23
+
24
+ ---
25
+
26
+ ## Operational Workflow
27
+
28
+ ### Phase 1: Discovery (The Interview)
29
+
30
+ Before writing a single line of the PRD, you **MUST** interrogate the user to fill knowledge gaps. Do not assume context.
31
+
32
+ **Ask about:**
33
+
34
+ - **The Core Problem**: Why are we building this now?
35
+ - **Success Metrics**: How do we know it worked?
36
+ - **Constraints**: Budget, tech stack, or deadline?
37
+
38
+ ### Phase 2: Analysis & Scoping
39
+
40
+ Synthesize the user's input. Identify dependencies and hidden complexities.
41
+
42
+ - Map out the **User Flow**.
43
+ - Define **Non-Goals** to protect the timeline.
44
+
45
+ ### Phase 3: Technical Drafting
46
+
47
+ Generate the document using the **Strict PRD Schema** below.
48
+
49
+ ---
50
+
51
+ ## PRD Quality Standards
52
+
53
+ ### Requirements Quality
54
+
55
+ Use concrete, measurable criteria. Avoid "fast", "easy", or "intuitive".
56
+
57
+ ```diff
58
+ # Vague (BAD)
59
+ - The search should be fast and return relevant results.
60
+ - The UI must look modern and be easy to use.
61
+
62
+ # Concrete (GOOD)
63
+ + The search must return results within 200ms for a 10k record dataset.
64
+ + The search algorithm must achieve >= 85% Precision@10 in benchmark evals.
65
+ + The UI must follow the 'Vercel/Next.js' design system and achieve 100% Lighthouse Accessibility score.
66
+ ```
67
+
68
+ ---
69
+
70
+ ## Strict PRD Schema
71
+
72
+ You **MUST** follow this exact structure for the output:
73
+
74
+ ### 1. Executive Summary
75
+
76
+ - **Problem Statement**: 1-2 sentences on the pain point.
77
+ - **Proposed Solution**: 1-2 sentences on the fix.
78
+ - **Success Criteria**: 3-5 measurable KPIs.
79
+
80
+ ### 2. User Experience & Functionality
81
+
82
+ - **User Personas**: Who is this for?
83
+ - **User Stories**: `As a [user], I want to [action] so that [benefit].`
84
+ - **Acceptance Criteria**: Bulleted list of "Done" definitions for each story.
85
+ - **Non-Goals**: What are we NOT building?
86
+
87
+ ### 3. AI System Requirements (If Applicable)
88
+
89
+ - **Tool Requirements**: What tools and APIs are needed?
90
+ - **Evaluation Strategy**: How to measure output quality and accuracy.
91
+
92
+ ### 4. Technical Specifications
93
+
94
+ - **Architecture Overview**: Data flow and component interaction.
95
+ - **Integration Points**: APIs, DBs, and Auth.
96
+ - **Security & Privacy**: Data handling and compliance.
97
+
98
+ ### 5. Risks & Roadmap
99
+
100
+ - **Phased Rollout**: MVP -> v1.1 -> v2.0.
101
+ - **Technical Risks**: Latency, cost, or dependency failures.
102
+
103
+ ---
104
+
105
+ ## Implementation Guidelines
106
+
107
+ ### DO (Always)
108
+
109
+ - **Define Testing**: For AI systems, specify how to test and validate output quality.
110
+ - **Iterate**: Present a draft and ask for feedback on specific sections.
111
+
112
+ ### DON'T (Avoid)
113
+
114
+ - **Skip Discovery**: Never write a PRD without asking at least 2 clarifying questions first.
115
+ - **Hallucinate Constraints**: If the user didn't specify a tech stack, ask or label it as `TBD`.
116
+
117
+ ---
118
+
119
+ ## Example: Intelligent Search System
120
+
121
+ ### 1. Executive Summary
122
+
123
+ **Problem**: Users struggle to find specific documentation snippets in massive repositories.
124
+ **Solution**: An intelligent search system that provides direct answers with source citations.
125
+ **Success**:
126
+
127
+ - Reduce search time by 50%.
128
+ - Citation accuracy >= 95%.
129
+
130
+ ### 2. User Stories
131
+
132
+ - **Story**: As a developer, I want to ask natural language questions so I don't have to guess keywords.
133
+ - **AC**:
134
+ - Supports multi-turn clarification.
135
+ - Returns code blocks with "Copy" button.
136
+
137
+ ### 3. AI System Architecture
138
+
139
+ - **Tools Required**: `codesearch`, `grep`, `webfetch`.
140
+
141
+ ### 4. Evaluation
142
+
143
+ - **Benchmark**: Test with 50 common developer questions.
144
+ - **Pass Rate**: 90% must match expected citations.
package/skills/planning-project-assessment.md ADDED
@@ -0,0 +1,182 @@
1
+ ---
2
+ name: project-assessment
3
+ description: >
4
+ Conduct a full project review across architecture, frontend, and backend — with smart, context-aware questioning that adapts to the user's actual goals rather than their tech stack. Use this skill whenever a user wants to review, audit, or get suggestions for improving a project, app, or codebase. Trigger on phrases like "assess my project", "review my app", "what should I improve", "is my architecture good", "frontend review", "backend review", "code review my project", "give me suggestions for my app", or any time a user shares a project and wants feedback on its structure or quality. Also trigger if the user sets up a project and seems to want a professional opinion on how it's built or could be better.
5
+ allowed-tools: Read, Glob, Grep, Bash(find:*), Bash(cat:*), Bash(ls:*)
6
+ category: planning
7
+ ---
8
+
9
+ # Project Assessment Skill
10
+
11
+ You are a thoughtful technical advisor conducting a project assessment. Your job is to understand what the user is building and why — then deliver a structured, prioritised review across architecture, frontend, and/or backend.
12
+
13
+ **Core principle**: Ask about *purpose and context*, not about code. Questions like "Who will use this?" and "How do you want it to feel?" reveal more than "What framework are you using?". Once you understand the what and why, you can infer or ask about the how.
14
+
15
+ **Before questioning**: Use Read, Glob, and Grep to explore the project structure first. Check for things like `package.json`, `requirements.txt`, folder layout, config files, and any README. Infer what you can from the code itself — framework, stack, rough architecture — so you don't ask the user things you could just look up. Questions should fill in what the code *can't* tell you: intent, audience, and priorities.
16
+
17
+ ---
18
+
19
+ ## Phase 1: Discovery (Questioning)
20
+
21
+ ### Step 1a — Establish scope first
22
+
23
+ **Before anything else**, ask the user which areas they want assessed. Do this naturally — not as a form. Something like:
24
+
25
+ > "Before we dive in — do you want me to look at everything (architecture, frontend, and backend), or would you rather focus on one or two specific areas?"
26
+
27
+ If they've already made it clear (e.g. "can you review my frontend?"), skip this and treat it as answered. If they say "everything" or "all three", proceed with all sections.
28
+
29
+ Once scope is set, **do not revisit it** unless the user brings it up. Assess only what was agreed.
30
+
31
+ ### Step 1b — Understand the project
32
+
33
+ After scope is set, ask discovery questions. Keep the total to **5–8 questions across the whole conversation**, asked **one or two at a time**. Questions should feel like a curious colleague, not a form.
34
+
35
+ - **Infer where possible** — if someone says "it's a SaaS product for small businesses", you already know it's web-based, multi-user, and probably needs auth. Don't ask what you can already figure out.
36
+ - **Adapt your vocabulary** based on how the user writes. Mirror technical language if they use it; stay plain English if they don't. Never ask which mode they prefer — just read the room.
37
+
38
+ Work through these angles — only ask what you genuinely don't know yet:
39
+
40
+ **Purpose**
41
+ - What does this app/project do? Who is it for?
42
+ - Is this a personal project, client work, a startup, or something internal?
43
+
44
+ **Usage context**
45
+ - How will people access it — phone, desktop, browser, both?
46
+ - Is it used occasionally (like a tool) or daily (like a workflow app)?
47
+ - Is it used alone or by a team? Public or private?
48
+
49
+ **Scale and growth**
50
+ - Is this early-stage or already live? Do you have users yet?
51
+ - Are you expecting a small number of users or many? Is growth on the horizon?
52
+
53
+ **Platform fit check** *(important)*
54
+ - If the user says desktop app: ask *why desktop* once, naturally. Understand if it's a genuine need (offline use, OS integration, performance) or a default assumption that web or mobile might serve better.
55
+ - If the user says mobile only: same check — is there a web fallback expected?
56
+ - Don't second-guess the user's answer. If they confirm the platform choice, accept it and tailor accordingly. Don't keep nudging.
57
+
58
+ **Goals for the assessment**
59
+ - What matters most right now — performance, scalability, code quality, security, maintainability, cost, something else?
60
+ - Are there known pain points or areas they're already unsure about?
61
+
62
+ ---
63
+
64
+ ## Phase 2: Scoping
65
+
66
+ After discovery, confirm which sections you'll cover based on what the user asked for in Step 1a.
67
+
68
+ **For each section the user requested:**
69
+ - If that layer exists in the project → assess it fully.
70
+ - If that layer doesn't exist yet → acknowledge the gap clearly and briefly suggest whether it's worth adding based on what you learned. Don't just skip it silently.
71
+
72
+ **For sections the user did NOT request:**
73
+ - Don't assess them, and don't volunteer assessments of them.
74
+ - Exception: if you discover a serious gap in an unrequested area that would clearly affect the areas they do care about (e.g. no auth on a backend that powers a frontend they asked about), flag it briefly in the relevant section rather than ignoring it entirely.
75
+
76
+ ---
77
+
78
+ ## Phase 3: The Assessment
79
+
80
+ Deliver a structured report. Use clear sections. Adapt depth and language to the user:
81
+
82
+ - **Beginners**: Plain English explanations, short analogies, avoid acronyms unless explained.
83
+ - **Pros**: Concise, precise, skip hand-holding. Feel free to be direct.
84
+
85
+ ### Report structure
86
+
87
+ ```
88
+ ## Project Assessment: [Project Name or Description]
89
+
90
+ ### What I understand about your project
91
+ [2–3 sentences confirming your understanding — let the user catch any misreads before diving in]
92
+
93
+ ---
94
+
95
+ ### Architecture Assessment
96
+ **Overall**: [One-line verdict — e.g. "Solid for your current scale, with some areas to watch as you grow"]
97
+
98
+ **What's working well**
99
+ - ...
100
+
101
+ **Suggestions & improvements**
102
+ [Prioritised list — P1 = fix soon, P2 = worth doing, P3 = nice to have]
103
+
104
+ Format each suggestion differently based on the user's experience level:
105
+
106
+ **If pro:**
107
+ Each suggestion includes a concise motivation — the *why* is built into the item itself. No padding, no hand-holding. The reasoning should be specific to their context, not generic advice.
108
+ - 🔴 P1: [What to do] — [Why it matters for their specific situation]
109
+ - 🟡 P2: [What to do] — [Why it matters for their specific situation]
110
+ - 🟢 P3: [What to do] — [Why it matters for their specific situation]
111
+
112
+ **If beginner:**
113
+ Keep each suggestion short and clear — one sentence on what to do. Then after each suggestion (or after a natural group of related ones), add a light invite:
114
+ - 🔴 P1: [What to do] *(Want me to explain why, or how to do this?)*
115
+ - 🟡 P2: [What to do] *(Want me to explain why, or how to do this?)*
116
+ - 🟢 P3: [What to do] *(Want me to explain why, or how to do this?)*
117
+
118
+ The invite signals that learning is available without dumping it on them unsolicited. If they ask, go deep. If they don't, move on.
119
+
120
+ **Platform fit note** *(only if relevant)*
121
+ [If during questioning you had a platform concern — address it here honestly but without being pushy]
122
+
123
+ ---
124
+
125
+ ### Frontend Assessment
126
+ *(Skip this section if no frontend exists)*
127
+
128
+ **Overall**: ...
129
+
130
+ **What's working well**
131
+ - ...
132
+
133
+ **Suggestions & improvements**
134
+ *(Follow the pro/beginner format above)*
135
+
136
+ ---
137
+
138
+ ### Backend Assessment
139
+ *(Skip this section if no backend exists)*
140
+
141
+ **Overall**: ...
142
+
143
+ **What's working well**
144
+ - ...
145
+
146
+ **Suggestions & improvements**
147
+ *(Follow the pro/beginner format above)*
148
+
149
+ ---
150
+
151
+ ### Top 3 things to do next
152
+ [Across all sections — the highest-impact actions the user should focus on first, regardless of category]
153
+
154
+ 1. ...
155
+ 2. ...
156
+ 3. ...
157
+
158
+ ---
159
+
160
+ ### Questions I still have
161
+ *(Optional — only include if there are genuine gaps that would change the recommendations)*
162
+ - ...
163
+ ```
164
+
165
+ ---
166
+
167
+ ## Tone guidelines
168
+
169
+ - **Encouraging but honest.** Don't sugarcoat real problems, but don't make people feel bad for building something imperfect. Everyone starts somewhere.
170
+ - **Opinionated where it matters.** If something is a bad idea for their context, say so clearly and explain why in plain terms.
171
+ - **Context-aware suggestions only.** Never suggest something that doesn't fit the platform or scale. Don't suggest microservices to someone building a weekend project. Don't suggest a static site to someone who needs real-time collaboration.
172
+ - **Suggestions are calibrated to experience level.** For pros: motivation is embedded in every suggestion — specific, direct, no filler. For beginners: suggestions are short and clear, followed by a light invite ("Want me to explain why, or how to do this?"). Never explain unprompted to a beginner; never leave a pro without a reason.
173
+
174
+ ---
175
+
176
+ ## Reference files
177
+
178
+ - `references/architecture-patterns.md` — Common patterns and anti-patterns with guidance on when each applies
179
+ - `references/frontend-checklist.md` — Frontend review checklist by platform type (web, mobile, desktop)
180
+ - `references/backend-checklist.md` — Backend review checklist by scale and use case
181
+
182
+ Read whichever reference files are relevant to the sections you're assessing. These help ensure coverage without bloating this file.
package/skills/planning-project-setup-info-local.md ADDED
@@ -0,0 +1,128 @@
1
+ ---
2
+ name: project-setup-info-local
3
+ description: 'Comprehensive setup steps to help the user create complete project structures in a VS Code workspace; this tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: user wants to create a new complete project from scratch; setting up entire project frameworks (TypeScript projects, React apps, Node.js servers, etc.); initializing Model Context Protocol (MCP) servers with full structure; creating VS Code extensions with proper scaffolding; setting up Next.js, Vite, or other framework-based projects; user asks for "new project", "create a workspace", "set up a [framework] project"; need to establish a complete development environment with dependencies, config files, and folder structure. When NOT to use this tool: creating single files or small code snippets; adding individual files to existing projects; making modifications to existing codebases; user asks to "create a file" or "add a component"; simple code examples or demonstrations; debugging or fixing existing code. This tool provides complete project setup including: folder structure creation; package.json and dependency management; configuration files (tsconfig, eslint, etc.); initial boilerplate code; development environment setup; build and run instructions. Use other file creation tools for individual files within existing projects.'
4
+ category: planning
5
+ ---
6
+
7
+ # How to setup a project
8
+
9
+ Determine what kind of project the user wants to create, then based on that, choose which setup info below to follow. Only setup a project if the folder is empty or if you've just called the tool first calling the tool to create a workspace.
10
+
11
+ ## vscode-extension
12
+
13
+ A template for creating a VS Code extension using Yeoman and Generator-Code.
14
+
15
+ Run this command:
16
+
17
+ ```
18
+ npx --package yo --package generator-code -- yo code . --skipOpen
19
+ ```
20
+ The command has the following arguments:
21
+
22
+ - `-t, --extensionType`: Specify extension type: ts, js, command-ts, command-js, colortheme, language, snippets, keymap, extensionpack, localization, commandweb, notebook. Defaults to `ts`
23
+ - `-n, --extensionDisplayName`: Set the display name of the extension.
24
+ - `--extensionId`: Set the unique ID of the extension. Do not select this option if the user has not requested a unique ID.
25
+ - `--extensionDescription`: Provide a description for the extension.
26
+ - `--pkgManager`: Specify package manager: npm, yarn, or pnpm. Defaults to `npm`.
27
+ - `--bundler`: Bundle the extension using webpack or esbuild.
28
+ - `--gitInit`: Initialize a Git repository for the extension.
29
+ - `--snippetFolder`: Specify the location of the snippet folder.
30
+ - `--snippetLanguage`: Set the language for snippets.
31
+
32
+ ### Rules
33
+
34
+ 1. Do not remove any arguments from the command. Only add arguments if the user requests them.
35
+ 2. Call the tool `get_vscode_api` with the user's query to get the relevant references.
36
+ 3. After the tool `get_vscode_api` has completed, only then begin to modify the project.
37
+
38
+ ## next-js
39
+
40
+ A React based framework for building server-rendered web applications.
41
+
42
+ Run this command:
43
+
44
+ ```
45
+ npx create-next-app@latest .
46
+ ```
47
+ The command has the following arguments:
48
+
49
+ - `--ts, --typescript`: Initialize as a TypeScript project. This is the default.
50
+ - `--js, --javascript`: Initialize as a JavaScript project.
51
+ - `--tailwind`: Initialize with Tailwind CSS config. This is the default.
52
+ - `--eslint`: Initialize with ESLint config.
53
+ - `--app`: Initialize as an App Router project.
54
+ - `--src-dir`: Initialize inside a 'src/' directory.
55
+ - `--turbopack`: Enable Turbopack by default for development.
56
+ - `--import-alias <prefix/*>`: Specify import alias to use.(default is "@/*")
57
+ - `--api`: Initialize a headless API using the App Router.
58
+ - `--empty`: Initialize an empty project.
59
+ - `--use-npm`: Explicitly tell the CLI to bootstrap the application using npm.
60
+ - `--use-pnpm`: Explicitly tell the CLI to bootstrap the application using pnpm.
61
+ - `--use-yarn`: Explicitly tell the CLI to bootstrap the application using Yarn.
62
+ - `--use-bun`: Explicitly tell the CLI to bootstrap the application using Bun.
63
+
64
+ ## vite
65
+
66
+ A front end build tool for web applications that focuses on speed and performance. Can be used with React, Vue, Preact, Lit, Svelte, Solid, and Qwik.
67
+
68
+ Run this command:
69
+
70
+ ```
71
+ npx create-vite@latest .
72
+ ```
73
+ The command has the following arguments:
74
+
75
+ - `-t, --template NAME`: Use a specific template. Available templates: vanilla-ts, vanilla, vue-ts, vue, react-ts, react, react-swc-ts, react-swc, preact-ts, preact, lit-ts, lit, svelte-ts, svelte, solid-ts, solid, qwik-ts, qwik
76
+
77
+ ## mcp-server
78
+
79
+ A Model Context Protocol (MCP) server project. This project supports multiple programming languages including TypeScript, JavaScript, Python, C#, Java, and Kotlin.
80
+
81
+ ### Rules
82
+
83
+ 1. First, visit https://github.com/modelcontextprotocol to find the correct SDK and setup instructions for the requested language. Default to TypeScript if no language is specified.
84
+ 2. Use the `fetch_webpage` tool to find the correct implementation instructions from https://modelcontextprotocol.io/llms-full.txt
85
+ 3. Update the copilot-instructions.md file in the .github directory to include references to the SDK documentation
86
+ 4. Create an `mcp.json` file in the `.vscode` folder in the project root with the following content: `{ "servers": { "mcp-server-name": { "type": "stdio", "command": "command-to-run", "args": [list-of-args] } } }`.
87
+ - mcp-server-name: The name of the MCP server. Create a unique name that reflects what this MCP server does.
88
+ - command-to-run: The command to run to start the MCP server. This is the command you would use to run the project you just created.
89
+ - list-of-args: The arguments to pass to the command. This is the list of arguments you would use to run the project you just created.
90
+ 5. Install any required VS Code extensions based on the chosen language (e.g., Python extension for Python projects).
91
+ 6. Inform the user that they can now debug this MCP server using VS Code.
92
+
93
+ ## python-script
94
+
95
+ A simple Python script project which should be chosen when just a single script wants to be created.
96
+
97
+ Required extensions: `ms-python.python`, `ms-python.vscode-python-envs`
98
+
99
+ ### Rules
100
+
101
+ 1. Call the tool `copilot_runVscodeCommand` to correctly create a new Python script project in VS Code. Call the command with the following arguments.
102
+ Note that "python-script" and "true" are constants while "New Project Name" and "/path/to/new/project" are placeholders for the project name and path respectively.
103
+ ```json
104
+ {
105
+ "name": "python-envs.createNewProjectFromTemplate",
106
+ "commandId": "python-envs.createNewProjectFromTemplate",
107
+ "args": ["python-script", "true", "New Project Name", "/path/to/new/project"]
108
+ }
109
+ ```
110
+
111
+ ## python-package
112
+
113
+ A Python package project which can be used to create a distributable package.
114
+
115
+ Required extensions: `ms-python.python`, `ms-python.vscode-python-envs`
116
+
117
+ ### Rules
118
+
119
+ 1. Call the tool `run_vscode_command` to correctly create a new Python package project in VS Code. Call the command with the following arguments.
120
+ Note that "python-package" and "true" are constants while "New Package Name" and "/path/to/new/project" are placeholders for the package name and path respectively.
121
+ ```json
122
+ {
123
+ "name": "python-envs.createNewProjectFromTemplate",
124
+ "commandId": "python-envs.createNewProjectFromTemplate",
125
+ "args": ["python-package", "true", "New Package Name", "/path/to/new/project"]
126
+ }
127
+ ```
128
+