convez.ai
AgenteEscrita & ConteúdoAvançado
extreme-structure

Manuscript Optimizer

extreme-structure/manuscript-optimization-plugin

Otimização de manuscritos chineses com lock de terminologia e proposições

Ver no GitHub
InicialPluginScore · de 0 a 100

Agent multi-papel para otimização de manuscritos técnicos e acadêmicos em chinês, usando modelo colaborativo 'Editor-in-Chief + 7 agentes' que executa diagnóstico, otimização por capítulo, integração de referências cruzadas e validação final. Garante consistência de terminologia, proposições centrais e estrutura em documentos longos através de validação por métricas duras em cada etapa.

Instalação

$npx convez-ai extreme-structure/manuscript-optimization-plugin

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Manuscritos técnicos/acadêmicos em chinês que intercalam termos em inglês
  • Documentos multi-capítulo exigindo consistência de terminologia e referências em todo o livro
  • Reescrita controlada onde proposições centrais e dados críticos não podem ser alterados

Veredito

Ferramenta especializada e bem-estruturada para otimização de manuscritos em chinês com requisitos rigorosos de consistência. Implementação robusta com agentes coordenados e validação por métricas, mas nicho específico (chinês) e complexidade operacional elevada limitam audiência potencial.

README

A tradução para o português deste README ainda está na fila.

Manuscript Optimizer

A multi-agent Claude Code plugin for optimizing Chinese technical/academic book manuscripts. Using an "Editor-in-Chief + 7 worker agents" collaboration model, it runs a complete pipeline over an entire manuscript — diagnosis → per-chapter optimization pipeline → cross-reference integration → final review — with script-based hard-metric validation at every step to guarantee consistency of terminology, core propositions, structure, and references.

Manuscript-specific configuration (core propositions, glossary, reference conventions, structure templates, protected data, etc.) is auto-generated by /manuscript-optimizer:init, which scans the target repository and writes to that repository's .manuscript/ directory. The plugin itself ships no manuscript content.

中文版见 README.md。

Use Cases

  • Chinese-primary technical or academic manuscripts that interleave English terms
  • Multi-chapter long documents requiring whole-book consistency (unified terminology, non-broken references, aligned structure)
  • Serious writing where you want AI rewriting while locking core propositions and key data against tampering

Workflow Overview

Phase 0  init      Scan manuscript → generate .manuscript/ config (propositions/terms/ref conventions/matrix)
Phase 1  diagnose  Per-chapter parallel diagnosis → optimization_plan.md (human reviews levels & budget)
Phase 2  optimize  Per-chapter optimization pipeline (parallel across chapters by Tier, strict serial within)
Phase 3  cross-ref Whole-book cross-reference scan & repair (full-book runs only)
Phase 4  finalize  Hard-metric script validation + soft-metric sampling → quality_report_final.md

Typical within-chapter pipeline (trimmed by intervention level):

theory-auditor → argument-engineer → case-engineer → style-harmonizer → [major level] reader-critic debate

Agent Roles

AgentPhaseCapabilityResponsibility
diagnostic-officerP1Read-onlyScan a single chapter, produce a structured QualityReport (5-dimension scoring)
theory-auditorP2.aRead-onlyValidate theoretical references: over-analogy, math errors, citation drift, missing boundary disclaimers
argument-engineerP2.bEditRestructure paragraphs, strengthen argument bridges, remove redundancy, improve prose rhythm
case-engineerP2.cEditBuild end-of-chapter case sections, generate illustrative quantitative data with mandatory labeling
style-harmonizerP2.dEditEnforce title formats, blockquotes, English-term preservation, Chinese punctuation, rhythm
reader-criticP2.eRead-onlySimulate the target reader; find cognitive breakpoints, undefined terms, skipped reasoning (major only)
cross-ref-coordinatorP3EditWhole-book reference scan, build index, fix broken/stale references

The Editor-in-Chief role is played by the manuscript-optimize skill, responsible for dispatch, conflict arbitration, budget guarding, and step-by-step git commits.

Commands (Skills)

CommandDescription
/manuscript-optimizer:init [manuscript-dir]Phase 0, generate .manuscript/ config (run this first)
/manuscript-optimizer:diagnose [chapter-ids|all]Phase 1 diagnosis only, no content changes, produces optimization plan
/manuscript-optimizer:optimize [chapter-ids|all]Full optimization workflow (Phases 1–4)
/manuscript-optimizer:finalizePhase 4 final review and report only

Validation Scripts

The plugin validates automatically via hooks after every Edit/Write, and runs a whole-book final check on session Stop:

  • scripts/validate_chapter.py — PostToolUse hook, single-chapter hard-metric validation
  • scripts/final_check.py — Stop hook / final review, whole-book scan
  • scripts/manuscript_lib.py — shared validation logic

Validation items: English-term preservation, full-text matching of core propositions, required structural elements, LaTeX formula pairing, illustrative-data labeling, protected-data integrity, manifest chapter completeness, and zero broken cross-references. Zero violations required.

Installation

This repository ships a local marketplace manifest (.claude-plugin/marketplace.json). In Claude Code:

/plugin marketplace add /Users/wangziren/PycharmProjects/manuscript-optimization-plugin
/plugin install manuscript-optimizer

Then run /manuscript-optimizer:init inside your manuscript repository (not this plugin repository) to begin.

Quick Start

# In the manuscript repository root
/manuscript-optimizer:init book/        # Generate .manuscript/, review propositions & protected data
git tag pre-optimization-baseline       # Establish a baseline (init will prompt)
/manuscript-optimizer:diagnose all      # Review optimization_plan.md
/manuscript-optimizer:optimize all      # Run the full workflow
/manuscript-optimizer:finalize          # Final review, produces quality_report_final.md

Design Principles

  • Config/code separation: the plugin holds zero manuscript content; all manuscript-specific info lives in the target repo's .manuscript/
  • Inviolable hard constraints: core propositions and protected data are validated verbatim against full-text anchors; AI rewriting may not tamper with them
  • Step-by-step traceability: each worker step is an independent git commit ([opt:<chapter>:<role>] ...), so failures are localizable and re-dispatchable
  • Budget guarding: pause and consult the user when cumulative spend exceeds 80% of budget while completion is below 50%

Repository Structure

.claude-plugin/    plugin.json + local marketplace manifest
agents/            7 worker agent definitions
skills/            init / diagnose / optimize / finalize commands
hooks/             PostToolUse + Stop validation hooks
scripts/           Python validation scripts (no third-party deps, Python ≥ 3.12)
docs/              agent / skill / hooks / plugin development guides

Development

The validation scripts have no third-party dependencies and require only Python 3.12+. The docs/ directory contains development guides for extension work.

Ver o original no GitHub

Bom para

Relacionados