Repository navigation
feat(web): new ASCII-T logo + refreshed agent skills #1286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
79ab474
feat(web): replace logo and favicons with the ASCII banner T
AmanVarshney01 825e2ba
docs(plugin): refresh agent skills and add a standalone better-t-stac…
AmanVarshney01 a5eea3c
docs(plugin): point skills at the hosted MCP and fix builder URL lists
AmanVarshney01 2d537a0
docs(plugin): mark axiom as creation-only in the add skills
AmanVarshney01 0f43c8b
docs(plugin): restructure skills for agents reading them cold
AmanVarshney01 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
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
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,20 +1,20 @@ | ||
| --- | ||
| description: Add addons/features (PWA, Tauri, docs, linters, task runners, MCP, …) to an existing Better-T-Stack project via the Better-T-Stack MCP server. | ||
| argument-hint: "<addons to add, e.g. pwa biome turborepo>" | ||
| description: Add addons/features (PWA, Tauri, docs, linters, task runners, MCP, …) or a workspace package to an existing Better-T-Stack project via the Better-T-Stack MCP server (or the CLI's add-json). | ||
| argument-hint: "<addons to add, e.g. pwa biome turborepo, or a package name>" | ||
| --- | ||
|
|
||
| # Add addons to a Better-T-Stack project | ||
| # Add to a Better-T-Stack project | ||
|
|
||
| User request: $ARGUMENTS | ||
|
|
||
| Add tooling/features to the current Better-T-Stack project using the Better-T-Stack MCP server instead of wiring it by hand. | ||
| Add tooling/features or a workspace package to the current Better-T-Stack project instead of wiring it by hand. Follow the **add-to-project** skill. | ||
|
|
||
| ## Steps | ||
|
|
||
| 1. **Confirm** the working directory is a Better-T-Stack project (look for `bts.jsonc`). | ||
| 2. **Determine the addon set** from the arguments above. Use `bts_get_schema` for nested addon options when needed. | ||
| 3. **Plan with `bts_plan_addons`** (dry run) and review the changes. Surface any conflicts (e.g. `nx`/`turborepo`/`vite-plus` are mutually exclusive). | ||
| 4. **Apply with `bts_add_addons`** once confirmed. | ||
| 1. **Confirm** the working directory is a Better-T-Stack project and read its `bts.jsonc` to learn the current stack. If it's missing, stop and tell the user — don't recreate it. | ||
| 2. **Determine the addon set** (or `package` name) from the arguments above. Use `bts_get_schema` (or `schema --name addonOptions`) for nested addon options when needed. | ||
| 3. **Plan with `bts_plan_addons`** — or, without the MCP, `create-better-t-stack add-json --input '<payload with "dryRun": true>'` — and review the changes. Surface any conflicts (e.g. `nx`/`turborepo`/`vite-plus` are mutually exclusive). | ||
| 4. **Apply with `bts_add_addons`** (or `add-json` without `dryRun`) once confirmed. | ||
| 5. **Report** what changed and any follow-up commands. | ||
|
|
||
| Always plan before applying. Don't add addons the user didn't ask for. | ||
| Always plan before applying. Don't add addons the user didn't ask for. Never hand-edit `bts.jsonc`. |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,21 +1,21 @@ | ||
| --- | ||
| description: Scaffold a new Better-T-Stack project. Plans a full, validated stack with the Better-T-Stack MCP server, confirms it, then generates the project. | ||
| description: Scaffold a new Better-T-Stack project. Plans a full, validated stack with the Better-T-Stack MCP server (or the CLI's create-json), confirms it, then generates the project. | ||
| argument-hint: "<project name and/or stack description>" | ||
| --- | ||
|
|
||
| # Create a Better-T-Stack project | ||
|
|
||
| User request: $ARGUMENTS | ||
|
|
||
| Scaffold a new project using the Better-T-Stack MCP server. Do not hand-roll the project structure, tooling, auth, or database wiring. | ||
| Scaffold a new project with Better-T-Stack. Do not hand-roll the project structure, tooling, auth, or database wiring. Follow the **scaffold-project** skill. | ||
|
|
||
| ## Steps | ||
|
|
||
| 1. **Parse the request.** Extract the project name and any stack preferences from the arguments above. If nothing was provided, ask what kind of project they want. | ||
| 2. **Resolve unknowns.** For any major choice not specified, either ask a brief question or pick a sensible default and state it. Call `bts_get_stack_guidance` and `bts_get_schema` when you need the authoritative option list or rules. | ||
| 2. **Resolve unknowns.** For any major choice not specified, either ask a brief question or pick a sensible default and state it. Call `bts_get_stack_guidance` and `bts_get_schema` (or `npx create-better-t-stack@latest schema --name createInput`) for the authoritative option list and rules. | ||
| 3. **Build a full explicit config.** Every field must be set explicitly (use `"none"`, `[]`, `true`/`false`). Required: `projectName`, `frontend`, `backend`, `runtime`, `database`, `orm`, `api`, `auth`, `payments`, `addons`, `examples`, `git`, `packageManager`, `install`, `dbSetup`, `webDeploy`, `serverDeploy`. | ||
| 4. **Plan with `bts_plan_project`** (dry run). Show the resolved stack and confirm it matches intent. | ||
| 5. **Create with `bts_create_project`** once confirmed. Use `install: false` to avoid MCP timeouts. | ||
| 4. **Plan** with `bts_plan_project` — or, without the MCP, `create-better-t-stack create-json --input '<config with "dryRun": true>'`. Show the resolved stack and confirm it matches intent. | ||
| 5. **Create** with `bts_create_project` (or `create-json` without `dryRun`) once confirmed. Use `install: false` to avoid timeouts. | ||
| 6. **Report** the stack and the exact next commands (`<packageManager> install`, `dev`, any DB setup). | ||
|
|
||
| Always plan before create. Never send a partial config. | ||
| Always plan before create. Never send a partial config. Never use `--yolo`. |
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When an agent uses this skill to add
axiomto an existing project, the plan always fails becauseaddHandlerInternalexplicitly rejects it as creation-only (apps/cli/src/helpers/core/add-handler.ts:456-461). Remove it from this add-flow list or clearly direct users to select it only during project creation.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 2d537a0.
axiomis removed from the addable list, with a note that it can only be chosen at creation becauseaddrejects it (add-handler.ts). The standalone skill's add section says the same.