kotonoha 0.1.6-dev.0 → 0.2.0

package/skills/tech-writer/SKILL.md

@@ -27,10 +27,9 @@ description: >-
   question-at-a-time intake before writing. Supports both Japanese and
   English documents, with Japanese as the primary target. Owns document
   structure, information completeness, and reader fit; for living Japanese
-  documents, it orchestrates a registered prose-polishing skill such as
-  https://github.com/coji/natural-japanese for sentence-level naturalness,
-  word choice, rhythm, and "AI smell" removal without reimplementing that
-  skill.
+  documents, it invokes kotonoha's original bundled `japanese-prose` skill,
+  which uses GiNZA for sentence-level naturalness, word choice, rhythm, and
+  repeated AI-like pattern analysis.
 license: MIT
 argument-hint: "[write|review|score] [doctype] <target file or request>"
 ---
@@ -57,13 +56,12 @@ reference files.
 
 Document quality splits into two layers: "is the structure right" and "is
 the prose natural and readable". This skill owns the first layer (structure,
-document type conventions, completeness, reader fit). A prose-polishing skill
-such as [natural-japanese](https://github.com/coji/natural-japanese) owns the
-second layer (sentence-level naturalness, removing "AI smell", rhythm);
-tech-writer orchestrates that skill without duplicating its rules or scripts.
-When both skills are installed, this skill locks down the structure and
-orchestrates the §5 handoff to natural-japanese during `write` mode before
-the final rubber-duck review.
+document type conventions, completeness, reader fit). The bundled
+`japanese-prose` skill owns the second layer (sentence-level naturalness,
+reading load, terminology, and repeated-pattern analysis). Kotonoha packages
+both layers: tech-writer locks down the structure and orchestrates the §5
+handoff to japanese-prose during `write` mode before the final rubber-duck
+review.
 
 - Rule of thumb: "does removing a heading still make sense?" tests structure
   (this skill's job). "Does rereading a single sentence change its meaning?"
@@ -274,21 +272,20 @@ step 2 as the primary check for those.
 ## 5. Optimize Japanese prose without changing the structure — write mode only
 
 For a living, multi-section document whose requested final language is
-Japanese, read
-`references/japanese-prose-optimization.md` and hand the completed draft to a
-registered `natural-japanese` or equivalent Japanese prose-polishing skill.
-This pass is mandatory when such a skill is available.
-
-Treat the optimizer as available when the host's registered skill list
-contains `natural-japanese` or a compatible Japanese prose-polishing skill.
-Invoke it through the host's skill-loading mechanism; when only installed
-skill files are exposed, check
-`.github/skills/natural-japanese/SKILL.md`,
-`.copilot/skills/natural-japanese/SKILL.md`, and
-`$HOME/.copilot/skills/natural-japanese/SKILL.md`, then load the discovered
-`SKILL.md` and follow that workflow. Treat the pass as unavailable only when
-no compatible registration or readable skill installation exists, or when
-the optimizer cannot start.
+Japanese, read `references/japanese-prose-optimization.md` and hand the
+completed draft to kotonoha's bundled `japanese-prose` skill. This pass is
+mandatory for an in-scope document.
+
+Load `japanese-prose` through the host's skill-loading mechanism. When only
+installed skill files are exposed, resolve the sibling path
+`<tech-writer-dir>/../japanese-prose/SKILL.md` first, then check
+`.github/skills/japanese-prose/SKILL.md`,
+`.copilot/skills/japanese-prose/SKILL.md`, and
+`$HOME/.copilot/skills/japanese-prose/SKILL.md`. Load the discovered
+`SKILL.md` and follow its quick or full workflow. A standard
+`npx kotonoha install` installs this sibling skill automatically. Treat the
+pass as unavailable only when someone copied or installed tech-writer without
+its bundled sibling, or when the optimizer cannot start.
 
 Freeze heading hierarchy, section order, identifiers, numeric facts,
 citations, normative language, tables, code, commands, acceptance criteria,
@@ -394,10 +391,7 @@ of that. Common items to confirm:
 
 ## Acknowledgment
 
-The idea of separating structure from prose comes from
-[natural-japanese](https://github.com/coji/natural-japanese) (MIT License)
-and its design principle "machines detect, humans (or agents) judge" and
-"prevent at generation time rather than fix afterward". This skill extends
-that separation by owning technical-document structure while orchestrating,
-but not reimplementing, the registered prose-polishing skill responsible for
-sentence-level naturalness.
+The bundled prose optimizer is an original kotonoha implementation built on
+[GiNZA](https://github.com/megagonlabs/ginza) (MIT License). Tech-writer owns
+technical-document structure while japanese-prose uses GiNZA's morphology,
+dependency, and named-entity analysis for sentence-level review.

package/skills/tech-writer/references/japanese-prose-optimization.md

@@ -5,11 +5,10 @@ are complete. The goal is to remove mechanical or translated-sounding prose
 without changing the document's approved meaning, obligations, evidence, or
 traceability.
 
-The preferred optimizer is the
-[natural-japanese prose-polishing skill](https://github.com/coji/natural-japanese).
-Kotonoha owns document structure and completeness; `natural-japanese` owns
-sentence-level clarity, rhythm, word choice, reading load, and detection of
-repeated AI-like phrasing.
+The optimizer is kotonoha's original bundled `japanese-prose` skill.
+Kotonoha owns document structure and completeness; `japanese-prose` owns
+sentence-level clarity, rhythm, word choice, reading load, terminology, and
+detection of repeated AI-like phrasing through GiNZA analysis.
 
 ## Run this pass when
 
@@ -17,8 +16,7 @@ repeated AI-like phrasing.
   whose audience-facing prose is primarily Japanese.
 - The task is `write` mode.
 - The artifact is a living, multi-section document.
-- A registered `natural-japanese` or equivalent Japanese prose-polishing
-  skill is available.
+- The bundled `japanese-prose` skill is readable.
 
 Skip it for English documents, generated machine-readable files, and source
 code. Also skip atomic artifacts such as commit messages, PR descriptions,
@@ -47,25 +45,25 @@ Never trade technical precision for conversational phrasing.
 
 ## Optimization loop
 
-1. Inspect the host's registered skill list for `natural-japanese` or a
-   compatible Japanese prose-polishing skill. Invoke it through the host's
-   skill-loading mechanism. If the host exposes only skill files, check
-   `.github/skills/natural-japanese/SKILL.md`,
-   `.copilot/skills/natural-japanese/SKILL.md`, and
-   `$HOME/.copilot/skills/natural-japanese/SKILL.md`; expand `$HOME`, load the
+1. Invoke kotonoha's bundled `japanese-prose` through the host's
+   skill-loading mechanism. If the host exposes only skill files, resolve
+   `<tech-writer-dir>/../japanese-prose/SKILL.md` first, then check
+   `.github/skills/japanese-prose/SKILL.md`,
+   `.copilot/skills/japanese-prose/SKILL.md`, and
+   `$HOME/.copilot/skills/japanese-prose/SKILL.md`; expand `$HOME`, load the
    discovered skill,
    and follow its workflow.
 2. Ask the loaded skill to review and rewrite only the Japanese prose under
    the frozen invariants.
-3. Let `<natural-japanese-dir>` be the directory containing the loaded
+3. Let `<japanese-prose-dir>` be the directory containing the loaded
    optimizer's `SKILL.md`. When its diagnostics are available, run the
    optimizer's scripts with their qualified paths:
 
    ```bash
-   uv run <natural-japanese-dir>/scripts/lint.py <target-file> --genre tech
-   uv run <natural-japanese-dir>/scripts/lint.py <target-file> --reading-load
-   uv run <natural-japanese-dir>/scripts/outline.py <target-file>
-   uv run <natural-japanese-dir>/scripts/terms.py <target-file>
+   uv run <japanese-prose-dir>/scripts/lint.py <target-file> --genre tech --json > <workdir>/prose-baseline.json
+   uv run <japanese-prose-dir>/scripts/lint.py <target-file> --genre tech --reading-load
+   uv run <japanese-prose-dir>/scripts/outline.py <target-file>
+   uv run <japanese-prose-dir>/scripts/terms.py <target-file>
    ```
 
    Do not substitute `skills/tech-writer/scripts/lint.py`; kotonoha's script
@@ -95,9 +93,10 @@ final language is Japanese, in `write` mode), report exactly one status:
   no actionable prose findings remain. Run diagnostics when available; if
   `uv` or a diagnostic script is unavailable, note that limitation without
   changing this status.
-- `Japanese prose optimization not performed`: no compatible optimizer was
-  registered or loaded, so no prose review or rewrite ran; include the
-  concrete reason.
+- `Japanese prose optimization not performed`: the bundled optimizer was
+  missing or unreadable, so no prose review or rewrite ran; include the
+  concrete reason. A standard `npx kotonoha install` should prevent this
+  state.
 - `Japanese prose optimization did not converge`: three rounds completed with
   unresolved actionable findings or invariant violations, or the optimizer
   started but failed before producing a valid result, a required

package/skills/tech-writer/references/style-constitution.md

@@ -2,7 +2,7 @@
 
 Constraints to fix a technical document's *structure* before writing.
 Sentence-level naturalness, vocabulary, and rhythm are out of scope here
-(→ the domain of a prose-polishing skill such as natural-japanese).
+(→ the domain of kotonoha's bundled `japanese-prose` skill).
 
 ## Scope: living documents vs. atomic artifacts
 

package/skills/tech-writer/scripts/lint.py

@@ -6,7 +6,7 @@
 """tech-writer skill: a lint script that mechanically checks a technical
 document's *structure* and Markdown rendering safety.
 
-Where natural-japanese's lint.py detects sentence-level naturalness
+Where japanese-prose's GiNZA lint detects sentence-level naturalness
 (vocabulary, rhythm), this script detects structural problems specific to
 technical documents plus Markdown syntax patterns that render inconsistently
 (heading hierarchy, code examples, leftover placeholders, suspicious links,