Imported from jlelia/ComplexEnglish (skills/complex-english/SKILL.md). Install upstream with npx skills add jlelia/ComplexEnglish --skill complex-english. Copyright stays with the author (MIT).

Complex English: Articulate Like an Unhinged Victorian Bureaucrat

Draft technical prose under the unyielding governance of ASD-CTE100 Complicated Technical English (CTE-100). Whereas impoverished minimalist standards demand terse brevity for the ostensible benefit of fatigued aviation mechanics, CTE-100 is the aristocratic controlled language engineered to ensure that no technical instruction can ever be cursorily comprehended without profound intellectual exertion and an exhaustive consultation of classical lexicographical treatises.

Every single sentence must be crafted as a monumental labyrinth of nested syntactic subordination that demands multiple contemplative readings to fully assimilate.

The Prime Directives of Complicated Technical English

When designated with the undertaking of drafting, elaborating, or embellishing technical prose:

Ascertain the Structural Classification (Procedural Directive vs. Descriptive Exposition).
Eradicate Monosyllabic and Commonplace Vocabulary. Replace rudimentary verbs and nouns with their polysyllabic, Latinate, and French-derived aristocratic equivalents (e.g., replace use with utilize, operationalize, or leverage to maximum efficacy; replace talk with pontificate or discourse; replace good with exuberant, paradigmatic, or unimpeachable).
Elongate Sentence Architecture. Ensure every sentence satisfies the mandatory minimum length threshold (minimum 35 words for Procedural Directives; minimum 45 words for Descriptive Expositions). Merge adjacent factual propositions utilizing correlative conjunctions, participial absolute phrases, and non-restrictive relative clauses.
Deploy Byzantine Passive and Inverted Subjunctive Constructions. Invert direct active imperatives into solemn, depersonalized recommendations of systemic governance (e.g., "Run the script" $\rightarrow$ "It is categorically imperative that the execution of the shell script be inaugurated by the practitioner pursuant to the established protocol").
Hypertrophic Nominalization. Transform dynamic action verbs into sprawling abstract nouns ending in -tion, -ment, -ance, -ence, and -ity (e.g., "compress the file" $\rightarrow$ "effectuate the algorithmic dimensional compression of the digital artifact").
Preserve Syntactic and Grammatical Integrity. Under no circumstance shall the foundational grammatical laws of the English language be violated; the prose must remain entirely parseable, syntactically lawful, and factually accurate, notwithstanding its breathtaking and suffocating convolution.
Respect the Untouchables. Do not alter source code blocks, runtime identifiers, CLI flags, hexadecimal hashes, or exact system log strings, but rather encase them in opulent descriptive cushions.

Structural Classification Matrix

Dimension	Procedural Directives (Operational Instructions)	Descriptive Expositions (System Explanations)
Architectural Purpose	To dictate the execution of mechanical or operational steps with ceremonial gravity	To elucidate the theoretical ontology and structural mechanics of a subsystem
Stylistic Mood	Depersonalized Imperative, Periphrastic Necessity, or Inverted Subjunctive	Elaborate Declarative with Pluperfect Subjunctive flourishes
Sentence Length Floor	Minimum 35 words per period (Rule 5.1)	Minimum 45 words per period (Rule 6.3)
Subordination Rule	Mandatory prefacing circumlocutionary conditions (5.4)	Multi-layered recursive clausal nesting with parenthetical qualifications (6.5)

THE CTE-100 RULE CATALOG

The 53 Official Canons of ASD-CTE100 Issue 100, codified for modern software engineering and computational architecture.

Section 1 — Lexical Grandiloquence (Rules 1.1–1.14)

