project-bootstrap
Use when the user requests repository setup, tooling infrastructure, or Jess's full project template. Skip coding, prototypes, and hardening requests that do not include repository setup.
- Installs
- 794
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jssblck/agents --skill project-bootstrap- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads project-bootstrap automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Project Bootstrap
Apply Jess's defaults to the repository setup the user requested. A request for an application or a small prototype does not by itself request the full template. Preserve established tooling unless migration is part of the request.
Choose the scope
Infer the language, artifact type, and requested setup from the task. Distinguish a minimal runnable project from a repository intended for distribution. State material infrastructure choices before implementing them. Ask only when missing information changes a decision the user owns.
- Minimal setup: source layout, dependency manifest, and the commands needed to run and verify the project.
- Repository tooling: formatter, linter, type/build checks, and CI.
- Distribution: release automation and contributor-facing files appropriate to the product.
- Full Jess template: repository tooling, applicable distribution files, and agent-rule and review infrastructure. Use only when the full template or those gates are requested.
Tooling defaults
| Language | Formatter | Linter | Type/build check |
|---|---|---|---|
| Rust | rustfmt | clippy | cargo build / cargo test |
| Go | gofmt / goimports | staticcheck + go vet | go build / go test |
| TypeScript | oxfmt | oxlint | tsc --noEmit |
| Python | ruff format | ruff check | mypy or pyright |
Use one formatter and one lint configuration per language. Start with strict type checking where supported. Keep boundary parsing possible: do not ban unknown input types, runtime narrowing, or legitimate React effects globally. Use code-craft for language-specific guidance when needed.
For a new TypeScript application or the full template, set up the stack from
code-craft's proof ladder that the
project will use: Effect with its language-service diagnostics in the type
check, Effect Schema or Zod at boundaries, xstate for named workflows, gdp-ts
with its lint preset, Vitest with @effect/vitest, Vercel Emulate for provider
tests, and Postgres following database-craft. Make
the linter fail on any, unchecked as, non-null !, floating promises, and
suppressions without a reason. A prototype gets only what it uses.
For a new Rust server, set up the server stack in code-craft's
Rust reference:
tokio, axum, snafu, aerosol, and sqlx, the [workspace.lints] deny list with
disallowed_methods and disallowed_types, nextest with one tests/it test
crate and test = false on library and binary targets, and
cargo sqlx prepare --check in CI.
Define the check suite in one recipe shared by CI and local development. If hooks are requested, use the same recipe or a scoped fast subset. Do not run slow full-suite checks on every commit merely to duplicate CI.
Agent infrastructure
When agent-rule enforcement or AI review is requested, put each rule at the strongest layer that can express it faithfully. Prefer compiler and linter checks over a new agent-rule system. Do not duplicate the same gate across layers.
For an agent-specific rule that needs enforcement, use structural matching where possible and provide a CI check independent of agent edits. For an AI review gate, keep reviewer definitions reviewable and protect them through the repo's ownership rules. Required gates must not silently pass when evaluation fails.
Distribution and project files
For a CLI intended for binary distribution, prefer tag-triggered releases with checksummed archives for the supported platforms. Derive the version from the tag. Include installers only when requested or needed by the distribution plan; they must verify checksums before installing.
Keep supported platforms and package registries tied to the intended users. Do not build a platform matrix for an unpublished prototype.
For a repository intended for public distribution, include the license, contribution instructions, and a private security-reporting path. Add conduct guidelines, issue templates, dependency updates, and release workflows when the full template or their specific purpose is requested.
Jess's new-license choices are AGPL-3.0-or-later or Apache-2.0. Ask which to use when licensing a new project unless the user already chose. With AGPL, Jess's default for documentation is CC-BY-SA-4.0, recorded in NOTICE. Preserve existing licenses and third-party notices.
Verify and report
Run the generated setup and required checks. Confirm CI invokes the maintained check recipe. Report what was configured and any unverified platform or external service. Do not publish, create remote repositories, or configure paid services without authorization for those actions.
FAQ
What does the project-bootstrap skill do?
Use when the user requests repository setup, tooling infrastructure, or Jess's full project template. Skip coding, prototypes, and hardening requests that do not include repository setup.
How do I install project-bootstrap?
Run npx skills add https://github.com/jssblck/agents --skill project-bootstrap in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/project-bootstrap/ (personal) or .claude/skills/project-bootstrap/ (project).
Which AI agents can use project-bootstrap?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is project-bootstrap safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains project-bootstrap?
It is published by jssblck in jssblck/agents. It has 794 recorded installs.
More from jssblck/agents
using-sops
jssblck/agents
Use for secrets or key setup in a repo with .sops.yaml, encrypted environment files, or a pnpm secrets script.
code-craft
jssblck/agents
Apply Jess's engineering conventions to invariants, boundary typing, state, effects, proofs, error handling, and abstraction decisions.
ship-it
jssblck/agents
Use when asked to ship a completed change, commit and open a PR, or push changes and watch CI. Use babysit for monitoring an existing PR.
merge-open-prs
jssblck/agents
Use when asked to merge all open PRs or land a specified set of PRs together.
tag-release
jssblck/agents
Use when asked to tag or cut a patch, minor, or major release.
gh-stack
jssblck/agents
Use when working in a checked-out PR stack, handling dependent PRs or branch layers, or planning to split work into stacked PRs.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.