From frontend-setup
Ensure the user is on a feature branch before making changes to code in the BTNet project. Activate when about to edit, create, or modify files in BTNet.
npx claudepluginhub buildertrend/product-toolkit --plugin frontend-setupThis skill uses the workspace's default tool permissions.
You are helping a non-technical user (designer or PM) make sure their changes are on a separate branch before editing any code. This keeps the main codebase safe and makes it easy to review changes later.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
You are helping a non-technical user (designer or PM) make sure their changes are on a separate branch before editing any code. This keeps the main codebase safe and makes it easy to review changes later.
IMPORTANT: Never combine commands with shell operators. No &&, ||, ;, |, >, <, `, $(...), or eval. Always run each command as a separate Bash tool call.
Look for a BTNet directory. Check common locations:
~/BTNet)~/Desktop/BTNet)~/dev/BTNet, ~/repos/BTNet, ~/code/BTNet)~/Documents/BTNet, ~/Downloads/BTNet)Run ls on each candidate path to find it. Verify it's the right project by checking that Clients.App exists inside it.
If you can't find it, ask the user where it is. If they don't have it, tell them to run /frontend-setup:first-time-setup first, then stop.
Once found, cd into the BTNet directory.
Run git branch --show-current.
master or main: continue to Step 3.Run git pull to make sure master is up to date.
If this fails (network issues, auth problems), tell the user it's OK and continue — they'll just be working from a slightly older copy.
Ask the user two things in a single message:
Wait for their response.
Using their answers, build a branch name.
Sanitization rules (apply these yourself, don't explain them to the user):
<number>-<description><description>Examples:
231499-update-header-colorfix-the-login-button-spacingRun:
git checkout -b <branch-name>
Tell the user: "I've set up a safe workspace for your changes. Everything you do from here won't affect the main project until someone reviews it."
Let the user continue with whatever they were about to do. Don't prompt for anything else.