veragem 0.1.0

data/template/.gitignore

@@ -0,0 +1,12 @@
+# Bundler's settings and gems (setup-ruby installs into vendor/), the built gems, the coverage
+/.bundle/
+/vendor/
+/pkg/
+/coverage/
+/doc/
+/tmp/
+# rbs collection install's (the lock, rbs_collection.lock.yaml, is committed)
+/.gem_rbs_collection/
+# Nix's build links, direnv's cache
+/result*
+/.direnv

data/template/.rubocop.yml

@@ -0,0 +1,27 @@
+# RuboCop's defaults, each new cop on as it ships, and its extensions for the tests, packaging (the
+# gem as distributions build it), performance and the Rakefile. The Ruby version is the gemspec's
+# required_ruby_version.
+plugins:
+  - rubocop-minitest
+  - rubocop-packaging
+  - rubocop-performance
+  - rubocop-rake
+
+inherit_mode:
+  merge:
+    - Exclude
+
+AllCops:
+  NewCops: enable
+  # `nix build`'s links: the gem installed, which the project index would take for a second copy
+  Exclude:
+    - "result*/**/*"
+  # the whole project indexed first (the rubydex gem), so the cops that can see across files do: a
+  # method defined twice in two files, a constant reassigned in another
+  UseProjectIndex: true
+
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  EnforcedStyle: double_quotes

data/template/AGENTS.md.erb

@@ -0,0 +1,75 @@
+# AGENTS.md
+
+Repository rules for `<%= name %>`. These apply to every contributor, human or AI-assisted.
+Adding a dependency or a tool, the tests' rules and the release are
+[CONTRIBUTING.md](CONTRIBUTING.md)'s.
+
+## 1. The lint and type policy is the design
+
+RuboCop runs with its defaults and every new cop as it ships (`NewCops: enable`), its Minitest,
+packaging, performance and Rake extensions on, and the project indexed first (`UseProjectIndex`, the
+rubydex gem) for the cops that look across files (`.rubocop.yml`). Steep checks `lib/` against the
+signatures in `sig/`, its strictest diagnostics on (`Steepfile`): every method of `lib/` is declared
+in `sig/`, and a warning fails as an error does. Gemfile.lock pins both, so the verdict is the same
+locally and in CI.
+
+**Never silence a new cop or diagnostic wholesale.** Either fix the site, or configure it in
+`.rubocop.yml` (or the Steepfile) with a comment saying why it is wrong for this codebase.
+
+The shell is held as the code is: shfmt formats it (`.editorconfig` holds its style) and it passes
+ShellCheck. The Nix is nixfmt's. The workflows pass actionlint and, with Dependabot's
+configuration, zizmor's security audit.
+
+## 2. Types: signatures by hand, TypeProf to start them
+
+`sig/` is written by hand and Steep holds `lib/` to it. `bundle exec rake typeprof` prints the
+signatures TypeProf infers from `lib/`: a start for a new method's, never a replacement for
+reading them -- it says `untyped` where it cannot tell. A signature is as narrow as the code
+allows: `untyped` only where the value truly is any value.
+
+## 3. Silence a cop or a diagnostic at the site, with a reason
+
+```ruby
+eval(code) # rubocop:disable Security/Eval -- code is this gem's own, never its input
+
+# the library declares no signature -- above: text after Steep's diagnostic name voids the ignore
+value = client.fetch # steep:ignore NoMethod
+```
+
+Name the cop or diagnostic. A reason that restates the rule is not a reason: say what makes the
+site safe. RuboCop reports a disable that no longer applies (`Lint/RedundantCopDisableDirective`),
+so a justification cannot outlive the code it justified.
+
+## 4. Comments: only what is essential
+
+A comment says what the code cannot: why it is so, the source it follows, the constraint it keeps.
+Make it concise and precise -- a line where a line does -- and never restate the code: that is
+noise, and it goes stale. A change that falsifies a comment rewrites it.
+
+## 5. Commits
+
+[Conventional Commits](https://www.conventionalcommits.org/) are enforced by `cog check` locally
+and in CI. The changelog is generated from the commits (`cliff.toml`), so the subject line is
+user-facing text; `chore`, `ci` and `style` commits stay out of it, and `!` or a `BREAKING CHANGE`
+footer lists a commit first:
+
+```
+feat: accept the name as a symbol too
+fix: strip a trailing newline from the name
+docs: explain the greeting's fallback
+build(deps): depend on json
+```
+
+The git hooks (`bundle exec rake hooks`) check the same before a commit and a push; never bypass
+them with `--no-verify`. `git revert` writes `Revert "..."`, which CI refuses: reword it as
+`revert: ...`.
+
+## 6. Before you claim a change is done
+
+Run `bundle exec rake checks`. It is what CI runs: RuboCop, Steep, the tests with every line,
+branch and method covered, bundler-audit, dprint, the commit messages, the shell, the workflows,
+and the flake's checks. Reporting "done" on a change that has not passed it is the one thing that
+wastes the most time here.
+
+If a check fails for reasons unrelated to your change, say so explicitly rather than working
+around it -- a broken check that everyone routes around stops protecting anything.

data/template/CODE_OF_CONDUCT.md.erb

@@ -0,0 +1,18 @@
+# Code of Conduct
+
+This repository is for technical development.
+
+- **Scope:** discussions, issues, and pull requests should focus on the
+  `<%= name %>` codebase, its architecture, and its implementation.
+- **Conduct:** be direct about code and considerate about people. Critique the
+  change, not the contributor.
+- **Moderation:** off-topic, abusive, or bad-faith content will be closed or
+  removed.
+
+<%- if email -%>
+Report conduct concerns to the maintainers at <%= email %>.
+<%- else -%>
+Report conduct concerns to the maintainers, or through GitHub's
+[report content](https://docs.github.com/en/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
+feature.
+<%- end -%>

data/template/CONTRIBUTING.md.erb

@@ -0,0 +1,183 @@
+# Contributing to `<%= name %>`
+
+Thank you for considering contributing to `<%= name %>`!
+
+A project just generated: start at [First steps](#first-steps), under Maintainers.
+
+## Prerequisites
+
+Either **Nix** -- `nix develop` gives Ruby and every tool below at the versions `flake.lock` pins
+-- or the tools installed yourself. The gems are Bundler's either way, from `Gemfile.lock`, as in
+CI (nixpkgs packages few of them, and older).
+
+- **[Ruby](https://www.ruby-lang.org) 4.0** or later, with Bundler (Ruby's own). `bin/setup`
+  installs the gems `Gemfile.lock` pins: Rake, RuboCop, its extensions and rubydex (its project
+  index), Steep, TypeProf, Minitest, SimpleCov, pbt, bundler-audit.
+- **[ShellCheck](https://www.shellcheck.net/)** and **[shfmt](https://github.com/mvdan/sh)** --
+  the shell's linter and formatter (its style is `.editorconfig`'s).
+- **[actionlint](https://github.com/rhysd/actionlint)** -- lints the workflows (and, through
+  ShellCheck, their `run:` scripts).
+- **[zizmor](https://docs.zizmor.sh/)** -- audits the workflows' security, and Dependabot's
+  configuration.
+- **[dprint](https://dprint.dev/)** -- formats the Markdown and TOML.
+- **[cocogitto](https://docs.cog.tools/)** (`cog`) -- enforces Conventional Commits.
+- **[git-cliff](https://git-cliff.org/)** -- writes the changelog at a release.
+- **[Nix](https://nixos.org)** for the last of `rake checks`, the flake's checks (`rake nix`):
+  without it, `rake checks` stops there, every other check passed.
+
+## Setup
+
+1. Fork this repository and create your branch from `main`.
+2. Clone your fork, and install the gems:
+
+```sh
+git clone https://github.com/<you>/<%= name %> && cd <%= name %>
+bin/setup
+```
+
+3. Optionally, `bundle exec rake hooks`: `.githooks/` then runs RuboCop, the shell, the workflows
+   and dprint before each commit, checks its message as a Conventional Commit, and every pushed
+   commit's message before a push: what CI would refuse, minutes earlier.
+   `git config --unset core.hooksPath` turns them off.
+
+## Guidelines
+
+Before you start, read [AGENTS.md](AGENTS.md): the lint and type policy, and what to do when a
+cop or a diagnostic fires. It applies to human and AI-assisted contributions alike.
+
+## Testing
+
+- **Pure functions:** isolate logic from side effects wherever possible and cover it with unit
+  tests (Minitest, `test/test_*.rb`).
+- **Properties:** where a rule holds for every input, state it as a property (pbt,
+  `Pbt.assert { Pbt.property(...) { ... } }`): it is checked on many generated inputs, and a
+  failure is shrunk to its smallest counterexample, with the seed that reproduces it.
+- **Regressions:** if you are fixing a bug, include a test that reproduces the previous failure.
+- **Coverage:** every line, branch and method of `lib/` (SimpleCov's `strict` profile,
+  `test/test_helper.rb`). Code a test cannot reach is questioned before it is excluded.
+
+## Development Workflow
+
+1. Every commit must be a [Conventional Commit](https://www.conventionalcommits.org/) (`cog check`
+   enforces it), and its subject is its changelog entry (git-cliff writes the changelog at each
+   release): write it for the gem's users.
+2. Run the checks. The Rakefile runs the workflows' commands:
+
+```sh
+bundle exec rake          # RuboCop, Steep, the tests: ruby-ci.yml
+bundle exec rake checks   # and bundler-audit, dprint, cog, the shell, the workflows, the flake's checks
+bundle exec rake format   # RuboCop's corrections, dprint and nixfmt, in place
+bundle exec rake typeprof # the signatures TypeProf infers from lib/, to start sig/ from
+nix build                 # the gem, built and installed by Nix (flake.nix)
+```
+
+`bundle exec rake -T` lists every task.
+
+A new dependency of the gem goes in the gemspec (`spec.add_dependency`), and, for the Nix package,
+its nixpkgs package in flake.nix's `dependencies` (`pkgs.rubyPackages_4_0.<gem>`): the flake's
+`library` check, which loads the gem with its dependencies, fails without it, or with a version
+the gemspec's requirement excludes -- one nixpkgs lacks is built there by `pkgs.buildRubyGem`. A
+new tool goes in the Gemfile, which the built gem never holds: its dependencies are the gemspec's
+alone. `bundle install` then updates the lock. Steep reads a library's signatures when the
+Steepfile names it (`library "json"`): the standard library's, and a gem's own (its `sig/`). A gem
+that ships none may have them in gem_rbs_collection, read through an RBS collection
+(`rbs collection init`, then `rbs collection install`, as rbs's `docs/collection.md` describes).
+
+## Creating a Pull Request
+
+1. Make sure `bundle exec rake checks` passes.
+2. Open a pull request against `main`, titled as a conventional commit: a squash merge of two or
+   more commits makes the title its commit, and so a changelog entry (CI checks it). Describe the
+   problem it solves, and link its issue (`Fixes #123`), if any.
+3. Wait for a maintainer's review.
+
+## Maintainers
+
+### First steps
+
+`bundle veragem` made the git repository and added its files. The lock is yours to write, from
+this machine, and then the first commit -- which `cog check` (run by `rake checks` and by CI)
+requires to follow [Conventional Commits](https://www.conventionalcommits.org/):
+
+```sh
+bin/setup
+git add .
+git commit -m "chore: initial commit from veragem"
+```
+
+With [Nix](https://nixos.org), `nix develop` first: its Ruby and tools are the ones `flake.lock`
+pins. A flake sees git's files only, so they are added already.
+
+Then, in whichever order suits you:
+
+- Push to `https://github.com/<%= github %>/<%= name %>`.
+- Enable the repository settings the auto-merge workflow needs, listed at the top of
+  `.github/workflows/dependabot-automerge.yml`: without required status checks, it merges bumps
+  that CI never gated.
+- Enable private vulnerability reporting (Settings → Advanced Security; a public repository's
+  alone): it is off by default, and [SECURITY.md](SECURITY.md) and the issue form point to it.
+- Enable the dependency graph (Settings → Advanced Security), if it is off: the dependency review
+  (`dependency-review.yml`) fails without it. A private repository's needs GitHub Code Security
+  too, an organization's; without it, delete the workflow.
+- Add a pending trusted publisher on [RubyGems](https://rubygems.org/profile/oidc/pending_trusted_publishers)
+  for the gem `<%= name %>`: this repository, the workflow `release.yml`, the environment
+  `release`. A release tag then publishes without a stored key, its first version too, and its
+  GitHub release follows RubyGems': without the publisher, neither is made.
+- If you limit the `release` environment's deployments (Settings → Environments), admit the
+  release tags, a rule of ref type Tag, `v*`: the RubyGems job runs on the tag, and an environment
+  that refuses it publishes nothing.
+<%- if exe -%>
+- After the first release, make the image public: GHCR publishes a new package as private (its
+  page, Package settings → Change visibility).
+- To publish the image to Docker Hub too: create its repository there, then set the repository
+  variable `DOCKERHUB_USERNAME` and the secret `DOCKERHUB_TOKEN` (an access token that writes) --
+  and the variable `DOCKERHUB_REPOSITORY` (`namespace/name`) unless it is `<username>/<%= name %>`.
+  A Docker Hub failure in the build (its login, its name, a push) holds GHCR's tag back too.
+<%- end -%>
+- Run `bundle exec rake checks` once to confirm your tools are complete: a step that stops on a
+  missing command names it ([Prerequisites](#prerequisites) lists them; `nix develop` has them
+  all).
+- `bundle exec rake hooks`, if you want git to run the quick checks before each commit and push
+  ([Setup](#setup)).
+- Make the project yours: the code, the tests, the signatures, the README and the gemspec's
+  summary.
+
+### Releasing
+
+From a clean `main`, CI green on it:
+
+```sh
+bundle exec rake changelog          # the changes the next release will list
+bundle exec rake "bump[minor]"      # or major, or patch
+bundle exec rake release
+```
+
+`rake bump` refuses a release with nothing in it -- the commits since the last tag must hold a
+change a user meets (`feat`, `fix`, `perf`, `build`...): `chore`, `ci` and `style` alone make
+none. It sets the version in `lib/<%= path %>/version.rb` (the first release keeps the version
+declared, whatever the level), updates the lock, writes the changelog (git-cliff) and commits.
+`rake release`, Bundler's own, builds the gem, tags `v<version>` and pushes the branch and the
+tag; it pushes no gem. The tag runs `release.yml`: the checks and the build, the push to RubyGems
+by Trusted Publishing, then the GitHub release of the same gem, its notes the changelog's new
+section.
+<%- if exe -%>
+Beside `release.yml`, waiting for no RubyGems push, `image.yml` publishes the command's OCI image
+to GHCR (`nix build .#image` builds it here).
+<%- end -%>
+
+`rake release` pushes to `main` directly: with "Require a pull request before merging" on, the
+maintainer cutting it needs the rule's bypass. A refused push leaves the release commit and
+removes the tag (Bundler's doing): run `rake release` again once allowed.
+
+## Updating the tools
+
+Dependabot moves the gems (`Gemfile.lock`) and the actions weekly, and the flake's inputs
+monthly; `dependabot-automerge.yml` merges the minor and patch bumps once the checks pass.
+dprint's plugins, pinned in `dprint.json`, move by hand: `dprint config update`. A new RuboCop
+brings new cops (`NewCops: enable`), a new Steep new diagnostics: read them before silencing any.
+A bump the new cops fail gets RuboCop's safe corrections as a commit on its branch
+(`rubocop-autocorrect.yml`). GitHub holds the workflows of a commit a workflow's token pushes
+until you approve them (the pull request's "Approve workflows to run"); corrected, the bump then
+merges as any bump. What safe corrections leave is yours to fix, in a pull request of yours too: a
+failed run's summary
+holds the corrections as a patch, to `git apply`.

data/template/Gemfile

@@ -0,0 +1,24 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# The gem's own dependencies are its gemspec's.
+gemspec
+
+# The development tools, unconstrained: Gemfile.lock pins them and Dependabot moves the lock. No
+# group needed: the built gem holds neither this file nor the lock, its dependencies the
+# gemspec's alone.
+gem "bundler-audit"
+gem "irb"
+gem "minitest"
+gem "pbt"
+gem "rake"
+gem "rubocop"
+gem "rubocop-minitest"
+gem "rubocop-packaging"
+gem "rubocop-performance"
+gem "rubocop-rake"
+gem "rubydex"
+gem "simplecov"
+gem "steep"
+gem "typeprof"

data/template/LICENSE-APACHE.erb

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright <%= year %> <%= author %>
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/template/LICENSE-MIT.erb

@@ -0,0 +1,7 @@
+Copyright <%= year %> <%= author %>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/template/README.md.erb

@@ -0,0 +1,82 @@
+# <%= name %>
+
+<%= summary %>
+
+## Requirements
+
+Ruby 4.0 or later.
+
+## Install
+
+```sh
+<%- if exe -%>
+gem install <%= name %>
+<%- else -%>
+bundle add <%= name %>
+<%- end -%>
+```
+<%- if exe -%>
+
+With Nix, `nix run github:<%= github %>/<%= name %>`. As an OCI image, for Linux on amd64 and arm64:
+
+```sh
+docker run --rm ghcr.io/<%= github.downcase %>/<%= name %> --version
+```
+<%- end -%>
+
+## Usage
+<%- if exe -%>
+
+```sh
+<%= name %> Ada # => Hello, Ada!
+```
+
+or, as a library:
+<%- end -%>
+
+```ruby
+require "<%= path %>"
+
+<%= constant %>.greeting("Ada") # => "Hello, Ada!"
+```
+
+## Development
+
+`bin/setup` installs the gems at `Gemfile.lock`'s versions (its first run writes the lock); then
+`bundle exec rake` runs the Ruby checks (RuboCop, Steep and the tests with their coverage gate)
+and `bundle exec rake checks` everything CI runs:
+
+```sh
+bin/setup
+bundle exec rake checks
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the tools those checks need, how a release is cut and,
+in a project just generated, its [first steps](CONTRIBUTING.md#first-steps); and
+[AGENTS.md](AGENTS.md) for the lint and type policy.
+
+## License
+<%- if license == "dual" -%>
+
+Licensed under either of
+
+- Apache License, Version 2.0 ([LICENSE-APACHE](LICENSE-APACHE) or
+  <http://www.apache.org/licenses/LICENSE-2.0>)
+- MIT license ([LICENSE-MIT](LICENSE-MIT) or <http://opensource.org/licenses/MIT>)
+
+at your option.
+
+### Contribution
+
+Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in
+the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without
+any additional terms or conditions.
+<%- elsif license == "mit" -%>
+
+Licensed under the MIT license ([LICENSE-MIT](LICENSE-MIT) or
+<http://opensource.org/licenses/MIT>).
+<%- else -%>
+
+Licensed under the Apache License, Version 2.0 ([LICENSE-APACHE](LICENSE-APACHE) or
+<http://www.apache.org/licenses/LICENSE-2.0>).
+<%- end -%>