@titan-design/style-profile 0.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Henry Jewkes
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,67 @@
+# @titan-design/style-profile
+
+Declare one code-style profile and export it as enforcement artifacts: an ESLint config, a
+ruff config, an EditorConfig, Claude rules, Claude hooks, a Claude skill, and a markdown
+style guide. Written standards become linters.
+
+Tier 2 of the titan-platform DAG (TP-131). No titan dependencies. `zod` v4 is a peer;
+`handlebars` is a regular dependency and renders the skill templates shipped in
+`templates/`.
+
+```sh
+npm install @titan-design/style-profile zod
+```
+
+## Profile
+
+A profile is a JSON document validated by `ProfileSchema`. Six categories (`naming`,
+`structure`, `documentation`, `errorHandling`, `formatting`, `patterns`) each map a rule
+name to a `StyleRule`:
+
+```ts
+{ convention: "camelCase", confidence: 0.93, stability: "high", fixability: "safe",
+  description: "...", examples: [{ good: "...", bad: "..." }],
+  extensions: { eslint: { rule: "no-throw-literal" }, ruff: { codes: ["E501"] } } }
+```
+
+`confidence` decides severity through `severityThresholds` (default error 0.85, warn 0.60,
+info 0.40). A rule below `info` is left out of every export.
+
+`readProfile(path)` and `writeProfile(path, profile)` parse through the schema;
+`validateProfile(data)` returns zod's `safeParse` result. `migrateProfile` walks the
+migrations registered with `registerMigration` up to `SCHEMA_VERSION` (`1.0.0`, none
+registered yet).
+
+## Export
+
+```ts
+import { exportProfile, readProfile, SUPPORTED_FORMATS } from "@titan-design/style-profile";
+
+const profile = await readProfile("code-style-profile.json");
+for (const file of exportProfile(profile, "ruff")) {
+  // file.path is relative to the target repo, file.content is the full text
+}
+```
+
+| Format | Files |
+|---|---|
+| `eslint` | `eslint.config.js` |
+| `ruff` | `ruff.toml` |
+| `editorconfig` | `.editorconfig` |
+| `markdown` | `style-guide.md` |
+| `claude-rules` | `.claude/rules/typescript.md` (none when no rule clears `info`) |
+| `hooks` | `.claude/settings.json` |
+| `skill` | `skill.md`, `references/naming.md`, `references/patterns.md`, `references/per-language/<lang>.md` |
+
+Each format also has its own generator (`generateEslintExport`, `generateRuffExport`, and so
+on). The rule builders in `eslint-rules` (`buildNamingConventionRule`,
+`buildFunctionLengthRule`, `buildFileNamingRule`, `buildJsdocRules`, `buildImportOrderRule`)
+return single `[ruleName, config]` pairs for callers that assemble their own ESLint config.
+
+## Provenance
+
+Ported unchanged from codewatch's `@codewatch/profile`. Generated headers and the hooks
+command still name `codewatch`, because the artifacts are byte-identical to the original's.
+
+The worked example and the gotchas live in the site's reference page,
+`site/reference/style-profile.md`.