Run any Skill in Manus with one click

setup-repo

Stars6

Forks0

UpdatedMay 27, 2026 at 20:16

Bootstrap a hybrid pnpm + Deno monorepo, add a package to an existing one, or scaffold an SPA package (Vite + React 19 + TanStack Router + Tailwind 4 + shadcn). Use when the user wants to set up a new repo, scaffold a project, create/add a package under packages/, or scaffold a frontend SPA. Asks like "set up a repo", "create a monorepo", "add a package", "scaffold an SPA", "new website package".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jtmenchaca

jtmenchaca/tidy-ts

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

16 files

SKILL.md

readonly

name	setup-repo
description	Bootstrap a hybrid pnpm + Deno monorepo, add a package to an existing one, or scaffold an SPA package (Vite + React 19 + TanStack Router + Tailwind 4 + shadcn). Use when the user wants to set up a new repo, scaffold a project, create/add a package under packages/, or scaffold a frontend SPA. Asks like "set up a repo", "create a monorepo", "add a package", "scaffold an SPA", "new website package".

Set Up a Repo

Covers three flows that share the same dependency invariant and file templates:

Bootstrapping a brand-new monorepo.
Adding a package to an existing monorepo.
Scaffolding an SPA package (composes with #1 or #2).

Load the rule files below for the path you need.

The Core Invariant

Root package.json owns versions. pnpm-workspace.yaml maps them with $name overrides. Package package.json files reference deps with "*".

Keep this intact at every step. Full rules in rules/dependencies.md.

Picking a flow

Bootstrapping a fresh repo? Load rules/new-repo.md.
Adding a package to an existing repo? Load rules/add-package.md.
Scaffolding an SPA package? Load rules/spa/overview.md. SPA is an add-on — combine it with one of the two above depending on whether the repo exists yet.

Shared supporting rules

All flows reference these:

rules/dependencies.md — the root-owns-versions invariant, adding new deps, JSR conventions.
rules/file-templates.md — concrete templates for package.json (root + package), pnpm-workspace.yaml, deno.jsonc.
rules/verify.md — pnpm install, deno check ., common failure modes.

SPA rules (load only if scaffolding an SPA)

rules/spa/overview.md — entry point and prompts.
rules/spa/vite-router-query.md — Vite config, main.tsx, TanStack Router + Query, tsconfig trio, router-generator patch.
rules/spa/tailwind-shadcn.md — Tailwind 4 + shadcn/ui wiring.
rules/spa/eslint.md — ESLint flat config.
rules/spa/deno-deploy.md — Deno Deploy (optional): CLI vs dashboard schema, gotchas, day-2 commands, env vars, logs.

Standing user rules

Never run git init as part of this skill — the user opts in separately.
Never report success without running pnpm check (or deno check .) — this is a hard rule in the user's global CLAUDE.md.
For SPA work, also verify in a browser before claiming success (the user's UI testing rule).

More from this repository

same repository

audit-prose

jtmenchaca/tidy-ts

Phrase-by-phrase audit of written prose against a defined reader, with explicit reader-question generation and strict avoidance of marketing constructions. Use when the user wants to tighten the writing in a document (manuscript, blog post, PRD, report) for clarity and to remove style drift.

2026-05-276

verify-citations

jtmenchaca/tidy-ts

Verify every citation in a document against the actual source. For each cited claim, find the real paper (DOI → PMID → title search → web), fetch the abstract or full text, and check whether the manuscript's framing matches what the paper actually says. Use when the user asks "are these citations real?", "do the cited findings match the source?", "verify the references in X", or wants a sanity check before submitting a manuscript.

2026-05-276

create-agent-test-tidy-ts

jtmenchaca/tidy-ts

How to dispatch sub-agents to test the tidy-ts-best-practices skill. Covers the strict access rules, anti-fabrication guardrails, plain-language task design, and prompt templates that produce honest, evidence-backed findings.

2026-05-266

publish-npm

jtmenchaca/tidy-ts

Publish the tidy-ts packages (shims, dataframe, graph) to npm. Walks through version bump, optional Rust/WASM/napi rebuilds, type checks, tests, npm builds, and publish. Use when the user wants to cut a new npm release ("publish to npm", "cut a release", "ship a new version").

2026-05-266

repo-portable

jtmenchaca/tidy-ts

Make the repo portable. Drive out hidden local sources of truth so tracked docs and GitHub Issues are the only durable knowledge. Use when the user wants to audit the repo for drift between local-only knowledge and tracked state, reconcile issues with PRD/phase labels, close stale backlog, find secret/data risk, or fix ad hoc doc homes.

2026-05-266

tidy-ts-best-practices

jtmenchaca/tidy-ts

Best practices for tidy-ts — typed DataFrames, statistics, regression, hypothesis testing, distributions, I/O, and cross-runtime shims. Use whenever writing or editing tidy-ts code so you reach for the right verbs, statistics, and patterns.

2026-05-266

name	setup-repo
description	Bootstrap a hybrid pnpm + Deno monorepo, add a package to an existing one, or scaffold an SPA package (Vite + React 19 + TanStack Router + Tailwind 4 + shadcn). Use when the user wants to set up a new repo, scaffold a project, create/add a package under packages/, or scaffold a frontend SPA. Asks like "set up a repo", "create a monorepo", "add a package", "scaffold an SPA", "new website package".

Set Up a Repo

Covers three flows that share the same dependency invariant and file templates:

Bootstrapping a brand-new monorepo.
Adding a package to an existing monorepo.
Scaffolding an SPA package (composes with #1 or #2).

Load the rule files below for the path you need.

The Core Invariant

Root package.json owns versions. pnpm-workspace.yaml maps them with $name overrides. Package package.json files reference deps with "*".

Keep this intact at every step. Full rules in rules/dependencies.md.

Picking a flow

Bootstrapping a fresh repo? Load rules/new-repo.md.
Adding a package to an existing repo? Load rules/add-package.md.
Scaffolding an SPA package? Load rules/spa/overview.md. SPA is an add-on — combine it with one of the two above depending on whether the repo exists yet.

Shared supporting rules

All flows reference these:

rules/dependencies.md — the root-owns-versions invariant, adding new deps, JSR conventions.
rules/file-templates.md — concrete templates for package.json (root + package), pnpm-workspace.yaml, deno.jsonc.
rules/verify.md — pnpm install, deno check ., common failure modes.

SPA rules (load only if scaffolding an SPA)

rules/spa/overview.md — entry point and prompts.
rules/spa/vite-router-query.md — Vite config, main.tsx, TanStack Router + Query, tsconfig trio, router-generator patch.
rules/spa/tailwind-shadcn.md — Tailwind 4 + shadcn/ui wiring.
rules/spa/eslint.md — ESLint flat config.
rules/spa/deno-deploy.md — Deno Deploy (optional): CLI vs dashboard schema, gotchas, day-2 commands, env vars, logs.

Standing user rules

Never run git init as part of this skill — the user opts in separately.
Never report success without running pnpm check (or deno check .) — this is a hard rule in the user's global CLAUDE.md.
For SPA work, also verify in a browser before claiming success (the user's UI testing rule).