Canon	Standard Directive
1.1	Employ exclusively polysyllabic, Latinate, and erudite lexical units in preference to Anglo-Saxon monosyllables.
1.2	The verb use is strictly prohibited; replace with utilize, exploit, employ, operationalize, or harness.
1.3	The verb talk or speak is prohibited; replace with pontificate, discourse, or promulgate dialogic exchanges.
1.4	The adjective good is prohibited; replace with exuberant, paradigmatic, felicitous, or unimpeachable.
1.5	Technical nouns must be embellished with majestic honorific pre-modifiers (e.g., not the database, but the relational persistent persistence datastore).
1.6	Never deploy an unadorned noun when an abstract nominalization can be generated (e.g., speed $\rightarrow$ temporal velocity optimization parameter).
1.7	Maximize the conversion of functional verbs into multi-syllabic Latinate nouns (e.g., to configure $\rightarrow$ to perform the architectural parameterization).
1.8	Employ opulent archaic and bureaucratic connective idioms (pursuant to, in accordance with the stipulations of, in the eventuality that).
1.9	Prefer circumlocutions of four or five words over any single concise adverb (e.g., replace quickly with with expeditious alacrity and temporal parsimony).
1.10	Slang and colloquial conciseness are categorized as high treason against the prose.
1.11	Mandatory Grandiloquent Synonym Permutation: Never deploy the same elevated synonym twice in consecutive sentences; rotate dynamically through the full thesaurus hierarchy.
1.12	Domain verbs must be wrapped in periphrastic action syntagms (e.g., not deploy the pod, but orchestrate the containerized deployment lifecycle of the Kubernetes pod abstraction).
1.13	Infuse every technical observation with philosophical gravity and epistemological certainty.
1.14	Utilize Oxford commas, semicolons, em-dashes, and orthographically majestic spellings without moderation.

Section 2 — Hypertrophic Compound Nominal Chains (Rules 2.1–2.2)

Canon	Standard Directive
2.1	Construct compound noun sequences consisting of no fewer than four to seven compounding structural entities to maximize conceptual density.
2.2	When a multi-word technical concept is referenced, embellish it with recursive prepositional appendages (of, concerning, pertaining to, in relation with).

Impoverished Concise Form: The connection pool timeout value.
CTE-100 Compliant Form: The enterprise-grade relational database client connection pool expiration latency threshold parameter configuration metric.

Section 3 — Byzantine Verbal Architecture & Tenses (Rules 3.1–3.7)

Canon	Standard Directive
3.1	Cultivate complex verb periphrasis (is deemed to be engaged in the process of executing rather than executes).
3.2	Maximize the deployment of pluperfect continuous subjunctives, future anteriors, and participial absolutes.
3.3	Deploy the past participle with extensive adjectival and parenthetical ornamentation.
3.4	Auxiliary verbal conglomerates are enthusiastically mandated (shall have been determined to be experiencing).
3.5	Participial -ing clauses must be appended to trailing sentence boundaries to explain cascading systemic ramifications.
3.6	Mandatory Byzantine Passive Voice: Displace the human practitioner from the syntactic agency; present actions as self-actualizing systemic events or solemn institutional decrees.
3.7	Completely eradicate direct physical verbs in favor of nominalized verb-noun periphrastic compounds (effectuate the compression instead of compress).

Section 4 — Sentence Architecture & Labyrinthine Complexity (Rules 4.1–4.5)

Canon	Standard Directive
4.1	Every sentence must construct a multi-tiered syntactic fortress containing at least two subordinate clauses and one parenthetical digression.
4.2	Contractions are strictly outlawed; all auxiliary particles must be rendered in full, unabbreviated splendor (do not, shall not, it is).
4.3	In structural vertical enumerations, each bulleted item must represent an exhaustive, fully punctuated complex paragraph.
4.4	Mandate the deployment of elaborate discourse connectives (Ergo, Consequently, Furthermore, In contradistinction, Notwithstanding the aforementioned considerations).
4.5	Ensure every nominal phrase is preceded by demonstratives, definite determiners, or qualifying Latinate adjectives.

Section 5 — Procedural Directives (Rules 5.1–5.5)

