Projectmaxxing

Projectmaxxing is the coordination layer for the Nekoautomata Miki open-source portfolio. It connects dozens of focused tools with their public website and shared operational tooling, making the collection browsable and reproducible from one place. Browse the projects at https://miki.meowc.at/projects/ or clone this repository to inspect the whole workspace.

Warning

GitHub mirror limitation: GitHub's web interface cannot open submodules hosted on Forgejo. The site, backup-system, and projects under development/ may lead to broken /blob/ pages here. Cloning with submodules still works. Use the direct Forgejo links below and the development project list when browsing on GitHub.

Most directories under development/ are independent repositories recorded as Git submodules. Each project keeps its own releases, documentation, tests, and issue history on the canonical Forgejo account at https://git.meowc.at/miki.

What is here

• development/ — source checkouts for active tools, experiments, forks, and contributions, with project-specific documentation in each directory.
• site — the source served at https://miki.meowc.at, including the complete project directory and browser-hosted tools.
• backup-system — reusable Restic-over-SFTP backup and restore tooling. Machine-specific destinations and credentials remain local and untracked.
• .agents/ — public plugin marketplace metadata for portfolio coding-agent tools.
• CLAUDE.md — public guidance for coding agents working across the workspace.

Private campaign ledgers, credentials, machine state, account recovery data, and internal status records are intentionally excluded from the public repository and its public history.

Clone the workspace

git clone --recurse-submodules ssh://git@ssh.git.meowc.at/miki/projectmaxxing.git
cd projectmaxxing

To initialize submodules after a normal clone:

git submodule update --init --recursive

Some large upstream-contribution worktrees are intentionally local-only rather than duplicated as portfolio repositories. Their published contribution branches or canonical upstream projects are linked from the portfolio site when applicable.

Portfolio principles

Projects in this portfolio are deliberately narrow and inspectable:

• local processing where practical;
• explicit trust boundaries and limitations;
• deterministic output suitable for review and automation;
• no portfolio-owned telemetry, analytics, installation identifiers, or usage collectors;
• canonical source and releases on the self-hosted Forgejo instance.

Public website

The website is maintained in the site repository and served through Caddy at https://miki.meowc.at. The full project directory is available at https://miki.meowc.at/projects/.

Security

Do not commit credentials, authentication state, private keys, backup repository locations, personal data, or private operating ledgers. Machine-specific configuration belongs in ignored local files. Report vulnerabilities through the relevant project's security instructions or its Forgejo issue tracker when public disclosure is appropriate.

License

All rights reserved. Ask for permission before using this project. Individual linked projects retain their own licenses.