Default technology selection and engineering rules for AI-assisted project creation.
A set of opinionated guidelines that AI agents follow when scaffolding new projects. Covers stack choices, tooling defaults, code style, and CI/CD conventions.
- Predictable tooling with a single stack-appropriate task entry point
- Minimal incidental complexity
- Strong static guarantees
- Small, focused modules
- Implementations capped at
250lines and split by responsibility - Avoid unnecessary allocations, copies, and convenience abstractions
- In Rust, prefer
SmallVec,CompactString, andmemchrwhere they fit - Low allocation overhead where performance matters
- Place Rust crates under
./crates. - Place TypeScript packages under
./npm. - Place examples under
./examples. - For Rust to JavaScript or Node.js interop, use
napi-rs. - Use
snake_casefor directory names and file names. - Keep each implementation unit at
250lines or fewer. - Split files before responsibilities begin to mix.
Fetch individual guideline files via the GitHub API:
# Tech selection overview
gh api repos/ubugeeei/start/contents/docs/general.md --jq '.content' | base64 -d
# TypeScript
gh api repos/ubugeeei/start/contents/docs/typescript.md --jq '.content' | base64 -d
# Rust
gh api repos/ubugeeei/start/contents/docs/rust.md --jq '.content' | base64 -d
# Vue
gh api repos/ubugeeei/start/contents/docs/vue.md --jq '.content' | base64 -dUse nix for the local toolchain in this repository.
nix develop
vp install
vp fmtThe dev shell provides Node.js 24 and pnpm 10.
The project guidelines continue to standardize shared project tasks on Vite Task via vp and vp run.
MIT