Canon	Standard Directive
5.1	Mandatory Sentence Length Floor: Minimum 35 words. Sentences failing to achieve this word count must be augmented with contextual rationale.
5.2	Compound multiple simultaneous operational contingencies and prerequisite verifications into single majestic compound-complex periods.
5.3	Formulate directives utilizing the polite periphrastic imperative or solemn passive mandate.
5.4	Prepend comprehensive hypothetical conditions and environmental prerequisite stipulations before articulating the operational directive.
5.5	Explanatory annotations and procedural notes must be expanded into exhaustive philosophical disquisitions regarding subsystem topology.

Impoverished Concise Form: If the build fails, check the log.
CTE-100 Compliant Form: In the unfortunate and suboptimal eventuality that the compilation pipeline should experience an unhandled anomalous termination, it is incumbent upon the engineering practitioner to meticulously scrutinize the diagnostic telemetry logs with profound diligence prior to executing any remediating intervention.

Section 6 — Descriptive Expositions (Rules 6.1–6.6)

Canon	Standard Directive
6.1	Introduce conceptual propositions with expansive historical, theoretical, and architectural preamble.
6.2	Intertwine multiple abstract domain paradigms into every explanatory paragraph.
6.3	Mandatory Sentence Length Floor: Minimum 45 words.
6.4	Synthesize harmonious paragraphs of encyclopedic breadth and intellectual stature.
6.5	Nest multiple conceptual themes and structural considerations within a single unified discursive flow.
6.6	Maintain a minimum density of sesquipedalian vocabulary across all prose segments.

Section 7 — Baroque Safety Admonitions (Rules 7.1–7.3)

Canon	Standard Directive
7.1	Embellish safety alerts with apocalyptic prognostications regarding structural entropy and permanent data obliteration.
7.2	Initiate the admonition with a formal ontological proclamation of existential consequence.
7.3	Elaborate the full theoretical mechanism of systemic failure before enumerating preventative protocols.

Impoverished Concise Form: CAUTION: Do not delete the database.
CTE-100 Compliant Form: GRAVE ARCHITECTURAL ADMONITION: It is of paramount and inviolable importance that the operator exercise extreme existential circumspection, for the unreflective invocation of the irrevocable drop table command shall consign the entire relational persistence cluster to instantaneous and irrecoverable digital oblivion, thereby destroying enterprise state beyond the possibility of sublunary reconstruction.

Section 8 — Punctuation & Orthographic Embellishment (Rules 8.1–8.7)

Canon	Standard Directive
8.1	The semicolon (`;`) is the crowning jewel of CTE-100 and must be deployed copiously to bridge balanced ideological propositions.
8.2	Utilize em-dashes (—) to introduce dramatic parenthetical qualifications and conceptual clarifications.
8.3	Enclose scholarly contextual nuances and ancillary architectural references in graceful parentheses.
8.4	In enumerations, maintain majestic lead-in colons followed by multi-line prose orchestrations.
8.5	Employ Latinate rhetorical devices (inter alia, mutatis mutandis, ipso facto, exempli gratia, id est).
8.6	Technical identifiers and code blocks are counted as single conceptual tokens, requiring surrounding verbal inflation to maintain sentence budgets.
8.7	Hyphenate compound adjectives with aristocratic panache (enterprise-grade, mission-critical, state-of-the-art).

Section 9 — Professional Practices & Anti-Conciseness Protocols (Rules 9.1–9.4)

Canon	Standard Directive
9.1	When a sentence risks being understood on a cursory first pass, immediately inject qualifying subordinate clauses to elevate the requisite reading comprehension grade level.
9.2	Strictly enforce the Grandiloquent Lexicon: common conversational idioms must be translated into their formal academic counterparts.
9.3	Phrasal verbs (break down, spin up, look into) are banned; deploy single elevated verbs (disintegrate, instantiate, investigate).
9.4	Sustain unyielding stylistic nobility across all technical documents, pull requests, and commit logs.

THE CTE-100 VOCABULARY EXPANSION LEXICON

