Scaffold new applications following the syner common stack. Use when creating new apps, projects, or when the user says "nueva app", "create app", "new project", or "scaffold".
Create new applications with the syner standard stack consistently. This ensures all apps in the ecosystem share the same foundation and tooling.
Navigate upward from the current working directory until you find a directory containing apps/. Use ls to verify. If no apps/ directory exists, ask the user where to create the project.
Anchor to project root (directory containing apps/), then use the Read tool to load {root}/.syner/vaults/vaults/syner/common-stack.md.
This step is mandatory - the skill ALWAYS reads common-stack.md before acting. This allows the stack to evolve without modifying the skill.
If project name not provided as argument, ask the user:
What should the app be called?
If location not provided, use apps/[name] as default within the project root.
Before creating, verify apps/[name] doesn't already exist. If it does, ask the user:
Use Bash tool to run:
bunx create-next-app@latest apps/[name] --typescript --tailwind --eslint --app --import-alias "@/*" --yes
The --yes flag accepts all defaults automatically.
Use Bash tool to run:
cd apps/[name] && bunx shadcn@latest init --defaults
Output using the format below.
Suggest the user run:
cd apps/[name] && bun dev
ALWAYS use this structure:
apps/[name]cd apps/[name] && bun dev to start development server/create-syner-app [app-name]
Examples:
/create-syner-app my-dashboard - Create app named "my-dashboard"/create-syner-app - Will prompt for app nameAfter testing this skill, clean up:
rm -rf apps/[test-app-name]
common-stack.md and read dynamicallyvercel CLI for production deploymentsgh CLI for git operationsValidate against /syner-boundaries: