dk-harness 0.1.0

package/LICENSE

@@ -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 [yyyy] [name of copyright owner]
+
+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.

package/README.md

@@ -0,0 +1,267 @@
+# dk-harness
+
+Harness for agentic development.
+
+This harness was created following OpenAI's Harness Engineering article:
+https://openai.com/ko-KR/index/harness-engineering/
+
+The goal is not only to test correctness, but to create an environment where an AI agent is pushed toward good behavior by default:
+
+- fast feedback
+- deterministic tooling
+- hard architectural boundaries
+- tests for real user behavior
+- checks that catch dependency, security, and maintenance anti-patterns early
+
+This repo should optimize for three stacks only:
+
+- `Next.js`
+- `Python`
+- `Rust`
+
+## Principles
+
+- Prefer tools that are fast enough to run locally on every change.
+- Enforce boundaries automatically instead of relying on code review.
+- Test user-visible behavior, not just implementation details.
+- Keep CI layered: fast checks first, slower UX checks after.
+- Make the same commands work locally and in CI.
+
+## Shared Foundation
+
+These are worth using no matter which stack a project uses.
+
+| Role | Recommended tools | Why |
+| --- | --- | --- |
+| Toolchain pinning | `mise` | Pin Node, Python, and Rust versions so agents and humans run the same toolchain. |
+| Task runner | `just` | Gives the agent a small, predictable command surface such as `just lint` and `just test`. |
+| Git hooks | `lefthook` or `pre-commit` | Run fast checks before bad changes spread. |
+| CI | `GitHub Actions` | Standardize the same harness in automation. |
+| Dependency updates | `Renovate` | Keeps dependencies current without relying on memory. |
+| Secrets scanning | `gitleaks` | Prevents obvious security mistakes from landing. |
+| Repo-wide vuln scanning | `osv-scanner` | One simple cross-ecosystem supply-chain check. |
+
+## By Role
+
+These are the categories the harness should cover across all stacks.
+
+| Role | What to enforce |
+| --- | --- |
+| Formatter / linter | Style, common mistakes, import hygiene, obvious bad patterns |
+| Type / static analysis | Type soundness, invalid assumptions, weak interfaces |
+| Dependency detection | Unused deps, missing deps, forbidden imports, circular dependencies |
+| Architecture boundaries | Rules like `ui -> app -> domain -> infra`, never the reverse |
+| Unit / integration tests | Behavioral correctness at module and service level |
+| End-to-end tests | Real user flows, cross-boundary regressions |
+| Accessibility / UX checks | Keyboard nav, labels, contrast, layout breakage, performance regressions |
+| Security / supply chain | Vulnerabilities, licenses, secrets, dependency policy |
+| Reproducibility | Same commands, same versions, same fixtures locally and in CI |
+
+## Next.js
+
+`Next.js` is where most user-experience anti-patterns show up, so this stack needs the strongest UX harness.
+
+| Role | Recommended tools | Notes |
+| --- | --- | --- |
+| Formatter / linter | `biome` | Good fast default for formatting and linting. |
+| Type checking | `tsc --noEmit` | Must run in CI even if the app builds. |
+| Dependency boundaries | `dependency-cruiser` | Enforce layer rules and catch circular imports. |
+| Unused files / exports / deps | `knip` | Very useful for agent-generated dead code. |
+| Unit / component tests | `vitest` + `@testing-library/react` | Fast feedback for UI logic and state transitions. |
+| API / network mocking | `msw` | Keeps tests deterministic and avoids flaky network coupling. |
+| Browser E2E | `playwright` | Test real flows, routing, auth, forms, and edge states. |
+| Accessibility | `@axe-core/playwright` | Catch common a11y regressions inside E2E tests. |
+| Visual regression | `playwright` screenshot assertions or `Chromatic` | Useful for catching broken layouts and style drift. |
+| Performance / UX budgets | `Lighthouse CI` | Catch slow pages, layout shift, and basic UX regressions. |
+| Component review | `Storybook` | Helpful when you want isolated state coverage and reviewable UI fixtures. |
+
+Recommended baseline for `Next.js`:
+
+- `biome`
+- `tsc --noEmit`
+- `dependency-cruiser`
+- `knip`
+- `vitest`
+- `playwright`
+- `@axe-core/playwright`
+- `Lighthouse CI`
+
+## Python
+
+Use Python for automation, agents, orchestration, APIs, and evaluation tools. The harness should favor speed and strictness.
+
+| Role | Recommended tools | Notes |
+| --- | --- | --- |
+| Package / env management | `uv` | Fast and reproducible Python environment management. |
+| Formatter / linter | `ruff` | Replaces several slower tools with one fast tool. |
+| Type checking | `basedpyright` or `pyright` | Strong static analysis for agent-written Python. |
+| Dependency detection | `deptry` | Finds undeclared and unused dependencies. |
+| Architecture boundaries | `import-linter` | Enforce import contracts between layers or packages. |
+| Unit / integration tests | `pytest` | The default testing backbone. |
+| Parallel test execution | `pytest-xdist` | Speeds up larger test suites. |
+| Property-based tests | `hypothesis` | Very good for catching edge cases agents often miss. |
+| Security scanning | `pip-audit` | Checks installed Python dependencies for known vulns. |
+| Security linting | `bandit` | Optional, but helpful for scripts that touch files, shells, or secrets. |
+
+Recommended baseline for `Python`:
+
+- `uv`
+- `ruff`
+- `basedpyright`
+- `deptry`
+- `import-linter`
+- `pytest`
+- `hypothesis`
+- `pip-audit`
+
+## Rust
+
+Use Rust when correctness, performance, and strong interfaces matter. The harness should lean into strict compiler- and lint-driven workflows.
+
+| Role | Recommended tools | Notes |
+| --- | --- | --- |
+| Formatter | `rustfmt` | Keep formatting non-negotiable. |
+| Linting | `clippy` | Strong default lint layer for correctness and idioms. |
+| Test runner | `cargo nextest` | Faster and better-scaled test execution than plain `cargo test`. |
+| Built-in tests | `cargo test` | Still the standard compatibility baseline. |
+| Unused dependency detection | `cargo-udeps` | Excellent at finding leftover crate deps. |
+| Dependency / license policy | `cargo-deny` | Good for security, sources, and license enforcement. |
+| Vulnerability scanning | `cargo-audit` | Checks crates against known advisories. |
+| Property-based tests | `proptest` | Useful for parser, protocol, and state-machine logic. |
+| Fuzzing | `cargo-fuzz` | Worth using for parsers, protocol handlers, and unsafe boundaries. |
+| Benchmarks | `criterion` | Helpful when performance regressions matter. |
+
+Recommended baseline for `Rust`:
+
+- `rustfmt`
+- `clippy`
+- `cargo nextest`
+- `cargo-udeps`
+- `cargo-deny`
+- `cargo-audit`
+- `proptest`
+
+## Suggested CI Lanes
+
+Do not run everything in one giant job. Split the harness by speed and purpose.
+
+1. `fast`: formatting, linting, type checks, dependency checks, architecture checks
+2. `test`: unit and integration tests
+3. `ux`: Playwright, accessibility, visual regression, Lighthouse
+4. `supply-chain`: vulnerability, license, and secret scanning
+
+## Minimal Opinionated Starter Set
+
+If I wanted a strong default harness for agentic development without making it too heavy, I would start with:
+
+- Shared: `mise`, `just`, `GitHub Actions`, `Renovate`, `gitleaks`, `osv-scanner`
+- `Next.js`: `biome`, `tsc --noEmit`, `dependency-cruiser`, `knip`, `vitest`, `playwright`, `@axe-core/playwright`, `Lighthouse CI`
+- `Python`: `uv`, `ruff`, `basedpyright`, `deptry`, `import-linter`, `pytest`, `hypothesis`, `pip-audit`
+- `Rust`: `rustfmt`, `clippy`, `cargo nextest`, `cargo-udeps`, `cargo-deny`, `cargo-audit`, `proptest`
+
+## What This Harness Should Catch
+
+The important thing is not just having tools, but making them block the kinds of failures agents are prone to produce:
+
+- dead code and unused dependencies
+- circular imports and broken architecture boundaries
+- passing builds with broken types
+- brittle tests that mock too much and verify too little
+- inaccessible UI and broken keyboard flows
+- layout regressions that still look fine in code review
+- slow pages and poor Core Web Vitals
+- dependency vulnerabilities and leaked secrets
+- environment drift between local runs and CI
+
+## Templates
+
+This repo can also act as a local template catalog.
+
+- `templates/next-monorepo`
+- `templates/next-axum-monorepo`
+- `templates/next-fastapi-monorepo`
+
+The source of truth for template discovery lives in [templates/registry.json](/home/kimdongkudavid/develop/personal/dk-harness/templates/registry.json).
+
+## CLI
+
+Use [bin/dk-harness](/home/kimdongkudavid/develop/personal/dk-harness/bin/dk-harness) to scaffold from the local catalog:
+
+```bash
+./bin/dk-harness list
+./bin/dk-harness next-monorepo my-app
+./bin/dk-harness new next-axum-monorepo my-service --init-git
+```
+
+The CLI copies from the local `templates/` directory, so edits made here immediately affect future scaffolds from this repo.
+
+You can also expose the same CLI through npm because the repo now defines a package binary in [package.json](/home/kimdongkudavid/develop/personal/dk-harness/package.json).
+
+Local repo usage with npm:
+
+```bash
+npm exec --package . -- dk-harness list
+npm exec --package . -- dk-harness next-monorepo my-app
+```
+
+If you publish the package to npm, consumers can run it without cloning the repo:
+
+```bash
+npx dk-harness@latest list
+npx dk-harness@latest next-monorepo my-app
+```
+
+The current CLI is a Python entrypoint, so machines using the npm binary still need `python3` available.
+
+## npm Publishing
+
+The package should publish as `dk-harness`.
+
+- It keeps the npm package name aligned with the installed binary name.
+- It matches the intended `npm exec` and `npx` workflows from issue `#3`.
+- We can add a separate `create-dk-harness` package later if we want an opinionated `npm create` onboarding flow.
+
+Release prerequisites:
+
+- `python3` must be on `PATH` because the published binary is a Python script.
+- Node.js and npm must be available to run `npm exec`, `npx`, `npm pack`, and `npm publish`.
+
+Release gate:
+
+```bash
+npm run release:check
+```
+
+That command verifies all of the following against the packed tarball, not the working tree:
+
+- `bin/dk-harness`, `templates/`, `README.md`, and `LICENSE` are included
+- the packaged CLI can run `dk-harness list`
+- scaffolding from the packaged CLI copies `.github/workflows/ci.yml`
+
+Suggested publish flow:
+
+```bash
+npm version <patch|minor|major>
+npm run release:check
+npm publish
+npm exec --yes --package dk-harness -- dk-harness list
+npx dk-harness@latest list
+```
+
+## Skills In Templates
+
+Skill-related project files follow the template if they are committed into the template directory.
+
+- Keep project-level files such as `skills-lock.json` if you want every generated project to inherit them.
+- Leave out machine-local folders such as `.agents/`, `.claude/`, `node_modules/`, and build output.
+
+## Standalone Template Repos
+
+If you also want each starter to live as its own GitHub repo, export from this repo and push from there:
+
+```bash
+./bin/dk-harness export next-monorepo ../dk-harness-next-monorepo --force
+./bin/dk-harness export next-axum-monorepo ../dk-harness-next-axum-monorepo --force
+```
+
+That keeps `dk-harness` as the source of truth locally while giving you separate repos to publish as template repositories on GitHub.

