Team Preset for Repeatable Full-Stack Setup
Create and reuse a team preset so every new project starts with the same defaults and enhancement stack.
Prerequisites
Section titled “Prerequisites”- Node.js 20.11+
tinkeriseinstalled- One existing project where you want to capture defaults
Step 1: Prepare a baseline project
Section titled “Step 1: Prepare a baseline project”tinkerise web next team-template --typescript --tailwind --eslintcd team-templatetinkerise add prettier husky ci docker envExpected result: a configured baseline project with common workflow enhancements.
Step 2: Create project defaults
Section titled “Step 2: Create project defaults”tinkerise config set packageManager pnpm --projecttinkerise config set defaultCategory web --projecttinkerise config set typescript true --projectThis writes a project config that the preset can capture.
Step 3: Save the preset
Section titled “Step 3: Save the preset”tinkerise preset save team-fullstack --framework next --category web --description "Team standard full-stack starter"Expected output: confirmation that team-fullstack was saved.
Step 4: Apply the preset in a new project
Section titled “Step 4: Apply the preset in a new project”mkdir ../team-productcd ../team-producttinkerise preset use team-fullstackExpected result: enhancement modules from the preset are applied in the new repo.
Step 5: Verify and inspect
Section titled “Step 5: Verify and inspect”tinkerise preset listtinkerise config list --projectConfirm the preset is discoverable and project defaults are visible.
Expected generated artifacts
Section titled “Expected generated artifacts”- Local preset JSON in the tinkerise presets directory
tinkerise.config.tsin project root (when project config is used)- Enhancement-generated files such as Docker/CI/Husky config files
Next steps
Section titled “Next steps”- Publish a shared preset package for wider reuse.
- Add testing defaults with
tinkerise add testing. - Review config and preset behavior in Configuration and Presets.