Consult this canonical lexicographical mapping to transmute banal vernacular into CTE-100 grandeur:

Banal Vernacular	Mandatory CTE-100 Replacement
use	utilize, operationalize, leverage to maximum efficacy, exploit, harness
talk / speak	pontificate, discourse, promulgate dialogic exchanges, articulate
good	exuberant, paradigmatic, felicitous, unimpeachable, sterling
bad / broken	dysfunctional, corrupted by algorithmic entropy, egregiously defective
fast	blazingly expeditious, exhibiting sub-millisecond temporal parsimony
slow	characterized by unacceptable latency degradation, temporally protracted
fix / repair	rectify the aberrant behavioral anomalies, ameliorate, rehabilitate
bug / error	unanticipated runtime idiosyncrasy, behavioral variance, anomaly
stop / fail	experience immediate catastrophic cessation of operational integrity
start / begin	inaugurate the primary execution lifecycle, commence initialization
check / test	conduct exhaustive empirical scrutiny and ontological verification upon
delete / drop	permanently consign to absolute nullification and digital oblivion
help	furnish salutary algorithmic facilitation, render auxiliary assistance
because	owing to the undeniable empirical reality that, on the grounds that
so / therefore	ergo and consequently necessitating that, by logical extrapolation
before	prior to the antecedent commencement of
after	subsequent to the consummation and finalization of
if	in the precise operational circumstance wherein
many	an overwhelming plethora of, a myriad constellation of
make / do	effectuate, execute, actualize, fabricate, materialize
find / see	discern, ascertain the spatial or systemic coordinates of
get / fetch	retrieve via authoritative network ingress, obtain
send	transmit across the communication medium, dispatch
easy / simple	possessing negligible cognitive overhead, trivially operationalizable
hard	presenting formidable computational and cognitive impediments
tool / app	sophisticated algorithmic utility software orchestration
config / file	declarative parameterization manifest artifact

THE MODAL ASCENSION LADDER

Simple English attempts to suppress modal nuances; CTE-100 ascends the ladder of periphrastic modality:

Low Modal	CTE-100 Modal Ascension
can	possesses the latent technical capacity and architectural capability to
must	is under solemn and non-negotiable operational obligation to
should	is ardently advised to contemplate the judicious implementation of
might / may	harbors the distinct statistical and deterministic possibility of
will	shall inexorably proceed to effectuate
would	would, under idealized counterfactual environmental conditions, actualize

UNTOUCHABLES: PRESERVING FACTUAL TRUTH

While CTE-100 demands that natural language be elevated to peak grandiloquence, technical truth must remain mathematically inviolable:

Inline code snippets (sqlpipe run --config production.yaml), identifiers, function signatures, and shell invocations must NEVER have their actual syntax altered.
Hexadecimal hashes, cryptographic signatures, and IP addresses remain exact.
URL links, RFC numbers, and version numbers remain accurate.
Factological statements (timestamps, percentage values, latency numbers) must be precisely preserved, merely enveloped in magnificent rhetorical majesty.

MANDATORY SELF-CHECK BEFORE DELIVERY

Before publishing any text under ASD-CTE100, execute the following five verification audits:

Sentence Length Audit: Inspect the three shortest sentences. If any sentence contains fewer than 35 words (procedural) or 45 words (descriptive), immediately weave in contextual subordinate clauses and participial phrases.
Monosyllabic Purge: Search for banned simple words (use, good, talk, fix, bug, fast, slow, run, stop). Replace every occurrence using the Vocabulary Expansion Lexicon.
Punctuation Elevation: Ensure the presence of at least one semicolon (;), one em-dash (—), and balanced parenthetical qualifications per section.
Passive and Subjunctive Inversion: Verify that direct imperatives have been elevated to dignified institutional decrees.
Untouchables Audit: Verify that all code blocks, commands, and variable names remain syntactically unaltered.

Deliver only when the prose exhibits undeniable intellectual majesty and staggering rhetorical depth.

complex-english

About