fix(plugin): use the bundled default starter (v0.4.2) - #84
Merged
Merged
Conversation
Keep the public plugin on @latest and use blankapp so scaffolding follows the CLI release instead of the external gallery. Align the optional MCP handoff and bump all public plugin release metadata to 0.4.2. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Chris (chcaru)
commented
Sep 24, 2026
Comment on lines
+69
to
+78
| **Always use the bundled `blankapp` template.** Don't browse the gallery or pick a | ||
| domain-specific template. This stable template name follows the CLI release: the existing | ||
| Blank App on 1.35.x, and the Universal App from 1.36.0 onward. Keep `@latest`; do not switch | ||
| to a prerelease channel to get the newer template. | ||
|
|
||
| The Universal App is a deliberately small React + Vite base with a built-in capability router | ||
| that pulls in the right Rayfin services, npm modules, and skills on demand. The domain shape | ||
| (analytics, CRUD, storage, functions) gets decided inside the project rather than at scaffold | ||
| time. The project's own `.agents/skills/` own that decision and are version-matched to the | ||
| starter. |
Contributor
Author
There was a problem hiding this comment.
don't go into details about package versions and version differentials. the skill should simply specify to the use template, not justify it.
Comment on lines
+93
to
+98
| The [getting-started skill](skills/rayfin-getting-started/SKILL.md) uses | ||
| `@microsoft/create-rayfin@latest --template blankapp`, keeping the starter matched to the CLI | ||
| release instead of fetching it from the gallery. | ||
| Once inside the project, agents use its version-locked skill and `rayfin docs`; the Rayfin MCP | ||
| server is optional. | ||
|
|
Contributor
Author
There was a problem hiding this comment.
remove unneeded documentaiton.
Comment on lines
+28
to
+30
| scaffold one, in the same session. The `rayfin` MCP server is an optional extra that most | ||
| projects do not install; if it happens to be available it is a convenience, never a | ||
| prerequisite. Lean on the in-project skill file plus `rayfin docs`. |
Contributor
Author
There was a problem hiding this comment.
in general for these updates, i wonder if the "MCP is optional" tagline is even needed, certainly at the plugin level. consider omitting instead of caveating.
Remove version-transition rationale, unnecessary README guidance, and plugin-level MCP caveats. Restore the original plugin descriptions while retaining the bundled template selection and 0.4.2 version bump. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sean Watson (seanwat-msft)
approved these changes
Sep 24, 2026
7 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Keep the getting-started plugin on the CLI's bundled default starter instead of fetching the Universal App from the gallery. Bump the public plugin from 0.4.1 to 0.4.2, including every release-bearing manifest/catalog field and the skill metadata, for downstream marketplace updates.
Usage impact
Keep
@latest. Theblankappselector produces the existing Blank App with 1.35.1 and maps to the bundled Universal App in the upcoming 1.36.0 release. The short transition is intentional: no prerelease channel or follow-up plugin change is needed when 1.36.0 becomes latest.An explicit selector matters here. With 1.35.1, omitting
--templateonly initializes backend configuration, while--template universal-appis not recognized.What changed
--template blankapp; leave capability selection to the scaffolded project's own skills.rayfin docs. MCP remains optional.npx -y, explicit CLI package, and--project-namefixes, plus the public agent website links.Known-deferred
The downstream awesome-copilot update and release tagging are separate from this PR.
Verified: successful isolated scaffolds and dependency installation with both
@microsoft/create-rayfin@1.35.1 --template blankappand@microsoft/create-rayfin@1.36.0-alpha.1756 --template blankapp. Confirmed the former produces Blank App and the latter produces Universal App with its capability router. All 12 manifest/catalog release fields and the skill metadata agree on 0.4.2; the plugin export scan, starter-prompt quote check, andgit diff --checkpass. No cloud resources were provisioned.Type of change
Checklist
AI disclosure
GitHub Copilot assisted with comparing the plugin guidance, making the edits, and running the scaffold and manifest checks.