package/bin/dk-harness

@@ -0,0 +1,206 @@
+#!/usr/bin/env python3
+
+from __future__ import annotations
+
+import argparse
+import json
+import shutil
+import subprocess
+import sys
+from pathlib import Path
+
+
+IGNORE_NAMES = {
+    ".DS_Store",
+    ".agents",
+    ".claude",
+    ".git",
+    ".next",
+    ".venv",
+    ".turbo",
+    "__pycache__",
+    "build",
+    "dist",
+    "node_modules",
+    "target",
+}
+
+REPO_ROOT = Path(__file__).resolve().parent.parent
+REGISTRY_PATH = REPO_ROOT / "templates" / "registry.json"
+
+
+def load_registry() -> dict[str, dict[str, str]]:
+    data = json.loads(REGISTRY_PATH.read_text())
+    return {entry["name"]: entry for entry in data["templates"]}
+
+
+def ignore_filter(_: str, names: list[str]) -> set[str]:
+    return {name for name in names if name in IGNORE_NAMES}
+
+
+def ensure_destination(path: Path, force: bool) -> None:
+    if not path.exists():
+        path.parent.mkdir(parents=True, exist_ok=True)
+        return
+
+    if not path.is_dir():
+        raise SystemExit(f"Destination exists and is not a directory: {path}")
+
+    if any(path.iterdir()):
+        if not force:
+            raise SystemExit(
+                f"Destination is not empty: {path}\n"
+                "Re-run with --force to replace it."
+            )
+        shutil.rmtree(path)
+        path.parent.mkdir(parents=True, exist_ok=True)
+
+
+def copy_template(template: dict[str, str], destination: Path, force: bool) -> None:
+    source = REPO_ROOT / template["path"]
+    if not source.exists():
+        raise SystemExit(f"Template path does not exist: {source}")
+
+    ensure_destination(destination, force)
+    shutil.copytree(source, destination, ignore=ignore_filter, dirs_exist_ok=True)
+
+
+def init_git_repo(destination: Path) -> None:
+    subprocess.run(
+        ["git", "init", "-b", "main"],
+        check=True,
+        cwd=destination,
+        stdout=subprocess.DEVNULL,
+        stderr=subprocess.DEVNULL,
+    )
+
+
+def print_template_list(registry: dict[str, dict[str, str]]) -> None:
+    print("Available templates:")
+    for name in sorted(registry):
+        entry = registry[name]
+        print(f"- {name}: {entry['description']}")
+        print(f"  local: {entry['path']}")
+        print(f"  repo:  {entry['repo']}")
+
+
+def resolve_template(registry: dict[str, dict[str, str]], template_name: str) -> dict[str, str]:
+    try:
+        return registry[template_name]
+    except KeyError as exc:
+        known = ", ".join(sorted(registry))
+        raise SystemExit(
+            f"Unknown template: {template_name}\nKnown templates: {known}"
+        ) from exc
+
+
+def build_parser() -> argparse.ArgumentParser:
+    parser = argparse.ArgumentParser(
+        prog="dk-harness",
+        description="Scaffold projects from the local harness template registry.",
+    )
+    subparsers = parser.add_subparsers(dest="command")
+
+    subparsers.add_parser("list", help="List available templates.")
+
+    new_parser = subparsers.add_parser("new", help="Create a new project from a template.")
+    new_parser.add_argument("template")
+    new_parser.add_argument("destination", nargs="?")
+    new_parser.add_argument("--force", action="store_true")
+    new_parser.add_argument("--init-git", action="store_true")
+
+    export_parser = subparsers.add_parser(
+        "export",
+        help="Copy a template to another directory, useful for syncing standalone template repos.",
+    )
+    export_parser.add_argument("template")
+    export_parser.add_argument("destination")
+    export_parser.add_argument("--force", action="store_true")
+
+    return parser
+
+
+def run_new(
+    registry: dict[str, dict[str, str]],
+    template_name: str,
+    destination: str | None,
+    *,
+    force: bool,
+    init_git: bool,
+) -> int:
+    template = resolve_template(registry, template_name)
+    target = Path(destination or template_name).resolve()
+    copy_template(template, target, force=force)
+
+    if init_git:
+        init_git_repo(target)
+
+    print(f"Created {target} from template '{template_name}'.")
+    if init_git:
+        print("Initialized a new git repository.")
+    return 0
+
+
+def run_export(
+    registry: dict[str, dict[str, str]],
+    template_name: str,
+    destination: str,
+    *,
+    force: bool,
+) -> int:
+    template = resolve_template(registry, template_name)
+    target = Path(destination).resolve()
+    copy_template(template, target, force=force)
+    print(f"Exported '{template_name}' to {target}.")
+    print(f"Configured standalone repo: {template['repo']}")
+    return 0
+
+
+def main(argv: list[str]) -> int:
+    registry = load_registry()
+    parser = build_parser()
+
+    if len(argv) > 1 and argv[1] not in {"list", "new", "export", "-h", "--help"}:
+        shorthand_parser = argparse.ArgumentParser(add_help=False)
+        shorthand_parser.add_argument("template")
+        shorthand_parser.add_argument("destination", nargs="?")
+        shorthand_parser.add_argument("--force", action="store_true")
+        shorthand_parser.add_argument("--init-git", action="store_true")
+        shorthand_args = shorthand_parser.parse_args(argv[1:])
+        return run_new(
+            registry,
+            shorthand_args.template,
+            shorthand_args.destination,
+            force=shorthand_args.force,
+            init_git=shorthand_args.init_git,
+        )
+
+    args = parser.parse_args(argv[1:])
+
+    if args.command == "list":
+        print_template_list(registry)
+        return 0
+
+    if args.command == "new":
+        return run_new(
+            registry,
+            args.template,
+            args.destination,
+            force=args.force,
+            init_git=args.init_git,
+        )
+
+    if args.command == "export":
+        return run_export(
+            registry,
+            args.template,
+            args.destination,
+            force=args.force,
+        )
+
+    parser.print_help()
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv))