base
Scaffolds a new TypeScript project from scratch. Use when starting a new project, bootstrapping a codebase, or setting up a project from zero.
What this skill does
## Step 1: Ask about the project
Ask the user to describe what the project is about. Use their response to populate `<project-name>` and `<project-description>` in later steps.
## Step 2: Install dependencies
```bash
bun add -d @biomejs/biome @types/bun @typescript/native-preview knip simple-git-hooks taze turbo ultracite vitest
```
## Step 3: Create package.json
```json
{
"name": "<project-name>",
"version": "0.1.0",
"private": true,
"type": "module",
"scripts": {
"lint": "biome check",
"types": "tsgo --build",
"test": "vitest run",
"unused": "knip",
"update": "taze --interactive"
},
"dependencies": {},
"devDependencies": {},
"simple-git-hooks": {
"pre-commit": "make validate"
},
"knip": {
"ignoreDependencies": [
"turbo"
],
"ignoreBinaries": [
"make"
]
},
"packageManager": "bun@<current-bun-version>"
}
```
Replace `<current-bun-version>` with the output of `bun --version`.
## Step 4: Create scripts/setup.ts
```ts
import { file, spawn } from "bun";
await installDependencies();
await installGitHooks();
await setupRemoteCache();
export async function installDependencies() {
await spawn(["bun", "install"]).exited;
console.log("Dependencies installed");
}
export async function installGitHooks() {
await spawn(["bunx", "simple-git-hooks"]).exited;
console.log("Git hooks installed");
}
export async function setupRemoteCache(isRetry?: boolean) {
const config = file(".turbo/config.json");
if (!((await config.exists()) && (await config.json()).teamId)) {
const stdio = isRetry ? "inherit" : "pipe";
const link = spawn(["turbo", "link"], { stdio: [stdio, stdio, stdio] });
if ((await link.exited) !== 0) {
const error = await new Response(link.stderr).text();
if (error.includes("User not found")) {
await spawn(["turbo", "login"]).exited;
await setupRemoteCache();
return;
}
if (error.includes("IO error")) {
await setupRemoteCache(true);
return;
}
}
}
console.log("Turbo remote cache configured");
}
```
## Step 5: Create scripts/setup.test.ts
```ts
import { beforeEach, describe, expect, test, vi } from "vitest";
const mockSpawn = vi.fn().mockReturnValue({
exited: Promise.resolve(0),
stderr: new Blob([""]),
});
const mockFile = vi.fn().mockReturnValue({
exists: () => Promise.resolve(false),
json: () => Promise.resolve({}),
});
vi.mock("bun", () => ({
spawn: (...args: unknown[]) => mockSpawn(...args),
file: (...args: unknown[]) => mockFile(...args),
}));
const { installDependencies, installGitHooks, setupRemoteCache } = await import("./setup");
function spawnReturns(exitCode: number, stderr = "") {
return mockSpawn.mockReturnValue({
exited: Promise.resolve(exitCode),
stderr: new Blob([stderr]),
});
}
function configReturns(exists: boolean, json: Record<string, unknown> = {}) {
mockFile.mockReturnValue({
exists: () => Promise.resolve(exists),
json: () => Promise.resolve(json),
});
}
beforeEach(() => {
mockSpawn.mockClear();
mockFile.mockClear();
spawnReturns(0);
configReturns(false);
});
describe("installDependencies", () => {
test("runs bun install", async () => {
await installDependencies();
expect(mockSpawn).toHaveBeenCalledWith(["bun", "install"]);
});
});
describe("installGitHooks", () => {
test("runs bunx simple-git-hooks", async () => {
await installGitHooks();
expect(mockSpawn).toHaveBeenCalledWith(["bunx", "simple-git-hooks"]);
});
});
describe("setupRemoteCache", () => {
test("skips linking when config already has teamId", async () => {
configReturns(true, { teamId: "team_123" });
mockSpawn.mockClear();
await setupRemoteCache();
expect(mockSpawn).not.toHaveBeenCalledWith(["turbo", "link"], expect.anything());
});
test("runs turbo link with piped stdio on first attempt", async () => {
await setupRemoteCache();
expect(mockSpawn).toHaveBeenCalledWith(["turbo", "link"], {
stdio: ["pipe", "pipe", "pipe"],
});
});
test("runs turbo login then retries on 'User not found' error", async () => {
mockSpawn
.mockReturnValueOnce({
exited: Promise.resolve(1),
stderr: new Blob(["User not found"]),
})
.mockReturnValueOnce({ exited: Promise.resolve(0) })
.mockReturnValueOnce({ exited: Promise.resolve(0) });
configReturns(false);
await setupRemoteCache();
expect(mockSpawn).toHaveBeenCalledWith(["turbo", "login"]);
});
test("retries with inherited stdio on 'IO error'", async () => {
mockSpawn
.mockReturnValueOnce({
exited: Promise.resolve(1),
stderr: new Blob(["IO error"]),
})
.mockReturnValueOnce({ exited: Promise.resolve(0) });
await setupRemoteCache();
expect(mockSpawn).toHaveBeenCalledWith(["turbo", "link"], {
stdio: ["inherit", "inherit", "inherit"],
});
});
});
```
## Step 6: Create Makefile
```makefile
setup:
bun run scripts/setup.ts
validate:
bun run turbo validate
```
## Step 7: Create turbo.json
```json
{
"$schema": "https://turbo.build/schema.json",
"tasks": {
"lint": {},
"types": {},
"test": {},
"unused": {},
"validate": {
"dependsOn": ["lint", "types", "test", "unused"]
}
}
}
```
## Step 8: Create tsconfig.json
```json
{
"compilerOptions": {
"allowImportingTsExtensions": true,
"allowJs": true,
"allowSyntheticDefaultImports": true,
"esModuleInterop": true,
"forceConsistentCasingInFileNames": true,
"incremental": true,
"isolatedModules": true,
"lib": ["esnext"],
"module": "esnext",
"moduleDetection": "force",
"moduleResolution": "bundler",
"noEmit": true,
"noUncheckedIndexedAccess": true,
"noUncheckedSideEffectImports": true,
"skipLibCheck": true,
"strict": true,
"target": "esnext",
"verbatimModuleSyntax": false
},
"exclude": ["node_modules"],
"include": ["**/*.ts"]
}
```
## Step 9: Create biome.jsonc
```jsonc
{
"$schema": "node_modules/@biomejs/biome/configuration_schema.json",
"extends": ["ultracite/core"],
"formatter": {
"lineWidth": 100
},
"linter": {
"rules": {
"correctness": {
"noUnusedImports": "warn"
}
}
}
}
```
## Step 10: Create .gitignore
```
# base
*.local*
*.tsbuildinfo
.DS_Store
.turbo
node_modules
```
## Step 11: Create .github/workflows/ci.yml
```yaml
name: CI
on:
push:
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
check:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Bun
uses: oven-sh/setup-bun@v1
- name: Cache Bun dependencies
uses: actions/cache@v4
with:
path: ~/.bun/install/cache
key: ${{ runner.os }}-bun-${{ hashFiles('**/bun.lock') }}
restore-keys: |
${{ runner.os }}-bun-
- name: Install dependencies
run: bun install
- name: Validate
run: make validate
env:
TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
TURBO_TEAM: ${{ vars.TURBO_TEAM }}
```
## Step 12: Create vitest.config.ts
```ts
import { defineConfig } from "vitest/config";
export default defineConfig({
test: {
projects: [
{
extends: true,
test: {
name: "unit",
include: ["**/*.test.ts"],
environment: "node",
},
},
],
},
});
```
## Step 13: Create AGENTS.md
```markdown
# <project-name>
<project-description>
## Tech Stack
- **Package manager:** Bun
- **Testing:** Vitest
## Conventions
<!-- Add project-specific conventions here as the codebase evolves -->
```
Then create a symlink so tools that look for `CLAUDE.md` find the same file:
```bash
ln -s AGENTS.md CLAUDE.md
```
## Step 14: Create README.md
```markdown
# <project-name>
<project-description>
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.