# \[GSoC 2026\] \[Draft Proposal\] Schema-Driven SPM Template Wizard for VS Code **URL:** \ **Category:** GSoC\ **Tags:** gsoc-2026\ **Created:** [March 9, 2026, 2:36am UTC](https://forums.swift.org/t/gsoc-2026-draft-proposal-schema-driven-spm-template-wizard-for-vs-code/85215 "2026-03-09T02:36:18Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![NJ-012](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/nj-012/32/44673_2.png) [@NJ-012](https://forums.swift.org/u/NJ-012)\ **Post date:** [March 9, 2026, 2:36am UTC](https://forums.swift.org/t/gsoc-2026-draft-proposal-schema-driven-spm-template-wizard-for-vs-code/85215/1 "2026-03-09T02:36:19Z")
Hi everyone, I’m Niyati, and I’ve been exploring the `vscode-swift` extension internals. I’ve drafted a proposal for a **Schema-Driven Template Wizard** to bring a first-class scaffolding experience to the IDE. **The Problem:** Currently, using SwiftPM templates in VS Code requires leaving the editor for the CLI, which creates friction for new developers and masks the power of the template system. **The Proposed Solution:** Instead of a static UI, I am proposing a dynamic Wizard that uses `swift package --experimental-dump-help` as the single source of truth. The extension will parse the JSON schema at runtime to generate a validated, native-feeling form. **Technical Highlights of the Proposal:** - **State Machine Architecture:** Using a pure transition function to manage the Wizard's lifecycle, ensuring predictable UI states. - **Robust IPC Protocol:** A typed discriminated union protocol for Extension Host ↔ Webview communication, including stale-response mitigation using `requestId` tagging. - **Resilient Subprocess Management:** Platform-specific handling for subprocess termination (SIGTERM/SIGKILL logic for Windows/Unix) and a fallback "kill switch" via user settings. - **Parser Heuristics:** A dedicated `parseKind` logic to map CLI arguments (flags, enums, paths) to VS Code UI components. I’ve focused heavily on making this project **measurable** and **architecturally sound** to ensure it aligns with the high standards of the Swift toolchain. **Full Proposal Link:** [GSoC 2026: Schema-Driven SPM Template Wizard](https://docs.google.com/document/d/1whlRrnXzlKOVGE0t6sobwasjeM4fry2PjvBCptPNu7k/edit?usp=sharing) (Open for comments) I would appreciate any feedback on the technical approach—specifically regarding the handling of experimental flags and the Webview IPC model. Thanks! — Niyati ---
**Author:** ![willpaceley](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/willpaceley/32/44610_2.png) [@willpaceley](https://forums.swift.org/u/willpaceley)\ **Post date:** [March 10, 2026, 7:03pm UTC](https://forums.swift.org/t/gsoc-2026-draft-proposal-schema-driven-spm-template-wizard-for-vs-code/85215/2 "2026-03-10T19:03:37Z")
Hey @NJ-012 , thanks for reaching out for feedback on your proposal. I took a cursory glance and noted a few inaccuracies that conflict with the state of the codebase, one notable one is the mention of an “existing telemetry infrastructure” which doesn’t exist. As I’m sure you can understand, we can only provide feedback on proposals that contain accurate analysis of the project. I also recommend trying to err on the side brevity, as a 19 page proposal is a lot to digest for this project idea! ---
**Author:** ![NJ-012](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/nj-012/32/44673_2.png) [@NJ-012](https://forums.swift.org/u/NJ-012)\ **Post date:** [March 11, 2026, 5:31am UTC](https://forums.swift.org/t/gsoc-2026-draft-proposal-schema-driven-spm-template-wizard-for-vs-code/85215/3 "2026-03-11T05:31:22Z")
Hi Will, Thanks for the direct feedback. You're right—in my effort to be thorough, I included some broad architectural assumptions (like the telemetry mention) that don't reflect the specific 'lean' nature of your codebase. I also agree that the current draft is far too dense for this project's scope. I'm going to strip this back significantly. My goal is to produce a much tighter, 5-page technical spec that focuses strictly on the actual schema logic and the VS Code implementation. I'll spend the next few days auditing the repository specifically to ensure the revised timeline and architecture are perfectly aligned with the existing codebase. I appreciate the steer on brevity! ---
**Author:** ![NJ-012](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/nj-012/32/44673_2.png) [@NJ-012](https://forums.swift.org/u/NJ-012)\ **Post date:** [March 19, 2026, 10:45am UTC](https://forums.swift.org/t/gsoc-2026-draft-proposal-schema-driven-spm-template-wizard-for-vs-code/85215/4 "2026-03-19T10:45:17Z")
I've attached the revised proposal above for reference: > **[GSoC\_2026\_Proposal\_Niyati.docx](https://docs.google.com/document/d/18nPG2W9txhxQkEzVfB-kugbEf6W5PqOe/edit?usp=sharing&ouid=109523122289102009443&rtpof=true&sd=true)** > > GSoC 2026 — Project Proposal SPM Template Wizard for the Swift VS Code Extension Candidate Niyati Joshi Organization Swift.org — swiftlang/vscode-swift Size / Level 200 hours · Intermediate Mentors Will Paceley, Matthew Bastien 1. Synopsis SE-0500... Comments are open on the document. If you have a moment before the submission deadline, I'd genuinely appreciate any feedback on the revised approach — particularly on the schema retrieval recommendation (Option A) and the createNewProject.ts integration point, since those are the two areas I'm least certain are aligned with what the team has in mind. No pressure if timing doesn't allow it — I wanted to make sure the document was accessible in case it's useful. Thanks again — Niyati