Tag: Tools

26 pages

• 02.02Project templates and starter reposEvery new tool starts from a known-good skeleton with CI, lint, auth, and deploy already wired.
• 01.01Project intake and scopingTurn "can we build a thing that…" into a scoped piece of work with a clear yes/no.
• 02.01Approved stack and when to deviateFewer technologies, deeper knowledge, easier handoffs.
• 01.02Definition of done"Done" means the same thing to everyone.
• 01.03Communication standardsThe right conversation in the right place, findable later.
• 01.04Documentation standardsDocumentation exists at three levels, and each has a home.
• 01.05Naming conventionsNames that sort, search, and read the same everywhere.
• 01.06Decision records (ADRs)Remember why we chose something so we don't relitigate it every six months.
• 02.03Folder and code structure conventionsOpen any repo and know where things are.
• 02.04Environment variables and config managementConfig is explicit, per environment, and never committed.
• 02.05Third-party services we useKnow what we depend on, who pays, and who holds the keys.
• 02.06Architecture decision logIndex of accepted ADRs (see 01.06 for the process).
• 03.01Account setup and multi-account handlingCommits land under the right identity, and personal/work accounts don't collide on Windows.
• 03.02Repo creation standardsEvery repo is discoverable, protected, and starts from a template.
• 03.03Branching strategyShort-lived branches, always-deployable main.
• 03.04Commit message conventionsHistory that explains itself and can generate changelogs.
• 03.05Pull request process and review checklistEvery change gets a second set of eyes without becoming a bottleneck.
• 03.06Releases, tags, and versioningKnow exactly what's running where.
• 03.07Issues, labels, and project boardsWork is visible and prioritized in one place.
• 04.01TypeScript / JavaScript styleCode that any teammate (or Claude Code) can read and extend without asking.
• 04.02Python styleConsistent Python across data scripts and Rhino tools, which run in different interpreters.
• 04.03C# style (Revit / Rhino plugins)Plugins that survive Revit and Rhino version upgrades.
• 04.04Linting, formatting, and pre-commit hooksMachines enforce style so reviewers don't have to.
• 04.05Testing standardsEnough tests to change code with confidence, not so many that they slow us down.
• 04.06Error handling and loggingFailures are visible, actionable, and never silent.
• 04.07Accessibility and responsive baselinesTools used on a laptop in a meeting and on a phone in the field.