@sha3/code-standards 0.1.2 → 0.1.3

package/README.md

@@ -112,6 +112,8 @@ After `init`, your new repo contains:
 
 That means the next step is **not** configuring tools. The next step is telling your assistant to obey `AGENTS.md` before coding.
 
+Generated project code is TypeScript-only: implementation and tests live in `.ts` files.
+
 ## TypeScript Example Files
 
 `init` now stores code examples in `.ts` files instead of embedding them inside `AGENTS.md`.
@@ -278,6 +280,7 @@ Commands:
 ### `init` options
 
 `init` always uses the current working directory as target.
+An existing `.git/` directory is allowed without `--force`.
 
 - `--template <node-lib|node-service>`
 - `--yes`

package/bin/code-standards.mjs

@@ -394,8 +394,9 @@ async function ensureTargetReady(targetPath, force) {
   }
 
   const entries = await readdir(targetPath);
+  const nonGitEntries = entries.filter((entry) => entry !== ".git");
 
-  if (entries.length > 0 && !force) {
+  if (nonGitEntries.length > 0 && !force) {
     throw new Error(
       `Target directory is not empty: ${targetPath}. Use --force to continue and overwrite files.`
     );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sha3/code-standards",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "AI-first code standards, tooling exports, and project initializer",
   "type": "module",
   "bin": {

package/resources/ai/templates/rules/functions.md

@@ -4,6 +4,8 @@
 - Functions MUST implement one responsibility.
 - Long functions MUST be split into private helper methods.
 - Types MUST be preferred over interfaces for local modeling unless a public contract requires an interface.
+- New implementation and test files MUST be `.ts`.
+- JavaScript source files (`.js`, `.mjs`, `.cjs`) are not allowed in `src/` or `test/`.
 
 Good example:
 

package/resources/ai/templates/rules/testing.md

@@ -2,6 +2,7 @@
 
 - Any behavior change MUST include or update tests.
 - Tests MUST validate behavior, not implementation details.
+- Test files MUST be TypeScript (`*.test.ts`).
 - Comments MUST be explicit and extensive when logic is non-trivial.
 - Async workflows MUST use `async/await` style only.
 

package/standards/architecture.md

@@ -15,7 +15,7 @@ Both templates SHOULD keep this baseline structure:
 
 - `src/` for implementation.
 - `test/` for automated tests.
-- `eslint.config.mjs`, `prettier.config.cjs`, and `tsconfig.json` at root.
+- Root tooling config files (`eslint`, `prettier`, `tsconfig`) at project root.
 
 ## Boundary Rules
 

package/standards/style.md

@@ -12,6 +12,8 @@ All code MUST follow the canonical rules in `standards/manifest.json`.
 ## TypeScript
 
 - Use strict TypeScript mode.
+- Project implementation and tests MUST be TypeScript-only (`.ts`).
+- JavaScript source files (`.js`, `.mjs`, `.cjs`) are not allowed in `src/` or `test/`.
 - Avoid `any` unless there is no viable alternative.
 - Prefer explicit return types for exported functions.
 - Use type-only imports when possible.

package/standards/testing.md

@@ -5,7 +5,7 @@ Projects MUST use the Node test runner.
 ## Location
 
 - Store tests under `test/`.
-- Use `*.test.ts` or `*.test.js` naming.
+- Use `*.test.ts` naming only.
 
 ## Commands