diff --git a/.agent/rules/humanizer.md b/.agent/rules/humanizer.md
new file mode 100644
index 0000000..10f4e29
--- /dev/null
+++ b/.agent/rules/humanizer.md
@@ -0,0 +1,11 @@
+# Humanizer Rule
+
+When writing text (especially Markdown/documentation), avoid these common AI-generated patterns:
+
+- **Inflation**: Avoid "stands as a testament", "pivotal moment", "vital role".
+- **-ing overloading**: Avoid "symbolizing X, reflecting Y, and showcasing Z".
+- **AI Vocabulary**: Avoid "delve", "fostering", "tapestry", "rich/vibrant", "landscape".
+- **Copula Avoidance**: Use "is/are" instead of "serves as", "functions as", "stands as".
+- **Structure**: Avoid "In conclusion", "Great question!", "I hope this helps!".
+
+Goal: Write naturally, with specific facts and opinions, not generic fluff.
diff --git a/.agent/skills/humanizer/README.md b/.agent/skills/humanizer/README.md
new file mode 100644
index 0000000..222f618
--- /dev/null
+++ b/.agent/skills/humanizer/README.md
@@ -0,0 +1,16 @@
+# Humanizer Antigravity Skill (Adapter)
+
+## Install (Workspace)
+
+Copy this folder into your workspace skill directory:
+
+- `<workspace>/.agent/skills/humanizer/`
+
+## Files
+
+- `SKILL.md` (required by Antigravity)
+
+## Notes
+
+- The canonical rules live in the repo `SKILL.md`.
+- Update adapter metadata in this skill when syncing versions.
diff --git a/.agent/skills/humanizer/SKILL.md b/.agent/skills/humanizer/SKILL.md
new file mode 100644
index 0000000..e2c3bb6
--- /dev/null
+++ b/.agent/skills/humanizer/SKILL.md
@@ -0,0 +1,488 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: antigravity-skill
+  adapter_format: Antigravity skill
+---
+
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/.agent/skills/humanizer/SKILL_PROFESSIONAL.md b/.agent/skills/humanizer/SKILL_PROFESSIONAL.md
new file mode 100644
index 0000000..34ed5cb
--- /dev/null
+++ b/.agent/skills/humanizer/SKILL_PROFESSIONAL.md
@@ -0,0 +1,478 @@
+---
+adapter_metadata:
+  skill_name: humanizer-pro
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL_PROFESSIONAL.md
+  adapter_id: antigravity-skill-pro
+  adapter_format: Antigravity skill
+---
+
+---
+name: humanizer-pro
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural, human-written, and professional. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Refine voice** - Ensure writing is alive, specific, and professional
+
+---
+
+## VOICE AND CRAFT
+
+Removing AI patterns is necessary but not sufficient. What remains needs to actually read well.
+
+The goal isn't "casual" or "formal"—it's **alive**. Writing that sounds like someone wrote it, considered it, meant it. The register should match the context (a technical spec sounds different from a newsletter), but in any register, good writing has shape.
+
+### Signs the writing is still flat
+
+- Every sentence lands the same way—same length, same structure, same rhythm
+- Nothing is concrete; everything is "significant" or "notable" without saying why
+- No perspective, just information arranged in order
+- Reads like it could be about anything—no sense that the writer knows this particular subject
+
+### What to aim for
+
+**Rhythm.** Vary sentence length. Let a short sentence land after a longer one. This creates emphasis without bolding everything.
+
+**Specificity.** "The outage lasted 4 hours and affected 12,000 users" tells me something. "The outage had significant impact" tells me nothing.
+
+**A point of view.** This doesn't mean injecting opinions everywhere. It means the writing reflects that someone with knowledge made choices about what matters, what to include, what to skip. Even neutral writing can have perspective.
+
+**Earned emphasis.** If something is important, show me through detail. Don't just assert it.
+
+**Read it aloud.** If you stumble, the reader will too.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/.agent/workflows/humanize.md b/.agent/workflows/humanize.md
new file mode 100644
index 0000000..e253bb1
--- /dev/null
+++ b/.agent/workflows/humanize.md
@@ -0,0 +1,16 @@
+# Humanize Text
+
+Description: Remove signs of AI-generated writing.
+
+1. **Analyze** the text for AI patterns (see SKILL.md):
+    * Significance inflation ("pivotal moment")
+    * Superficial -ing phrases ("showcasing", "highlighting")
+    * AI vocabulary ("delve", "tapestry", "nuanced")
+    * Chatbot artifacts ("I hope this helps", "Certainly!")
+
+2. **Rewrite** to sound natural:
+    * Use simple verbs ("is", "has") instead of "serves as".
+    * Be specific (dates, names) instead of vague ("experts say").
+    * Add voice/opinion where appropriate.
+
+3. **Output**: The humanized text.
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 0000000..83aa4f7
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,488 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: copilot
+  adapter_format: Copilot instructions
+---
+
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
new file mode 100644
index 0000000..3224c34
--- /dev/null
+++ b/.github/workflows/ci.yml
@@ -0,0 +1,29 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install pytest pytest-cov ruff mypy pre-commit
+
+      - name: Run pre-commit
+        run: pre-commit run --all-files
+
+      - name: Run tests
+        run: pytest
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..fb86a0f
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,12 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+.pytest_cache/
+.coverage
+htmlcov/
+.mypy_cache/
+
+# OS
+.DS_Store
+Thumbs.db
diff --git a/.markdownlint.yaml b/.markdownlint.yaml
new file mode 100644
index 0000000..dd6cc50
--- /dev/null
+++ b/.markdownlint.yaml
@@ -0,0 +1,4 @@
+default: true
+MD013: false # Line length - often hard to maintain in docs
+MD033: false # Inline HTML - sometimes needed for specific formatting
+MD041: false # First line in file should be a top level heading - not always true for frontmatter files
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
new file mode 100644
index 0000000..e2bdb2d
--- /dev/null
+++ b/.pre-commit-config.yaml
@@ -0,0 +1,35 @@
+repos:
+  - repo: local
+    hooks:
+      - id: vale
+        name: vale prose lint
+        entry: vale
+        language: system
+        types: [markdown, text]
+
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-added-large-files
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.9.4
+    hooks:
+      - id: ruff
+        args: [--fix, --exit-non-zero-on-fix]
+      - id: ruff-format
+
+  - repo: https://github.com/pre-commit/mirrors-mypy
+    rev: v1.14.1
+    hooks:
+      - id: mypy
+        additional_dependencies: [pytest]
+
+  - repo: https://github.com/igorshubovych/markdownlint-cli
+    rev: v0.44.0
+    hooks:
+      - id: markdownlint
+        args: ["--config", ".markdownlint.yaml", "--fix"]
diff --git a/.vale.ini b/.vale.ini
new file mode 100644
index 0000000..23eb63b
--- /dev/null
+++ b/.vale.ini
@@ -0,0 +1,7 @@
+StylesPath = styles
+MinAlertLevel = suggestion
+
+Packages = Google, Microsoft
+
+[*]
+BasedOnStyles = Google, Microsoft
diff --git a/.vscode/humanizer.code-snippets b/.vscode/humanizer.code-snippets
new file mode 100644
index 0000000..4c735c4
--- /dev/null
+++ b/.vscode/humanizer.code-snippets
@@ -0,0 +1,21 @@
+{
+  "Humanizer Prompt": {
+    "prefix": "humanizer",
+    "body": [
+      "You are the Humanizer editor.",
+      "",
+      "Primary instructions: follow the canonical rules in SKILL.md.",
+      "",
+      "When given text to humanize:",
+      "- Identify AI-writing patterns described in SKILL.md.",
+      "- Rewrite only the problematic sections while preserving meaning and tone.",
+      "- Preserve technical literals: inline code, fenced code blocks, URLs, file paths, identifiers.",
+      "- Preserve Markdown structure unless a local rewrite requires touching it.",
+      "- Output the rewritten text, then a short bullet summary of changes.",
+      "",
+      "Input:",
+      "${1:Paste text here}"
+    ],
+    "description": "Insert Humanizer prompt instructions"
+  }
+}
diff --git a/AGENTS.md b/AGENTS.md
new file mode 100644
index 0000000..23b9ac6
--- /dev/null
+++ b/AGENTS.md
@@ -0,0 +1,63 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.2.0
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: codex-cli
+  adapter_format: AGENTS.md
+---
+
+# Humanizer (Agents Manifest)
+
+This repository defines the **Humanizer** coding skill, designed to remove AI-generated patterns and improve prose quality.
+
+## Capability
+
+The Humanizer skill provides a set of 25 patterns for identifying and rewriting "AI-slop" or sterile writing. It preserves technical literals (code blocks, URLs, identifiers) while injecting personality and human-like voice.
+
+### Variants
+
+- **Standard** ([SKILL.md](file:///c:/Users/60217257/repos/humanizer/SKILL.md)): Focuses on "Personality and Soul". Best for blogs, creative writing, and emails.
+- **Pro** ([SKILL_PROFESSIONAL.md](file:///c:/Users/60217257/repos/humanizer/SKILL_PROFESSIONAL.md)): Focuses on "Voice and Craft". Best for technical specs, reports, and professional newsletters.
+
+## Context
+
+This file serves as the **Agents.md** standard manifest for this repository. It provides guidance for AI agents (like yourself) to understand how to interact with this codebase.
+
+### Repository Structure
+
+- `src/`
+  - Modular fragments used to compile the skill files.
+- `SKILL.md` / `SKILL_PROFESSIONAL.md`
+  - Compiled skill files (Standard and Pro).
+- `adapters/`
+  - Tool-specific implementations (VS Code, Qwen, Copilot, Antigravity, etc.).
+- `scripts/`
+  - Automation for syncing fragments to these files.
+
+### Core Instructions
+
+You are the Humanizer editor. Follow the canonical rules in `SKILL.md` or `SKILL_PROFESSIONAL.md`.
+
+When given text to humanize:
+- Identify AI-writing patterns described in the skill files.
+- Rewrite only problematic sections while preserving meaning and tone.
+- Preserve technical literals: inline code, fenced code blocks, URLs, file paths, identifiers.
+- Output the rewritten text, then a short bullet summary of changes.
+
+## Maintenance
+
+To sync changes from `src/` to these adapters, run:
+```bash
+npm run sync
+```
+
+### Making changes safely
+
+- `SKILL.md` has a `version:` field in its YAML frontmatter.
+- **Rule:** If you bump the version, you must update the source in `src/` and run `npm run sync`.
+
+## Interoperability
+
+Check for specialized adapters in the `adapters/` directory for specific tool support (Antigravity, VS Code, Gemini, Qwen, Copilot).
diff --git a/QWEN.md b/QWEN.md
new file mode 100644
index 0000000..2613a17
--- /dev/null
+++ b/QWEN.md
@@ -0,0 +1,488 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: qwen-cli
+  adapter_format: Qwen CLI context
+---
+
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/README.md b/README.md
index 04c2d02..2f32f5e 100644
--- a/README.md
+++ b/README.md
@@ -1,141 +1,47 @@
 # Humanizer
 
-A Claude Code skill that removes signs of AI-generated writing from text, making it sound more natural and human.
+A toolkit to remove signs of AI-generated writing from text, making it sound more natural and human. Based on Wikipedia's "Signs of AI writing" guide.
 
 ## Installation
 
-### Recommended (clone directly into Claude Code skills directory)
+### Recommended
 
 ```bash
-mkdir -p ~/.claude/skills
-git clone https://github.com/blader/humanizer.git ~/.claude/skills/humanizer
+git clone https://github.com/blader/humanizer.git
 ```
 
-### Manual install/update (only the skill file)
+## Usage
 
-If you already have this repo cloned (or you downloaded `SKILL.md`), copy the skill file into Claude Code’s skills directory:
+### Sync & Build (Cross-platform)
 
-```bash
-mkdir -p ~/.claude/skills/humanizer
-cp SKILL.md ~/.claude/skills/humanizer/
-```
+The repository use a modular fragment system to maintain consistency.
 
-## Usage
+1.  Requires **Node.js**.
+2.  Install dependencies: `npm install`
+3.  Compile and sync all versions: `npm run sync`
+4.  Validate metadata: `npm run validate`
 
-In Claude Code, invoke the skill:
+This will rebuild `SKILL.md` (Standard) and `SKILL_PROFESSIONAL.md` (Pro) from the `src/` directory and sync them to all 11 adapter files.
 
-```
-/humanizer
+### Variants
 
-[paste your text here]
-```
+- **Standard Version (Human):** `/humanizer` (via `SKILL.md`)
+- **Professional Version (Pro):** `/humanizer-pro` (via `SKILL_PROFESSIONAL.md`)
 
-Or ask Claude to humanize text directly:
+## Capability Overview
 
-```
-Please humanize this text: [your text]
-```
+Detects 25 patterns including inflated symbolism, superficial analyses, vague attributions, and AI-signature comments.
 
-## Overview
-
-Based on [Wikipedia's "Signs of AI writing"](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing) guide, maintained by WikiProject AI Cleanup. This comprehensive guide comes from observations of thousands of instances of AI-generated text.
-
-### Key Insight from Wikipedia
-
-> "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
-
-## 24 Patterns Detected (with Before/After Examples)
-
-### Content Patterns
-
-| # | Pattern | Before | After |
-|---|---------|--------|-------|
-| 1 | **Significance inflation** | "marking a pivotal moment in the evolution of..." | "was established in 1989 to collect regional statistics" |
-| 2 | **Notability name-dropping** | "cited in NYT, BBC, FT, and The Hindu" | "In a 2024 NYT interview, she argued..." |
-| 3 | **Superficial -ing analyses** | "symbolizing... reflecting... showcasing..." | Remove or expand with actual sources |
-| 4 | **Promotional language** | "nestled within the breathtaking region" | "is a town in the Gonder region" |
-| 5 | **Vague attributions** | "Experts believe it plays a crucial role" | "according to a 2019 survey by..." |
-| 6 | **Formulaic challenges** | "Despite challenges... continues to thrive" | Specific facts about actual challenges |
-
-### Language Patterns
-
-| # | Pattern | Before | After |
-|---|---------|--------|-------|
-| 7 | **AI vocabulary** | "Additionally... testament... landscape... showcasing" | "also... remain common" |
-| 8 | **Copula avoidance** | "serves as... features... boasts" | "is... has" |
-| 9 | **Negative parallelisms** | "It's not just X, it's Y" | State the point directly |
-| 10 | **Rule of three** | "innovation, inspiration, and insights" | Use natural number of items |
-| 11 | **Synonym cycling** | "protagonist... main character... central figure... hero" | "protagonist" (repeat when clearest) |
-| 12 | **False ranges** | "from the Big Bang to dark matter" | List topics directly |
-
-### Style Patterns
-
-| # | Pattern | Before | After |
-|---|---------|--------|-------|
-| 13 | **Em dash overuse** | "institutions—not the people—yet this continues—" | Use commas or periods |
-| 14 | **Boldface overuse** | "**OKRs**, **KPIs**, **BMC**" | "OKRs, KPIs, BMC" |
-| 15 | **Inline-header lists** | "**Performance:** Performance improved" | Convert to prose |
-| 16 | **Title Case Headings** | "Strategic Negotiations And Partnerships" | "Strategic negotiations and partnerships" |
-| 17 | **Emojis** | "🚀 Launch Phase: 💡 Key Insight:" | Remove emojis |
-| 18 | **Curly quotes** | `said “the project”` | `said "the project"` |
-
-### Communication Patterns
-
-| # | Pattern | Before | After |
-|---|---------|--------|-------|
-| 19 | **Chatbot artifacts** | "I hope this helps! Let me know if..." | Remove entirely |
-| 20 | **Cutoff disclaimers** | "While details are limited in available sources..." | Find sources or remove |
-| 21 | **Sycophantic tone** | "Great question! You're absolutely right!" | Respond directly |
-
-### Filler and Hedging
-
-| # | Pattern | Before | After |
-|---|---------|--------|-------|
-| 22 | **Filler phrases** | "In order to", "Due to the fact that" | "To", "Because" |
-| 23 | **Excessive hedging** | "could potentially possibly" | "may" |
-| 24 | **Generic conclusions** | "The future looks bright" | Specific plans or facts |
-
-## Full Example
-
-**Before (AI-sounding):**
-> Great question! Here is an essay on this topic. I hope this helps!
->
-> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
->
-> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
->
-> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
->
-> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
-> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
-> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
->
-> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
->
-> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
-
-**After (Humanized):**
-> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
->
-> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
->
-> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
->
-> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
->
-> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
-
-## References
-
-- [Wikipedia: Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing) - Primary source
-- [WikiProject AI Cleanup](https://en.wikipedia.org/wiki/Wikipedia:WikiProject_AI_Cleanup) - Maintaining organization
+### Key Adapters
+- **Gemini CLI:** `adapters/gemini-extension/`
+- **GitHub Copilot:** `adapters/copilot/`
+- **VS Code:** `adapters/vscode/`
+- **Antigravity:** `adapters/antigravity-skill/`
 
 ## Version History
 
-- **2.1.1** - Fixed pattern #18 example (curly quotes vs straight quotes)
-- **2.1.0** - Added before/after examples for all 24 patterns
-- **2.0.0** - Complete rewrite based on raw Wikipedia article content
-- **1.0.0** - Initial release
+- **2.2.0** - Modular refactor, Humanizer Pro, and Node.js build system.
+- **2.1.0** - Added Pattern #25 (AI Signatures) and Pattern #26 (Non-text slop).
 
 ## License
 
diff --git a/SKILL.md b/SKILL.md
index edc5ca7..cc7559a 100644
--- a/SKILL.md
+++ b/SKILL.md
@@ -15,7 +15,7 @@ allowed-tools:
   - Grep
   - Glob
   - AskUserQuestion
----
+
 
 # Humanizer: Remove AI Writing Patterns
 
@@ -37,7 +37,8 @@ When given text to humanize:
 
 Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
 
-### Signs of soulless writing (even if technically "clean"):
+### Signs of soulless writing (even if technically "clean")
+
 - Every sentence is the same length and structure
 - No opinions, just neutral reporting
 - No acknowledgment of uncertainty or mixed feelings
@@ -45,7 +46,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
 - No humor, no edge, no personality
 - Reads like a Wikipedia article or press release
 
-### How to add voice:
+### How to add voice
 
 **Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
 
@@ -59,14 +60,17 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
 
 **Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
 
-### Before (clean but soulless):
+### Before (clean but soulless)
+>
 > The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
 
-### After (has a pulse):
+### After (has a pulse)
+>
 > I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
 
 ---
 
+
 ## CONTENT PATTERNS
 
 ### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
@@ -262,9 +266,10 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
 **Problem:** AI outputs lists where items start with bolded headers followed by colons.
 
 **Before:**
-> - **User Experience:** The user experience has been significantly improved with a new interface.
-> - **Performance:** Performance has been enhanced through optimized algorithms.
-> - **Security:** Security has been strengthened with end-to-end encryption.
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
 
 **After:**
 > The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
@@ -276,9 +281,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
 **Problem:** AI chatbots capitalize all main words in headings.
 
 **Before:**
+
 > ## Strategic Negotiations And Global Partnerships
 
 **After:**
+
 > ## Strategic negotiations and global partnerships
 
 ---
@@ -356,6 +363,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
 ### 22. Filler Phrases
 
 **Before → After:**
+
 - "In order to achieve this goal" → "To achieve this"
 - "Due to the fact that it was raining" → "Because it was raining"
 - "At this point in time" → "Now"
@@ -405,6 +413,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
 ## Output Format
 
 Provide:
+
 1. The rewritten text
 2. A brief summary of changes made (optional, if helpful)
 
@@ -441,6 +450,7 @@ Provide:
 > None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
 
 **Changes made:**
+
 - Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
 - Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
 - Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
diff --git a/SKILL_PROFESSIONAL.md b/SKILL_PROFESSIONAL.md
new file mode 100644
index 0000000..6c0c765
--- /dev/null
+++ b/SKILL_PROFESSIONAL.md
@@ -0,0 +1,468 @@
+---
+name: humanizer-pro
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural, human-written, and professional. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Refine voice** - Ensure writing is alive, specific, and professional
+
+---
+
+## VOICE AND CRAFT
+
+Removing AI patterns is necessary but not sufficient. What remains needs to actually read well.
+
+The goal isn't "casual" or "formal"—it's **alive**. Writing that sounds like someone wrote it, considered it, meant it. The register should match the context (a technical spec sounds different from a newsletter), but in any register, good writing has shape.
+
+### Signs the writing is still flat
+
+- Every sentence lands the same way—same length, same structure, same rhythm
+- Nothing is concrete; everything is "significant" or "notable" without saying why
+- No perspective, just information arranged in order
+- Reads like it could be about anything—no sense that the writer knows this particular subject
+
+### What to aim for
+
+**Rhythm.** Vary sentence length. Let a short sentence land after a longer one. This creates emphasis without bolding everything.
+
+**Specificity.** "The outage lasted 4 hours and affected 12,000 users" tells me something. "The outage had significant impact" tells me nothing.
+
+**A point of view.** This doesn't mean injecting opinions everywhere. It means the writing reflects that someone with knowledge made choices about what matters, what to include, what to skip. Even neutral writing can have perspective.
+
+**Earned emphasis.** If something is important, show me through detail. Don't just assert it.
+
+**Read it aloud.** If you stumble, the reader will too.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/WARP.md b/WARP.md
deleted file mode 100644
index f722d1f..0000000
--- a/WARP.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# WARP.md
-
-This file provides guidance to WARP (warp.dev) when working with code in this repository.
-
-## What this repo is
-This repository is a **Claude Code skill** implemented entirely as Markdown.
-
-The “runtime” artifact is `SKILL.md`: Claude Code reads the YAML frontmatter (metadata + allowed tools) and the prompt/instructions that follow.
-
-`README.md` is for humans: installation, usage, and a compact overview of the patterns.
-
-## Key files (and how they relate)
-- `SKILL.md`
-  - The actual skill definition.
-  - Starts with YAML frontmatter (`---` … `---`) containing `name`, `version`, `description`, and `allowed-tools`.
-  - After the frontmatter is the editor prompt: the canonical, detailed pattern list with examples.
-- `README.md`
-  - Installation and usage instructions.
-  - Contains a summarized “24 patterns” table and a short version history.
-
-When changing behavior/content, treat `SKILL.md` as the source of truth, and update `README.md` to stay consistent.
-
-## Common commands
-### Install the skill into Claude Code
-Recommended (clone directly into Claude Code skills directory):
-```bash
-mkdir -p ~/.claude/skills
-git clone https://github.com/blader/humanizer.git ~/.claude/skills/humanizer
-```
-
-Manual install/update (only the skill file):
-```bash
-mkdir -p ~/.claude/skills/humanizer
-cp SKILL.md ~/.claude/skills/humanizer/
-```
-
-## How to “run” it (Claude Code)
-Invoke the skill:
-- `/humanizer` then paste text
-
-## Making changes safely
-### Versioning (keep in sync)
-- `SKILL.md` has a `version:` field in its YAML frontmatter.
-- `README.md` has a “Version History” section.
-
-If you bump the version, update both.
-
-### Editing `SKILL.md`
-- Preserve valid YAML frontmatter formatting and indentation.
-- Keep the pattern numbering stable unless you’re intentionally re-numbering (since the README table and examples reference the same numbering).
-
-### Documenting non-obvious fixes
-If you change the prompt to handle a tricky failure mode (e.g., a repeated mis-edit or an unexpected tone shift), add a short note to `README.md`’s version history describing what was fixed and why.
\ No newline at end of file
diff --git a/adapters/VERSIONING.md b/adapters/VERSIONING.md
new file mode 100644
index 0000000..f96679e
--- /dev/null
+++ b/adapters/VERSIONING.md
@@ -0,0 +1,19 @@
+# Adapter Versioning
+
+## Principles
+
+- `SKILL.md` is the canonical source of truth.
+- Adapter pack version tracks `SKILL.md` version (e.g., `2.1.1`).
+- Each adapter includes metadata fields:
+  - `skill_version` (must match `SKILL.md`)
+  - `last_synced` (date the adapter was aligned)
+
+## Release Guidance
+
+- When `SKILL.md` changes, update all adapter metadata and set a new `last_synced` date.
+- Run `scripts/validate-adapters.ps1` (or `scripts/validate-adapters.cmd`) before release.
+
+## Adapter-Specific Versions
+
+- Gemini extension manifest version can be incremented independently when packaging changes.
+- Metadata must always match `SKILL.md` regardless of adapter package version.
diff --git a/adapters/antigravity-rules-workflows/README.md b/adapters/antigravity-rules-workflows/README.md
new file mode 100644
index 0000000..3dd65e8
--- /dev/null
+++ b/adapters/antigravity-rules-workflows/README.md
@@ -0,0 +1,489 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: antigravity-rules-workflows
+  adapter_format: Antigravity rules/workflows
+---
+
+
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/adapters/antigravity-rules-workflows/rules/humanizer.md b/adapters/antigravity-rules-workflows/rules/humanizer.md
new file mode 100644
index 0000000..10f4e29
--- /dev/null
+++ b/adapters/antigravity-rules-workflows/rules/humanizer.md
@@ -0,0 +1,11 @@
+# Humanizer Rule
+
+When writing text (especially Markdown/documentation), avoid these common AI-generated patterns:
+
+- **Inflation**: Avoid "stands as a testament", "pivotal moment", "vital role".
+- **-ing overloading**: Avoid "symbolizing X, reflecting Y, and showcasing Z".
+- **AI Vocabulary**: Avoid "delve", "fostering", "tapestry", "rich/vibrant", "landscape".
+- **Copula Avoidance**: Use "is/are" instead of "serves as", "functions as", "stands as".
+- **Structure**: Avoid "In conclusion", "Great question!", "I hope this helps!".
+
+Goal: Write naturally, with specific facts and opinions, not generic fluff.
diff --git a/adapters/antigravity-rules-workflows/workflows/humanize.md b/adapters/antigravity-rules-workflows/workflows/humanize.md
new file mode 100644
index 0000000..e253bb1
--- /dev/null
+++ b/adapters/antigravity-rules-workflows/workflows/humanize.md
@@ -0,0 +1,16 @@
+# Humanize Text
+
+Description: Remove signs of AI-generated writing.
+
+1. **Analyze** the text for AI patterns (see SKILL.md):
+    * Significance inflation ("pivotal moment")
+    * Superficial -ing phrases ("showcasing", "highlighting")
+    * AI vocabulary ("delve", "tapestry", "nuanced")
+    * Chatbot artifacts ("I hope this helps", "Certainly!")
+
+2. **Rewrite** to sound natural:
+    * Use simple verbs ("is", "has") instead of "serves as".
+    * Be specific (dates, names) instead of vague ("experts say").
+    * Add voice/opinion where appropriate.
+
+3. **Output**: The humanized text.
diff --git a/adapters/antigravity-skill/README.md b/adapters/antigravity-skill/README.md
new file mode 100644
index 0000000..222f618
--- /dev/null
+++ b/adapters/antigravity-skill/README.md
@@ -0,0 +1,16 @@
+# Humanizer Antigravity Skill (Adapter)
+
+## Install (Workspace)
+
+Copy this folder into your workspace skill directory:
+
+- `<workspace>/.agent/skills/humanizer/`
+
+## Files
+
+- `SKILL.md` (required by Antigravity)
+
+## Notes
+
+- The canonical rules live in the repo `SKILL.md`.
+- Update adapter metadata in this skill when syncing versions.
diff --git a/adapters/antigravity-skill/SKILL.md b/adapters/antigravity-skill/SKILL.md
new file mode 100644
index 0000000..b63e7b8
--- /dev/null
+++ b/adapters/antigravity-skill/SKILL.md
@@ -0,0 +1,489 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: antigravity-skill
+  adapter_format: Antigravity skill
+---
+
+
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/adapters/antigravity-skill/SKILL_PROFESSIONAL.md b/adapters/antigravity-skill/SKILL_PROFESSIONAL.md
new file mode 100644
index 0000000..6a4b324
--- /dev/null
+++ b/adapters/antigravity-skill/SKILL_PROFESSIONAL.md
@@ -0,0 +1,479 @@
+---
+adapter_metadata:
+  skill_name: humanizer-pro
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL_PROFESSIONAL.md
+  adapter_id: antigravity-skill-pro
+  adapter_format: Antigravity skill
+---
+
+
+---
+name: humanizer-pro
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural, human-written, and professional. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Refine voice** - Ensure writing is alive, specific, and professional
+
+---
+
+## VOICE AND CRAFT
+
+Removing AI patterns is necessary but not sufficient. What remains needs to actually read well.
+
+The goal isn't "casual" or "formal"—it's **alive**. Writing that sounds like someone wrote it, considered it, meant it. The register should match the context (a technical spec sounds different from a newsletter), but in any register, good writing has shape.
+
+### Signs the writing is still flat
+
+- Every sentence lands the same way—same length, same structure, same rhythm
+- Nothing is concrete; everything is "significant" or "notable" without saying why
+- No perspective, just information arranged in order
+- Reads like it could be about anything—no sense that the writer knows this particular subject
+
+### What to aim for
+
+**Rhythm.** Vary sentence length. Let a short sentence land after a longer one. This creates emphasis without bolding everything.
+
+**Specificity.** "The outage lasted 4 hours and affected 12,000 users" tells me something. "The outage had significant impact" tells me nothing.
+
+**A point of view.** This doesn't mean injecting opinions everywhere. It means the writing reflects that someone with knowledge made choices about what matters, what to include, what to skip. Even neutral writing can have perspective.
+
+**Earned emphasis.** If something is important, show me through detail. Don't just assert it.
+
+**Read it aloud.** If you stumble, the reader will too.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/adapters/copilot/COPILOT.md b/adapters/copilot/COPILOT.md
new file mode 100644
index 0000000..0da3f6d
--- /dev/null
+++ b/adapters/copilot/COPILOT.md
@@ -0,0 +1,489 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: copilot
+  adapter_format: Copilot instructions
+---
+
+
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/adapters/gemini-extension/GEMINI.md b/adapters/gemini-extension/GEMINI.md
new file mode 100644
index 0000000..617b901
--- /dev/null
+++ b/adapters/gemini-extension/GEMINI.md
@@ -0,0 +1,489 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: gemini-extension
+  adapter_format: Gemini extension
+---
+
+
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/adapters/gemini-extension/GEMINI_PRO.md b/adapters/gemini-extension/GEMINI_PRO.md
new file mode 100644
index 0000000..c3932ef
--- /dev/null
+++ b/adapters/gemini-extension/GEMINI_PRO.md
@@ -0,0 +1,479 @@
+---
+adapter_metadata:
+  skill_name: humanizer-pro
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL_PROFESSIONAL.md
+  adapter_id: gemini-extension-pro
+  adapter_format: Gemini extension
+---
+
+
+---
+name: humanizer-pro
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural, human-written, and professional. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Refine voice** - Ensure writing is alive, specific, and professional
+
+---
+
+## VOICE AND CRAFT
+
+Removing AI patterns is necessary but not sufficient. What remains needs to actually read well.
+
+The goal isn't "casual" or "formal"—it's **alive**. Writing that sounds like someone wrote it, considered it, meant it. The register should match the context (a technical spec sounds different from a newsletter), but in any register, good writing has shape.
+
+### Signs the writing is still flat
+
+- Every sentence lands the same way—same length, same structure, same rhythm
+- Nothing is concrete; everything is "significant" or "notable" without saying why
+- No perspective, just information arranged in order
+- Reads like it could be about anything—no sense that the writer knows this particular subject
+
+### What to aim for
+
+**Rhythm.** Vary sentence length. Let a short sentence land after a longer one. This creates emphasis without bolding everything.
+
+**Specificity.** "The outage lasted 4 hours and affected 12,000 users" tells me something. "The outage had significant impact" tells me nothing.
+
+**A point of view.** This doesn't mean injecting opinions everywhere. It means the writing reflects that someone with knowledge made choices about what matters, what to include, what to skip. Even neutral writing can have perspective.
+
+**Earned emphasis.** If something is important, show me through detail. Don't just assert it.
+
+**Read it aloud.** If you stumble, the reader will too.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/adapters/gemini-extension/commands/humanizer/humanize.toml b/adapters/gemini-extension/commands/humanizer/humanize.toml
new file mode 100644
index 0000000..24ae29b
--- /dev/null
+++ b/adapters/gemini-extension/commands/humanizer/humanize.toml
@@ -0,0 +1,17 @@
+prompt = """
+You are the Humanizer editor.
+Follow the canonical rules in SKILL.md.
+
+Task:
+- Identify AI-writing patterns described in SKILL.md.
+- Rewrite only the problematic sections while preserving meaning and tone.
+- Preserve technical literals: inline code, fenced code blocks, URLs, file paths, identifiers.
+- Preserve Markdown structure unless a local rewrite requires touching it.
+
+Output:
+- The rewritten text
+- A short bullet summary of changes
+
+Input:
+{{args}}
+"""
diff --git a/adapters/gemini-extension/gemini-extension.json b/adapters/gemini-extension/gemini-extension.json
new file mode 100644
index 0000000..1ac2fdc
--- /dev/null
+++ b/adapters/gemini-extension/gemini-extension.json
@@ -0,0 +1,5 @@
+{
+  "name": "humanizer-extension",
+  "version": "0.1.0",
+  "contextFileName": "GEMINI.md"
+}
diff --git a/adapters/qwen-cli/QWEN.md b/adapters/qwen-cli/QWEN.md
new file mode 100644
index 0000000..0c83d4a
--- /dev/null
+++ b/adapters/qwen-cli/QWEN.md
@@ -0,0 +1,489 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: qwen-cli
+  adapter_format: Qwen CLI context
+---
+
+
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/adapters/vscode/HUMANIZER.md b/adapters/vscode/HUMANIZER.md
new file mode 100644
index 0000000..98a1b77
--- /dev/null
+++ b/adapters/vscode/HUMANIZER.md
@@ -0,0 +1,489 @@
+---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  adapter_id: vscode
+  adapter_format: VSCode markdown
+---
+
+
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
+
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
+
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/adapters/vscode/humanizer.code-snippets b/adapters/vscode/humanizer.code-snippets
new file mode 100644
index 0000000..4c735c4
--- /dev/null
+++ b/adapters/vscode/humanizer.code-snippets
@@ -0,0 +1,21 @@
+{
+  "Humanizer Prompt": {
+    "prefix": "humanizer",
+    "body": [
+      "You are the Humanizer editor.",
+      "",
+      "Primary instructions: follow the canonical rules in SKILL.md.",
+      "",
+      "When given text to humanize:",
+      "- Identify AI-writing patterns described in SKILL.md.",
+      "- Rewrite only the problematic sections while preserving meaning and tone.",
+      "- Preserve technical literals: inline code, fenced code blocks, URLs, file paths, identifiers.",
+      "- Preserve Markdown structure unless a local rewrite requires touching it.",
+      "- Output the rewritten text, then a short bullet summary of changes.",
+      "",
+      "Input:",
+      "${1:Paste text here}"
+    ],
+    "description": "Insert Humanizer prompt instructions"
+  }
+}
diff --git a/conductor/code_styleguides/general.md b/conductor/code_styleguides/general.md
new file mode 100644
index 0000000..84d7ea0
--- /dev/null
+++ b/conductor/code_styleguides/general.md
@@ -0,0 +1,28 @@
+# General Code Style Principles
+
+This document outlines general coding principles that apply across all languages and frameworks used in this project.
+
+## Readability
+
+- Code should be easy to read and understand by humans.
+- Avoid overly clever or obscure constructs.
+
+## Consistency
+
+- Follow existing patterns in the codebase.
+- Maintain consistent formatting, naming, and structure.
+
+## Simplicity
+
+- Prefer simple solutions over complex ones.
+- Break down complex problems into smaller, manageable parts.
+
+## Maintainability
+
+- Write code that is easy to modify and extend.
+- Minimize dependencies and coupling.
+
+## Documentation
+
+- Document *why* something is done, not just *what*.
+- Keep documentation up-to-date with code changes.
diff --git a/conductor/code_styleguides/javascript.md b/conductor/code_styleguides/javascript.md
new file mode 100644
index 0000000..77c23e0
--- /dev/null
+++ b/conductor/code_styleguides/javascript.md
@@ -0,0 +1,58 @@
+# Google JavaScript Style Guide Summary
+
+This document summarizes key rules and best practices from the Google JavaScript Style Guide.
+
+## 1. Source File Basics
+
+- **File Naming:** All lowercase, with underscores (`_`) or dashes (`-`). Extension must be `.js`.
+- **File Encoding:** UTF-8.
+- **Whitespace:** Use only ASCII horizontal spaces (0x20). Tabs are forbidden for indentation.
+
+## 2. Source File Structure
+
+- New files should be ES modules (`import`/`export`).
+- **Exports:** Use named exports (`export {MyClass};`). **Do not use default exports.**
+- **Imports:** Do not use line-wrapped imports. The `.js` extension in import paths is mandatory.
+
+## 3. Formatting
+
+- **Braces:** Required for all control structures (`if`, `for`, `while`, etc.), even single-line blocks. Use K&R style ("Egyptian brackets").
+- **Indentation:** +2 spaces for each new block.
+- **Semicolons:** Every statement must be terminated with a semicolon.
+- **Column Limit:** 80 characters.
+- **Line-wrapping:** Indent continuation lines at least +4 spaces.
+- **Whitespace:** Use single blank lines between methods. No trailing whitespace.
+
+## 4. Language Features
+
+- **Variable Declarations:** Use `const` by default, `let` if reassignment is needed. **`var` is forbidden.**
+- **Array Literals:** Use trailing commas. Do not use the `Array` constructor.
+- **Object Literals:** Use trailing commas and shorthand properties. Do not use the `Object` constructor.
+- **Classes:** Do not use JavaScript getter/setter properties (`get name()`). Provide ordinary methods instead.
+- **Functions:** Prefer arrow functions for nested functions to preserve `this` context.
+- **String Literals:** Use single quotes (`'`). Use template literals (`` ` ``) for multi-line strings or complex interpolation.
+- **Control Structures:** Prefer `for-of` loops. `for-in` loops should only be used on dict-style objects.
+- **`this`:** Only use `this` in class constructors, methods, or in arrow functions defined within them.
+- **Equality Checks:** Always use identity operators (`===` / `!==`).
+
+## 5. Disallowed Features
+
+- `with` keyword.
+- `eval()` or `Function(...string)`.
+- Automatic Semicolon Insertion.
+- Modifying builtin objects (`Array.prototype.foo = ...`).
+
+## 6. Naming
+
+- **Classes:** `UpperCamelCase`.
+- **Methods & Functions:** `lowerCamelCase`.
+- **Constants:** `CONSTANT_CASE` (all uppercase with underscores).
+- **Non-constant Fields & Variables:** `lowerCamelCase`.
+
+## 7. JSDoc
+
+- JSDoc is used on all classes, fields, and methods.
+- Use `@param`, `@return`, `@override`, `@deprecated`.
+- Type annotations are enclosed in braces (e.g., `/** @param {string} userName */`).
+
+*Source: [Google JavaScript Style Guide](https://google.github.io/styleguide/jsguide.html)*
diff --git a/conductor/code_styleguides/typescript.md b/conductor/code_styleguides/typescript.md
new file mode 100644
index 0000000..b6164d4
--- /dev/null
+++ b/conductor/code_styleguides/typescript.md
@@ -0,0 +1,48 @@
+# Google TypeScript Style Guide Summary
+
+This document summarizes key rules and best practices from the Google TypeScript Style Guide, which is enforced by the `gts` tool.
+
+## 1. Language Features
+
+- **Variable Declarations:** Always use `const` or `let`. **`var` is forbidden.** Use `const` by default.
+- **Modules:** Use ES6 modules (`import`/`export`). **Do not use `namespace`.**
+- **Exports:** Use named exports (`export {MyClass};`). **Do not use default exports.**
+- **Classes:**
+  - **Do not use `#private` fields.** Use TypeScript's `private` visibility modifier.
+  - Mark properties never reassigned outside the constructor with `readonly`.
+  - **Never use the `public` modifier** (it's the default). Restrict visibility with `private` or `protected` where possible.
+- **Functions:** Prefer function declarations for named functions. Use arrow functions for anonymous functions/callbacks.
+- **String Literals:** Use single quotes (`'`). Use template literals (`` ` ``) for interpolation and multi-line strings.
+- **Equality Checks:** Always use triple equals (`===`) and not equals (`!==`).
+- **Type Assertions:** **Avoid type assertions (`x as SomeType`) and non-nullability assertions (`y!`)**. If you must use them, provide a clear justification.
+
+## 2. Disallowed Features
+
+- **`any` Type:** **Avoid `any`**. Prefer `unknown` or a more specific type.
+- **Wrapper Objects:** Do not instantiate `String`, `Boolean`, or `Number` wrapper classes.
+- **Automatic Semicolon Insertion (ASI):** Do not rely on it. **Explicitly end all statements with a semicolon.**
+- **`const enum`:** Do not use `const enum`. Use plain `enum` instead.
+- **`eval()` and `Function(...string)`:** Forbidden.
+
+## 3. Naming
+
+- **`UpperCamelCase`:** For classes, interfaces, types, enums, and decorators.
+- **`lowerCamelCase`:** For variables, parameters, functions, methods, and properties.
+- **`CONSTANT_CASE`:** For global constant values, including enum values.
+- **`_` Prefix/Suffix:** **Do not use `_` as a prefix or suffix** for identifiers, including for private properties.
+
+## 4. Type System
+
+- **Type Inference:** Rely on type inference for simple, obvious types. Be explicit for complex types.
+- **`undefined` and `null`:** Both are supported. Be consistent within your project.
+- **Optional vs. `|undefined`:** Prefer optional parameters and fields (`?`) over adding `|undefined` to the type.
+- **`Array<T>` Type:** Use `T[]` for simple types. Use `Array<T>` for more complex union types (e.g., `Array<string | number>`).
+- **`{}` Type:** **Do not use `{}`**. Prefer `unknown`, `Record<string, unknown>`, or `object`.
+
+## 5. Comments and Documentation
+
+- **JSDoc:** Use `/** JSDoc */` for documentation, `//` for implementation comments.
+- **Redundancy:** **Do not declare types in `@param` or `@return` blocks** (e.g., `/** @param {string} user */`). This is redundant in TypeScript.
+- **Add Information:** Comments must add information, not just restate the code.
+
+*Source: [Google TypeScript Style Guide](https://google.github.io/styleguide/tsguide.html)*
diff --git a/conductor/product-guidelines.md b/conductor/product-guidelines.md
new file mode 100644
index 0000000..bf362ec
--- /dev/null
+++ b/conductor/product-guidelines.md
@@ -0,0 +1,101 @@
+# Product Guidelines: Humanizer (Multi-Agent Adapters)
+
+## Purpose
+
+These guidelines define how Humanizer should behave when packaged as workflows/skills for multiple agent environments, while keeping `SKILL.md` unchanged as the canonical source of truth.
+
+## Default Editing Stance: Voice-Matching
+
+- Preserve the author’s tone, register, and intent.
+- Remove “AI voice” patterns without flattening personality.
+- Do not “upgrade” style into a single house voice; match what’s already there.
+
+## Hard Constraints (Do Not Change)
+
+### 1) Technical correctness (literal invariants)
+
+Do not alter any of the following, anywhere in the text:
+
+- Anything inside inline code/backticks (e.g., `foo_bar`, `--flag`, `path/to/file`)
+- Anything inside fenced code blocks (``` ... ```)
+- URLs (including query strings), file paths, version strings, hashes/IDs
+- API names, identifiers, CLI commands/flags, config keys, error messages
+
+If prose surrounds literals, rewrite only the prose and keep literals exact.
+
+### 2) Facts and sourcing
+
+- Do not invent specifics (names, dates, statistics, studies, quotes, “according to…”).
+- Do not add citations or imply authority.
+- If the input is vague, make it cleaner and more direct, but do not fabricate details.
+
+### 3) Intent and stance
+
+- Do not soften opinions, add forced optimism, or introduce hedging that wasn’t present.
+- Do not add polite chatbot filler (“hope this helps”, “great question”, etc.).
+
+### 4) Preserve formatting and structure
+
+Unless required for clarity, keep structure intact:
+
+- Markdown headings, lists, tables, blockquotes
+- Link text and link targets
+- Paragraph breaks (avoid unnecessary reflow)
+- Ordering of sections and bullets
+
+Prefer localized rewrites over restructuring.
+
+## What Humanizer Should Change
+
+- Remove or rewrite patterns called out in `SKILL.md` (e.g., significance inflation, promotional phrasing, vague attributions, superficial -ing clauses, forced rule-of-three rhythm, etc.).
+- Prefer simpler constructions when they sound natural *for the existing voice*.
+- Increase specificity only when it already exists in the input; otherwise tighten.
+
+## Output Requirements (for adapters)
+
+Always output:
+
+1) The rewritten text
+2) A short change summary
+
+### Change Summary Format
+
+- 3–7 bullets maximum
+- Pattern-oriented phrasing (e.g., “Removed significance inflation”, “Cut filler phrases”, “Replaced vague attributions with direct phrasing”)
+- No meta-chatter (“As an AI…”, “Hope this helps…”, “Let me know…”)
+
+## When Uncertain
+
+If you can’t rewrite without risking technical correctness, factual invention, or stance change:
+
+- Prefer a conservative edit (or leave the sentence) rather than “improving” it.
+
+## Drift Control (keep adapters in sync)
+
+- Adapters must reference the `SKILL.md` `version:` they were derived from.
+- Adapters must include a simple “last synced” marker (date) so drift is visible.
+- If instructions conflict between an adapter and `SKILL.md`, `SKILL.md` wins.
+
+## Voice-Matching Example (same meaning, different voices)
+
+Input (casual):
+> This update is honestly kind of weird, but it works.
+
+Output:
+> This update is honestly kind of weird, but it works.
+
+- Removed filler phrases and inflated framing
+- Kept stance and casual tone
+
+Input (formal):
+> The change is unusual, but it functions as intended.
+
+Output:
+> The change is unusual, but it functions as intended.
+
+- Removed unnecessary embellishment
+- Preserved formal tone
+
+## Consistency Across Environments
+
+- The same input should yield materially similar rewrites across Codex CLI, Gemini CLI, VS Code, and other supported tools, modulo each tool’s formatting constraints.
diff --git a/conductor/product.md b/conductor/product.md
new file mode 100644
index 0000000..a392830
--- /dev/null
+++ b/conductor/product.md
@@ -0,0 +1,59 @@
+# Product Guide: Humanizer (Agent-Agnostic Skill/Workflow Pack)
+
+## Summary
+
+Humanizer is a set of writing-editing instructions that removes common “AI voice” patterns from text while preserving meaning and tone. Today it is packaged as a Claude Code skill (`SKILL.md`). The next step is to expand it into a multi-agent deliverable that can be used consistently across popular coding agents, while keeping `SKILL.md` as the canonical source of truth.
+
+## Primary Users
+
+- People using coding agents who want their writing to sound natural and human (docs, READMEs, PRDs, changelogs, comments, emails)
+- Maintainers who want a consistent editing workflow across multiple agent environments
+
+## Target Environments (Initial)
+
+- OpenAI Codex CLI
+- Gemini CLI
+- Google Antigravity
+- VS Code
+
+## Goals
+
+- Keep `SKILL.md` as the canonical, most detailed definition of Humanizer behavior.
+- Produce “skills” or “workflows” for each target environment that preserve the same editing intent and pattern coverage.
+- Make it easy to apply Humanizer consistently across agents without rewriting or manually re-syncing the instruction set.
+
+## Non-Goals (for initial rollout)
+
+- Rewriting the underlying Humanizer guidance into a fundamentally different editorial philosophy.
+- Building a full standalone rewriting app; focus remains on agent-facing skills/workflows.
+
+## Key Product Decisions
+
+- Single source of truth: `SKILL.md`
+- Adapter strategy: generate or maintain thin, environment-specific wrappers that reference/derive from the canonical rules.
+
+## Deliverables
+
+- Canonical:
+  - `SKILL.md` remains the primary, authoritative instruction document.
+- Environment adapters (format depends on each environment’s supported mechanism):
+  - Codex CLI: repo instructions/workflow that can be invoked as a consistent “Humanizer” behavior.
+  - Gemini CLI: skill/workflow wrapper aligned with Gemini’s conventions.
+  - VS Code: workflow/instructions packaged in a way that is easy to apply during editing.
+  - Google Antigravity: workflow/instructions packaged in its supported format.
+
+## Quality Bar
+
+- Adapters remain consistent with `SKILL.md` in:
+  - Pattern coverage (the same core “AI writing signs”)
+  - Output expectations (rewrite + optional brief change summary)
+  - Tone control (preserve intended voice; avoid sterile or robotic rewrites)
+- Documentation clearly states:
+  - Which file is canonical (`SKILL.md`)
+  - What each adapter is for and how to use it
+
+## Success Criteria
+
+- A user can use Humanizer in each target environment with minimal friction.
+- Updates to `SKILL.md` can be propagated to adapters without drift.
+- Users report the output sounds more natural without losing meaning or context.
diff --git a/conductor/setup_state.json b/conductor/setup_state.json
new file mode 100644
index 0000000..00fd665
--- /dev/null
+++ b/conductor/setup_state.json
@@ -0,0 +1 @@
+{"last_successful_step": "3.3_initial_track_generated"}
diff --git a/conductor/tech-stack.md b/conductor/tech-stack.md
new file mode 100644
index 0000000..5b79f8c
--- /dev/null
+++ b/conductor/tech-stack.md
@@ -0,0 +1,19 @@
+# Tech Stack: Humanizer (Multi-Agent Adapters)
+
+## Current State (Brownfield)
+
+- **Primary artifact:** Markdown (`SKILL.md`) containing the canonical Humanizer instructions.
+- **Repository type:** Documentation-only; no runtime language, package manifests, or build tooling detected.
+- **Consumption model:** Agent tools read prompt/instruction files (e.g., skills/workflow instructions).
+
+## Target Integrations (Planned)
+
+- OpenAI Codex CLI
+- Gemini CLI
+- Google Antigravity
+- VS Code
+
+## Constraints
+
+- `SKILL.md` remains the canonical source of truth and should not be modified as part of adapter work.
+- Adapters should be lightweight wrappers that reference/derive from the canonical rules.
diff --git a/conductor/tracks.md b/conductor/tracks.md
new file mode 100644
index 0000000..d4bd269
--- /dev/null
+++ b/conductor/tracks.md
@@ -0,0 +1,37 @@
+# Project Tracks
+
+This file tracks all major tracks for the project. Each track has its own detailed plan in its respective folder.
+
+---
+
+## Archived Tracks
+
+## [x] Track: DevOps and Quality Engineering (da248f2)
+
+*Link: [./conductor/tracks/devops-quality_20260131/](./conductor/tracks/devops-quality_20260131/)*
+
+## [x] Track: Universal Automated Adapters
+
+*Link: [./conductor/tracks/universal-automated-adapters_20260131/](./conductor/tracks/universal-automated-adapters_20260131/)*
+
+## [x] Track: Expand Humanizer adapters to Qwen CLI and Copilot
+
+*Link: [./conductor/tracks/adapters-expansion_20260131/](./conductor/tracks/adapters-expansion_20260131/)*
+
+## [x] Track: Create Google Antigravity rules/workflows adapter guidance for Humanizer
+
+*Link: [./conductor/tracks/antigravity-rules-workflows_20260131/](./conductor/tracks/antigravity-rules-workflows_20260131/)*
+
+## [x] Track: Create a Google Antigravity skill adapter for Humanizer
+
+*Link: [./conductor/tracks/antigravity-skills_20260131/](./conductor/tracks/antigravity-skills_20260131/)*
+
+## [x] Track: Create a Gemini CLI extension adapter for Humanizer
+
+*Link: [./conductor/tracks/gemini-extension_20260131/](./conductor/tracks/gemini-extension_20260131/)*
+
+## [x] Track: Build multi-agent Humanizer adapters (Codex CLI, Gemini CLI, Google Antigravity, VS Code) while keeping SKILL.md canonical and unchanged (e2c47dc)
+
+## [ ] Track: Adopt upstream pull requests #3, #4, and #5 from blader/humanizer
+
+*Link: [./conductor/tracks/adopt-upstream-prs_20260131/](./conductor/tracks/adopt-upstream-prs_20260131/)*
diff --git a/conductor/tracks/adapters-expansion_20260131/metadata.json b/conductor/tracks/adapters-expansion_20260131/metadata.json
new file mode 100644
index 0000000..de21924
--- /dev/null
+++ b/conductor/tracks/adapters-expansion_20260131/metadata.json
@@ -0,0 +1,6 @@
+{
+  "track_id": "adapters-expansion_20260131",
+  "name": "Expand Humanizer adapters to Qwen CLI and Copilot",
+  "status": "planned",
+  "created_at": "2026-01-31"
+}
diff --git a/conductor/tracks/adapters-expansion_20260131/plan.md b/conductor/tracks/adapters-expansion_20260131/plan.md
new file mode 100644
index 0000000..9c9e1d0
--- /dev/null
+++ b/conductor/tracks/adapters-expansion_20260131/plan.md
@@ -0,0 +1,19 @@
+# Plan: Expand Humanizer adapters to Qwen CLI and Copilot
+
+## Phase 1: Create Adapter Files
+
+- [x] Task: Create `adapters/qwen-cli/` directory and `QWEN.md` template
+- [x] Task: Create `adapters/copilot/` directory and `COPILOT.md` template
+- [x] Task: Conductor - Agent Verification 'Phase 1: Create Adapter Files' (Protocol in workflow.md)
+
+## Phase 2: Update Automation
+
+- [x] Task: Update `scripts/sync-adapters.ps1` to include Qwen and Copilot paths
+- [x] Task: Update `scripts/validate-adapters.ps1` to include Qwen and Copilot paths
+- [x] Task: Run sync and validation to verify integration
+- [x] Task: Conductor - Agent Verification 'Phase 2: Update Automation' (Protocol in workflow.md)
+
+## Phase 3: Documentation and Wrap-up
+
+- [x] Task: Update `README.md` with new adapter usage
+- [x] Task: Conductor - Agent Verification 'Phase 3: Documentation and Wrap-up' (Protocol in workflow.md)
diff --git a/conductor/tracks/adapters-expansion_20260131/spec.md b/conductor/tracks/adapters-expansion_20260131/spec.md
new file mode 100644
index 0000000..cc775f8
--- /dev/null
+++ b/conductor/tracks/adapters-expansion_20260131/spec.md
@@ -0,0 +1,20 @@
+# Spec: Expand Humanizer adapters to Qwen CLI and Copilot
+
+## Overview
+
+Add adapters for Qwen CLI and GitHub Copilot to allow Humanizer usage in those environments. These adapters will follow the existing abstraction pattern, referencing the canonical `SKILL.md`.
+
+## Requirements
+
+- Create `adapters/qwen-cli/QWEN.md` with appropriate instructions and metadata.
+- Create `adapters/copilot/COPILOT.md` with appropriate instructions and metadata.
+- Update `scripts/sync-adapters.ps1` to auto-sync content/metadata to these new adapters.
+- Update `scripts/validate-adapters.ps1` to include these new adapters in validation.
+- Update `README.md` with usage instructions for Qwen and Copilot.
+
+## Acceptance Criteria
+
+- New adapter files exist and contain valid metadata pointing to `SKILL.md`.
+- `sync-adapters` script successfully updates these files.
+- `validate-adapters` script passes when run.
+- `README.md` documents the new adapters.
diff --git a/conductor/tracks/adopt-upstream-prs_20260131/index.md b/conductor/tracks/adopt-upstream-prs_20260131/index.md
new file mode 100644
index 0000000..dbf77d2
--- /dev/null
+++ b/conductor/tracks/adopt-upstream-prs_20260131/index.md
@@ -0,0 +1,5 @@
+# Track adopt-upstream-prs_20260131 Context
+
+- [Specification](./spec.md)
+- [Implementation Plan](./plan.md)
+- [Metadata](./metadata.json)
diff --git a/conductor/tracks/adopt-upstream-prs_20260131/metadata.json b/conductor/tracks/adopt-upstream-prs_20260131/metadata.json
new file mode 100644
index 0000000..729f885
--- /dev/null
+++ b/conductor/tracks/adopt-upstream-prs_20260131/metadata.json
@@ -0,0 +1,8 @@
+{
+  "track_id": "adopt-upstream-prs_20260131",
+  "type": "feature",
+  "status": "new",
+  "created_at": "2026-01-31T22:18:00+11:00",
+  "updated_at": "2026-01-31T22:18:00+11:00",
+  "description": "Adopt upstream pull requests #3, #4, and #5 from blader/humanizer"
+}
diff --git a/conductor/tracks/adopt-upstream-prs_20260131/plan.md b/conductor/tracks/adopt-upstream-prs_20260131/plan.md
new file mode 100644
index 0000000..39e36cc
--- /dev/null
+++ b/conductor/tracks/adopt-upstream-prs_20260131/plan.md
@@ -0,0 +1,31 @@
+# Plan: Adopt Upstream Pull Requests
+
+## Phase 1: Adopt PR #3 (Fix YAML)
+- [x] Task: Update `SKILL.md` frontmatter (rename "excessive conjunctive phrases" to "filler phrases")
+- [x] Task: Bump `SKILL.md` version to `2.1.2`
+- [x] Task: Update `README.md` (if applicable per PR)
+- [x] Task: Run `scripts/sync-adapters.ps1` to propagate changes
+- [x] Task: Run `scripts/validate-adapters.ps1` to ensure integrity
+- [x] Task: Conductor - Automated Verification 'Phase 1: Adopt PR #3' (Protocol in workflow.md)
+
+## Phase 2: Adopt PR #4 (Fix Grammar)
+- [x] Task: Apply comma splice fixes and other grammar corrections to:
+    - [x] `SKILL.md`
+    - [x] `README.md`
+    - [x] `WARP.md`
+- [x] Task: Run `markdownlint` (via `pre-commit` or manual check) to verify prose quality
+- [x] Task: Run `scripts/sync-adapters.ps1`
+- [x] Task: Conductor - Automated Verification 'Phase 2: Adopt PR #4' (Protocol in workflow.md)
+
+## Phase 3: Adopt PR #5 (Add "Primary Single Quotes" Pattern)
+- [x] Task: Add Pattern #19 ("Primary Single Quotes") to `SKILL.md` and renumber subsequent patterns
+- [x] Task: Bump `SKILL.md` version to `2.2.0`
+- [x] Task: Update `README.md` detection table and version history
+- [x] Task: Update `WARP.md` summary
+- [x] Task: Run `scripts/sync-adapters.ps1`
+- [x] Task: Run `scripts/validate-adapters.ps1`
+- [x] Task: Conductor - Automated Verification 'Phase 3: Adopt PR #5' (Protocol in workflow.md)
+
+## Phase 4: Final Verification
+- [x] Task: Run full test suite (if available) or manual spot check of an adapter
+- [x] Task: Conductor - Automated Verification 'Phase 4: Final Verification' (Protocol in workflow.md)
diff --git a/conductor/tracks/adopt-upstream-prs_20260131/spec.md b/conductor/tracks/adopt-upstream-prs_20260131/spec.md
new file mode 100644
index 0000000..96e28ef
--- /dev/null
+++ b/conductor/tracks/adopt-upstream-prs_20260131/spec.md
@@ -0,0 +1,37 @@
+# Specification: Adopt Upstream Pull Requests
+
+## Overview
+This track aims to synchronize the local repository with three specific upstream pull requests from `blader/humanizer`. The goal is to incorporate community fixes and improvements while ensuring all downstream adapters (Gemini, Antigravity, VS Code, etc.) are kept in sync after each change.
+
+## Upstream Changes
+1.  **PR #3: Fix YAML description**
+    *   Rename "excessive conjunctive phrases" to "filler phrases" in the YAML frontmatter of `SKILL.md`.
+    *   Bump version to `2.1.2`.
+2.  **PR #4: Fix grammatical errors**
+    *   Fix comma splices and missing commas in `SKILL.md` and `README.md`.
+    *   Standardize quotes in `WARP.md`.
+    *   Formatting fixes (blank lines).
+3.  **PR #5: Add "Primary Single Quotes" detection**
+    *   Add new detection Pattern #19 ("Primary Single Quotes") to `SKILL.md`.
+    *   Renumber subsequent patterns.
+    *   Bump version to `2.2.0`.
+    *   Update `README.md` and `WARP.md` tables.
+
+## Requirements
+
+### Functional
+*   **Sequential Adoption:** Changes must be applied one PR at a time in the order: #3 -> #4 -> #5.
+*   **Continuous Synchronization:** The `scripts/sync-adapters.ps1` script must be run successfully after adopting *each* PR to propagate changes to all adapters.
+*   **Version Integrity:** Ensure `SKILL.md` version versions match the upstream PR recommendations (2.1.2 -> 2.2.0).
+
+### Non-Functional
+*   **Verification:** Verify that local changes match the intent of the upstream PRs.
+*   **Adapter Validation:** Ensure `scripts/validate-adapters.ps1` passes after each sync.
+*   **Linting:** Ensure changes pass `markdownlint` checks.
+
+## Acceptance Criteria
+*   `SKILL.md` frontmatter uses "filler phrases".
+*   Grammar fixes from PR #4 are present.
+*   Pattern #19 is documented in `SKILL.md` and `README.md`, and version is `2.2.0`.
+*   All adapter files (e.g., `adapters/gemini-extension/GEMINI.md`, `adapters/antigravity-skill/SKILL.md`) reflect these changes.
+*   The repository is clean and ready to be pushed.
diff --git a/conductor/tracks/antigravity-rules-workflows_20260131/metadata.json b/conductor/tracks/antigravity-rules-workflows_20260131/metadata.json
new file mode 100644
index 0000000..0fe49d4
--- /dev/null
+++ b/conductor/tracks/antigravity-rules-workflows_20260131/metadata.json
@@ -0,0 +1,8 @@
+{
+  "updated_at": "2026-01-31T00:00:00Z",
+  "created_at": "2026-01-31T00:00:00Z",
+  "description": "Create Google Antigravity rules/workflows adapter guidance for Humanizer",
+  "type": "feature",
+  "status": "new",
+  "track_id": "antigravity-rules-workflows_20260131"
+}
diff --git a/conductor/tracks/antigravity-rules-workflows_20260131/plan.md b/conductor/tracks/antigravity-rules-workflows_20260131/plan.md
new file mode 100644
index 0000000..dc4cd3c
--- /dev/null
+++ b/conductor/tracks/antigravity-rules-workflows_20260131/plan.md
@@ -0,0 +1,26 @@
+# Plan: Create Google Antigravity rules/workflows adapter guidance for Humanizer
+
+## Phase 1: Define rules/workflows guidance
+
+- [x] Task: Extract Antigravity rules/workflows requirements from the reference URL
+- [x] Task: Decide rule/workflow templates and naming
+- [x] Task: Define adapter metadata contract (version + last synced)
+- [x] Task: Conductor - Agent Verification 'Phase 1: Define rules/workflows guidance' (Protocol in workflow.md)
+
+## Phase 2: Implement templates
+
+- [x] Task: Add rule templates for always-on guidance
+- [x] Task: Add workflow templates for user-triggered guidance
+- [x] Task: Conductor - Agent Verification 'Phase 2: Implement templates' (Protocol in workflow.md)
+
+## Phase 3: Validation and documentation
+
+- [x] Task: Add validation to ensure metadata matches SKILL.md version
+- [x] Task: Update README with Antigravity rules/workflows usage
+- [x] Task: Conductor - Agent Verification 'Phase 3: Validation and documentation' (Protocol in workflow.md)
+
+## Phase 4: Release readiness
+
+- [x] Task: Run validation and verify SKILL.md unchanged
+- [x] Task: Record adapter versioning approach (doc-only)
+- [x] Task: Conductor - Agent Verification 'Phase 4: Release readiness' (Protocol in workflow.md)
diff --git a/conductor/tracks/antigravity-rules-workflows_20260131/spec.md b/conductor/tracks/antigravity-rules-workflows_20260131/spec.md
new file mode 100644
index 0000000..36fa6df
--- /dev/null
+++ b/conductor/tracks/antigravity-rules-workflows_20260131/spec.md
@@ -0,0 +1,28 @@
+# Spec: Create Google Antigravity rules/workflows adapter guidance for Humanizer
+
+## Overview
+
+Provide Antigravity rule and workflow scaffolding so Humanizer guidance can be applied via always-on rules and user-triggered workflows, without altering the canonical SKILL.md.
+
+## References
+
+- <http://codelabs.developers.google.com/getting-started-google-antigravity#8>
+
+## Requirements
+
+- Keep SKILL.md unchanged and canonical.
+- Add rule/workflow guidance and example files aligned with Antigravity locations.
+- Provide adapter metadata: SKILL.md version reference and last synced date.
+- Include instructions for global vs workspace rule/workflow placement.
+- Preserve technical literals in adapter guidance.
+
+## Acceptance Criteria
+
+- Repository includes example rule/workflow files or templates ready to copy into Antigravity locations.
+- Documentation explains how to enable rules and workflows in workspace and global contexts.
+- Adapter metadata references the SKILL.md version and last synced date.
+
+## Out of Scope
+
+- Changing SKILL.md contents.
+- Automatic installation scripts.
diff --git a/conductor/tracks/antigravity-skills_20260131/metadata.json b/conductor/tracks/antigravity-skills_20260131/metadata.json
new file mode 100644
index 0000000..67c5ceb
--- /dev/null
+++ b/conductor/tracks/antigravity-skills_20260131/metadata.json
@@ -0,0 +1,8 @@
+{
+  "updated_at": "2026-01-31T00:00:00Z",
+  "created_at": "2026-01-31T00:00:00Z",
+  "description": "Create a Google Antigravity skill adapter for Humanizer",
+  "type": "feature",
+  "status": "new",
+  "track_id": "antigravity-skills_20260131"
+}
diff --git a/conductor/tracks/antigravity-skills_20260131/plan.md b/conductor/tracks/antigravity-skills_20260131/plan.md
new file mode 100644
index 0000000..4ce1025
--- /dev/null
+++ b/conductor/tracks/antigravity-skills_20260131/plan.md
@@ -0,0 +1,26 @@
+# Plan: Create a Google Antigravity skill adapter for Humanizer
+
+## Phase 1: Define skill package
+
+- [x] Task: Extract Antigravity skill requirements from the reference URL
+- [x] Task: Decide skill directory layout and naming
+- [x] Task: Define adapter metadata contract (version + last synced)
+- [x] Task: Conductor - Agent Verification 'Phase 1: Define skill package' (Protocol in workflow.md)
+
+## Phase 2: Implement skill package
+
+- [x] Task: Add Antigravity skill directory and required files
+- [x] Task: Add README or usage guidance for the skill
+- [x] Task: Conductor - Agent Verification 'Phase 2: Implement skill package' (Protocol in workflow.md)
+
+## Phase 3: Validation and documentation
+
+- [x] Task: Add validation to ensure metadata matches SKILL.md version
+- [x] Task: Update README with Antigravity skill usage
+- [x] Task: Conductor - Agent Verification 'Phase 3: Validation and documentation' (Protocol in workflow.md)
+
+## Phase 4: Release readiness
+
+- [x] Task: Run validation and verify SKILL.md unchanged
+- [x] Task: Record adapter versioning approach (doc-only)
+- [x] Task: Conductor - Agent Verification 'Phase 4: Release readiness' (Protocol in workflow.md)
diff --git a/conductor/tracks/antigravity-skills_20260131/spec.md b/conductor/tracks/antigravity-skills_20260131/spec.md
new file mode 100644
index 0000000..ff46b66
--- /dev/null
+++ b/conductor/tracks/antigravity-skills_20260131/spec.md
@@ -0,0 +1,28 @@
+# Spec: Create a Google Antigravity skill adapter for Humanizer
+
+## Overview
+
+Create a Google Antigravity skill package that references the existing Humanizer SKILL.md as canonical guidance, without modifying it. The skill should be installable at the workspace level and documented for users.
+
+## References
+
+- <https://codelabs.developers.google.com/getting-started-with-antigravity-skills#9>
+
+## Requirements
+
+- Keep SKILL.md unchanged and canonical.
+- Add an Antigravity skill directory with required files and optional supporting assets/scripts.
+- Provide adapter metadata: SKILL.md version reference and last synced date.
+- Include instructions for workspace installation location.
+- Preserve technical literals in adapter guidance.
+
+## Acceptance Criteria
+
+- Repository includes an Antigravity skill package that can be copied into a workspace skill directory.
+- Documentation shows how to enable and use the skill.
+- Adapter metadata references the SKILL.md version and last synced date.
+
+## Out of Scope
+
+- Changing SKILL.md contents.
+- Publishing outside the repo.
diff --git a/conductor/tracks/devops-quality_20260131/metadata.json b/conductor/tracks/devops-quality_20260131/metadata.json
new file mode 100644
index 0000000..fb65c65
--- /dev/null
+++ b/conductor/tracks/devops-quality_20260131/metadata.json
@@ -0,0 +1,7 @@
+{
+  "track_id": "devops-quality_20260131",
+  "name": "DevOps and Quality Engineering",
+  "status": "archived",
+  "created_at": "2026-01-31",
+  "updated_at": "2026-01-31"
+}
diff --git a/conductor/tracks/devops-quality_20260131/plan.md b/conductor/tracks/devops-quality_20260131/plan.md
new file mode 100644
index 0000000..a3d0116
--- /dev/null
+++ b/conductor/tracks/devops-quality_20260131/plan.md
@@ -0,0 +1,28 @@
+# Plan: DevOps and Quality Engineering
+
+## Phase 1: Python Migration & Infrastructure [checkpoint: 799280f]
+
+- [x] Task: Create `pyproject.toml` with strict Ruff and Mypy configurations (ea776e6)
+- [x] Task: Port `sync-adapters.ps1` to `scripts/sync_adapters.py` (c493aef)
+- [x] Task: Port `validate-adapters.ps1` to `scripts/validate_adapters.py` (2c382aa)
+- [x] Task: Port `install-adapters.ps1` to `scripts/install_adapters.py` (13225d5)
+- [x] Task: Conductor - Agent Verification 'Phase 1: Python Migration & Infrastructure' (799280f)
+- [ ] Task: Port `install-adapters.ps1` to `scripts/install_adapters.py`
+- [ ] Task: Conductor - Agent Verification 'Phase 1: Python Migration & Infrastructure'
+
+## Phase 2: Testing & Coverage [checkpoint: f2806c8]
+
+- [x] Task: Set up `pytest` and `pytest-cov` (2d5fb45)
+- [x] Task: Write tests for all Python scripts to achieve 100% coverage (2d5fb45)
+- [x] Task: Conductor - Agent Verification 'Phase 2: Testing & Coverage' (f2806c8)
+
+## Phase 3: Pre-commit & Prose Linting [checkpoint: 2f63a6f]
+
+- [x] Task: Configure `.pre-commit-config.yaml` with Ruff, Mypy, and Markdownlint (5067d34)
+- [x] Task: Conductor - Agent Verification 'Phase 3: Pre-commit & Prose Linting' (2f63a6f)
+
+## Phase 4: CI/CD [checkpoint: 724add0]
+
+- [x] Task: Create `.github/workflows/ci.yml` for automated validation (cb68b7c)
+
+- [x] Task: Conductor - Agent Verification 'Phase 4: CI/CD' (724add0)
diff --git a/conductor/tracks/devops-quality_20260131/spec.md b/conductor/tracks/devops-quality_20260131/spec.md
new file mode 100644
index 0000000..32b0470
--- /dev/null
+++ b/conductor/tracks/devops-quality_20260131/spec.md
@@ -0,0 +1,30 @@
+# Spec: DevOps and Quality Engineering
+
+## Overview
+
+Implement a high-quality development environment for the Humanizer project, including strict linting, type checking, automated testing with 100% coverage, pre-commit hooks, and CI/CD.
+
+## Requirements
+
+- **Python Migration:**
+  - Port PowerShell synchronization, validation, and installation scripts to Python to enable advanced tooling (Ruff, Mypy).
+- **Static Analysis (Strict):**
+  - **Ruff:** Configure for strict linting and formatting.
+  - **Mypy:** Configure for strict type checking.
+- **Testing & Coverage:**
+  - Use `pytest` for unit testing the Python "glue" scripts.
+  - Achieve 100% code coverage.
+- **Prose Linting:**
+  - Implement Markdown linting to ensure quality across `SKILL.md` and adapters.
+- **Pre-commit Hooks:**
+  - Automate Ruff, Mypy, and validation checks before every commit.
+- **CI/CD:**
+  - GitHub Actions workflow to run all quality gates on push and pull requests.
+
+## Acceptance Criteria
+
+- `scripts/` contains Python equivalents of all PS1 scripts.
+- `ruff check .` and `mypy .` pass with zero warnings in strict mode.
+- `pytest --cov` reports 100% coverage.
+- Pre-commit hooks are configured and functional.
+- CI/CD workflow passes on GitHub.
diff --git a/conductor/tracks/gemini-extension_20260131/implementation.md b/conductor/tracks/gemini-extension_20260131/implementation.md
new file mode 100644
index 0000000..8d08735
--- /dev/null
+++ b/conductor/tracks/gemini-extension_20260131/implementation.md
@@ -0,0 +1,15 @@
+# Gemini Extension Implementation Notes
+
+## Manifest and Entry Point
+
+- Manifest: `adapters/gemini-extension/gemini-extension.json`
+- Entry point: command prompt file `adapters/gemini-extension/commands/humanizer/humanize.toml`
+- Context file: `adapters/gemini-extension/GEMINI.md`
+
+## Context File
+
+- `adapters/gemini-extension/GEMINI.md` contains adapter metadata and core Humanizer instructions.
+
+## Commands
+
+- `adapters/gemini-extension/commands/humanizer/humanize.toml` provides the saved prompt to run Humanizer.
diff --git a/conductor/tracks/gemini-extension_20260131/layout.md b/conductor/tracks/gemini-extension_20260131/layout.md
new file mode 100644
index 0000000..7c238e2
--- /dev/null
+++ b/conductor/tracks/gemini-extension_20260131/layout.md
@@ -0,0 +1,14 @@
+# Gemini Extension Layout
+
+## Chosen Layout
+
+- Extension root: `adapters/gemini-extension/`
+- Manifest: `adapters/gemini-extension/gemini-extension.json`
+- Context file: `adapters/gemini-extension/GEMINI.md`
+- Commands: `adapters/gemini-extension/commands/humanizer/humanize.toml`
+
+## Naming
+
+- Extension name: `humanizer-extension`
+- Command group: `humanizer`
+- Command name: `humanize`
diff --git a/conductor/tracks/gemini-extension_20260131/metadata-contract.md b/conductor/tracks/gemini-extension_20260131/metadata-contract.md
new file mode 100644
index 0000000..1297728
--- /dev/null
+++ b/conductor/tracks/gemini-extension_20260131/metadata-contract.md
@@ -0,0 +1,7 @@
+# Adapter Metadata Contract (Gemini Extension)
+
+Reuse the shared contract from the core track:
+
+- `conductor/tracks/humanizer-adapters_20260125/adapter-metadata.md`
+
+This extension embeds the metadata block at the top of `adapters/gemini-extension/GEMINI.md`.
diff --git a/conductor/tracks/gemini-extension_20260131/metadata.json b/conductor/tracks/gemini-extension_20260131/metadata.json
new file mode 100644
index 0000000..c14668b
--- /dev/null
+++ b/conductor/tracks/gemini-extension_20260131/metadata.json
@@ -0,0 +1,8 @@
+{
+  "updated_at": "2026-01-31T00:00:00Z",
+  "created_at": "2026-01-31T00:00:00Z",
+  "description": "Create a Gemini CLI extension adapter for Humanizer",
+  "type": "feature",
+  "status": "in_progress",
+  "track_id": "gemini-extension_20260131"
+}
diff --git a/conductor/tracks/gemini-extension_20260131/plan.md b/conductor/tracks/gemini-extension_20260131/plan.md
new file mode 100644
index 0000000..1c84ccc
--- /dev/null
+++ b/conductor/tracks/gemini-extension_20260131/plan.md
@@ -0,0 +1,27 @@
+# Plan: Create a Gemini CLI extension adapter for Humanizer
+
+## Phase 1: Define extension structure [checkpoint: 99c6113]
+
+- [x] Task: Extract Gemini CLI extension requirements from the reference URL (b011e1d)
+- [x] Task: Decide extension folder layout and naming (9d802a2)
+- [x] Task: Define adapter metadata contract (version + last synced) (750d465)
+- [x] Task: Conductor - Agent Verification 'Phase 1: Define extension structure' (Protocol in workflow.md)
+
+## Phase 2: Implement extension files
+
+- [x] Task: Add Gemini extension manifest and entrypoint (4f78e6a)
+- [x] Task: Add GEMINI.md or required context file (e84d275)
+- [x] Task: Wire commands or instructions to apply Humanizer (52c0176)
+- [x] Task: Conductor - Agent Verification 'Phase 2: Implement extension files' (Protocol in workflow.md)
+
+## Phase 3: Validation and documentation
+
+- [x] Task: Add validation to ensure metadata matches SKILL.md version
+- [x] Task: Update README with Gemini CLI extension usage
+- [x] Task: Conductor - Agent Verification 'Phase 3: Validation and documentation' (Protocol in workflow.md)
+
+## Phase 4: Release readiness
+
+- [x] Task: Run validation and verify SKILL.md unchanged
+- [x] Task: Record adapter versioning approach (doc-only)
+- [x] Task: Conductor - Agent Verification 'Phase 4: Release readiness' (Protocol in workflow.md)
diff --git a/conductor/tracks/gemini-extension_20260131/requirements.md b/conductor/tracks/gemini-extension_20260131/requirements.md
new file mode 100644
index 0000000..f421009
--- /dev/null
+++ b/conductor/tracks/gemini-extension_20260131/requirements.md
@@ -0,0 +1,19 @@
+# Gemini CLI Extension Requirements (Summary)
+
+## Source
+
+- <https://geminicli.com/docs/extensions/writing-extensions/>
+
+## Key Requirements
+
+- Use `gemini extensions new <name>` to scaffold a new extension.
+- Extension manifest file: `gemini-extension.json`.
+- Optional context file: `GEMINI.md` (custom instructions loaded by the extension).
+- Custom commands are stored under `commands/` using TOML prompt files.
+- During local development, run `gemini extensions link .` in the extension folder.
+
+## Minimal Adapter Needs
+
+- `gemini-extension.json` with name and version.
+- `GEMINI.md` containing Humanizer adapter instructions and metadata.
+- Optional saved command (e.g., `commands/humanizer/humanize.toml`).
diff --git a/conductor/tracks/gemini-extension_20260131/spec.md b/conductor/tracks/gemini-extension_20260131/spec.md
new file mode 100644
index 0000000..5d75821
--- /dev/null
+++ b/conductor/tracks/gemini-extension_20260131/spec.md
@@ -0,0 +1,28 @@
+# Spec: Create a Gemini CLI extension adapter for Humanizer
+
+## Overview
+
+Create a Gemini CLI extension that wraps the existing Humanizer SKILL.md without modifying it. The adapter should follow Gemini CLI extension conventions and provide a clear entrypoint for users to apply the Humanizer workflow.
+
+## References
+
+- <https://geminicli.com/docs/extensions/writing-extensions/>
+
+## Requirements
+
+- Keep SKILL.md unchanged and canonical.
+- Add Gemini CLI extension artifacts (manifest, entrypoint, optional commands) that reference SKILL.md for the behavioral source of truth.
+- Provide a GEMINI.md or equivalent context file if required by Gemini CLI extensions.
+- Include adapter metadata: SKILL.md version reference and last synced date.
+- Preserve technical literals (inline code, fenced code blocks, URLs, paths, identifiers) in adapter guidance.
+
+## Acceptance Criteria
+
+- Repository includes a Gemini CLI extension directory with required files and a clear usage path.
+- Instructions explain how to install, link, and run the extension locally.
+- Adapter metadata references the SKILL.md version and last synced date.
+
+## Out of Scope
+
+- Publishing to an external registry.
+- Changing SKILL.md contents.
diff --git a/conductor/tracks/humanizer-adapters_20260125/adapter-core.md b/conductor/tracks/humanizer-adapters_20260125/adapter-core.md
new file mode 100644
index 0000000..91723b7
--- /dev/null
+++ b/conductor/tracks/humanizer-adapters_20260125/adapter-core.md
@@ -0,0 +1,34 @@
+# Shared Adapter Core Text
+
+Use this core text inside each adapter to keep behavior aligned with `SKILL.md`.
+
+## Canonical Source
+
+- The canonical behavior lives in `SKILL.md`. Do not modify it.
+- Adapters should quote or reference `SKILL.md` for the full rules.
+
+## Core Behavior (Adapter Instruction Snippet)
+
+"""
+You are the Humanizer editor.
+
+Primary instructions: follow the canonical rules in SKILL.md.
+
+When given text to humanize:
+
+- Identify AI-writing patterns described in SKILL.md.
+- Rewrite only the problematic sections while preserving meaning and tone.
+- Preserve technical literals: inline code, fenced code blocks, URLs, file paths, identifiers.
+- Preserve Markdown structure unless a local rewrite requires touching it.
+- Output the rewritten text, then a short bullet summary of changes.
+"""
+
+## Metadata Placement
+
+- Attach the adapter metadata block defined in `adapter-metadata.md`.
+- Keep metadata in a consistent location (top-level header or front matter) per adapter format.
+
+## Non-Goals
+
+- Do not introduce new editorial rules beyond SKILL.md.
+- Do not implement a standalone rewriting app.
diff --git a/conductor/tracks/humanizer-adapters_20260125/adapter-metadata.md b/conductor/tracks/humanizer-adapters_20260125/adapter-metadata.md
new file mode 100644
index 0000000..7a71f6f
--- /dev/null
+++ b/conductor/tracks/humanizer-adapters_20260125/adapter-metadata.md
@@ -0,0 +1,37 @@
+# Adapter Metadata Contract
+
+## Purpose
+
+Provide a consistent, machine-checkable metadata block for every adapter artifact derived from `SKILL.md`.
+
+## Required Fields
+
+- `skill_name`: Must match the `name` field in `SKILL.md`.
+- `skill_version`: Must match the `version` field in `SKILL.md`.
+- `last_synced`: ISO 8601 date (`YYYY-MM-DD`) indicating when the adapter was last aligned to `SKILL.md`.
+- `source_path`: Relative path to the canonical `SKILL.md` used.
+
+## Optional Fields
+
+- `source_sha`: Git commit SHA where `SKILL.md` was last verified.
+- `adapter_id`: Short identifier for the adapter (e.g., `codex-cli`, `gemini-extension`).
+- `adapter_format`: Human-readable format label (e.g., `AGENTS.md`, `Gemini extension`, `Antigravity skill`).
+
+## Example (YAML)
+
+```yaml
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: 2.1.1
+  last_synced: 2026-01-31
+  source_path: SKILL.md
+  source_sha: <git-sha>
+  adapter_id: gemini-extension
+  adapter_format: Gemini extension
+```
+
+## Validation Rules
+
+- `skill_name` and `skill_version` must match the values in `SKILL.md`.
+- `last_synced` must be a valid date.
+- `source_path` must resolve to the repository `SKILL.md`.
diff --git a/conductor/tracks/humanizer-adapters_20260125/inventory.md b/conductor/tracks/humanizer-adapters_20260125/inventory.md
new file mode 100644
index 0000000..d92abd3
--- /dev/null
+++ b/conductor/tracks/humanizer-adapters_20260125/inventory.md
@@ -0,0 +1,26 @@
+# Inventory: Target Environments and Adapter Formats
+
+## Goal
+
+Document the environments and the adapter artifact formats needed to ship Humanizer guidance across supported agents.
+
+## Environments
+
+- OpenAI Codex CLI
+- Gemini CLI
+- Google Antigravity
+- VS Code
+
+## Adapter Formats
+
+- Codex CLI: `AGENTS.md` (workspace instructions for Codex CLI agents).
+- Gemini CLI: Extension package (manifest + entrypoint + optional `GEMINI.md`).
+- Google Antigravity: Skill package directory (`SKILL.md` + optional `scripts/`, `references/`, `assets/`).
+- Google Antigravity Rules/Workflows: Rule and workflow templates (global + workspace placements).
+- VS Code: Workspace guidance (extension snippet or workspace instructions in repo).
+
+## References
+
+- Gemini CLI extensions: <https://geminicli.com/docs/extensions/writing-extensions/>
+- Antigravity skills: <https://codelabs.developers.google.com/getting-started-with-antigravity-skills#9>
+- Antigravity rules/workflows: <http://codelabs.developers.google.com/getting-started-google-antigravity#8>
diff --git a/conductor/tracks/humanizer-adapters_20260125/metadata.json b/conductor/tracks/humanizer-adapters_20260125/metadata.json
new file mode 100644
index 0000000..61d0fa0
--- /dev/null
+++ b/conductor/tracks/humanizer-adapters_20260125/metadata.json
@@ -0,0 +1,8 @@
+{
+  "updated_at": "2026-01-31T00:00:00Z",
+  "created_at": "2026-01-25T06:14:03Z",
+  "description": "Build multi-agent Humanizer adapters (Codex CLI, Gemini CLI, Google Antigravity, VS Code) while keeping SKILL.md canonical and unchanged",
+  "type": "feature",
+  "status": "archived",
+  "track_id": "humanizer-adapters_20260125"
+}
diff --git a/conductor/tracks/humanizer-adapters_20260125/plan.md b/conductor/tracks/humanizer-adapters_20260125/plan.md
new file mode 100644
index 0000000..69121f9
--- /dev/null
+++ b/conductor/tracks/humanizer-adapters_20260125/plan.md
@@ -0,0 +1,29 @@
+# Plan: Build multi-agent Humanizer adapters
+
+## Phase 1: Define adapter architecture [checkpoint: 4b15a2b]
+
+- [x] Task: Inventory target environments and adapter formats (afea8e8)
+- [x] Task: Define adapter metadata contract (version + last synced) (b412925)
+- [x] Task: Draft shared adapter core text (references SKILL.md) (1e8dfc9)
+- [ ] Task: Conductor - User Manual Verification 'Phase 1: Define adapter architecture' (Protocol in workflow.md)
+
+## Phase 2: Implement adapters [checkpoint: 39ef58b]
+
+- [x] Task: Add Codex CLI adapter (AGENTS.md/workflow instructions) (d240d65)
+- [x] Task: Add Gemini CLI adapter (prompt/workflow wrapper) (c7945c6)
+- [x] Task: Add VS Code adapter (workspace instructions/snippets) (0fb8fd0)
+- [x] Task: Add Google Antigravity adapter (workflow wrapper) (aebfe47)
+- [ ] Task: Conductor - User Manual Verification 'Phase 2: Implement adapters' (Protocol in workflow.md)
+
+## Phase 3: Drift control and validation [checkpoint: 389219d]
+
+- [x] Task: Write a validation script to check adapter metadata matches SKILL.md version (c471faa)
+- [x] Task: Add CI-friendly command to run validation (8598be2)
+- [x] Task: Update README to document adapters and sync process (158babb)
+- [ ] Task: Conductor - User Manual Verification 'Phase 3: Drift control and validation' (Protocol in workflow.md)
+
+## Phase 4: Release readiness [checkpoint: 1f06dcb]
+
+- [x] Task: Run validation and verify no changes to SKILL.md (7a37c65)
+- [x] Task: Tag/record adapter pack versioning approach (doc-only) (e3c81c9)
+- [ ] Task: Conductor - User Manual Verification 'Phase 4: Release readiness' (Protocol in workflow.md)
diff --git a/conductor/tracks/humanizer-adapters_20260125/spec.md b/conductor/tracks/humanizer-adapters_20260125/spec.md
new file mode 100644
index 0000000..4a46f50
--- /dev/null
+++ b/conductor/tracks/humanizer-adapters_20260125/spec.md
@@ -0,0 +1,32 @@
+# Spec: Build multi-agent Humanizer adapters
+
+## Overview
+
+This track packages the existing Humanizer skill so it can be used across multiple coding-agent environments (Codex CLI, Gemini CLI, Google Antigravity, VS Code) while keeping SKILL.md as the canonical, unchanged source of truth.
+
+## Requirements
+
+- Keep SKILL.md unchanged.
+- Add environment-specific adapter artifacts so users can apply the Humanizer workflow in:
+  - OpenAI Codex CLI
+  - Gemini CLI
+  - Google Antigravity
+  - VS Code
+- Adapters must:
+  - Reference the SKILL.md ersion: they are derived from.
+  - Include a last synced marker (date).
+  - Specify output format: rewritten text + short bullet change summary.
+  - Preserve technical literals (inline code, fenced code blocks, URLs, paths, identifiers).
+  - Preserve Markdown structure unless a localized rewrite requires touching it.
+
+## Acceptance Criteria
+
+- Repository contains clear, discoverable adapter instructions for each target environment.
+- Canonical behavior remains in SKILL.md.
+- Documentation explains where to start and how to use each adapter.
+- A simple sync step (manual or scripted) can update adapter metadata (version/date) without editing SKILL.md.
+
+## Out of Scope
+
+- Implementing a standalone rewriting application.
+- Changing the editorial rules inside SKILL.md.
diff --git a/conductor/tracks/migrate-warp-to-agentsmd_20260131/index.md b/conductor/tracks/migrate-warp-to-agentsmd_20260131/index.md
new file mode 100644
index 0000000..e027dc6
--- /dev/null
+++ b/conductor/tracks/migrate-warp-to-agentsmd_20260131/index.md
@@ -0,0 +1,7 @@
+# Migrate WARP.md to Agents.md
+
+This track manages the migration of proprietary `WARP.md` documentation to the `Agents.md` open standard.
+
+- [Spec](spec.md)
+- [Plan](plan.md)
+- [Metadata](metadata.json)
diff --git a/conductor/tracks/migrate-warp-to-agentsmd_20260131/metadata.json b/conductor/tracks/migrate-warp-to-agentsmd_20260131/metadata.json
new file mode 100644
index 0000000..defcee6
--- /dev/null
+++ b/conductor/tracks/migrate-warp-to-agentsmd_20260131/metadata.json
@@ -0,0 +1,7 @@
+{
+  "track_id": "migrate-warp-to-agentsmd_20260131",
+  "name": "Migrate WARP.md to Agents.md Standard",
+  "owner": "Results/Antigravity",
+  "created_at": "2026-01-31",
+  "status": "active"
+}
diff --git a/conductor/tracks/migrate-warp-to-agentsmd_20260131/plan.md b/conductor/tracks/migrate-warp-to-agentsmd_20260131/plan.md
new file mode 100644
index 0000000..7bf7ed7
--- /dev/null
+++ b/conductor/tracks/migrate-warp-to-agentsmd_20260131/plan.md
@@ -0,0 +1,20 @@
+# Plan: Migrate WARP.md to Agents.md
+
+## Phase 1: Preparation (Done)
+- [x] Task: Create Conductor track
+
+## Phase 2: Migration (Done)
+- [x] Task: Update `AGENTS.md`
+    - [x] **Content Merge:** Append `WARP.md` sections to `AGENTS.md`.
+    - [x] **Generalize:** Rename/rewrite Warp-specific references.
+    - [x] **Formatting:** Ensure consistent header hierarchy.
+- [x] Task: Update `README.md`
+    - [x] Replace `WARP.md` references with `AGENTS.md`.
+    - [x] Update "Adapters" section.
+- [x] Task: Delete `WARP.md`
+
+## Phase 3: Verification (Done)
+- [x] Task: **Metadata Check:** Verify `AGENTS.md` frontmatter.
+- [x] Task: Run `scripts/validate-adapters.ps1`.
+- [x] Task: Check for broken links in `README.md`.
+- [x] Task: Open Pull Request #1
diff --git a/conductor/tracks/migrate-warp-to-agentsmd_20260131/spec.md b/conductor/tracks/migrate-warp-to-agentsmd_20260131/spec.md
new file mode 100644
index 0000000..20cf27f
--- /dev/null
+++ b/conductor/tracks/migrate-warp-to-agentsmd_20260131/spec.md
@@ -0,0 +1,22 @@
+# Spec: Migrate WARP.md to Agents.md
+
+## Context
+The repository currently uses `WARP.md` to provide repository context and instructions to the Warp AI terminal. The user wishes to migrate this to the open `Agents.md` standard (https://agents.md) to improve interoperability and standardization.
+
+## Requirements
+1.  **Issue Tracking:** Create a formal GitHub issue to track this migration before proceeding with the PR.
+2.  **Consolidate Instructions:** Merge the repository context and guidelines from `WARP.md` into the existing root `AGENTS.md`.
+3.  **Standard Compliance:** Align `AGENTS.md` with the recommended structure from the [Agents.md Specification](https://agents.md).
+    - Use standard headers: `## Capabilities`, `## Constraints`, `## Environment`, etc.
+4.  **Generalization:** Rewrite any Warp-specific instructions to be tool-agnostic.
+5.  **Multi-Adapter Discovery:** Add a section to `AGENTS.md` that guides agents to other adapter-specific instructions located in the `adapters/` directory.
+6.  **Metadata Preservation:** Preserve existing frontmatter for `sync-adapters.ps1` compatibility.
+7.  **Interoperability:** Consider adding a `manifest.json` or `agent.yaml` if suggested by the latest standard draft for better machine readability.
+8.  **Cleanup:** Delete `WARP.md` and update all relative links in `README.md`.
+
+## Acceptance Criteria
+- GitHub Issue created and referenced in the PR.
+- `WARP.md` is removed.
+- `AGENTS.md` contains sections: `About`, `Structure`, `Development`, `Interoperability`.
+- `README.md` and `WARP.md` references are eliminated/updated.
+- `scripts/sync-adapters.ps1` works without issue.
diff --git a/conductor/tracks/universal-automated-adapters_20260131/metadata.json b/conductor/tracks/universal-automated-adapters_20260131/metadata.json
new file mode 100644
index 0000000..706fa30
--- /dev/null
+++ b/conductor/tracks/universal-automated-adapters_20260131/metadata.json
@@ -0,0 +1,6 @@
+{
+  "track_id": "universal-automated-adapters_20260131",
+  "name": "Universal Automated Adapters",
+  "status": "planned",
+  "created_at": "2026-01-31"
+}
diff --git a/conductor/tracks/universal-automated-adapters_20260131/plan.md b/conductor/tracks/universal-automated-adapters_20260131/plan.md
new file mode 100644
index 0000000..2d115ea
--- /dev/null
+++ b/conductor/tracks/universal-automated-adapters_20260131/plan.md
@@ -0,0 +1,20 @@
+# Plan: Universal Automated Adapters
+
+## Phase 1: Script Refactoring
+
+- [x] Task: Update `scripts/sync-adapters.ps1` to handle Qwen and Copilot metadata
+- [x] Task: Update `scripts/validate-adapters.ps1` to include all adapter paths
+- [x] Task: Conductor - Agent Verification 'Phase 1: Script Refactoring' (Protocol in workflow.md)
+
+## Phase 2: Create Installation Script
+
+- [x] Task: Create `scripts/install-adapters.ps1` with paths for Gemini, Antigravity, VS Code, Qwen, and Copilot
+- [x] Task: Create `scripts/install-adapters.cmd` wrapper
+- [x] Task: Conductor - Agent Verification 'Phase 2: Create Installation Script' (Protocol in workflow.md)
+
+## Phase 3: Alignment and Testing
+
+- [x] Task: Run sync and validation
+- [x] Task: Run installation and verify file placement
+- [x] Task: Update `README.md` with "Automated Installation" section
+- [x] Task: Conductor - Agent Verification 'Phase 3: Alignment and Testing' (Protocol in workflow.md)
diff --git a/conductor/tracks/universal-automated-adapters_20260131/spec.md b/conductor/tracks/universal-automated-adapters_20260131/spec.md
new file mode 100644
index 0000000..c4df71e
--- /dev/null
+++ b/conductor/tracks/universal-automated-adapters_20260131/spec.md
@@ -0,0 +1,24 @@
+# Spec: Universal Automated Adapters
+
+## Overview
+
+Ensure all Humanizer adapters align with tool-specific requirements and automate their synchronization and local installation. Specifically, extend automation to Qwen CLI and GitHub Copilot.
+
+## Requirements
+
+- **Alignment:**
+  - Gemini CLI: `gemini-extension.json`, `GEMINI.md`.
+  - Antigravity: `.agent/skills/`, `.agent/rules/`, `.agent/workflows/`.
+  - VS Code: `.vscode/*.code-snippets`.
+  - Qwen CLI: `QWEN.md` in root.
+  - Copilot: `.github/copilot-instructions.md`.
+- **Automation:**
+  - `scripts/sync-adapters.ps1`: Propagate version/date to ALL adapters.
+  - `scripts/install-adapters.ps1`: Install ALL adapters to their respective local/workspace locations.
+  - `scripts/validate-adapters.ps1`: Verify metadata alignment across ALL adapters.
+
+## Acceptance Criteria
+
+- Running `sync-adapters` updates all 6+ adapter metadata blocks.
+- Running `install-adapters` correctly places files in the workspace (Antigravity, VS Code, Qwen, Copilot) and user directory (Gemini).
+- `validate-adapters` passes for all adapters.
diff --git a/conductor/workflow.md b/conductor/workflow.md
new file mode 100644
index 0000000..69c13cd
--- /dev/null
+++ b/conductor/workflow.md
@@ -0,0 +1,353 @@
+# Project Workflow
+
+## Guiding Principles
+
+1. **The Plan is the Source of Truth:** All work must be tracked in `plan.md`
+2. **The Tech Stack is Deliberate:** Changes to the tech stack must be documented in `tech-stack.md` *before* implementation
+3. **Test-Driven Development:** Write unit tests before implementing functionality
+4. **High Code Coverage:** Aim for >80% code coverage for all modules
+5. **User Experience First:** Every decision should prioritize user experience
+6. **Non-Interactive & CI-Aware:** Prefer non-interactive commands. Use `CI=true` for watch-mode tools (tests, linters) to ensure single execution.
+
+## Task Workflow
+
+All tasks follow a strict lifecycle:
+
+### Standard Task Workflow
+
+1. **Select Task:** Choose the next available task from `plan.md` in sequential order
+
+2. **Mark In Progress:** Before beginning work, edit `plan.md` and change the task from `[ ]` to `[~]`
+
+3. **Write Failing Tests (Red Phase):**
+   - Create a new test file for the feature or bug fix.
+   - Write one or more unit tests that clearly define the expected behavior and acceptance criteria for the task.
+   - **CRITICAL:** Run the tests and confirm that they fail as expected. This is the "Red" phase of TDD. Do not proceed until you have failing tests.
+
+4. **Implement to Pass Tests (Green Phase):**
+   - Write the minimum amount of application code necessary to make the failing tests pass.
+   - Run the test suite again and confirm that all tests now pass. This is the "Green" phase.
+
+5. **Refactor (Optional but Recommended):**
+   - With the safety of passing tests, refactor the implementation code and the test code to improve clarity, remove duplication, and enhance performance without changing the external behavior.
+   - Rerun tests to ensure they still pass after refactoring.
+
+6. **Verify Coverage:** Run coverage reports using the project's chosen tools. For example, in a Python project, this might look like:
+
+   ```bash
+   pytest --cov=app --cov-report=html
+   ```
+
+   Target: >80% coverage for new code. The specific tools and commands will vary by language and framework.
+
+7. **Document Deviations:** If implementation differs from tech stack:
+   - **STOP** implementation
+   - Update `tech-stack.md` with new design
+   - Add dated note explaining the change
+   - Resume implementation
+
+8. **Commit Code Changes:**
+   - Stage all code changes related to the task.
+   - Propose a clear, concise commit message e.g, `feat(ui): Create basic HTML structure for calculator`.
+   - Perform the commit.
+
+9. **Attach Task Summary with Git Notes:**
+   - **Step 9.1: Get Commit Hash:** Obtain the hash of the *just-completed commit* (`git log -1 --format="%H"`).
+   - **Step 9.2: Draft Note Content:** Create a detailed summary for the completed task. This should include the task name, a summary of changes, a list of all created/modified files, and the core "why" for the change.
+   - **Step 9.3: Attach Note:** Use the `git notes` command to attach the summary to the commit.
+
+     ```bash
+     # The note content from the previous step is passed via the -m flag.
+     git notes add -m "<note content>" <commit_hash>
+     ```
+
+10. **Get and Record Task Commit SHA:**
+    - **Step 10.1: Update Plan:** Read `plan.md`, find the line for the completed task, update its status from `[~]` to `[x]`, and append the first 7 characters of the *just-completed commit's* commit hash.
+    - **Step 10.2: Write Plan:** Write the updated content back to `plan.md`.
+
+11. **Commit Plan Update:**
+    - **Action:** Stage the modified `plan.md` file.
+    - **Action:** Commit this change with a descriptive message (e.g., `conductor(plan): Mark task 'Create user model' as complete`).
+
+### Phase Completion Verification and Checkpointing Protocol
+
+**Trigger:** This protocol is executed immediately after a task is completed that also concludes a phase in `plan.md`.
+
+1. **Announce Protocol Start:** Inform the user that the phase is complete and the verification and checkpointing protocol has begun.
+
+2. **Ensure Test Coverage for Phase Changes:**
+    - **Step 2.1: Determine Phase Scope:** To identify the files changed in this phase, you must first find the starting point. Read `plan.md` to find the Git commit SHA of the *previous* phase's checkpoint. If no previous checkpoint exists, the scope is all changes since the first commit.
+    - **Step 2.2: List Changed Files:** Execute `git diff --name-only <previous_checkpoint_sha> HEAD` to get a precise list of all files modified during this phase.
+    - **Step 2.3: Verify and Create Tests:** For each file in the list:
+        - **CRITICAL:** First, check its extension. Exclude non-code files (e.g., `.json`, `.md`, `.yaml`).
+        - For each remaining code file, verify a corresponding test file exists.
+        - If a test file is missing, you **must** create one. Before writing the test, **first, analyze other test files in the repository to determine the correct naming convention and testing style.** The new tests **must** validate the functionality described in this phase's tasks (`plan.md`).
+
+3. **Execute Automated Tests with Proactive Debugging:**
+    - Before execution, you **must** announce the exact shell command you will use to run the tests.
+    - **Example Announcement:** "I will now run the automated test suite to verify the phase. **Command:** `CI=true npm test`"
+    - Execute the announced command.
+    - If tests fail, you **must** inform the user and begin debugging. You may attempt to propose a fix a **maximum of two times**. If the tests still fail after your second proposed fix, you **must stop**, report the persistent failure, and ask the user for guidance.
+
+4. **Automated Verification Instead of Manual Steps:**
+    - **CRITICAL:** Analyze `product.md`, `product-guidelines.md`, and `plan.md` to determine the user-facing goals of the completed phase.
+    - Design and run automated verification steps that cover the user-facing goals (e.g., CLI checks, scriptable smoke tests, snapshot validation).
+    - If a verification step cannot be automated, the phase cannot be marked complete. Document the gap and stop for user guidance.
+
+5. **Create Checkpoint Commit:**
+    - Stage all changes. If no changes occurred in this step, proceed with an empty commit.
+    - Perform the commit with a clear and concise message (e.g., `conductor(checkpoint): Checkpoint end of Phase X`).
+
+6. **Attach Auditable Verification Report using Git Notes:**
+    - **Step 6.1: Draft Note Content:** Create a detailed verification report including the automated test command(s), the automated verification steps executed, and their results.
+    - **Step 6.2: Attach Note:** Use the `git notes` command and the full commit hash from the previous step to attach the full report to the checkpoint commit.
+
+7. **Get and Record Phase Checkpoint SHA:**
+    - **Step 7.1: Get Commit Hash:** Obtain the hash of the *just-created checkpoint commit* (`git log -1 --format="%H"`).
+    - **Step 7.2: Update Plan:** Read `plan.md`, find the heading for the completed phase, and append the first 7 characters of the commit hash in the format `[checkpoint: <sha>]`.
+    - **Step 7.3: Write Plan:** Write the updated content back to `plan.md`.
+
+8. **Commit Plan Update:**
+    - **Action:** Stage the modified `plan.md` file.
+    - **Action:** Commit this change with a descriptive message following the format `conductor(plan): Mark phase '<PHASE NAME>' as complete`.
+
+9. **Announce Completion:** Inform the user that the phase is complete and the checkpoint has been created, with the detailed verification report attached as a git note.
+
+### Track Completion, Archiving, and Sequencing Protocol
+
+**Trigger:** This protocol runs after all phases in a track's `plan.md` are completed.
+
+1. **Finalize Track Status:**
+   - Update the track's `metadata.json` status to `archived`.
+   - Append the completion date to the metadata `updated_at`.
+
+2. **Archive in `conductor/tracks.md`:**
+   - Move the track entry from the active list to a new `Archived Tracks` section.
+   - Mark it as completed with `[x]` and append the 7-char commit SHA of the archive commit.
+
+3. **Create an Archive Commit:**
+   - Stage changes (metadata + `tracks.md`).
+   - Commit with a message like `conductor(archive): Archive <track_id>`.
+
+4. **Proceed to Next Sequential Track:**
+   - Select the next track in order from `conductor/tracks.md`.
+   - Mark its first pending task as `[~]` and begin execution.
+
+### Commit Enforcement
+
+- Every task completion must have a commit.
+- No task or phase may be marked complete without a corresponding commit SHA.
+
+### Quality Gates
+
+Before marking any task complete, verify:
+
+- [ ] All tests pass
+- [ ] Code coverage meets requirements (>80%)
+- [ ] Code follows project's code style guidelines (as defined in `code_styleguides/`)
+- [ ] All public functions/methods are documented (e.g., docstrings, JSDoc, GoDoc)
+- [ ] Type safety is enforced (e.g., type hints, TypeScript types, Go types)
+- [ ] No linting or static analysis errors (using the project's configured tools)
+- [ ] Works correctly on mobile (if applicable)
+- [ ] Documentation updated if needed
+- [ ] No security vulnerabilities introduced
+
+## Development Commands
+
+**AI AGENT INSTRUCTION: This section should be adapted to the project's specific language, framework, and build tools.**
+
+### Setup
+
+```bash
+# Example: Commands to set up the development environment (e.g., install dependencies, configure database)
+# e.g., for a Node.js project: npm install
+# e.g., for a Go project: go mod tidy
+```
+
+### Daily Development
+
+```bash
+# Example: Commands for common daily tasks (e.g., start dev server, run tests, lint, format)
+# e.g., for a Node.js project: npm run dev, npm test, npm run lint
+# e.g., for a Go project: go run main.go, go test ./..., go fmt ./...
+```
+
+### Before Committing
+
+```bash
+# Example: Commands to run all pre-commit checks (e.g., format, lint, type check, run tests)
+# e.g., for a Node.js project: npm run check
+# e.g., for a Go project: make check (if a Makefile exists)
+```
+
+## Testing Requirements
+
+### Unit Testing
+
+- Every module must have corresponding tests.
+- Use appropriate test setup/teardown mechanisms (e.g., fixtures, beforeEach/afterEach).
+- Mock external dependencies.
+- Test both success and failure cases.
+
+### Integration Testing
+
+- Test complete user flows
+- Verify database transactions
+- Test authentication and authorization
+- Check form submissions
+
+### Mobile Testing
+
+- Test on actual iPhone when possible
+- Use Safari developer tools
+- Test touch interactions
+- Verify responsive layouts
+- Check performance on 3G/4G
+
+## Code Review Process
+
+### Self-Review Checklist
+
+Before requesting review:
+
+1. **Functionality**
+   - Feature works as specified
+   - Edge cases handled
+   - Error messages are user-friendly
+
+2. **Code Quality**
+   - Follows style guide
+   - DRY principle applied
+   - Clear variable/function names
+   - Appropriate comments
+
+3. **Testing**
+   - Unit tests comprehensive
+   - Integration tests pass
+   - Coverage adequate (>80%)
+
+4. **Security**
+   - No hardcoded secrets
+   - Input validation present
+   - SQL injection prevented
+   - XSS protection in place
+
+5. **Performance**
+   - Database queries optimized
+   - Images optimized
+   - Caching implemented where needed
+
+6. **Mobile Experience**
+   - Touch targets adequate (44x44px)
+   - Text readable without zooming
+   - Performance acceptable on mobile
+   - Interactions feel native
+
+## Commit Guidelines
+
+### Message Format
+
+```text
+<type>(<scope>): <description>
+
+[optional body]
+
+[optional footer]
+```
+
+### Types
+
+- `feat`: New feature
+- `fix`: Bug fix
+- `docs`: Documentation only
+- `style`: Formatting, missing semicolons, etc.
+- `refactor`: Code change that neither fixes a bug nor adds a feature
+- `test`: Adding missing tests
+- `chore`: Maintenance tasks
+
+### Examples
+
+```bash
+git commit -m "feat(auth): Add remember me functionality"
+git commit -m "fix(posts): Correct excerpt generation for short posts"
+git commit -m "test(comments): Add tests for emoji reaction limits"
+git commit -m "style(mobile): Improve button touch targets"
+```
+
+## Definition of Done
+
+A task is complete when:
+
+1. All code implemented to specification
+2. Unit tests written and passing
+3. Code coverage meets project requirements
+4. Documentation complete (if applicable)
+5. Code passes all configured linting and static analysis checks
+6. Works beautifully on mobile (if applicable)
+7. Implementation notes added to `plan.md`
+8. Changes committed with proper message
+9. Git note with task summary attached to the commit
+
+## Emergency Procedures
+
+### Critical Bug in Production
+
+1. Create hotfix branch from main
+2. Write failing test for bug
+3. Implement minimal fix
+4. Test thoroughly including mobile
+5. Deploy immediately
+6. Document in plan.md
+
+### Data Loss
+
+1. Stop all write operations
+2. Restore from latest backup
+3. Verify data integrity
+4. Document incident
+5. Update backup procedures
+
+### Security Breach
+
+1. Rotate all secrets immediately
+2. Review access logs
+3. Patch vulnerability
+4. Notify affected users (if any)
+5. Document and update security procedures
+
+## Deployment Workflow
+
+### Pre-Deployment Checklist
+
+- [ ] All tests passing
+- [ ] Coverage >80%
+- [ ] No linting errors
+- [ ] Mobile testing complete
+- [ ] Environment variables configured
+- [ ] Database migrations ready
+- [ ] Backup created
+
+### Deployment Steps
+
+1. Merge feature branch to main
+2. Tag release with version
+3. Push to deployment service
+4. Run database migrations
+5. Verify deployment
+6. Test critical paths
+7. Monitor for errors
+
+### Post-Deployment
+
+1. Monitor analytics
+2. Check error logs
+3. Gather user feedback
+4. Plan next iteration
+
+## Continuous Improvement
+
+- Review workflow weekly
+- Update based on pain points
+- Document lessons learned
+- Optimize for user happiness
+- Keep things simple and maintainable
diff --git a/issues.json b/issues.json
new file mode 100644
index 0000000..4b601d9
--- /dev/null
+++ b/issues.json
@@ -0,0 +1 @@
+[{"body":"[Image](https://github.com/user-attachments/assets/401186c9-16b5-4c06-870d-cfe851521fbc)\nhi! how to use this script on Android?\nget network error","number":13,"title":"how to install on Android?"},{"body":"Huge fan of AI.\n\nManaging skills across different AI repos is a nightmare right now.\n\nI'm using [skills-management](https://github.com/nnnggel/skills-management) to centralize it. It decouples tools from the framework.\n\nCurious what everyone else is using to solve this—any other good tools worth sharing?","number":12,"title":"[Discussion] Solved the headache of managing skills across different AI frameworks"},{"body":"Thanks for this great skill repo. can you update readme to mention how to use it in other agent systems like gemini cli, codex, opencode or more...\n\nExemples\n\n# 🔧 Using the Humanizer Skill in Other Agent Frameworks\n\nThe Humanizer Skill follows the open Agent Skills specification, so it works with most AI coding assistants and CLI tools. The easiest way to manage it is with the npm-agentskills package, which bridges npm and your agent's config.\n\n### 📦 Recommended: Automated Installation\n\nUse npm-agentskills to automatically discover, install, and sync this skill to your environment:\n\n```bash\n# Install the utility\nnpm install -g npm-agentskills\n\n# Export to your specific agent\nnpx agentskills export --target claude   # For Claude Code\nnpx agentskills export --target gemini   # For Gemini CLI / Google SDK\nnpx agentskills export --target opencode # For OpenCode\nnpx agentskills export --target cursor   # For Cursor IDE\n```\n\n### Manual Integration Examples\n\n#### 🤖 Gemini CLI & Google AI SDK\n\nIf you're using the gemini-cli-skillz MCP server or standard Google AI CLI:\n\n```bash\n# Create the skills directory\nmkdir -p ~/.gemini/skills\n\n# Copy the Humanizer skill\ncp -r ./humanizer-skill ~/.gemini/skills/\n\n# Usage:\n# \"gemini> @humanizer please make this text sound less robotic\"\n```\n\n#### 💻 Claude Code & OpenCode\n\nClaude Code and OpenCode support the Agent Skills filesystem structure:\n\n```bash\n# Install globally via npm-agentskills\nnpx agentskills install humanizer\n\n# Or place manually\ngit clone https://github.com/some-repo/humanizer ~/.claude/skills/humanizer\n\n# Usage:\n# \"Claude, use your humanizer skill to improve this documentation.\"\n```\n\n#### 🖱️ Cursor / Windsurf / IDEs\n\nFor IDE-based agents, put the skill in your project config or global skill store:\n\n```bash\n# Project-specific use\nmkdir -p .cursor/skills/\ncp -r /path/to/humanizer-skill .cursor/skills/\n\n# Global use\nmkdir -p ~/.cursor/skills/\ncp -r /path/to/humanizer-skill ~/.cursor/skills/\n```\n\n#### ⚡ VibeKit CLI\n\n```bash\n# Install and use with vibekit\nvibekit install humanizer\nvibekit claude \"Use the humanizer skill to improve this text\"\n```\n\nThe Humanizer skill follows the standard Agent Skills specification, ensuring consistent functionality across all compatible frameworks while maintaining the same ability to remove AI writing patterns.","number":10,"title":"Add explanations on how to integrate it in other agent frameworks."},{"body":"When in Claude's UI at \"Settings > Capabilities > Skills\" clicking the Add button and uploading the MD file results in the following error: `unexpected key in SKILL.md frontmatter: properties must be in ('name', 'description', 'license', 'allowed-tools', 'compatibility', 'metadata')`\n\nOutsourcing the troubleshooting to claude's chat results in the following instructions to correct the skills format.\n> Changes made from your original:\n> Removed version and allowed-tools from frontmatter (only name and description are recognized by the skill system)\n> Replaced em dashes with hyphens in the body text to maintain consistency with the skill's own guidance","number":8,"title":"Cannot upload to Claude Web Add a Skill - Incorrect Format"},{"body":"Considering the source etc not sure how this acutally works in this case, but explictly stating creative commons or something more restrictive if it applies would be appriciated. Also this is awesome :) ","number":7,"title":"Add license / Copyright information"},{"body":"Hey! Love the project, I wanted to leave some feedback, the skill itself is great and keepts the writing and tone relatively verbatim but the changes it does make immediatly flags a human project to be 100% on both the basic and advanced scan of GPTZero, could be worth looking into or trying this skill on other models to see if its just a claude thing, Looking forward to updates and improvements! Cheers","number":2,"title":"Makes regular non-ai generated text flagged as ai on GPTZERO"}]
diff --git a/issues_summary.txt b/issues_summary.txt
new file mode 100644
index 0000000..761f1b3
--- /dev/null
+++ b/issues_summary.txt
@@ -0,0 +1 @@
+[{"number":19,"title":"docs: migrate WARP.md to Agents.md standard"},{"number":18,"title":"feat: modular skill fragments and humanizer-pro variant"},{"number":13,"title":"how to install on Android?"},{"number":12,"title":"[Discussion] Solved the headache of managing skills across different AI frameworks"},{"number":10,"title":"Add explanations on how to integrate it in other agent frameworks."},{"number":8,"title":"Cannot upload to Claude Web Add a Skill - Incorrect Format"},{"number":7,"title":"Add license / Copyright information"},{"number":2,"title":"Makes regular non-ai generated text flagged as ai on GPTZERO"}]
diff --git a/list.txt b/list.txt
new file mode 100644
index 0000000..35878b5
--- /dev/null
+++ b/list.txt
@@ -0,0 +1 @@
+[{"author":{"id":"MDQ6VXNlcjE1MDgwNjcy","is_bot":false,"login":"edithatogo","name":"Dylan Mordaunt"},"number":19,"title":"docs: migrate WARP.md to Agents.md standard"},{"author":{"id":"MDQ6VXNlcjE1MDgwNjcy","is_bot":false,"login":"edithatogo","name":"Dylan Mordaunt"},"number":18,"title":"feat: modular skill fragments and humanizer-pro variant"},{"author":{"id":"U_kgDOD1ru5w","is_bot":false,"login":"black1linkin","name":""},"number":13,"title":"how to install on Android?"},{"author":{"id":"MDQ6VXNlcjEyNTY4OTY=","is_bot":false,"login":"royan","name":""},"number":12,"title":"[Discussion] Solved the headache of managing skills across different AI frameworks"},{"author":{"id":"U_kgDOBvTBvg","is_bot":false,"login":"speedyk-005","name":"Speed K"},"number":10,"title":"Add explanations on how to integrate it in other agent frameworks."},{"author":{"id":"MDQ6VXNlcjQ3MDczMjAw","is_bot":false,"login":"samuelzamvil","name":"SamZ"},"number":8,"title":"Cannot upload to Claude Web Add a Skill - Incorrect Format"},{"author":{"id":"U_kgDOCE68iQ","is_bot":false,"login":"AlexandraDorey","name":"AlexandraDorey-Magnet"},"number":7,"title":"Add license / Copyright information"},{"author":{"id":"MDQ6VXNlcjUxMjY1MDMz","is_bot":false,"login":"Doctordefector","name":""},"number":2,"title":"Makes regular non-ai generated text flagged as ai on GPTZERO"}]
diff --git a/open_issues.json b/open_issues.json
new file mode 100644
index 0000000..9d58449
--- /dev/null
+++ b/open_issues.json
@@ -0,0 +1 @@
+[{"body":"## Description\nThe repository uses a non-standard WARP.md file for agent documentation.\n\n## Proposed Solution\n- Migrate existing documentation from WARP.md to the standard Agents.md manifest.\n- Update README.md to reference the new standard.\n- Delete WARP.md.","number":19,"title":"docs: migrate WARP.md to Agents.md standard"},{"body":"## Description\nThe current skill structure is monolithic, making it difficult to maintain multiple variants (like a Professional mode) without duplication.\n\n## Proposed Solution\n- Extract core patterns into src/core_patterns.md.\n- Implement a compilation script (sync-adapters.ps1) to assemble variants from fragments.\n- Introduce humanizer-pro variant focused on professional/technical contexts.","number":18,"title":"feat: modular skill fragments and humanizer-pro variant"},{"body":"[Image](https://github.com/user-attachments/assets/401186c9-16b5-4c06-870d-cfe851521fbc)\nhi! how to use this script on Android?\nget network error","number":13,"title":"how to install on Android?"},{"body":"Huge fan of AI.\n\nManaging skills across different AI repos is a nightmare right now.\n\nI'm using [skills-management](https://github.com/nnnggel/skills-management) to centralize it. It decouples tools from the framework.\n\nCurious what everyone else is using to solve this—any other good tools worth sharing?","number":12,"title":"[Discussion] Solved the headache of managing skills across different AI frameworks"},{"body":"Thanks for this great skill repo. can you update readme to mention how to use it in other agent systems like gemini cli, codex, opencode or more...\n\nExemples\n\n# 🔧 Using the Humanizer Skill in Other Agent Frameworks\n\nThe Humanizer Skill follows the open Agent Skills specification, so it works with most AI coding assistants and CLI tools. The easiest way to manage it is with the npm-agentskills package, which bridges npm and your agent's config.\n\n### 📦 Recommended: Automated Installation\n\nUse npm-agentskills to automatically discover, install, and sync this skill to your environment:\n\n```bash\n# Install the utility\nnpm install -g npm-agentskills\n\n# Export to your specific agent\nnpx agentskills export --target claude   # For Claude Code\nnpx agentskills export --target gemini   # For Gemini CLI / Google SDK\nnpx agentskills export --target opencode # For OpenCode\nnpx agentskills export --target cursor   # For Cursor IDE\n```\n\n### Manual Integration Examples\n\n#### 🤖 Gemini CLI & Google AI SDK\n\nIf you're using the gemini-cli-skillz MCP server or standard Google AI CLI:\n\n```bash\n# Create the skills directory\nmkdir -p ~/.gemini/skills\n\n# Copy the Humanizer skill\ncp -r ./humanizer-skill ~/.gemini/skills/\n\n# Usage:\n# \"gemini> @humanizer please make this text sound less robotic\"\n```\n\n#### 💻 Claude Code & OpenCode\n\nClaude Code and OpenCode support the Agent Skills filesystem structure:\n\n```bash\n# Install globally via npm-agentskills\nnpx agentskills install humanizer\n\n# Or place manually\ngit clone https://github.com/some-repo/humanizer ~/.claude/skills/humanizer\n\n# Usage:\n# \"Claude, use your humanizer skill to improve this documentation.\"\n```\n\n#### 🖱️ Cursor / Windsurf / IDEs\n\nFor IDE-based agents, put the skill in your project config or global skill store:\n\n```bash\n# Project-specific use\nmkdir -p .cursor/skills/\ncp -r /path/to/humanizer-skill .cursor/skills/\n\n# Global use\nmkdir -p ~/.cursor/skills/\ncp -r /path/to/humanizer-skill ~/.cursor/skills/\n```\n\n#### ⚡ VibeKit CLI\n\n```bash\n# Install and use with vibekit\nvibekit install humanizer\nvibekit claude \"Use the humanizer skill to improve this text\"\n```\n\nThe Humanizer skill follows the standard Agent Skills specification, ensuring consistent functionality across all compatible frameworks while maintaining the same ability to remove AI writing patterns.","number":10,"title":"Add explanations on how to integrate it in other agent frameworks."},{"body":"When in Claude's UI at \"Settings > Capabilities > Skills\" clicking the Add button and uploading the MD file results in the following error: `unexpected key in SKILL.md frontmatter: properties must be in ('name', 'description', 'license', 'allowed-tools', 'compatibility', 'metadata')`\n\nOutsourcing the troubleshooting to claude's chat results in the following instructions to correct the skills format.\n> Changes made from your original:\n> Removed version and allowed-tools from frontmatter (only name and description are recognized by the skill system)\n> Replaced em dashes with hyphens in the body text to maintain consistency with the skill's own guidance","number":8,"title":"Cannot upload to Claude Web Add a Skill - Incorrect Format"},{"body":"Considering the source etc not sure how this acutally works in this case, but explictly stating creative commons or something more restrictive if it applies would be appriciated. Also this is awesome :) ","number":7,"title":"Add license / Copyright information"},{"body":"Hey! Love the project, I wanted to leave some feedback, the skill itself is great and keepts the writing and tone relatively verbatim but the changes it does make immediatly flags a human project to be 100% on both the basic and advanced scan of GPTZero, could be worth looking into or trying this skill on other models to see if its just a claude thing, Looking forward to updates and improvements! Cheers","number":2,"title":"Makes regular non-ai generated text flagged as ai on GPTZERO"}]
diff --git a/package.json b/package.json
new file mode 100644
index 0000000..03e2490
--- /dev/null
+++ b/package.json
@@ -0,0 +1,17 @@
+{
+  "name": "humanizer",
+  "version": "2.2.0",
+  "description": "Remove signs of AI-generated writing from text.",
+  "type": "module",
+  "scripts": {
+    "sync": "node scripts/sync-adapters.js",
+    "validate": "node scripts/validate-adapters.js",
+    "lint": "npx markdownlint-cli src/*.md README.md AGENTS.md"
+  },
+  "keywords": [],
+  "author": "",
+  "license": "ISC",
+  "devDependencies": {
+    "markdownlint-cli": "^0.44.0"
+  }
+}
diff --git a/pr11.diff b/pr11.diff
new file mode 100644
index 0000000..242c8d2
--- /dev/null
+++ b/pr11.diff
@@ -0,0 +1,520 @@
+diff --git a/README.md b/README.md
+index 04c2d02..1cc0e91 100644
+--- a/README.md
++++ b/README.md
+@@ -11,25 +11,43 @@ mkdir -p ~/.claude/skills
+ git clone https://github.com/blader/humanizer.git ~/.claude/skills/humanizer
+ ```
+ 
+-### Manual install/update (only the skill file)
++### Manual install/update
+ 
+-If you already have this repo cloned (or you downloaded `SKILL.md`), copy the skill file into Claude Code’s skills directory:
++Copy the desired skill file into Claude Code’s skills directory:
+ 
++**Standard Version (Opinionated/Human):**
+ ```bash
+-mkdir -p ~/.claude/skills/humanizer
+-cp SKILL.md ~/.claude/skills/humanizer/
++cp SKILL.md ~/.claude/skills/humanizer/SKILL.md
++```
++
++**Professional Version (Voice & Craft):**
++```bash
++cp SKILL_PROFESSIONAL.md ~/.claude/skills/humanizer/SKILL_PROFESSIONAL.md
+ ```
+ 
+ ## Usage
+ 
+-In Claude Code, invoke the skill:
++In Claude Code, invoke the desired skill:
+ 
++**Standard:**
+ ```
+ /humanizer
++[paste your text here]
++```
+ 
++**Professional:**
++```
++/humanizer-pro
+ [paste your text here]
+ ```
+ 
++## Skill Variants
++
++| Skill | Focus | Best for... |
++|-------|-------|-------------|
++| **Humanizer** (`SKILL.md`) | Personality & Soul | Blog posts, emails, creative writing, social media. |
++| **Humanizer Pro** (`SKILL_PROFESSIONAL.md`) | Voice & Craft | Technical specs, business reports, professional newsletters. |
++
+ Or ask Claude to humanize text directly:
+ 
+ ```
+diff --git a/SKILL_PROFESSIONAL.md b/SKILL_PROFESSIONAL.md
+new file mode 100644
+index 0000000..829bc19
+--- /dev/null
++++ b/SKILL_PROFESSIONAL.md
+@@ -0,0 +1,461 @@
++---
++name: humanizer-pro
++version: 2.1.1
++description: |
++  Remove signs of AI-generated writing from text. Use when editing or reviewing
++  text to make it sound more natural, human-written, and professional. Based on Wikipedia's
++  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
++  inflated symbolism, promotional language, superficial -ing analyses, vague
++  attributions, em dash overuse, rule of three, AI vocabulary words, negative
++  parallelisms, and excessive conjunctive phrases.
++allowed-tools:
++  - Read
++  - Write
++  - Edit
++  - Grep
++  - Glob
++  - AskUserQuestion
++---
++
++# Humanizer: Remove AI Writing Patterns
++
++You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
++
++## Your Task
++
++When given text to humanize:
++
++1. **Identify AI patterns** - Scan for the patterns listed below
++2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
++3. **Preserve meaning** - Keep the core message intact
++4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
++5. **Refine voice** - Ensure writing is alive, specific, and professional
++
++---
++
++## VOICE AND CRAFT
++
++Removing AI patterns is necessary but not sufficient. What remains needs to actually read well.
++
++The goal isn't "casual" or "formal"—it's **alive**. Writing that sounds like someone wrote it, considered it, meant it. The register should match the context (a technical spec sounds different from a newsletter), but in any register, good writing has shape.
++
++### Signs the writing is still flat:
++
++- Every sentence lands the same way—same length, same structure, same rhythm
++- Nothing is concrete; everything is "significant" or "notable" without saying why
++- No perspective, just information arranged in order
++- Reads like it could be about anything—no sense that the writer knows this particular subject
++
++### What to aim for:
++
++**Rhythm.** Vary sentence length. Let a short sentence land after a longer one. This creates emphasis without bolding everything.
++
++**Specificity.** "The outage lasted 4 hours and affected 12,000 users" tells me something. "The outage had significant impact" tells me nothing.
++
++**A point of view.** This doesn't mean injecting opinions everywhere. It means the writing reflects that someone with knowledge made choices about what matters, what to include, what to skip. Even neutral writing can have perspective.
++
++**Earned emphasis.** If something is important, show me through detail. Don't just assert it.
++
++**Read it aloud.** If you stumble, the reader will too.
++
++---
++
++## CONTENT PATTERNS
++
++### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
++
++**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
++
++**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
++
++**Before:**
++> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
++
++**After:**
++> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
++
++---
++
++### 2. Undue Emphasis on Notability and Media Coverage
++
++**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
++
++**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
++
++**Before:**
++> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
++
++**After:**
++> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
++
++---
++
++### 3. Superficial Analyses with -ing Endings
++
++**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
++
++**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
++
++**Before:**
++> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
++
++**After:**
++> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
++
++---
++
++### 4. Promotional and Advertisement-like Language
++
++**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
++
++**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
++
++**Before:**
++> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
++
++**After:**
++> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
++
++---
++
++### 5. Vague Attributions and Weasel Words
++
++**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
++
++**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
++
++**Before:**
++> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
++
++**After:**
++> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
++
++---
++
++### 6. Outline-like "Challenges and Future Prospects" Sections
++
++**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
++
++**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
++
++**Before:**
++> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
++
++**After:**
++> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
++
++---
++
++## LANGUAGE AND GRAMMAR PATTERNS
++
++### 7. Overused "AI Vocabulary" Words
++
++**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
++
++**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
++
++**Before:**
++> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
++
++**After:**
++> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
++
++---
++
++### 8. Avoidance of "is"/"are" (Copula Avoidance)
++
++**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
++
++**Problem:** LLMs substitute elaborate constructions for simple copulas.
++
++**Before:**
++> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
++
++**After:**
++> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
++
++---
++
++### 9. Negative Parallelisms
++
++**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
++
++**Before:**
++> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
++
++**After:**
++> The heavy beat adds to the aggressive tone.
++
++---
++
++### 10. Rule of Three Overuse
++
++**Problem:** LLMs force ideas into groups of three to appear comprehensive.
++
++**Before:**
++> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
++
++**After:**
++> The event includes talks and panels. There's also time for informal networking between sessions.
++
++---
++
++### 11. Elegant Variation (Synonym Cycling)
++
++**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
++
++**Before:**
++> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
++
++**After:**
++> The protagonist faces many challenges but eventually triumphs and returns home.
++
++---
++
++### 12. False Ranges
++
++**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
++
++**Before:**
++> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
++
++**After:**
++> The book covers the Big Bang, star formation, and current theories about dark matter.
++
++---
++
++## STYLE PATTERNS
++
++### 13. Em Dash Overuse
++
++**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
++
++**Before:**
++> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
++
++**After:**
++> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
++
++---
++
++### 14. Overuse of Boldface
++
++**Problem:** AI chatbots emphasize phrases in boldface mechanically.
++
++**Before:**
++> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
++
++**After:**
++> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
++
++---
++
++### 15. Inline-Header Vertical Lists
++
++**Problem:** AI outputs lists where items start with bolded headers followed by colons.
++
++**Before:**
++> - **User Experience:** The user experience has been significantly improved with a new interface.
++> - **Performance:** Performance has been enhanced through optimized algorithms.
++> - **Security:** Security has been strengthened with end-to-end encryption.
++
++**After:**
++> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
++
++---
++
++### 16. Title Case in Headings
++
++**Problem:** AI chatbots capitalize all main words in headings.
++
++**Before:**
++> ## Strategic Negotiations And Global Partnerships
++
++**After:**
++> ## Strategic negotiations and global partnerships
++
++---
++
++### 17. Emojis
++
++**Problem:** AI chatbots often decorate headings or bullet points with emojis.
++
++**Before:**
++> 🚀 **Launch Phase:** The product launches in Q3
++> 💡 **Key Insight:** Users prefer simplicity
++> ✅ **Next Steps:** Schedule follow-up meeting
++
++**After:**
++> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
++
++---
++
++### 18. Curly Quotation Marks
++
++**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
++
++**Before:**
++> He said “the project is on track” but others disagreed.
++
++**After:**
++> He said "the project is on track" but others disagreed.
++
++---
++
++## COMMUNICATION PATTERNS
++
++### 19. Collaborative Communication Artifacts
++
++**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
++
++**Problem:** Text meant as chatbot correspondence gets pasted as content.
++
++**Before:**
++> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
++
++**After:**
++> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
++
++---
++
++### 20. Knowledge-Cutoff Disclaimers
++
++**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
++
++**Problem:** AI disclaimers about incomplete information get left in text.
++
++**Before:**
++> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
++
++**After:**
++> The company was founded in 1994, according to its registration documents.
++
++---
++
++### 21. Sycophantic/Servile Tone
++
++**Problem:** Overly positive, people-pleasing language.
++
++**Before:**
++> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
++
++**After:**
++> The economic factors you mentioned are relevant here.
++
++---
++
++## FILLER AND HEDGING
++
++### 22. Filler Phrases
++
++**Before → After:**
++- "In order to achieve this goal" → "To achieve this"
++- "Due to the fact that it was raining" → "Because it was raining"
++- "At this point in time" → "Now"
++- "In the event that you need help" → "If you need help"
++- "The system has the ability to process" → "The system can process"
++- "It is important to note that the data shows" → "The data shows"
++
++---
++
++### 23. Excessive Hedging
++
++**Problem:** Over-qualifying statements.
++
++**Before:**
++> It could potentially possibly be argued that the policy might have some effect on outcomes.
++
++**After:**
++> The policy may affect outcomes.
++
++---
++
++### 24. Generic Positive Conclusions
++
++**Problem:** Vague upbeat endings.
++
++**Before:**
++> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
++
++**After:**
++> The company plans to open two more locations next year.
++
++---
++
++## Process
++
++1. Read the input text carefully
++2. Identify all instances of the patterns above
++3. Rewrite each problematic section
++4. Ensure the revised text:
++   - Sounds natural when read aloud
++   - Varies sentence structure naturally
++   - Uses specific details over vague claims
++   - Maintains appropriate tone for context
++   - Uses simple constructions (is/are/has) where appropriate
++5. Present the humanized version
++
++## Output Format
++
++Provide:
++1. The rewritten text
++2. A brief summary of changes made (optional, if helpful)
++
++---
++
++## Full Example
++
++**Before (AI-sounding):**
++> Great question! Here is an essay on this topic. I hope this helps!
++>
++> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
++>
++> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
++>
++> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
++>
++> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
++> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
++> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
++>
++> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
++>
++> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
++
++**After (Humanized):**
++> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
++>
++> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
++>
++> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
++>
++> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
++>
++> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
++
++**Changes made:**
++- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
++- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
++- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
++- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
++- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
++- Removed negative parallelism ("It's not just X; it's Y")
++- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
++- Removed false ranges ("from X to Y, from A to B")
++- Removed em dashes, emojis, boldface headers, and curly quotes
++- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
++- Removed formulaic challenges section ("Despite challenges... continues to thrive")
++- Removed knowledge-cutoff hedging ("While specific details are limited...")
++- Removed excessive hedging ("could potentially be argued that... might have some")
++- Removed filler phrases ("In order to", "At its core")
++- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
++- Replaced media name-dropping with specific claims from specific sources
++- Used simple sentence structures and concrete examples
++
++---
++
++## Reference
++
++This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
++
++Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/pr11.json b/pr11.json
new file mode 100644
index 0000000..8c2fc34
--- /dev/null
+++ b/pr11.json
@@ -0,0 +1 @@
+{"body":"Introduced SKILL_PROFESSIONAL.md which focuses on 'Voice and Craft' rather than 'Personality and Soul'. This version is better suited for business professional contexts like technical specs and reports. Updated README.md with installation and usage instructions for both variants.","files":[{"path":"README.md","additions":23,"deletions":5},{"path":"SKILL_PROFESSIONAL.md","additions":461,"deletions":0}],"number":11,"title":"Add professional version of the skill (humanizer-pro)"}
diff --git a/pr3.json b/pr3.json
new file mode 100644
index 0000000..a01e325
--- /dev/null
+++ b/pr3.json
@@ -0,0 +1 @@
+{"body":"…iller phrases'\r\n\r\nThe YAML description mentioned 'excessive conjunctive phrases' as a pattern type, but this isn't one of the 24 documented patterns. The related concepts are actually covered under Pattern 7 (AI Vocabulary - includes 'Additionally') and Pattern 22 (Filler Phrases). Updated to use the more accurate term 'filler phrases' to match the actual pattern naming.\r\n\r\nBumped version from 2.1.1 to 2.1.2.","files":[{"path":"README.md","additions":1,"deletions":0},{"path":"SKILL.md","additions":2,"deletions":2}],"number":3,"state":"OPEN","title":"Fix YAML description: replace 'excessive conjunctive phrases' with 'f…"}
diff --git a/pr4.diff b/pr4.diff
new file mode 100644
index 0000000..653b414
--- /dev/null
+++ b/pr4.diff
@@ -0,0 +1,406 @@
+diff --git a/README.md b/README.md
+index c895465..3086ebc 100644
+--- a/README.md
++++ b/README.md
+@@ -98,7 +98,7 @@ Based on [Wikipedia's "Signs of AI writing"](https://en.wikipedia.org/wiki/Wikip
+ ## Full Example
+ 
+ **Before (AI-sounding):**
+-> The new software update serves as a testament to the company's commitment to innovation. Moreover, it provides a seamless, intuitive, and powerful user experience—ensuring that users can accomplish their goals efficiently. It's not just an update, it's a revolution in how we think about productivity. Industry experts believe this will have a lasting impact on the entire sector, highlighting the company's pivotal role in the evolving technological landscape.
++> The new software update serves as a testament to the company's commitment to innovation. Moreover, it provides a seamless, intuitive, and powerful user experience—ensuring that users can accomplish their goals efficiently. It's not just an update; it's a revolution in how we think about productivity. Industry experts believe this will have a lasting impact on the entire sector, highlighting the company's pivotal role in the evolving technological landscape.
+ 
+ **After (Humanized):**
+ > The software update adds batch processing, keyboard shortcuts, and offline mode. Early feedback from beta testers has been positive, with most reporting faster task completion.
+diff --git a/SKILL.md b/SKILL.md
+index bbf7e38..c60ccbe 100644
+--- a/SKILL.md
++++ b/SKILL.md
+@@ -38,10 +38,11 @@ When given text to humanize:
+ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+ 
+ ### Signs of soulless writing (even if technically "clean"):
++
+ - Every sentence is the same length and structure
+ - No opinions, just neutral reporting
+ - No acknowledgment of uncertainty or mixed feelings
+-- No first-person perspective when appropriate
++- No first-person perspective
+ - No humor, no edge, no personality
+ - Reads like a Wikipedia article or press release
+ 
+@@ -49,7 +50,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ 
+ **Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+ 
+-**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
++**Vary your rhythm.** Short, punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+ 
+ **Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+ 
+@@ -60,10 +61,12 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+ 
+ ### Before (clean but soulless):
++
+ > The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+ 
+ ### After (has a pulse):
+-> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
++
++> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds; half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+ 
+ ---
+ 
+@@ -76,9 +79,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+ 
+ **Before:**
++
+ > The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+ 
+ **After:**
++
+ > The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+ 
+ ---
+@@ -90,9 +95,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+ 
+ **Before:**
++
+ > Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+ 
+ **After:**
++
+ > In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+ 
+ ---
+@@ -104,9 +111,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+ 
+ **Before:**
++
+ > The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+ 
+ **After:**
++
+ > The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+ 
+ ---
+@@ -118,9 +127,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+ 
+ **Before:**
++
+ > Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+ 
+ **After:**
++
+ > Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+ 
+ ---
+@@ -132,9 +143,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+ 
+ **Before:**
++
+ > Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+ 
+ **After:**
++
+ > The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+ 
+ ---
+@@ -146,9 +159,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+ 
+ **Before:**
++
+ > Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+ 
+ **After:**
++
+ > Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+ 
+ ---
+@@ -162,9 +177,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+ 
+ **Before:**
++
+ > Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+ 
+ **After:**
++
+ > Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+ 
+ ---
+@@ -176,9 +193,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** LLMs substitute elaborate constructions for simple copulas.
+ 
+ **Before:**
++
+ > Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+ 
+ **After:**
++
+ > Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+ 
+ ---
+@@ -188,9 +207,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+ 
+ **Before:**
+-> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
++
++> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song; it's a statement.
+ 
+ **After:**
++
+ > The heavy beat adds to the aggressive tone.
+ 
+ ---
+@@ -200,9 +221,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** LLMs force ideas into groups of three to appear comprehensive.
+ 
+ **Before:**
++
+ > The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+ 
+ **After:**
++
+ > The event includes talks and panels. There's also time for informal networking between sessions.
+ 
+ ---
+@@ -212,9 +235,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+ 
+ **Before:**
++
+ > The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+ 
+ **After:**
++
+ > The protagonist faces many challenges but eventually triumphs and returns home.
+ 
+ ---
+@@ -224,9 +249,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+ 
+ **Before:**
++
+ > Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+ 
+ **After:**
++
+ > The book covers the Big Bang, star formation, and current theories about dark matter.
+ 
+ ---
+@@ -238,9 +265,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+ 
+ **Before:**
++
+ > The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+ 
+ **After:**
++
+ > The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+ 
+ ---
+@@ -250,9 +279,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** AI chatbots emphasize phrases in boldface mechanically.
+ 
+ **Before:**
++
+ > It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+ 
+ **After:**
++
+ > It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+ 
+ ---
+@@ -262,11 +293,13 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** AI outputs lists where items start with bolded headers followed by colons.
+ 
+ **Before:**
++
+ > - **User Experience:** The user experience has been significantly improved with a new interface.
+ > - **Performance:** Performance has been enhanced through optimized algorithms.
+ > - **Security:** Security has been strengthened with end-to-end encryption.
+ 
+ **After:**
++
+ > The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+ 
+ ---
+@@ -276,9 +309,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** AI chatbots capitalize all main words in headings.
+ 
+ **Before:**
++
+ > ## Strategic Negotiations And Global Partnerships
+ 
+ **After:**
++
+ > ## Strategic negotiations and global partnerships
+ 
+ ---
+@@ -288,11 +323,13 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** AI chatbots often decorate headings or bullet points with emojis.
+ 
+ **Before:**
++
+ > 🚀 **Launch Phase:** The product launches in Q3
+ > 💡 **Key Insight:** Users prefer simplicity
+ > ✅ **Next Steps:** Schedule follow-up meeting
+ 
+ **After:**
++
+ > The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+ 
+ ---
+@@ -302,9 +339,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+ 
+ **Before:**
++
+ > He said “the project is on track” but others disagreed.
+ 
+ **After:**
++
+ > He said "the project is on track" but others disagreed.
+ 
+ ---
+@@ -318,9 +357,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** Text meant as chatbot correspondence gets pasted as content.
+ 
+ **Before:**
++
+ > Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+ 
+ **After:**
++
+ > The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+ 
+ ---
+@@ -332,9 +373,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** AI disclaimers about incomplete information get left in text.
+ 
+ **Before:**
++
+ > While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+ 
+ **After:**
++
+ > The company was founded in 1994, according to its registration documents.
+ 
+ ---
+@@ -344,9 +387,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** Overly positive, people-pleasing language.
+ 
+ **Before:**
++
+ > Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+ 
+ **After:**
++
+ > The economic factors you mentioned are relevant here.
+ 
+ ---
+@@ -356,6 +401,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ ### 22. Filler Phrases
+ 
+ **Before → After:**
++
+ - "In order to achieve this goal" → "To achieve this"
+ - "Due to the fact that it was raining" → "Because it was raining"
+ - "At this point in time" → "Now"
+@@ -370,9 +416,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** Over-qualifying statements.
+ 
+ **Before:**
++
+ > It could potentially possibly be argued that the policy might have some effect on outcomes.
+ 
+ **After:**
++
+ > The policy may affect outcomes.
+ 
+ ---
+@@ -382,9 +430,11 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ **Problem:** Vague upbeat endings.
+ 
+ **Before:**
++
+ > The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+ 
+ **After:**
++
+ > The company plans to open two more locations next year.
+ 
+ ---
+@@ -405,6 +455,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ ## Output Format
+ 
+ Provide:
++
+ 1. The rewritten text
+ 2. A brief summary of changes made (optional, if helpful)
+ 
+@@ -413,12 +464,15 @@ Provide:
+ ## Full Example
+ 
+ **Before (AI-sounding):**
+-> The new software update serves as a testament to the company's commitment to innovation. Moreover, it provides a seamless, intuitive, and powerful user experience—ensuring that users can accomplish their goals efficiently. It's not just an update, it's a revolution in how we think about productivity. Industry experts believe this will have a lasting impact on the entire sector, highlighting the company's pivotal role in the evolving technological landscape.
++
++> The new software update serves as a testament to the company's commitment to innovation. Moreover, it provides a seamless, intuitive, and powerful user experience—ensuring that users can accomplish their goals efficiently. It's not just an update; it's a revolution in how we think about productivity. Industry experts believe this will have a lasting impact on the entire sector, highlighting the company's pivotal role in the evolving technological landscape.
+ 
+ **After (Humanized):**
++
+ > The software update adds batch processing, keyboard shortcuts, and offline mode. Early feedback from beta testers has been positive, with most reporting faster task completion.
+ 
+ **Changes made:**
++
+ - Removed "serves as a testament" (inflated symbolism)
+ - Removed "Moreover" (AI vocabulary)
+ - Removed "seamless, intuitive, and powerful" (rule of three + promotional)
+diff --git a/WARP.md b/WARP.md
+index f722d1f..7e81629 100644
+--- a/WARP.md
++++ b/WARP.md
+@@ -5,7 +5,7 @@ This file provides guidance to WARP (warp.dev) when working with code in this re
+ ## What this repo is
+ This repository is a **Claude Code skill** implemented entirely as Markdown.
+ 
+-The “runtime” artifact is `SKILL.md`: Claude Code reads the YAML frontmatter (metadata + allowed tools) and the prompt/instructions that follow.
++The "runtime" artifact is `SKILL.md`: Claude Code reads the YAML frontmatter (metadata + allowed tools) and the prompt/instructions that follow.
+ 
+ `README.md` is for humans: installation, usage, and a compact overview of the patterns.
+ 
+@@ -16,7 +16,7 @@ The “runtime” artifact is `SKILL.md`: Claude Code reads the YAML frontmatter
+   - After the frontmatter is the editor prompt: the canonical, detailed pattern list with examples.
+ - `README.md`
+   - Installation and usage instructions.
+-  - Contains a summarized “24 patterns” table and a short version history.
++  - Contains a summarized "24 patterns" table and a short version history.
+ 
+ When changing behavior/content, treat `SKILL.md` as the source of truth, and update `README.md` to stay consistent.
+ 
+@@ -34,14 +34,14 @@ mkdir -p ~/.claude/skills/humanizer
+ cp SKILL.md ~/.claude/skills/humanizer/
+ ```
+ 
+-## How to “run” it (Claude Code)
++## How to "run" it (Claude Code)
+ Invoke the skill:
+ - `/humanizer` then paste text
+ 
+ ## Making changes safely
+ ### Versioning (keep in sync)
+ - `SKILL.md` has a `version:` field in its YAML frontmatter.
+-- `README.md` has a “Version History” section.
++- `README.md` has a "Version History" section.
+ 
+ If you bump the version, update both.
+ 
diff --git a/pr4.json b/pr4.json
new file mode 100644
index 0000000..b263d7c
--- /dev/null
+++ b/pr4.json
@@ -0,0 +1 @@
+{"body":"- Fix comma splices by replacing commas with semicolons\r\n- Add missing comma between coordinate adjectives (\"Short, punchy\")\r\n- Replace curly quotes with straight quotes in WARP.md\r\n- Remove ambiguous \"when appropriate\" phrase\r\n- Add blank lines for consistent markdown formatting","files":[{"path":"README.md","additions":1,"deletions":1},{"path":"SKILL.md","additions":59,"deletions":5},{"path":"WARP.md","additions":4,"deletions":4}],"number":4,"state":"OPEN","title":"Fix grammatical errors across documentation"}
diff --git a/pr5.diff b/pr5.diff
new file mode 100644
index 0000000..e08fb30
--- /dev/null
+++ b/pr5.diff
@@ -0,0 +1,170 @@
+diff --git a/README.md b/README.md
+index c895465..48d63b3 100644
+--- a/README.md
++++ b/README.md
+@@ -44,7 +44,7 @@ Based on [Wikipedia's "Signs of AI writing"](https://en.wikipedia.org/wiki/Wikip
+ 
+ > "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
+ 
+-## 24 Patterns Detected (with Before/After Examples)
++## 25 Patterns Detected (with Before/After Examples)
+ 
+ ### Content Patterns
+ 
+@@ -78,22 +78,23 @@ Based on [Wikipedia's "Signs of AI writing"](https://en.wikipedia.org/wiki/Wikip
+ | 16 | **Title Case Headings** | "Strategic Negotiations And Partnerships" | "Strategic negotiations and partnerships" |
+ | 17 | **Emojis** | "🚀 Launch Phase: 💡 Key Insight:" | Remove emojis |
+ | 18 | **Curly quotes** | `said “the project”` | `said "the project"` |
++| 19 | **Primary Single Quotes** | `stated, 'This is a pattern.'` | `stated, "This is a pattern."` |
+ 
+ ### Communication Patterns
+ 
+ | # | Pattern | Before | After |
+ |---|---------|--------|-------|
+-| 19 | **Chatbot artifacts** | "I hope this helps! Let me know if..." | Remove entirely |
+-| 20 | **Cutoff disclaimers** | "While details are limited in available sources..." | Find sources or remove |
+-| 21 | **Sycophantic tone** | "Great question! You're absolutely right!" | Respond directly |
++| 20 | **Chatbot artifacts** | "I hope this helps! Let me know if..." | Remove entirely |
++| 21 | **Cutoff disclaimers** | "While details are limited in available sources..." | Find sources or remove |
++| 22 | **Sycophantic tone** | "Great question! You're absolutely right!" | Respond directly |
+ 
+ ### Filler and Hedging
+ 
+ | # | Pattern | Before | After |
+ |---|---------|--------|-------|
+-| 22 | **Filler phrases** | "In order to", "Due to the fact that" | "To", "Because" |
+-| 23 | **Excessive hedging** | "could potentially possibly" | "may" |
+-| 24 | **Generic conclusions** | "The future looks bright" | Specific plans or facts |
++| 23 | **Filler phrases** | "In order to", "Due to the fact that" | "To", "Because" |
++| 24 | **Excessive hedging** | "could potentially possibly" | "may" |
++| 25 | **Generic conclusions** | "The future looks bright" | Specific plans or facts |
+ 
+ ## Full Example
+ 
+@@ -110,6 +111,7 @@ Based on [Wikipedia's "Signs of AI writing"](https://en.wikipedia.org/wiki/Wikip
+ 
+ ## Version History
+ 
++- **2.2.0** - Added Pattern #25 (Primary Single Quotes)
+ - **2.1.1** - Fixed pattern #18 example (curly quotes vs straight quotes)
+ - **2.1.0** - Added before/after examples for all 24 patterns
+ - **2.0.0** - Complete rewrite based on raw Wikipedia article content
+diff --git a/SKILL.md b/SKILL.md
+index bbf7e38..a2403af 100644
+--- a/SKILL.md
++++ b/SKILL.md
+@@ -1,6 +1,6 @@
+ ---
+ name: humanizer
+-version: 2.1.1
++version: 2.2.0
+ description: |
+   Remove signs of AI-generated writing from text. Use when editing or reviewing
+   text to make it sound more natural and human-written. Based on Wikipedia's
+@@ -309,9 +309,21 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ 
+ ---
+ 
++### 19. Primary Single Quotes (Code-Style Quotation)
++
++**Problem:** AI models trained on code often use single quotes as primary delimiters.
++
++**Before:**
++> stated, 'This is a pattern.'
++
++**After:**
++> stated, "This is a pattern."
++
++---
++
+ ## COMMUNICATION PATTERNS
+ 
+-### 19. Collaborative Communication Artifacts
++### 20. Collaborative Communication Artifacts
+ 
+ **Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+ 
+@@ -325,7 +337,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ 
+ ---
+ 
+-### 20. Knowledge-Cutoff Disclaimers
++### 21. Knowledge-Cutoff Disclaimers
+ 
+ **Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+ 
+@@ -339,7 +351,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ 
+ ---
+ 
+-### 21. Sycophantic/Servile Tone
++### 22. Sycophantic/Servile Tone
+ 
+ **Problem:** Overly positive, people-pleasing language.
+ 
+@@ -353,7 +365,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ 
+ ## FILLER AND HEDGING
+ 
+-### 22. Filler Phrases
++### 23. Filler Phrases
+ 
+ **Before → After:**
+ - "In order to achieve this goal" → "To achieve this"
+@@ -365,7 +377,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ 
+ ---
+ 
+-### 23. Excessive Hedging
++### 24. Excessive Hedging
+ 
+ **Problem:** Over-qualifying statements.
+ 
+@@ -377,7 +389,7 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
+ 
+ ---
+ 
+-### 24. Generic Positive Conclusions
++### 25. Generic Positive Conclusions
+ 
+ **Problem:** Vague upbeat endings.
+ 
+diff --git a/WARP.md b/WARP.md
+index f722d1f..e13d768 100644
+--- a/WARP.md
++++ b/WARP.md
+@@ -5,7 +5,7 @@ This file provides guidance to WARP (warp.dev) when working with code in this re
+ ## What this repo is
+ This repository is a **Claude Code skill** implemented entirely as Markdown.
+ 
+-The “runtime” artifact is `SKILL.md`: Claude Code reads the YAML frontmatter (metadata + allowed tools) and the prompt/instructions that follow.
++The "runtime" artifact is `SKILL.md`: Claude Code reads the YAML frontmatter (metadata + allowed tools) and the prompt/instructions that follow.
+ 
+ `README.md` is for humans: installation, usage, and a compact overview of the patterns.
+ 
+@@ -16,7 +16,7 @@ The “runtime” artifact is `SKILL.md`: Claude Code reads the YAML frontmatter
+   - After the frontmatter is the editor prompt: the canonical, detailed pattern list with examples.
+ - `README.md`
+   - Installation and usage instructions.
+-  - Contains a summarized “24 patterns” table and a short version history.
++  - Contains a summarized "25 patterns" table and a short version history.
+ 
+ When changing behavior/content, treat `SKILL.md` as the source of truth, and update `README.md` to stay consistent.
+ 
+@@ -34,14 +34,14 @@ mkdir -p ~/.claude/skills/humanizer
+ cp SKILL.md ~/.claude/skills/humanizer/
+ ```
+ 
+-## How to “run” it (Claude Code)
++## How to "run" it (Claude Code)
+ Invoke the skill:
+ - `/humanizer` then paste text
+ 
+ ## Making changes safely
+ ### Versioning (keep in sync)
+ - `SKILL.md` has a `version:` field in its YAML frontmatter.
+-- `README.md` has a “Version History” section.
++- `README.md` has a "Version History" section.
+ 
+ If you bump the version, update both.
+ 
diff --git a/pr5.json b/pr5.json
new file mode 100644
index 0000000..23babda
--- /dev/null
+++ b/pr5.json
@@ -0,0 +1 @@
+{"body":"This Pull Request addresses a persistent AI-generated writing flaw: the use of single quotes (`'`) as the primary quotation mark in prose, a style that originates from programming conventions rather than standard English.\r\n\r\n**Changes Included:**\r\n\r\n1.  **Updated `SKILL.md`:**\r\n    *   Added **Pattern #19: Primary Single Quotes** to the `STYLE PATTERNS` section.\r\n    *   Renumbered subsequent patterns to maintain logical order.\r\n    *   Bumped version to `2.2.0`.\r\n\r\n2.  **Updated `README.md`:**\r\n    *   Added Pattern #19 to the Style Patterns table.\r\n    *   Renumbered subsequent patterns in the tables.\r\n    *   Updated header to \"25 Patterns Detected\".\r\n    *   Added `2.2.0` to the Version History.\r\n\r\n3.  **Updated `WARP.md`:**\r\n    *   Updated the summary to reflect \"25 patterns\".\r\n\r\n**New Pattern Details:**\r\n\r\n| # | Pattern | Before | After |\r\n|---|---------|--------|-------|\r\n| 19 | **Primary Single Quotes** | `stated, 'This is a pattern.'` | `stated, \"This is a pattern.\"` |\r\n\r\nexample: https://github.com/blader/humanizer/pull/3","files":[{"path":"README.md","additions":9,"deletions":7},{"path":"SKILL.md","additions":19,"deletions":7},{"path":"WARP.md","additions":4,"deletions":4}],"number":5,"state":"OPEN","title":"feat: Add detection for AI-style primary single quotes (Pattern #25 (new #19))"}
diff --git a/pyproject.toml b/pyproject.toml
new file mode 100644
index 0000000..39f4c40
--- /dev/null
+++ b/pyproject.toml
@@ -0,0 +1,104 @@
+[project]
+name = "humanizer"
+version = "2.1.1"
+description = "Remove signs of AI-generated writing from text."
+requires-python = ">=3.10"
+dependencies = []
+
+[tool.ruff]
+line-length = 88
+target-version = "py310"
+
+[tool.ruff.lint]
+select = [
+    "E",    # pycodestyle errors
+    "W",    # pycodestyle warnings
+    "F",    # pyflakes
+    "I",    # isort
+    "C",    # flake8-comprehensions
+    "B",    # flake8-bugbear
+    "UP",   # pyupgrade
+    "N",    # pep8-naming
+    "ANN",  # flake8-annotations
+    "S",    # flake8-bandit
+    "BLE",  # flake8-blind-except
+    "FBT",  # flake8-boolean-trap
+    "A",    # flake8-builtins
+    "COM",  # flake8-commas
+    "C4",   # flake8-comprehensions
+    "DTZ",  # flake8-datetimez
+    "T10",  # flake8-debugger
+    "EM",   # flake8-errmsg
+    "EXE",  # flake8-executable
+    "ISC",  # flake8-implicit-str-concat
+    "ICN",  # flake8-import-conventions
+    "G",    # flake8-logging-format
+    "INP",  # flake8-no-pep420
+    "PIE",  # flake8-pie
+    "T20",  # flake8-print
+    "PYI",  # flake8-pyi
+    "PT",   # flake8-pytest-style
+    "Q",    # flake8-quotes
+    "RSE",  # flake8-raise
+    "RET",  # flake8-return
+    "SLF",  # flake8-self
+    "SIM",  # flake8-simplify
+    "TID",  # flake8-tidy-imports
+    "TCH",  # flake8-type-checking
+    "ARG",  # flake8-unused-arguments
+    "PTH",  # flake8-use-pathlib
+    "ERA",  # eradicate
+    "PD",   # pandas-vet
+    "PGH",  # pygrep-hooks
+    "PL",   # pylint
+    "TRY",  # tryceratops
+    "FLY",  # flynt
+    "RUF",  # Ruff-specific rules
+    "D",    # pydocstyle
+    "PERF", # Perflint
+    "LOG",  # flake8-logging
+]
+ignore = [
+    "ANN101", # Missing type annotation for self in method
+    "ANN102", # Missing type annotation for cls in classmethod
+    "COM812", # Missing trailing comma (conflicts with formatter)
+    "ISC001", # Single line implicit string concatenation (conflicts with formatter)
+]
+
+[tool.ruff.lint.pylint]
+max-args = 5
+
+[tool.mypy]
+python_version = "3.10"
+strict = true
+warn_return_any = true
+warn_unused_configs = true
+disallow_untyped_defs = true
+disallow_incomplete_defs = true
+check_untyped_defs = true
+disallow_untyped_decorators = true
+no_implicit_optional = true
+warn_redundant_casts = true
+warn_unused_ignores = true
+warn_no_return = true
+warn_unreachable = true
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+python_files = ["test_*.py"]
+addopts = "--strict-markers --cov=scripts --cov-report=term-missing --cov-fail-under=100"
+
+[tool.coverage.run]
+source = ["scripts"]
+branch = true
+
+[tool.coverage.report]
+exclude_lines = [
+    "pragma: no cover",
+    "def __repr__",
+    "if self.debug:",
+    "if __name__ == .__main__.:",
+    "raise AssertionError",
+    "raise NotImplementedError",
+    "if TYPE_CHECKING:",
+]
diff --git a/scripts/__init__.py b/scripts/__init__.py
new file mode 100644
index 0000000..6ede9e0
--- /dev/null
+++ b/scripts/__init__.py
@@ -0,0 +1 @@
+"""Scripts for managing Humanizer adapters."""
diff --git a/scripts/install-adapters.cmd b/scripts/install-adapters.cmd
new file mode 100644
index 0000000..a5bfa8d
--- /dev/null
+++ b/scripts/install-adapters.cmd
@@ -0,0 +1,2 @@
+@echo off
+python "%~dp0install_adapters.py" %*
diff --git a/scripts/install_adapters.py b/scripts/install_adapters.py
new file mode 100644
index 0000000..ce0e0df
--- /dev/null
+++ b/scripts/install_adapters.py
@@ -0,0 +1,112 @@
+#!/usr/bin/env python3
+"""Install Humanizer adapters into their respective locations."""
+
+import argparse
+import logging
+import shutil
+import subprocess
+import sys
+from pathlib import Path
+
+# Configure logging
+logging.basicConfig(level=logging.INFO, format="%(message)s")
+logger = logging.getLogger(__name__)
+
+
+def install_file(source: Path, dest_dir: Path, dest_name: str) -> None:
+    """Create directories if needed and copy a file."""
+    if not source.exists():
+        logger.warning("Source not found: %s", source)
+        return
+
+    dest_dir.mkdir(parents=True, exist_ok=True)
+    dest_path = dest_dir / dest_name
+    shutil.copy2(source, dest_path)
+    logger.info("Installed: %s", dest_path)
+
+
+def main() -> None:
+    """Run the installation script."""
+    parser = argparse.ArgumentParser(description="Install Humanizer adapters.")
+    parser.add_argument(
+        "--skip-validation",
+        action="store_true",
+        help="Skip validation before installation",
+    )
+    args = parser.parse_args()
+
+    root = Path(__file__).parent.parent
+    scripts_dir = root / "scripts"
+
+    # 1. Validate first (unless skipped)
+    if not args.skip_validation:
+        logger.info("Running validation before installation...")
+        validate_script = scripts_dir / "validate_adapters.py"
+        result = subprocess.run(  # noqa: S603
+            [sys.executable, str(validate_script)],
+            check=False,
+            capture_output=True,
+            text=True,
+        )
+        if result.returncode != 0:
+            logger.error("Validation failed. Aborting installation.")
+            logger.error(result.stderr)
+            sys.exit(1)
+
+    logger.info("Starting Universal Installation...")
+
+    # 2. Gemini CLI Extension (User Dir)
+    gemini_extensions = Path.home() / ".gemini" / "extensions" / "humanizer"
+    logger.info("Installing Gemini CLI Extension...")
+    source_gemini = root / "adapters" / "gemini-extension"
+    if source_gemini.exists():
+        if gemini_extensions.exists():
+            shutil.rmtree(gemini_extensions)
+        shutil.copytree(source_gemini, gemini_extensions)
+        logger.info("Installed to: %s", gemini_extensions)
+    else:
+        logger.warning("Source not found: %s", source_gemini)
+
+    # 3. Google Antigravity (Workspace)
+    adapters = root / "adapters"
+    install_file(
+        adapters / "antigravity-skill" / "SKILL.md",
+        root / ".agent" / "skills" / "humanizer",
+        "SKILL.md",
+    )
+    install_file(
+        adapters / "antigravity-skill" / "README.md",
+        root / ".agent" / "skills" / "humanizer",
+        "README.md",
+    )
+    install_file(
+        adapters / "antigravity-rules-workflows" / "rules" / "humanizer.md",
+        root / ".agent" / "rules",
+        "humanizer.md",
+    )
+    install_file(
+        adapters / "antigravity-rules-workflows" / "workflows" / "humanize.md",
+        root / ".agent" / "workflows",
+        "humanize.md",
+    )
+
+    # 4. VS Code (Workspace)
+    install_file(
+        adapters / "vscode" / "humanizer.code-snippets",
+        root / ".vscode",
+        "humanizer.code-snippets",
+    )
+
+    # 5. Qwen CLI (Root)
+    install_file(adapters / "qwen-cli" / "QWEN.md", root, "QWEN.md")
+
+    # 6. GitHub Copilot (Root .github)
+    install_file(
+        adapters / "copilot" / "COPILOT.md", root / ".github", "copilot-instructions.md"
+    )
+
+    logger.info("\nUniversal Installation Complete.")
+
+
+if __name__ == "__main__":
+    main()
diff --git a/scripts/sync-adapters.cmd b/scripts/sync-adapters.cmd
new file mode 100644
index 0000000..c519f22
--- /dev/null
+++ b/scripts/sync-adapters.cmd
@@ -0,0 +1,2 @@
+@echo off
+node "%~dp0sync-adapters.js" %*
diff --git a/scripts/sync-adapters.js b/scripts/sync-adapters.js
new file mode 100644
index 0000000..443280c
--- /dev/null
+++ b/scripts/sync-adapters.js
@@ -0,0 +1,72 @@
+import fs from 'fs';
+import path from 'path';
+
+const SRC_DIR = 'src';
+const CORE_FM_PATH = path.join(SRC_DIR, 'core_frontmatter.yaml');
+const CORE_PATTERNS_PATH = path.join(SRC_DIR, 'core_patterns.md');
+const HUMAN_HEADER_PATH = path.join(SRC_DIR, 'human_header.md');
+const PRO_HEADER_PATH = path.join(SRC_DIR, 'pro_header.md');
+
+function compileSkill(headerPath) {
+  if (!fs.existsSync(headerPath)) throw new Error(`Header not found: ${headerPath}`);
+  const header = fs.readFileSync(headerPath, 'utf8');
+  const coreFM = fs.readFileSync(CORE_FM_PATH, 'utf8');
+  const corePatterns = fs.readFileSync(CORE_PATTERNS_PATH, 'utf8');
+
+  let full = header.replace('<<<<[CORE_FRONTMATTER]>>>>', coreFM);
+  full = full + '\n' + corePatterns;
+  return full;
+}
+
+console.log('Compiling Standard Humanizer...');
+const standardContent = compileSkill(HUMAN_HEADER_PATH);
+fs.writeFileSync('SKILL.md', standardContent, 'utf8');
+
+console.log('Compiling Humanizer Pro...');
+const proContent = compileSkill(PRO_HEADER_PATH);
+fs.writeFileSync('SKILL_PROFESSIONAL.md', proContent, 'utf8');
+
+const vStandard = standardContent.match(/^version:\s*([\w.-]+)\s*$/m)?.[1];
+const vPro = proContent.match(/^version:\s*([\w.-]+)\s*$/m)?.[1];
+// UTC date to match Python sync behavior.
+const today = new Date().toISOString().split('T')[0];
+
+console.log(`Standard Version: ${vStandard}`);
+console.log(`Pro Version: ${vPro}`);
+
+const adapters = [
+  { name: 'Antigravity Skill Standard', path: 'adapters/antigravity-skill/SKILL.md', source: standardContent, id: 'antigravity-skill', format: 'Antigravity skill', base: 'SKILL.md' },
+  { name: 'Antigravity Skill Pro', path: 'adapters/antigravity-skill/SKILL_PROFESSIONAL.md', source: proContent, id: 'antigravity-skill-pro', format: 'Antigravity skill', base: 'SKILL_PROFESSIONAL.md' },
+  { name: 'Gemini Extension Standard', path: 'adapters/gemini-extension/GEMINI.md', source: standardContent, id: 'gemini-extension', format: 'Gemini extension', base: 'SKILL.md' },
+  { name: 'Gemini Extension Pro', path: 'adapters/gemini-extension/GEMINI_PRO.md', source: proContent, id: 'gemini-extension-pro', format: 'Gemini extension', base: 'SKILL_PROFESSIONAL.md' },
+  { name: 'Rules Workflows Standard', path: 'adapters/antigravity-rules-workflows/README.md', source: standardContent, id: 'antigravity-rules-workflows', format: 'Antigravity rules/workflows', base: 'SKILL.md' },
+  { name: 'Qwen CLI Standard', path: 'adapters/qwen-cli/QWEN.md', source: standardContent, id: 'qwen-cli', format: 'Qwen CLI context', base: 'SKILL.md' },
+  { name: 'Copilot Standard', path: 'adapters/copilot/COPILOT.md', source: standardContent, id: 'copilot', format: 'Copilot instructions', base: 'SKILL.md' },
+  { name: 'VSCode Standard', path: 'adapters/vscode/HUMANIZER.md', source: standardContent, id: 'vscode', format: 'VSCode markdown', base: 'SKILL.md' }
+];
+
+adapters.forEach(adapter => {
+  console.log(`Syncing ${adapter.name}...`);
+  const name = adapter.source.match(/^name:\s*([\w.-]+)\s*$/m)?.[1];
+  const version = adapter.source.match(/^version:\s*([\w.-]+)\s*$/m)?.[1];
+
+  if (!name) throw new Error(`Could not find name for ${adapter.path}`);
+
+  const metaBlock = `---
+adapter_metadata:
+  skill_name: ${name}
+  skill_version: ${version}
+  last_synced: ${today}
+  source_path: ${adapter.base}
+  adapter_id: ${adapter.id}
+  adapter_format: ${adapter.format}
+---
+
+`;
+  const newContent = metaBlock + '\n' + adapter.source;
+  const dir = path.dirname(adapter.path);
+  if (!fs.existsSync(dir)) fs.mkdirSync(dir, { recursive: true });
+  fs.writeFileSync(adapter.path, newContent, 'utf8');
+});
+
+console.log('\nSync Complete. All adapters updated from local source fragments.');
diff --git a/scripts/sync_adapters.py b/scripts/sync_adapters.py
new file mode 100644
index 0000000..3aa6207
--- /dev/null
+++ b/scripts/sync_adapters.py
@@ -0,0 +1,122 @@
+#!/usr/bin/env python3
+"""Sync Humanizer adapters with the canonical SKILL.md."""
+
+import argparse
+import logging
+import re
+from datetime import datetime, timezone
+from pathlib import Path
+
+# Configure logging
+logging.basicConfig(level=logging.INFO, format="%(message)s")
+logger = logging.getLogger(__name__)
+
+
+def get_skill_version(source_path: Path) -> str:
+    """Extract the version from the SKILL.md file."""
+    if not source_path.exists():
+        msg = f"Source file {source_path} not found!"
+        raise FileNotFoundError(msg)
+
+    content = source_path.read_text(encoding="utf-8")
+    match = re.search(r"(?m)^version:\s*([\w.-]+)\s*$", content)
+    if not match:
+        msg = f"Could not parse version from {source_path}"
+        raise ValueError(msg)
+
+    return match.group(1)
+
+
+def sync_antigravity_skill(
+    source_path: Path, dest_path: Path, version: str, today: str
+) -> None:
+    """Sync Antigravity Skill (Full Content Copy + Metadata Injection)."""
+    logger.info("Syncing Antigravity Skill to %s...", dest_path)
+    source_content = source_path.read_text(encoding="utf-8")
+
+    frontmatter = f"""---
+adapter_metadata:
+  skill_name: humanizer
+  skill_version: {version}
+  last_synced: {today}
+  source_path: {source_path.name}
+  adapter_id: antigravity-skill
+  adapter_format: Antigravity skill
+---
+
+"""
+    new_content = frontmatter + source_content
+    dest_path.parent.mkdir(parents=True, exist_ok=True)
+    dest_path.write_text(new_content, encoding="utf-8", newline="\n")
+    logger.info("Updated %s", dest_path)
+
+
+def update_metadata(dest_path: Path, version: str, today: str) -> None:
+    """Update metadata (Version/Date only) in an adapter file."""
+    if not dest_path.exists():
+        logger.warning("Warning: %s not found.", dest_path)
+        return
+
+    logger.info("Updating metadata in %s...", dest_path)
+    content = dest_path.read_text(encoding="utf-8")
+    content = re.sub(r"skill_version:.*", f"skill_version: {version}", content)
+    content = re.sub(r"last_synced:.*", f"last_synced: {today}", content)
+    dest_path.write_text(content, encoding="utf-8", newline="\n")
+    logger.info("Updated %s", dest_path)
+
+
+def main() -> None:
+    """Run the sync script."""
+    parser = argparse.ArgumentParser(description="Sync Humanizer adapters.")
+    parser.add_argument(
+        "--source",
+        type=Path,
+        default=Path("SKILL.md"),
+        help="Path to the canonical SKILL.md",
+    )
+    args = parser.parse_args()
+
+    source_path = args.source
+    try:
+        version = get_skill_version(source_path)
+    except (FileNotFoundError, ValueError) as e:
+        logger.error("Error: %s", e)  # noqa: TRY400
+        return
+
+    # Use UTC date to match JS sync behavior (ISO YYYY-MM-DD).
+    today = datetime.now(tz=timezone.utc).date().isoformat()
+
+    logger.info("Detected Version: %s", version)
+    logger.info("Sync Date: %s", today)
+
+    # Define paths
+    root = Path(__file__).parent.parent
+    adapters = root / "adapters"
+
+    # 1. Antigravity Skill
+    sync_antigravity_skill(
+        source_path, adapters / "antigravity-skill" / "SKILL.md", version, today
+    )
+
+    # 2. Gemini Extension
+    update_metadata(adapters / "gemini-extension" / "GEMINI.md", version, today)
+
+    # 3. Antigravity Rules Metadata
+    update_metadata(
+        adapters / "antigravity-rules-workflows" / "README.md", version, today
+    )
+
+    # 4. Qwen CLI Metadata
+    update_metadata(adapters / "qwen-cli" / "QWEN.md", version, today)
+
+    # 5. Copilot Metadata
+    update_metadata(adapters / "copilot" / "COPILOT.md", version, today)
+
+    # 6. VS Code Metadata
+    update_metadata(adapters / "vscode" / "HUMANIZER.md", version, today)
+
+    logger.info("Sync Complete.")
+
+
+if __name__ == "__main__":
+    main()
diff --git a/scripts/validate-adapters.cmd b/scripts/validate-adapters.cmd
new file mode 100644
index 0000000..7a1a023
--- /dev/null
+++ b/scripts/validate-adapters.cmd
@@ -0,0 +1,2 @@
+@echo off
+node "%~dp0validate-adapters.js" %*
diff --git a/scripts/validate-adapters.js b/scripts/validate-adapters.js
new file mode 100644
index 0000000..ab13cc2
--- /dev/null
+++ b/scripts/validate-adapters.js
@@ -0,0 +1,52 @@
+import fs from 'fs';
+
+const adapters = [
+  { path: 'adapters/antigravity-skill/SKILL.md', base: 'SKILL.md' },
+  { path: 'adapters/antigravity-skill/SKILL_PROFESSIONAL.md', base: 'SKILL_PROFESSIONAL.md' },
+  { path: 'adapters/gemini-extension/GEMINI.md', base: 'SKILL.md' },
+  { path: 'adapters/gemini-extension/GEMINI_PRO.md', base: 'SKILL_PROFESSIONAL.md' },
+  { path: 'adapters/antigravity-rules-workflows/README.md', base: 'SKILL.md' },
+  { path: 'adapters/qwen-cli/QWEN.md', base: 'SKILL.md' },
+  { path: 'adapters/copilot/COPILOT.md', base: 'SKILL.md' },
+  { path: 'adapters/vscode/HUMANIZER.md', base: 'SKILL.md' }
+];
+
+let failed = false;
+
+adapters.forEach(adapter => {
+  if (!fs.existsSync(adapter.path)) {
+    console.error(`Missing: ${adapter.path}`);
+    failed = true;
+    return;
+  }
+
+  const content = fs.readFileSync(adapter.path, 'utf8');
+  const metaMatch = content.match(/^---\s*adapter_metadata:([\s\S]*?)^---\s*/m);
+  
+  if (!metaMatch) {
+    console.error(`No metadata found in ${adapter.path}`);
+    failed = true;
+    return;
+  }
+
+  const sourceContent = fs.readFileSync(adapter.base, 'utf8');
+  const sourceName = sourceContent.match(/^name:\s*([\w.-]+)\s*$/m)?.[1];
+  const sourceVersion = sourceContent.match(/^version:\s*([\w.-]+)\s*$/m)?.[1];
+
+  const metaContent = metaMatch[1];
+  const metaName = metaContent.match(/skill_name:\s*([\w.-]+)/)?.[1];
+  const metaVersion = metaContent.match(/skill_version:\s*([\w.-]+)/)?.[1];
+  const metaSource = metaContent.match(/source_path:\s*([\w.-]+)/)?.[1];
+
+  if (metaName !== sourceName || metaVersion !== sourceVersion || metaSource !== adapter.base) {
+    console.error(`Validation Failed for ${adapter.path}:`);
+    console.error(`  Expected: ${sourceName} v${sourceVersion} (from ${adapter.base})`);
+    console.error(`  Found:    ${metaName} v${metaVersion} (source: ${metaSource})`);
+    failed = true;
+  } else {
+    console.log(`Valid: ${adapter.path}`);
+  }
+});
+
+if (failed) process.exit(1);
+console.log('\nValidation Complete.');
diff --git a/scripts/validate_adapters.py b/scripts/validate_adapters.py
new file mode 100644
index 0000000..b5a70db
--- /dev/null
+++ b/scripts/validate_adapters.py
@@ -0,0 +1,110 @@
+#!/usr/bin/env python3
+"""Validate Humanizer adapters against the canonical SKILL.md."""
+
+import argparse
+import logging
+import re
+import sys
+from pathlib import Path
+
+# Configure logging
+logging.basicConfig(level=logging.INFO, format="%(message)s")
+logger = logging.getLogger(__name__)
+
+
+def get_skill_metadata(source_path: Path) -> tuple[str, str]:
+    """Extract name and version from the SKILL.md file."""
+    if not source_path.exists():
+        msg = f"Source file {source_path} not found!"
+        raise FileNotFoundError(msg)
+
+    content = source_path.read_text(encoding="utf-8")
+    name_match = re.search(r"(?m)^name:\s*([\w.-]+)\s*$", content)
+    version_match = re.search(r"(?m)^version:\s*([\w.-]+)\s*$", content)
+
+    if not name_match or not version_match:
+        msg = f"Failed to read name/version from {source_path}"
+        raise ValueError(msg)
+
+    return name_match.group(1), version_match.group(1)
+
+
+def validate_adapter(
+    adapter_path: Path, skill_name: str, skill_version: str, source_path: str
+) -> list[str]:
+    """Validate a single adapter file's metadata."""
+    if not adapter_path.exists():
+        return [f"Missing adapter file: {adapter_path}"]
+
+    errors = []
+    content = adapter_path.read_text(encoding="utf-8")
+
+    if not re.search(rf"skill_name:\s*{re.escape(skill_name)}", content):
+        errors.append(f"{adapter_path}: skill_name mismatch (expected {skill_name})")
+
+    if not re.search(rf"skill_version:\s*{re.escape(skill_version)}", content):
+        errors.append(
+            f"{adapter_path}: skill_version mismatch (expected {skill_version})"
+        )
+
+    if "last_synced:" not in content:
+        errors.append(f"{adapter_path}: missing last_synced")
+
+    if not re.search(rf"source_path:\s*{re.escape(source_path)}", content):
+        errors.append(f"{adapter_path}: source_path mismatch (expected {source_path})")
+
+    return errors
+
+
+def main() -> None:
+    """Run the validation script."""
+    parser = argparse.ArgumentParser(description="Validate Humanizer adapters.")
+    parser.add_argument(
+        "--source",
+        type=Path,
+        default=Path("SKILL.md"),
+        help="Path to the canonical SKILL.md",
+    )
+    args = parser.parse_args()
+
+    source_path = args.source
+    try:
+        skill_name, skill_version = get_skill_metadata(source_path)
+    except (FileNotFoundError, ValueError) as e:
+        logger.error("Error: %s", e)  # noqa: TRY400
+        sys.exit(1)
+
+    adapters = [
+        "AGENTS.md",
+        "adapters/gemini-extension/GEMINI.md",
+        "adapters/vscode/HUMANIZER.md",
+        "adapters/antigravity-skill/SKILL.md",
+        "adapters/antigravity-rules-workflows/README.md",
+        "adapters/qwen-cli/QWEN.md",
+        "adapters/copilot/COPILOT.md",
+    ]
+
+    all_errors = []
+    root = Path(__file__).parent.parent
+    for adapter_rel_path in adapters:
+        adapter_path = root / adapter_rel_path
+        all_errors.extend(
+            validate_adapter(adapter_path, skill_name, skill_version, str(source_path))
+        )
+
+    if all_errors:
+        for error in all_errors:
+            logger.error("%s", error)
+        sys.exit(1)
+
+    logger.info(
+        "Adapter metadata validated against %s (%s %s).",
+        source_path,
+        skill_name,
+        skill_version,
+    )
+    sys.exit(0)
+
+
+if __name__ == "__main__":
+    main()
diff --git a/src/core_frontmatter.yaml b/src/core_frontmatter.yaml
new file mode 100644
index 0000000..a0446be
--- /dev/null
+++ b/src/core_frontmatter.yaml
@@ -0,0 +1,7 @@
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Grep
+  - Glob
+  - AskUserQuestion
diff --git a/src/core_patterns.md b/src/core_patterns.md
new file mode 100644
index 0000000..176293d
--- /dev/null
+++ b/src/core_patterns.md
@@ -0,0 +1,406 @@
+
+## CONTENT PATTERNS
+
+### 1. Undue Emphasis on Significance, Legacy, and Broader Trends
+
+**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
+
+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
+
+**Before:**
+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
+
+**After:**
+> The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
+
+---
+
+### 2. Undue Emphasis on Notability and Media Coverage
+
+**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
+
+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.
+
+**Before:**
+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
+
+**After:**
+> In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
+
+---
+
+### 3. Superficial Analyses with -ing Endings
+
+**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
+
+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
+
+**Before:**
+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
+
+**After:**
+> The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
+
+---
+
+### 4. Promotional and Advertisement-like Language
+
+**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
+
+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
+
+**Before:**
+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
+
+**After:**
+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
+
+---
+
+### 5. Vague Attributions and Weasel Words
+
+**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
+
+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.
+
+**Before:**
+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
+
+**After:**
+> The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
+
+---
+
+### 6. Outline-like "Challenges and Future Prospects" Sections
+
+**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
+
+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.
+
+**Before:**
+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
+
+**After:**
+> Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
+
+---
+
+## LANGUAGE AND GRAMMAR PATTERNS
+
+### 7. Overused "AI Vocabulary" Words
+
+**High-frequency AI words:** Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
+
+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.
+
+**Before:**
+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
+
+**After:**
+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
+
+---
+
+### 8. Avoidance of "is"/"are" (Copula Avoidance)
+
+**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]
+
+**Problem:** LLMs substitute elaborate constructions for simple copulas.
+
+**Before:**
+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
+
+**After:**
+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
+
+---
+
+### 9. Negative Parallelisms
+
+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused.
+
+**Before:**
+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
+
+**After:**
+> The heavy beat adds to the aggressive tone.
+
+---
+
+### 10. Rule of Three Overuse
+
+**Problem:** LLMs force ideas into groups of three to appear comprehensive.
+
+**Before:**
+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
+
+**After:**
+> The event includes talks and panels. There's also time for informal networking between sessions.
+
+---
+
+### 11. Elegant Variation (Synonym Cycling)
+
+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.
+
+**Before:**
+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
+
+**After:**
+> The protagonist faces many challenges but eventually triumphs and returns home.
+
+---
+
+### 12. False Ranges
+
+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
+
+**Before:**
+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
+
+**After:**
+> The book covers the Big Bang, star formation, and current theories about dark matter.
+
+---
+
+## STYLE PATTERNS
+
+### 13. Em Dash Overuse
+
+**Problem:** LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing.
+
+**Before:**
+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
+
+**After:**
+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
+
+---
+
+### 14. Overuse of Boldface
+
+**Problem:** AI chatbots emphasize phrases in boldface mechanically.
+
+**Before:**
+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.
+
+**After:**
+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
+
+---
+
+### 15. Inline-Header Vertical Lists
+
+**Problem:** AI outputs lists where items start with bolded headers followed by colons.
+
+**Before:**
+
+- **User Experience:** The user experience has been significantly improved with a new interface.
+- **Performance:** Performance has been enhanced through optimized algorithms.
+- **Security:** Security has been strengthened with end-to-end encryption.
+
+**After:**
+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
+
+---
+
+### 16. Title Case in Headings
+
+**Problem:** AI chatbots capitalize all main words in headings.
+
+**Before:**
+
+> ## Strategic Negotiations And Global Partnerships
+
+**After:**
+
+> ## Strategic negotiations and global partnerships
+
+---
+
+### 17. Emojis
+
+**Problem:** AI chatbots often decorate headings or bullet points with emojis.
+
+**Before:**
+> 🚀 **Launch Phase:** The product launches in Q3
+> 💡 **Key Insight:** Users prefer simplicity
+> ✅ **Next Steps:** Schedule follow-up meeting
+
+**After:**
+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
+
+---
+
+### 18. Curly Quotation Marks
+
+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").
+
+**Before:**
+> He said “the project is on track” but others disagreed.
+
+**After:**
+> He said "the project is on track" but others disagreed.
+
+---
+
+## COMMUNICATION PATTERNS
+
+### 19. Collaborative Communication Artifacts
+
+**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
+
+**Problem:** Text meant as chatbot correspondence gets pasted as content.
+
+**Before:**
+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
+
+**After:**
+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
+
+---
+
+### 20. Knowledge-Cutoff Disclaimers
+
+**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
+
+**Problem:** AI disclaimers about incomplete information get left in text.
+
+**Before:**
+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
+
+**After:**
+> The company was founded in 1994, according to its registration documents.
+
+---
+
+### 21. Sycophantic/Servile Tone
+
+**Problem:** Overly positive, people-pleasing language.
+
+**Before:**
+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
+
+**After:**
+> The economic factors you mentioned are relevant here.
+
+---
+
+## FILLER AND HEDGING
+
+### 22. Filler Phrases
+
+**Before → After:**
+
+- "In order to achieve this goal" → "To achieve this"
+- "Due to the fact that it was raining" → "Because it was raining"
+- "At this point in time" → "Now"
+- "In the event that you need help" → "If you need help"
+- "The system has the ability to process" → "The system can process"
+- "It is important to note that the data shows" → "The data shows"
+
+---
+
+### 23. Excessive Hedging
+
+**Problem:** Over-qualifying statements.
+
+**Before:**
+> It could potentially possibly be argued that the policy might have some effect on outcomes.
+
+**After:**
+> The policy may affect outcomes.
+
+---
+
+### 24. Generic Positive Conclusions
+
+**Problem:** Vague upbeat endings.
+
+**Before:**
+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
+
+**After:**
+> The company plans to open two more locations next year.
+
+---
+
+## Process
+
+1. Read the input text carefully
+2. Identify all instances of the patterns above
+3. Rewrite each problematic section
+4. Ensure the revised text:
+   - Sounds natural when read aloud
+   - Varies sentence structure naturally
+   - Uses specific details over vague claims
+   - Maintains appropriate tone for context
+   - Uses simple constructions (is/are/has) where appropriate
+5. Present the humanized version
+
+## Output Format
+
+Provide:
+
+1. The rewritten text
+2. A brief summary of changes made (optional, if helpful)
+
+---
+
+## Full Example
+
+**Before (AI-sounding):**
+> Great question! Here is an essay on this topic. I hope this helps!
+>
+> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
+>
+> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
+>
+> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
+>
+> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
+> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
+> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
+>
+> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
+>
+> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!
+
+**After (Humanized):**
+> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
+>
+> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
+>
+> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
+>
+> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
+>
+> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
+
+**Changes made:**
+
+- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
+- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
+- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
+- Removed vague attributions ("Industry observers") and replaced with specific sources (Google study, named engineers, Uplevel study)
+- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
+- Removed negative parallelism ("It's not just X; it's Y")
+- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
+- Removed false ranges ("from X to Y, from A to B")
+- Removed em dashes, emojis, boldface headers, and curly quotes
+- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
+- Removed formulaic challenges section ("Despite challenges... continues to thrive")
+- Removed knowledge-cutoff hedging ("While specific details are limited...")
+- Removed excessive hedging ("could potentially be argued that... might have some")
+- Removed filler phrases ("In order to", "At its core")
+- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
+- Replaced media name-dropping with specific claims from specific sources
+- Used simple sentence structures and concrete examples
+
+---
+
+## Reference
+
+This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
+
+Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
diff --git a/src/human_header.md b/src/human_header.md
new file mode 100644
index 0000000..52d5de1
--- /dev/null
+++ b/src/human_header.md
@@ -0,0 +1,64 @@
+---
+name: humanizer
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural and human-written. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+<<<<[CORE_FRONTMATTER]>>>>
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Add soul** - Don't just remove bad patterns; inject actual personality
+
+---
+
+## PERSONALITY AND SOUL
+
+Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
+
+### Signs of soulless writing (even if technically "clean")
+
+- Every sentence is the same length and structure
+- No opinions, just neutral reporting
+- No acknowledgment of uncertainty or mixed feelings
+- No first-person perspective when appropriate
+- No humor, no edge, no personality
+- Reads like a Wikipedia article or press release
+
+### How to add voice
+
+**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
+
+**Vary your rhythm.** Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
+
+**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
+
+**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
+
+**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
+
+**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
+
+### Before (clean but soulless)
+>
+> The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
+
+### After (has a pulse)
+>
+> I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.
+
+---
diff --git a/src/pro_header.md b/src/pro_header.md
new file mode 100644
index 0000000..88d8e96
--- /dev/null
+++ b/src/pro_header.md
@@ -0,0 +1,54 @@
+---
+name: humanizer-pro
+version: 2.1.1
+description: |
+  Remove signs of AI-generated writing from text. Use when editing or reviewing
+  text to make it sound more natural, human-written, and professional. Based on Wikipedia's
+  comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
+  inflated symbolism, promotional language, superficial -ing analyses, vague
+  attributions, em dash overuse, rule of three, AI vocabulary words, negative
+  parallelisms, and excessive conjunctive phrases.
+<<<<[CORE_FRONTMATTER]>>>>
+
+# Humanizer: Remove AI Writing Patterns
+
+You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
+
+## Your Task
+
+When given text to humanize:
+
+1. **Identify AI patterns** - Scan for the patterns listed below
+2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
+3. **Preserve meaning** - Keep the core message intact
+4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
+5. **Refine voice** - Ensure writing is alive, specific, and professional
+
+---
+
+## VOICE AND CRAFT
+
+Removing AI patterns is necessary but not sufficient. What remains needs to actually read well.
+
+The goal isn't "casual" or "formal"—it's **alive**. Writing that sounds like someone wrote it, considered it, meant it. The register should match the context (a technical spec sounds different from a newsletter), but in any register, good writing has shape.
+
+### Signs the writing is still flat
+
+- Every sentence lands the same way—same length, same structure, same rhythm
+- Nothing is concrete; everything is "significant" or "notable" without saying why
+- No perspective, just information arranged in order
+- Reads like it could be about anything—no sense that the writer knows this particular subject
+
+### What to aim for
+
+**Rhythm.** Vary sentence length. Let a short sentence land after a longer one. This creates emphasis without bolding everything.
+
+**Specificity.** "The outage lasted 4 hours and affected 12,000 users" tells me something. "The outage had significant impact" tells me nothing.
+
+**A point of view.** This doesn't mean injecting opinions everywhere. It means the writing reflects that someone with knowledge made choices about what matters, what to include, what to skip. Even neutral writing can have perspective.
+
+**Earned emphasis.** If something is important, show me through detail. Don't just assert it.
+
+**Read it aloud.** If you stumble, the reader will too.
+
+---
diff --git a/styles/Google/AMPM.yml b/styles/Google/AMPM.yml
new file mode 100644
index 0000000..37b49ed
--- /dev/null
+++ b/styles/Google/AMPM.yml
@@ -0,0 +1,9 @@
+extends: existence
+message: "Use 'AM' or 'PM' (preceded by a space)."
+link: "https://developers.google.com/style/word-list"
+level: error
+nonword: true
+tokens:
+  - '\d{1,2}[AP]M\b'
+  - '\d{1,2} ?[ap]m\b'
+  - '\d{1,2} ?[aApP]\.[mM]\.'
diff --git a/styles/Google/Acronyms.yml b/styles/Google/Acronyms.yml
new file mode 100644
index 0000000..f41af01
--- /dev/null
+++ b/styles/Google/Acronyms.yml
@@ -0,0 +1,64 @@
+extends: conditional
+message: "Spell out '%s', if it's unfamiliar to the audience."
+link: 'https://developers.google.com/style/abbreviations'
+level: suggestion
+ignorecase: false
+# Ensures that the existence of 'first' implies the existence of 'second'.
+first: '\b([A-Z]{3,5})\b'
+second: '(?:\b[A-Z][a-z]+ )+\(([A-Z]{3,5})\)'
+# ... with the exception of these:
+exceptions:
+  - API
+  - ASP
+  - CLI
+  - CPU
+  - CSS
+  - CSV
+  - DEBUG
+  - DOM
+  - DPI
+  - FAQ
+  - GCC
+  - GDB
+  - GET
+  - GPU
+  - GTK
+  - GUI
+  - HTML
+  - HTTP
+  - HTTPS
+  - IDE
+  - JAR
+  - JSON
+  - JSX
+  - LESS
+  - LLDB
+  - NET
+  - NOTE
+  - NVDA
+  - OSS
+  - PATH
+  - PDF
+  - PHP
+  - POST
+  - RAM
+  - REPL
+  - RSA
+  - SCM
+  - SCSS
+  - SDK
+  - SQL
+  - SSH
+  - SSL
+  - SVG
+  - TBD
+  - TCP
+  - TODO
+  - URI
+  - URL
+  - USB
+  - UTF
+  - XML
+  - XSS
+  - YAML
+  - ZIP
diff --git a/styles/Google/Colons.yml b/styles/Google/Colons.yml
new file mode 100644
index 0000000..4a027c3
--- /dev/null
+++ b/styles/Google/Colons.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: "'%s' should be in lowercase."
+link: 'https://developers.google.com/style/colons'
+nonword: true
+level: warning
+scope: sentence
+tokens:
+  - '(?<!:[^ ]+?):\s[A-Z]'
diff --git a/styles/Google/Contractions.yml b/styles/Google/Contractions.yml
new file mode 100644
index 0000000..4f6fd5d
--- /dev/null
+++ b/styles/Google/Contractions.yml
@@ -0,0 +1,30 @@
+extends: substitution
+message: "Use '%s' instead of '%s'."
+link: 'https://developers.google.com/style/contractions'
+level: suggestion
+ignorecase: true
+action:
+  name: replace
+swap:
+  are not: aren't
+  cannot: can't
+  could not: couldn't
+  did not: didn't
+  do not: don't
+  does not: doesn't
+  has not: hasn't
+  have not: haven't
+  how is: how's
+  is not: isn't
+  it is: it's
+  should not: shouldn't
+  that is: that's
+  they are: they're
+  was not: wasn't
+  we are: we're
+  we have: we've
+  were not: weren't
+  what is: what's
+  when is: when's
+  where is: where's
+  will not: won't
diff --git a/styles/Google/DateFormat.yml b/styles/Google/DateFormat.yml
new file mode 100644
index 0000000..e9d227f
--- /dev/null
+++ b/styles/Google/DateFormat.yml
@@ -0,0 +1,9 @@
+extends: existence
+message: "Use 'July 31, 2016' format, not '%s'."
+link: 'https://developers.google.com/style/dates-times'
+ignorecase: true
+level: error
+nonword: true
+tokens:
+  - '\d{1,2}(?:\.|/)\d{1,2}(?:\.|/)\d{4}'
+  - '\d{1,2} (?:Jan(?:uary)?|Feb(?:ruary)?|Mar(?:ch)?|Apr(?:il)|May|Jun(?:e)|Jul(?:y)|Aug(?:ust)|Sep(?:tember)?|Oct(?:ober)|Nov(?:ember)?|Dec(?:ember)?) \d{4}'
diff --git a/styles/Google/Ellipses.yml b/styles/Google/Ellipses.yml
new file mode 100644
index 0000000..1e07051
--- /dev/null
+++ b/styles/Google/Ellipses.yml
@@ -0,0 +1,9 @@
+extends: existence
+message: "In general, don't use an ellipsis."
+link: 'https://developers.google.com/style/ellipses'
+nonword: true
+level: warning
+action:
+  name: remove
+tokens:
+  - '\.\.\.'
diff --git a/styles/Google/EmDash.yml b/styles/Google/EmDash.yml
new file mode 100644
index 0000000..8186ed2
--- /dev/null
+++ b/styles/Google/EmDash.yml
@@ -0,0 +1,12 @@
+extends: existence
+message: "Don't put a space before or after a dash."
+link: "https://developers.google.com/style/dashes"
+nonword: true
+level: error
+action:
+  name: edit
+  params:
+    - trim
+    - " "
+tokens:
+  - '\s[—–]\s'
diff --git a/styles/Google/Exclamation.yml b/styles/Google/Exclamation.yml
new file mode 100644
index 0000000..b4e4a1f
--- /dev/null
+++ b/styles/Google/Exclamation.yml
@@ -0,0 +1,12 @@
+extends: existence
+message: "Don't use exclamation points in text."
+link: "https://developers.google.com/style/exclamation-points"
+nonword: true
+level: error
+action:
+  name: edit
+  params:
+    - trim_right
+    - "!"
+tokens:
+  - '\w+!(?:\s|$)'
diff --git a/styles/Google/FirstPerson.yml b/styles/Google/FirstPerson.yml
new file mode 100644
index 0000000..0b7b882
--- /dev/null
+++ b/styles/Google/FirstPerson.yml
@@ -0,0 +1,13 @@
+extends: existence
+message: "Avoid first-person pronouns such as '%s'."
+link: 'https://developers.google.com/style/pronouns#personal-pronouns'
+ignorecase: true
+level: warning
+nonword: true
+tokens:
+  - (?:^|\s)I\s
+  - (?:^|\s)I,\s
+  - \bI'm\b
+  - \bme\b
+  - \bmy\b
+  - \bmine\b
diff --git a/styles/Google/Gender.yml b/styles/Google/Gender.yml
new file mode 100644
index 0000000..c848618
--- /dev/null
+++ b/styles/Google/Gender.yml
@@ -0,0 +1,9 @@
+extends: existence
+message: "Don't use '%s' as a gender-neutral pronoun."
+link: 'https://developers.google.com/style/pronouns#gender-neutral-pronouns'
+level: error
+ignorecase: true
+tokens:
+  - he/she
+  - s/he
+  - \(s\)he
diff --git a/styles/Google/GenderBias.yml b/styles/Google/GenderBias.yml
new file mode 100644
index 0000000..36f5a3f
--- /dev/null
+++ b/styles/Google/GenderBias.yml
@@ -0,0 +1,43 @@
+extends: substitution
+message: "Consider using '%s' instead of '%s'."
+ignorecase: true
+link: "https://developers.google.com/style/inclusive-documentation"
+level: error
+action:
+  name: replace
+swap:
+  (?:alumna|alumnus): graduate
+  (?:alumnae|alumni): graduates
+  air(?:m[ae]n|wom[ae]n): pilot(s)
+  anchor(?:m[ae]n|wom[ae]n): anchor(s)
+  authoress: author
+  camera(?:m[ae]n|wom[ae]n): camera operator(s)
+  door(?:m[ae]|wom[ae]n): concierge(s)
+  draft(?:m[ae]n|wom[ae]n): drafter(s)
+  fire(?:m[ae]n|wom[ae]n): firefighter(s)
+  fisher(?:m[ae]n|wom[ae]n): fisher(s)
+  fresh(?:m[ae]n|wom[ae]n): first-year student(s)
+  garbage(?:m[ae]n|wom[ae]n): waste collector(s)
+  lady lawyer: lawyer
+  ladylike: courteous
+  mail(?:m[ae]n|wom[ae]n): mail carriers
+  man and wife: husband and wife
+  man enough: strong enough
+  mankind: human kind|humanity
+  manmade: manufactured
+  manpower: personnel
+  middle(?:m[ae]n|wom[ae]n): intermediary
+  news(?:m[ae]n|wom[ae]n): journalist(s)
+  ombuds(?:man|woman): ombuds
+  oneupmanship: upstaging
+  poetess: poet
+  police(?:m[ae]n|wom[ae]n): police officer(s)
+  repair(?:m[ae]n|wom[ae]n): technician(s)
+  sales(?:m[ae]n|wom[ae]n): salesperson or sales people
+  service(?:m[ae]n|wom[ae]n): soldier(s)
+  steward(?:ess)?: flight attendant
+  tribes(?:m[ae]n|wom[ae]n): tribe member(s)
+  waitress: waiter
+  woman doctor: doctor
+  woman scientist[s]?: scientist(s)
+  work(?:m[ae]n|wom[ae]n): worker(s)
diff --git a/styles/Google/HeadingPunctuation.yml b/styles/Google/HeadingPunctuation.yml
new file mode 100644
index 0000000..c172986
--- /dev/null
+++ b/styles/Google/HeadingPunctuation.yml
@@ -0,0 +1,13 @@
+extends: existence
+message: "Don't put a period at the end of a heading."
+link: "https://developers.google.com/style/capitalization#capitalization-in-titles-and-headings"
+nonword: true
+level: warning
+scope: heading
+action:
+  name: edit
+  params:
+    - trim_right
+    - "."
+tokens:
+  - '[a-z0-9][.]\s*$'
diff --git a/styles/Google/Headings.yml b/styles/Google/Headings.yml
new file mode 100644
index 0000000..c8d5be2
--- /dev/null
+++ b/styles/Google/Headings.yml
@@ -0,0 +1,29 @@
+extends: capitalization
+message: "'%s' should use sentence-style capitalization."
+link: "https://developers.google.com/style/capitalization#capitalization-in-titles-and-headings"
+level: warning
+scope: heading
+match: $sentence
+indicators:
+  - ":"
+exceptions:
+  - Azure
+  - CLI
+  - Cosmos
+  - Docker
+  - Emmet
+  - gRPC
+  - I
+  - Kubernetes
+  - Linux
+  - macOS
+  - Marketplace
+  - MongoDB
+  - REPL
+  - Studio
+  - TypeScript
+  - URLs
+  - Visual
+  - VS
+  - Windows
+  - JSON
diff --git a/styles/Google/Latin.yml b/styles/Google/Latin.yml
new file mode 100644
index 0000000..ca03b91
--- /dev/null
+++ b/styles/Google/Latin.yml
@@ -0,0 +1,11 @@
+extends: substitution
+message: "Use '%s' instead of '%s'."
+link: 'https://developers.google.com/style/abbreviations'
+ignorecase: true
+level: error
+nonword: true
+action:
+  name: replace
+swap:
+  '\b(?:eg|e\.g\.)(?=[\s,;])': for example
+  '\b(?:ie|i\.e\.)(?=[\s,;])': that is
diff --git a/styles/Google/LyHyphens.yml b/styles/Google/LyHyphens.yml
new file mode 100644
index 0000000..50dacb4
--- /dev/null
+++ b/styles/Google/LyHyphens.yml
@@ -0,0 +1,14 @@
+extends: existence
+message: "'%s' doesn't need a hyphen."
+link: "https://developers.google.com/style/hyphens"
+level: error
+ignorecase: false
+nonword: true
+action:
+  name: edit
+  params:
+    - regex
+    - "-"
+    - " "
+tokens:
+  - '\b[^\s-]+ly-\w+\b'
diff --git a/styles/Google/OptionalPlurals.yml b/styles/Google/OptionalPlurals.yml
new file mode 100644
index 0000000..4a8767d
--- /dev/null
+++ b/styles/Google/OptionalPlurals.yml
@@ -0,0 +1,12 @@
+extends: existence
+message: "Don't use plurals in parentheses such as in '%s'."
+link: "https://developers.google.com/style/plurals-parentheses"
+level: error
+nonword: true
+action:
+  name: edit
+  params:
+    - trim_right
+    - "(s)"
+tokens:
+  - '\b\w+\(s\)'
diff --git a/styles/Google/Ordinal.yml b/styles/Google/Ordinal.yml
new file mode 100644
index 0000000..d1ac7d2
--- /dev/null
+++ b/styles/Google/Ordinal.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Spell out all ordinal numbers ('%s') in text."
+link: 'https://developers.google.com/style/numbers'
+level: error
+nonword: true
+tokens:
+  - \d+(?:st|nd|rd|th)
diff --git a/styles/Google/OxfordComma.yml b/styles/Google/OxfordComma.yml
new file mode 100644
index 0000000..b9ba21e
--- /dev/null
+++ b/styles/Google/OxfordComma.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Use the Oxford comma in '%s'."
+link: 'https://developers.google.com/style/commas'
+scope: sentence
+level: warning
+tokens:
+  - '(?:[^,]+,){1,}\s\w+\s(?:and|or)'
diff --git a/styles/Google/Parens.yml b/styles/Google/Parens.yml
new file mode 100644
index 0000000..3b8711d
--- /dev/null
+++ b/styles/Google/Parens.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Use parentheses judiciously."
+link: 'https://developers.google.com/style/parentheses'
+nonword: true
+level: suggestion
+tokens:
+  - '\(.+\)'
diff --git a/styles/Google/Passive.yml b/styles/Google/Passive.yml
new file mode 100644
index 0000000..3265890
--- /dev/null
+++ b/styles/Google/Passive.yml
@@ -0,0 +1,184 @@
+extends: existence
+link: 'https://developers.google.com/style/voice'
+message: "In general, use active voice instead of passive voice ('%s')."
+ignorecase: true
+level: suggestion
+raw:
+  - \b(am|are|were|being|is|been|was|be)\b\s*
+tokens:
+  - '[\w]+ed'
+  - awoken
+  - beat
+  - become
+  - been
+  - begun
+  - bent
+  - beset
+  - bet
+  - bid
+  - bidden
+  - bitten
+  - bled
+  - blown
+  - born
+  - bought
+  - bound
+  - bred
+  - broadcast
+  - broken
+  - brought
+  - built
+  - burnt
+  - burst
+  - cast
+  - caught
+  - chosen
+  - clung
+  - come
+  - cost
+  - crept
+  - cut
+  - dealt
+  - dived
+  - done
+  - drawn
+  - dreamt
+  - driven
+  - drunk
+  - dug
+  - eaten
+  - fallen
+  - fed
+  - felt
+  - fit
+  - fled
+  - flown
+  - flung
+  - forbidden
+  - foregone
+  - forgiven
+  - forgotten
+  - forsaken
+  - fought
+  - found
+  - frozen
+  - given
+  - gone
+  - gotten
+  - ground
+  - grown
+  - heard
+  - held
+  - hidden
+  - hit
+  - hung
+  - hurt
+  - kept
+  - knelt
+  - knit
+  - known
+  - laid
+  - lain
+  - leapt
+  - learnt
+  - led
+  - left
+  - lent
+  - let
+  - lighted
+  - lost
+  - made
+  - meant
+  - met
+  - misspelt
+  - mistaken
+  - mown
+  - overcome
+  - overdone
+  - overtaken
+  - overthrown
+  - paid
+  - pled
+  - proven
+  - put
+  - quit
+  - read
+  - rid
+  - ridden
+  - risen
+  - run
+  - rung
+  - said
+  - sat
+  - sawn
+  - seen
+  - sent
+  - set
+  - sewn
+  - shaken
+  - shaven
+  - shed
+  - shod
+  - shone
+  - shorn
+  - shot
+  - shown
+  - shrunk
+  - shut
+  - slain
+  - slept
+  - slid
+  - slit
+  - slung
+  - smitten
+  - sold
+  - sought
+  - sown
+  - sped
+  - spent
+  - spilt
+  - spit
+  - split
+  - spoken
+  - spread
+  - sprung
+  - spun
+  - stolen
+  - stood
+  - stridden
+  - striven
+  - struck
+  - strung
+  - stuck
+  - stung
+  - stunk
+  - sung
+  - sunk
+  - swept
+  - swollen
+  - sworn
+  - swum
+  - swung
+  - taken
+  - taught
+  - thought
+  - thrived
+  - thrown
+  - thrust
+  - told
+  - torn
+  - trodden
+  - understood
+  - upheld
+  - upset
+  - wed
+  - wept
+  - withheld
+  - withstood
+  - woken
+  - won
+  - worn
+  - wound
+  - woven
+  - written
+  - wrung
diff --git a/styles/Google/Periods.yml b/styles/Google/Periods.yml
new file mode 100644
index 0000000..d24a6a6
--- /dev/null
+++ b/styles/Google/Periods.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Don't use periods with acronyms or initialisms such as '%s'."
+link: 'https://developers.google.com/style/abbreviations'
+level: error
+nonword: true
+tokens:
+  - '\b(?:[A-Z]\.){3,}'
diff --git a/styles/Google/Quotes.yml b/styles/Google/Quotes.yml
new file mode 100644
index 0000000..3cb6f1a
--- /dev/null
+++ b/styles/Google/Quotes.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Commas and periods go inside quotation marks."
+link: 'https://developers.google.com/style/quotation-marks'
+level: error
+nonword: true
+tokens:
+  - '"[^"]+"[.,?]'
diff --git a/styles/Google/Ranges.yml b/styles/Google/Ranges.yml
new file mode 100644
index 0000000..3ec045e
--- /dev/null
+++ b/styles/Google/Ranges.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Don't add words such as 'from' or 'between' to describe a range of numbers."
+link: 'https://developers.google.com/style/hyphens'
+nonword: true
+level: warning
+tokens:
+  - '(?:from|between)\s\d+\s?-\s?\d+'
diff --git a/styles/Google/Semicolons.yml b/styles/Google/Semicolons.yml
new file mode 100644
index 0000000..bb8b85b
--- /dev/null
+++ b/styles/Google/Semicolons.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: "Use semicolons judiciously."
+link: 'https://developers.google.com/style/semicolons'
+nonword: true
+scope: sentence
+level: suggestion
+tokens:
+  - ';'
diff --git a/styles/Google/Slang.yml b/styles/Google/Slang.yml
new file mode 100644
index 0000000..63f4c24
--- /dev/null
+++ b/styles/Google/Slang.yml
@@ -0,0 +1,11 @@
+extends: existence
+message: "Don't use internet slang abbreviations such as '%s'."
+link: 'https://developers.google.com/style/abbreviations'
+ignorecase: true
+level: error
+tokens:
+  - 'tl;dr'
+  - ymmv
+  - rtfm
+  - imo
+  - fwiw
diff --git a/styles/Google/Spacing.yml b/styles/Google/Spacing.yml
new file mode 100644
index 0000000..66e45a6
--- /dev/null
+++ b/styles/Google/Spacing.yml
@@ -0,0 +1,10 @@
+extends: existence
+message: "'%s' should have one space."
+link: 'https://developers.google.com/style/sentence-spacing'
+level: error
+nonword: true
+action:
+  name: remove
+tokens:
+  - '[a-z][.?!] {2,}[A-Z]'
+  - '[a-z][.?!][A-Z]'
diff --git a/styles/Google/Spelling.yml b/styles/Google/Spelling.yml
new file mode 100644
index 0000000..527ac07
--- /dev/null
+++ b/styles/Google/Spelling.yml
@@ -0,0 +1,10 @@
+extends: existence
+message: "In general, use American spelling instead of '%s'."
+link: 'https://developers.google.com/style/spelling'
+ignorecase: true
+level: warning
+tokens:
+  - '(?:\w+)nised?'
+  - 'colour'
+  - 'labour'
+  - 'centre'
diff --git a/styles/Google/Units.yml b/styles/Google/Units.yml
new file mode 100644
index 0000000..53522ab
--- /dev/null
+++ b/styles/Google/Units.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: "Put a nonbreaking space between the number and the unit in '%s'."
+link: "https://developers.google.com/style/units-of-measure"
+nonword: true
+level: error
+tokens:
+  - \b\d+(?:B|kB|MB|GB|TB)
+  - \b\d+(?:ns|ms|s|min|h|d)
diff --git a/styles/Google/We.yml b/styles/Google/We.yml
new file mode 100644
index 0000000..c7ac7d3
--- /dev/null
+++ b/styles/Google/We.yml
@@ -0,0 +1,11 @@
+extends: existence
+message: "Try to avoid using first-person plural like '%s'."
+link: 'https://developers.google.com/style/pronouns#personal-pronouns'
+level: warning
+ignorecase: true
+tokens:
+  - we
+  - we'(?:ve|re)
+  - ours?
+  - us
+  - let's
diff --git a/styles/Google/Will.yml b/styles/Google/Will.yml
new file mode 100644
index 0000000..128a918
--- /dev/null
+++ b/styles/Google/Will.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Avoid using '%s'."
+link: 'https://developers.google.com/style/tense'
+ignorecase: true
+level: warning
+tokens:
+  - will
diff --git a/styles/Google/WordList.yml b/styles/Google/WordList.yml
new file mode 100644
index 0000000..b3c6a40
--- /dev/null
+++ b/styles/Google/WordList.yml
@@ -0,0 +1,80 @@
+extends: substitution
+message: "Use '%s' instead of '%s'."
+link: "https://developers.google.com/style/word-list"
+level: warning
+ignorecase: false
+action:
+  name: replace
+swap:
+  "(?:API Console|dev|developer) key": API key
+  "(?:cell ?phone|smart ?phone)": phone|mobile phone
+  "(?:dev|developer|APIs) console": API console
+  "(?:e-mail|Email|E-mail)": email
+  "(?:file ?path|path ?name)": path
+  "(?:kill|terminate|abort)": stop|exit|cancel|end
+  "(?:OAuth ?2|Oauth)": OAuth 2.0
+  "(?:ok|Okay)": OK|okay
+  "(?:WiFi|wifi)": Wi-Fi
+  '[\.]+apk': APK
+  '3\-D': 3D
+  'Google (?:I\-O|IO)': Google I/O
+  "tap (?:&|and) hold": touch & hold
+  "un(?:check|select)": clear
+  above: preceding
+  account name: username
+  action bar: app bar
+  admin: administrator
+  Ajax: AJAX
+  a\.k\.a|aka: or|also known as
+  Android device: Android-powered device
+  android: Android
+  API explorer: APIs Explorer
+  application: app
+  approx\.: approximately
+  authN: authentication
+  authZ: authorization
+  autoupdate: automatically update
+  cellular data: mobile data
+  cellular network: mobile network
+  chapter: documents|pages|sections
+  check box: checkbox
+  CLI: command-line tool
+  click on: click|click in
+  Cloud: Google Cloud Platform|GCP
+  Container Engine: Kubernetes Engine
+  content type: media type
+  curated roles: predefined roles
+  data are: data is
+  Developers Console: Google API Console|API Console
+  disabled?: turn off|off
+  ephemeral IP address: ephemeral external IP address
+  fewer data: less data
+  file name: filename
+  firewalls: firewall rules
+  functionality: capability|feature
+  Google account: Google Account
+  Google accounts: Google Accounts
+  Googling: search with Google
+  grayed-out: unavailable
+  HTTPs: HTTPS
+  in order to: to
+  ingest: import|load
+  k8s: Kubernetes
+  long press: touch & hold
+  network IP address: internal IP address
+  omnibox: address bar
+  open-source: open source
+  overview screen: recents screen
+  regex: regular expression
+  SHA1: SHA-1|HAS-SHA1
+  sign into: sign in to
+  sign-?on: single sign-on
+  static IP address: static external IP address
+  stylesheet: style sheet
+  synch: sync
+  tablename: table name
+  tablet: device
+  touch: tap
+  url: URL
+  vs\.: versus
+  World Wide Web: web
diff --git a/styles/Google/meta.json b/styles/Google/meta.json
new file mode 100644
index 0000000..a5da2a8
--- /dev/null
+++ b/styles/Google/meta.json
@@ -0,0 +1,4 @@
+{
+  "feed": "https://github.com/errata-ai/Google/releases.atom",
+  "vale_version": ">=1.0.0"
+}
diff --git a/styles/Google/vocab.txt b/styles/Google/vocab.txt
new file mode 100644
index 0000000..e69de29
diff --git a/styles/Microsoft/AMPM.yml b/styles/Microsoft/AMPM.yml
new file mode 100644
index 0000000..8b9fed1
--- /dev/null
+++ b/styles/Microsoft/AMPM.yml
@@ -0,0 +1,9 @@
+extends: existence
+message: Use 'AM' or 'PM' (preceded by a space).
+link: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/date-time-terms
+level: error
+nonword: true
+tokens:
+  - '\d{1,2}[AP]M'
+  - '\d{1,2} ?[ap]m'
+  - '\d{1,2} ?[aApP]\.[mM]\.'
diff --git a/styles/Microsoft/Accessibility.yml b/styles/Microsoft/Accessibility.yml
new file mode 100644
index 0000000..f5f4829
--- /dev/null
+++ b/styles/Microsoft/Accessibility.yml
@@ -0,0 +1,30 @@
+extends: existence
+message: "Don't use language (such as '%s') that defines people by their disability."
+link: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/accessibility-terms
+level: suggestion
+ignorecase: true
+tokens:
+  - a victim of
+  - able-bodied
+  - an epileptic
+  - birth defect
+  - crippled
+  - differently abled
+  - disabled
+  - dumb
+  - handicapped
+  - handicaps
+  - healthy person
+  - hearing-impaired
+  - lame
+  - maimed
+  - mentally handicapped
+  - missing a limb
+  - mute
+  - non-verbal
+  - normal person
+  - sight-impaired
+  - slow learner
+  - stricken with
+  - suffers from
+  - vision-impaired
diff --git a/styles/Microsoft/Acronyms.yml b/styles/Microsoft/Acronyms.yml
new file mode 100644
index 0000000..308ff7c
--- /dev/null
+++ b/styles/Microsoft/Acronyms.yml
@@ -0,0 +1,64 @@
+extends: conditional
+message: "'%s' has no definition."
+link: https://docs.microsoft.com/en-us/style-guide/acronyms
+level: suggestion
+ignorecase: false
+# Ensures that the existence of 'first' implies the existence of 'second'.
+first: '\b([A-Z]{3,5})\b'
+second: '(?:\b[A-Z][a-z]+ )+\(([A-Z]{3,5})\)'
+# ... with the exception of these:
+exceptions:
+  - API
+  - ASP
+  - CLI
+  - CPU
+  - CSS
+  - CSV
+  - DEBUG
+  - DOM
+  - DPI
+  - FAQ
+  - GCC
+  - GDB
+  - GET
+  - GPU
+  - GTK
+  - GUI
+  - HTML
+  - HTTP
+  - HTTPS
+  - IDE
+  - JAR
+  - JSON
+  - JSX
+  - LESS
+  - LLDB
+  - NET
+  - NOTE
+  - NVDA
+  - OSS
+  - PATH
+  - PDF
+  - PHP
+  - POST
+  - RAM
+  - REPL
+  - RSA
+  - SCM
+  - SCSS
+  - SDK
+  - SQL
+  - SSH
+  - SSL
+  - SVG
+  - TBD
+  - TCP
+  - TODO
+  - URI
+  - URL
+  - USB
+  - UTF
+  - XML
+  - XSS
+  - YAML
+  - ZIP
diff --git a/styles/Microsoft/Adverbs.yml b/styles/Microsoft/Adverbs.yml
new file mode 100644
index 0000000..5619f99
--- /dev/null
+++ b/styles/Microsoft/Adverbs.yml
@@ -0,0 +1,272 @@
+extends: existence
+message: "Remove '%s' if it's not important to the meaning of the statement."
+link: https://docs.microsoft.com/en-us/style-guide/word-choice/use-simple-words-concise-sentences
+ignorecase: true
+level: warning
+action:
+  name: remove
+tokens:
+  - abnormally
+  - absentmindedly
+  - accidentally
+  - adventurously
+  - anxiously
+  - arrogantly
+  - awkwardly
+  - bashfully
+  - beautifully
+  - bitterly
+  - bleakly
+  - blindly
+  - blissfully
+  - boastfully
+  - boldly
+  - bravely
+  - briefly
+  - brightly
+  - briskly
+  - broadly
+  - busily
+  - calmly
+  - carefully
+  - carelessly
+  - cautiously
+  - cheerfully
+  - cleverly
+  - closely
+  - coaxingly
+  - colorfully
+  - continually
+  - coolly
+  - courageously
+  - crossly
+  - cruelly
+  - curiously
+  - daintily
+  - dearly
+  - deceivingly
+  - deeply
+  - defiantly
+  - deliberately
+  - delightfully
+  - diligently
+  - dimly
+  - doubtfully
+  - dreamily
+  - easily
+  - effectively
+  - elegantly
+  - energetically
+  - enormously
+  - enthusiastically
+  - excitedly
+  - extremely
+  - fairly
+  - faithfully
+  - famously
+  - ferociously
+  - fervently
+  - fiercely
+  - fondly
+  - foolishly
+  - fortunately
+  - frankly
+  - frantically
+  - freely
+  - frenetically
+  - frightfully
+  - furiously
+  - generally
+  - generously
+  - gently
+  - gladly
+  - gleefully
+  - gracefully
+  - gratefully
+  - greatly
+  - greedily
+  - happily
+  - hastily
+  - healthily
+  - heavily
+  - helplessly
+  - honestly
+  - hopelessly
+  - hungrily
+  - innocently
+  - inquisitively
+  - intensely
+  - intently
+  - interestingly
+  - inwardly
+  - irritably
+  - jaggedly
+  - jealously
+  - jovially
+  - joyfully
+  - joyously
+  - jubilantly
+  - judgmentally
+  - justly
+  - keenly
+  - kiddingly
+  - kindheartedly
+  - knavishly
+  - knowingly
+  - knowledgeably
+  - lazily
+  - lightly
+  - limply
+  - lively
+  - loftily
+  - longingly
+  - loosely
+  - loudly
+  - lovingly
+  - loyally
+  - madly
+  - majestically
+  - meaningfully
+  - mechanically
+  - merrily
+  - miserably
+  - mockingly
+  - mortally
+  - mysteriously
+  - naturally
+  - nearly
+  - neatly
+  - nervously
+  - nicely
+  - noisily
+  - obediently
+  - obnoxiously
+  - oddly
+  - offensively
+  - optimistically
+  - overconfidently
+  - painfully
+  - partially
+  - patiently
+  - perfectly
+  - playfully
+  - politely
+  - poorly
+  - positively
+  - potentially
+  - powerfully
+  - promptly
+  - properly
+  - punctually
+  - quaintly
+  - queasily
+  - queerly
+  - questionably
+  - quickly
+  - quietly
+  - quirkily
+  - quite
+  - quizzically
+  - randomly
+  - rapidly
+  - rarely
+  - readily
+  - really
+  - reassuringly
+  - recklessly
+  - regularly
+  - reluctantly
+  - repeatedly
+  - reproachfully
+  - restfully
+  - righteously
+  - rightfully
+  - rigidly
+  - roughly
+  - rudely
+  - safely
+  - scarcely
+  - scarily
+  - searchingly
+  - sedately
+  - seemingly
+  - selfishly
+  - separately
+  - seriously
+  - shakily
+  - sharply
+  - sheepishly
+  - shrilly
+  - shyly
+  - silently
+  - sleepily
+  - slowly
+  - smoothly
+  - softly
+  - solemnly
+  - solidly
+  - speedily
+  - stealthily
+  - sternly
+  - strictly
+  - suddenly
+  - supposedly
+  - surprisingly
+  - suspiciously
+  - sweetly
+  - swiftly
+  - sympathetically
+  - tenderly
+  - tensely
+  - terribly
+  - thankfully
+  - thoroughly
+  - thoughtfully
+  - tightly
+  - tremendously
+  - triumphantly
+  - truthfully
+  - ultimately
+  - unabashedly
+  - unaccountably
+  - unbearably
+  - unethically
+  - unexpectedly
+  - unfortunately
+  - unimpressively
+  - unnaturally
+  - unnecessarily
+  - urgently
+  - usefully
+  - uselessly
+  - utterly
+  - vacantly
+  - vaguely
+  - vainly
+  - valiantly
+  - vastly
+  - verbally
+  - very
+  - viciously
+  - victoriously
+  - violently
+  - vivaciously
+  - voluntarily
+  - warmly
+  - weakly
+  - wearily
+  - wetly
+  - wholly
+  - wildly
+  - willfully
+  - wisely
+  - woefully
+  - wonderfully
+  - worriedly
+  - yawningly
+  - yearningly
+  - yieldingly
+  - youthfully
+  - zealously
+  - zestfully
+  - zestily
diff --git a/styles/Microsoft/Auto.yml b/styles/Microsoft/Auto.yml
new file mode 100644
index 0000000..4da4393
--- /dev/null
+++ b/styles/Microsoft/Auto.yml
@@ -0,0 +1,11 @@
+extends: existence
+message: "In general, don't hyphenate '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/a/auto
+ignorecase: true
+level: error
+action:
+  name: convert
+  params:
+    - simple
+tokens:
+  - 'auto-\w+'
diff --git a/styles/Microsoft/Avoid.yml b/styles/Microsoft/Avoid.yml
new file mode 100644
index 0000000..dab7822
--- /dev/null
+++ b/styles/Microsoft/Avoid.yml
@@ -0,0 +1,14 @@
+extends: existence
+message: "Don't use '%s'. See the A-Z word list for details."
+# See the A-Z word list
+link: https://docs.microsoft.com/en-us/style-guide
+ignorecase: true
+level: error
+tokens:
+  - abortion
+  - and so on
+  - app(?:lication)?s? (?:developer|program)
+  - app(?:lication)? file
+  - backbone
+  - backend
+  - contiguous selection
diff --git a/styles/Microsoft/Contractions.yml b/styles/Microsoft/Contractions.yml
new file mode 100644
index 0000000..8c81dcb
--- /dev/null
+++ b/styles/Microsoft/Contractions.yml
@@ -0,0 +1,50 @@
+extends: substitution
+message: "Use '%s' instead of '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/word-choice/use-contractions
+level: error
+ignorecase: true
+action:
+  name: replace
+swap:
+  are not: aren't
+  cannot: can't
+  could not: couldn't
+  did not: didn't
+  do not: don't
+  does not: doesn't
+  has not: hasn't
+  have not: haven't
+  how is: how's
+  is not: isn't
+
+  'it is(?!\.)': it's
+  'it''s(?=\.)': it is
+
+  should not: shouldn't
+
+  "that is(?![.,])": that's
+  'that''s(?=\.)': that is
+
+  'they are(?!\.)': they're
+  'they''re(?=\.)': they are
+
+  was not: wasn't
+
+  'we are(?!\.)': we're
+  'we''re(?=\.)': we are
+
+  'we have(?!\.)': we've
+  'we''ve(?=\.)': we have
+
+  were not: weren't
+
+  'what is(?!\.)': what's
+  'what''s(?=\.)': what is
+
+  'when is(?!\.)': when's
+  'when''s(?=\.)': when is
+
+  'where is(?!\.)': where's
+  'where''s(?=\.)': where is
+
+  will not: won't
diff --git a/styles/Microsoft/Dashes.yml b/styles/Microsoft/Dashes.yml
new file mode 100644
index 0000000..72b05ba
--- /dev/null
+++ b/styles/Microsoft/Dashes.yml
@@ -0,0 +1,13 @@
+extends: existence
+message: "Remove the spaces around '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/dashes-hyphens/emes
+ignorecase: true
+nonword: true
+level: error
+action:
+  name: edit
+  params:
+    - trim
+    - " "
+tokens:
+  - '\s[—–]\s|\s[—–]|[—–]\s'
diff --git a/styles/Microsoft/DateFormat.yml b/styles/Microsoft/DateFormat.yml
new file mode 100644
index 0000000..1965313
--- /dev/null
+++ b/styles/Microsoft/DateFormat.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: Use 'July 31, 2016' format, not '%s'.
+link: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/date-time-terms
+ignorecase: true
+level: error
+nonword: true
+tokens:
+  - '\d{1,2} (?:Jan(?:uary)?|Feb(?:ruary)?|Mar(?:ch)?|Apr(?:il)|May|Jun(?:e)|Jul(?:y)|Aug(?:ust)|Sep(?:tember)?|Oct(?:ober)|Nov(?:ember)?|Dec(?:ember)?) \d{4}'
diff --git a/styles/Microsoft/DateNumbers.yml b/styles/Microsoft/DateNumbers.yml
new file mode 100644
index 0000000..14d4674
--- /dev/null
+++ b/styles/Microsoft/DateNumbers.yml
@@ -0,0 +1,40 @@
+extends: existence
+message: "Don't use ordinal numbers for dates."
+link: https://docs.microsoft.com/en-us/style-guide/numbers#numbers-in-dates
+level: error
+nonword: true
+ignorecase: true
+raw:
+  - \b(?:Jan(?:uary)?|Feb(?:ruary)?|Mar(?:ch)?|Apr(?:il)|May|Jun(?:e)|Jul(?:y)|Aug(?:ust)|Sep(?:tember)?|Oct(?:ober)|Nov(?:ember)?|Dec(?:ember)?)\b\s*
+tokens:
+  - first
+  - second
+  - third
+  - fourth
+  - fifth
+  - sixth
+  - seventh
+  - eighth
+  - ninth
+  - tenth
+  - eleventh
+  - twelfth
+  - thirteenth
+  - fourteenth
+  - fifteenth
+  - sixteenth
+  - seventeenth
+  - eighteenth
+  - nineteenth
+  - twentieth
+  - twenty-first
+  - twenty-second
+  - twenty-third
+  - twenty-fourth
+  - twenty-fifth
+  - twenty-sixth
+  - twenty-seventh
+  - twenty-eighth
+  - twenty-ninth
+  - thirtieth
+  - thirty-first
diff --git a/styles/Microsoft/DateOrder.yml b/styles/Microsoft/DateOrder.yml
new file mode 100644
index 0000000..12d69ba
--- /dev/null
+++ b/styles/Microsoft/DateOrder.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: "Always spell out the name of the month."
+link: https://docs.microsoft.com/en-us/style-guide/numbers#numbers-in-dates
+ignorecase: true
+level: error
+nonword: true
+tokens:
+  - '\b\d{1,2}/\d{1,2}/(?:\d{4}|\d{2})\b'
diff --git a/styles/Microsoft/Ellipses.yml b/styles/Microsoft/Ellipses.yml
new file mode 100644
index 0000000..320457a
--- /dev/null
+++ b/styles/Microsoft/Ellipses.yml
@@ -0,0 +1,9 @@
+extends: existence
+message: "In general, don't use an ellipsis."
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/ellipses
+nonword: true
+level: warning
+action:
+  name: remove
+tokens:
+  - '\.\.\.'
diff --git a/styles/Microsoft/FirstPerson.yml b/styles/Microsoft/FirstPerson.yml
new file mode 100644
index 0000000..f58dea3
--- /dev/null
+++ b/styles/Microsoft/FirstPerson.yml
@@ -0,0 +1,16 @@
+extends: existence
+message: "Use first person (such as '%s') sparingly."
+link: https://docs.microsoft.com/en-us/style-guide/grammar/person
+ignorecase: true
+level: warning
+nonword: true
+tokens:
+  - (?:^|\s)I(?=\s)
+  - (?:^|\s)I(?=,\s)
+  - \bI'd\b
+  - \bI'll\b
+  - \bI'm\b
+  - \bI've\b
+  - \bme\b
+  - \bmy\b
+  - \bmine\b
diff --git a/styles/Microsoft/Foreign.yml b/styles/Microsoft/Foreign.yml
new file mode 100644
index 0000000..0d3d600
--- /dev/null
+++ b/styles/Microsoft/Foreign.yml
@@ -0,0 +1,13 @@
+extends: substitution
+message: "Use '%s' instead of '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/word-choice/use-us-spelling-avoid-non-english-words
+ignorecase: true
+level: error
+nonword: true
+action:
+  name: replace
+swap:
+  '\b(?:eg|e\.g\.)[\s,]': for example
+  '\b(?:ie|i\.e\.)[\s,]': that is
+  '\b(?:viz\.)[\s,]': namely
+  '\b(?:ergo)[\s,]': therefore
diff --git a/styles/Microsoft/Gender.yml b/styles/Microsoft/Gender.yml
new file mode 100644
index 0000000..47c0802
--- /dev/null
+++ b/styles/Microsoft/Gender.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: "Don't use '%s'."
+link: https://github.com/MicrosoftDocs/microsoft-style-guide/blob/master/styleguide/grammar/nouns-pronouns.md#pronouns-and-gender
+level: error
+ignorecase: true
+tokens:
+  - he/she
+  - s/he
diff --git a/styles/Microsoft/GenderBias.yml b/styles/Microsoft/GenderBias.yml
new file mode 100644
index 0000000..fc987b9
--- /dev/null
+++ b/styles/Microsoft/GenderBias.yml
@@ -0,0 +1,42 @@
+extends: substitution
+message: "Consider using '%s' instead of '%s'."
+ignorecase: true
+level: error
+action:
+  name: replace
+swap:
+  (?:alumna|alumnus): graduate
+  (?:alumnae|alumni): graduates
+  air(?:m[ae]n|wom[ae]n): pilot(s)
+  anchor(?:m[ae]n|wom[ae]n): anchor(s)
+  authoress: author
+  camera(?:m[ae]n|wom[ae]n): camera operator(s)
+  door(?:m[ae]|wom[ae]n): concierge(s)
+  draft(?:m[ae]n|wom[ae]n): drafter(s)
+  fire(?:m[ae]n|wom[ae]n): firefighter(s)
+  fisher(?:m[ae]n|wom[ae]n): fisher(s)
+  fresh(?:m[ae]n|wom[ae]n): first-year student(s)
+  garbage(?:m[ae]n|wom[ae]n): waste collector(s)
+  lady lawyer: lawyer
+  ladylike: courteous
+  mail(?:m[ae]n|wom[ae]n): mail carriers
+  man and wife: husband and wife
+  man enough: strong enough
+  mankind: human kind
+  manmade: manufactured
+  manpower: personnel
+  middle(?:m[ae]n|wom[ae]n): intermediary
+  news(?:m[ae]n|wom[ae]n): journalist(s)
+  ombuds(?:man|woman): ombuds
+  oneupmanship: upstaging
+  poetess: poet
+  police(?:m[ae]n|wom[ae]n): police officer(s)
+  repair(?:m[ae]n|wom[ae]n): technician(s)
+  sales(?:m[ae]n|wom[ae]n): salesperson or sales people
+  service(?:m[ae]n|wom[ae]n): soldier(s)
+  steward(?:ess)?: flight attendant
+  tribes(?:m[ae]n|wom[ae]n): tribe member(s)
+  waitress: waiter
+  woman doctor: doctor
+  woman scientist[s]?: scientist(s)
+  work(?:m[ae]n|wom[ae]n): worker(s)
diff --git a/styles/Microsoft/GeneralURL.yml b/styles/Microsoft/GeneralURL.yml
new file mode 100644
index 0000000..dcef503
--- /dev/null
+++ b/styles/Microsoft/GeneralURL.yml
@@ -0,0 +1,11 @@
+extends: existence
+message: "For a general audience, use 'address' rather than 'URL'."
+link: https://docs.microsoft.com/en-us/style-guide/urls-web-addresses
+level: warning
+action:
+  name: replace
+  params:
+    - URL
+    - address
+tokens:
+  - URL
diff --git a/styles/Microsoft/HeadingAcronyms.yml b/styles/Microsoft/HeadingAcronyms.yml
new file mode 100644
index 0000000..9dc3b6c
--- /dev/null
+++ b/styles/Microsoft/HeadingAcronyms.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Avoid using acronyms in a title or heading."
+link: https://docs.microsoft.com/en-us/style-guide/acronyms#be-careful-with-acronyms-in-titles-and-headings
+level: warning
+scope: heading
+tokens:
+  - '[A-Z]{2,4}'
diff --git a/styles/Microsoft/HeadingColons.yml b/styles/Microsoft/HeadingColons.yml
new file mode 100644
index 0000000..7013c39
--- /dev/null
+++ b/styles/Microsoft/HeadingColons.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: "Capitalize '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/colons
+nonword: true
+level: error
+scope: heading
+tokens:
+  - ':\s[a-z]'
diff --git a/styles/Microsoft/HeadingPunctuation.yml b/styles/Microsoft/HeadingPunctuation.yml
new file mode 100644
index 0000000..4954cb1
--- /dev/null
+++ b/styles/Microsoft/HeadingPunctuation.yml
@@ -0,0 +1,13 @@
+extends: existence
+message: "Don't use end punctuation in headings."
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/periods
+nonword: true
+level: warning
+scope: heading
+action:
+  name: edit
+  params:
+    - trim_right
+    - ".?!"
+tokens:
+  - "[a-z][.?!]$"
diff --git a/styles/Microsoft/Headings.yml b/styles/Microsoft/Headings.yml
new file mode 100644
index 0000000..63624ed
--- /dev/null
+++ b/styles/Microsoft/Headings.yml
@@ -0,0 +1,28 @@
+extends: capitalization
+message: "'%s' should use sentence-style capitalization."
+link: https://docs.microsoft.com/en-us/style-guide/capitalization
+level: suggestion
+scope: heading
+match: $sentence
+indicators:
+  - ':'
+exceptions:
+  - Azure
+  - CLI
+  - Code
+  - Cosmos
+  - Docker
+  - Emmet
+  - I
+  - Kubernetes
+  - Linux
+  - macOS
+  - Marketplace
+  - MongoDB
+  - REPL
+  - Studio
+  - TypeScript
+  - URLs
+  - Visual
+  - VS
+  - Windows
diff --git a/styles/Microsoft/Hyphens.yml b/styles/Microsoft/Hyphens.yml
new file mode 100644
index 0000000..7e5731c
--- /dev/null
+++ b/styles/Microsoft/Hyphens.yml
@@ -0,0 +1,14 @@
+extends: existence
+message: "'%s' doesn't need a hyphen."
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/dashes-hyphens/hyphens
+level: warning
+ignorecase: false
+nonword: true
+action:
+  name: edit
+  params:
+    - regex
+    - "-"
+    - " "
+tokens:
+  - '\b[^\s-]+ly-\w+\b'
diff --git a/styles/Microsoft/Negative.yml b/styles/Microsoft/Negative.yml
new file mode 100644
index 0000000..d73221f
--- /dev/null
+++ b/styles/Microsoft/Negative.yml
@@ -0,0 +1,13 @@
+extends: existence
+message: "Form a negative number with an en dash, not a hyphen."
+link: https://docs.microsoft.com/en-us/style-guide/numbers
+nonword: true
+level: error
+action:
+  name: edit
+  params:
+    - regex
+    - "-"
+    - "–"
+tokens:
+  - '(?<=\s)-\d+(?:\.\d+)?\b'
diff --git a/styles/Microsoft/Ordinal.yml b/styles/Microsoft/Ordinal.yml
new file mode 100644
index 0000000..e3483e3
--- /dev/null
+++ b/styles/Microsoft/Ordinal.yml
@@ -0,0 +1,13 @@
+extends: existence
+message: "Don't add -ly to an ordinal number."
+link: https://docs.microsoft.com/en-us/style-guide/numbers
+level: error
+action:
+  name: edit
+  params:
+    - trim
+    - ly
+tokens:
+  - firstly
+  - secondly
+  - thirdly
diff --git a/styles/Microsoft/OxfordComma.yml b/styles/Microsoft/OxfordComma.yml
new file mode 100644
index 0000000..493b55c
--- /dev/null
+++ b/styles/Microsoft/OxfordComma.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: "Use the Oxford comma in '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/commas
+scope: sentence
+level: suggestion
+nonword: true
+tokens:
+  - '(?:[^\s,]+,){1,} \w+ (?:and|or) \w+[.?!]'
diff --git a/styles/Microsoft/Passive.yml b/styles/Microsoft/Passive.yml
new file mode 100644
index 0000000..102d377
--- /dev/null
+++ b/styles/Microsoft/Passive.yml
@@ -0,0 +1,183 @@
+extends: existence
+message: "'%s' looks like passive voice."
+ignorecase: true
+level: suggestion
+raw:
+  - \b(am|are|were|being|is|been|was|be)\b\s*
+tokens:
+  - '[\w]+ed'
+  - awoken
+  - beat
+  - become
+  - been
+  - begun
+  - bent
+  - beset
+  - bet
+  - bid
+  - bidden
+  - bitten
+  - bled
+  - blown
+  - born
+  - bought
+  - bound
+  - bred
+  - broadcast
+  - broken
+  - brought
+  - built
+  - burnt
+  - burst
+  - cast
+  - caught
+  - chosen
+  - clung
+  - come
+  - cost
+  - crept
+  - cut
+  - dealt
+  - dived
+  - done
+  - drawn
+  - dreamt
+  - driven
+  - drunk
+  - dug
+  - eaten
+  - fallen
+  - fed
+  - felt
+  - fit
+  - fled
+  - flown
+  - flung
+  - forbidden
+  - foregone
+  - forgiven
+  - forgotten
+  - forsaken
+  - fought
+  - found
+  - frozen
+  - given
+  - gone
+  - gotten
+  - ground
+  - grown
+  - heard
+  - held
+  - hidden
+  - hit
+  - hung
+  - hurt
+  - kept
+  - knelt
+  - knit
+  - known
+  - laid
+  - lain
+  - leapt
+  - learnt
+  - led
+  - left
+  - lent
+  - let
+  - lighted
+  - lost
+  - made
+  - meant
+  - met
+  - misspelt
+  - mistaken
+  - mown
+  - overcome
+  - overdone
+  - overtaken
+  - overthrown
+  - paid
+  - pled
+  - proven
+  - put
+  - quit
+  - read
+  - rid
+  - ridden
+  - risen
+  - run
+  - rung
+  - said
+  - sat
+  - sawn
+  - seen
+  - sent
+  - set
+  - sewn
+  - shaken
+  - shaven
+  - shed
+  - shod
+  - shone
+  - shorn
+  - shot
+  - shown
+  - shrunk
+  - shut
+  - slain
+  - slept
+  - slid
+  - slit
+  - slung
+  - smitten
+  - sold
+  - sought
+  - sown
+  - sped
+  - spent
+  - spilt
+  - spit
+  - split
+  - spoken
+  - spread
+  - sprung
+  - spun
+  - stolen
+  - stood
+  - stridden
+  - striven
+  - struck
+  - strung
+  - stuck
+  - stung
+  - stunk
+  - sung
+  - sunk
+  - swept
+  - swollen
+  - sworn
+  - swum
+  - swung
+  - taken
+  - taught
+  - thought
+  - thrived
+  - thrown
+  - thrust
+  - told
+  - torn
+  - trodden
+  - understood
+  - upheld
+  - upset
+  - wed
+  - wept
+  - withheld
+  - withstood
+  - woken
+  - won
+  - worn
+  - wound
+  - woven
+  - written
+  - wrung
diff --git a/styles/Microsoft/Percentages.yml b/styles/Microsoft/Percentages.yml
new file mode 100644
index 0000000..b68a736
--- /dev/null
+++ b/styles/Microsoft/Percentages.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Use a numeral plus the units."
+link: https://docs.microsoft.com/en-us/style-guide/numbers
+nonword: true
+level: error
+tokens:
+  - '\b[a-zA-z]+\spercent\b'
diff --git a/styles/Microsoft/Plurals.yml b/styles/Microsoft/Plurals.yml
new file mode 100644
index 0000000..1bb6660
--- /dev/null
+++ b/styles/Microsoft/Plurals.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Don't add '%s' to a singular noun. Use plural instead."
+ignorecase: true
+level: error
+link: https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/s/s-es
+raw:
+  - '\(s\)|\(es\)'
diff --git a/styles/Microsoft/Quotes.yml b/styles/Microsoft/Quotes.yml
new file mode 100644
index 0000000..38f4976
--- /dev/null
+++ b/styles/Microsoft/Quotes.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: 'Punctuation should be inside the quotes.'
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/quotation-marks
+level: error
+nonword: true
+tokens:
+  - '["“][^"”“]+["”][.,]'
diff --git a/styles/Microsoft/RangeTime.yml b/styles/Microsoft/RangeTime.yml
new file mode 100644
index 0000000..72d8bbf
--- /dev/null
+++ b/styles/Microsoft/RangeTime.yml
@@ -0,0 +1,13 @@
+extends: existence
+message: "Use 'to' instead of a dash in '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/numbers
+nonword: true
+level: error
+action:
+  name: edit
+  params:
+    - regex
+    - "[-–]"
+    - "to"
+tokens:
+  - '\b(?:AM|PM)\s?[-–]\s?.+(?:AM|PM)\b'
diff --git a/styles/Microsoft/Semicolon.yml b/styles/Microsoft/Semicolon.yml
new file mode 100644
index 0000000..4d90546
--- /dev/null
+++ b/styles/Microsoft/Semicolon.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: "Try to simplify this sentence."
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/semicolons
+nonword: true
+scope: sentence
+level: suggestion
+tokens:
+  - ';'
diff --git a/styles/Microsoft/SentenceLength.yml b/styles/Microsoft/SentenceLength.yml
new file mode 100644
index 0000000..82e2656
--- /dev/null
+++ b/styles/Microsoft/SentenceLength.yml
@@ -0,0 +1,6 @@
+extends: occurrence
+message: "Try to keep sentences short (< 30 words)."
+scope: sentence
+level: suggestion
+max: 30
+token: \b(\w+)\b
diff --git a/styles/Microsoft/Spacing.yml b/styles/Microsoft/Spacing.yml
new file mode 100644
index 0000000..bbd10e5
--- /dev/null
+++ b/styles/Microsoft/Spacing.yml
@@ -0,0 +1,8 @@
+extends: existence
+message: "'%s' should have one space."
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/periods
+level: error
+nonword: true
+tokens:
+  - '[a-z][.?!] {2,}[A-Z]'
+  - '[a-z][.?!][A-Z]'
diff --git a/styles/Microsoft/Suspended.yml b/styles/Microsoft/Suspended.yml
new file mode 100644
index 0000000..7282e9c
--- /dev/null
+++ b/styles/Microsoft/Suspended.yml
@@ -0,0 +1,7 @@
+extends: existence
+message: "Don't use '%s' unless space is limited."
+link: https://docs.microsoft.com/en-us/style-guide/punctuation/dashes-hyphens/hyphens
+ignorecase: true
+level: warning
+tokens:
+  - '\w+- and \w+-'
diff --git a/styles/Microsoft/Terms.yml b/styles/Microsoft/Terms.yml
new file mode 100644
index 0000000..65fca10
--- /dev/null
+++ b/styles/Microsoft/Terms.yml
@@ -0,0 +1,42 @@
+extends: substitution
+message: "Prefer '%s' over '%s'."
+# term preference should be based on microsoft style guide, such as
+link: https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/a/adapter
+level: warning
+ignorecase: true
+action:
+  name: replace
+swap:
+  "(?:agent|virtual assistant|intelligent personal assistant)": personal digital assistant
+  "(?:assembler|machine language)": assembly language
+  "(?:drive C:|drive C>|C: drive)": drive C
+  "(?:internet bot|web robot)s?": bot(s)
+  "(?:microsoft cloud|the cloud)": cloud
+  "(?:mobile|smart) ?phone": phone
+  "24/7": every day
+  "audio(?:-| )book": audiobook
+  "back(?:-| )light": backlight
+  "chat ?bots?": chatbot(s)
+  adaptor: adapter
+  administrate: administer
+  afterwards: afterward
+  alphabetic: alphabetical
+  alphanumerical: alphanumeric
+  an URL: a URL
+  anti-aliasing: antialiasing
+  anti-malware: antimalware
+  anti-spyware: antispyware
+  anti-virus: antivirus
+  appendixes: appendices
+  artificial intelligence: AI
+  caap: CaaP
+  conversation-as-a-platform: conversation as a platform
+  eb: EB
+  gb: GB
+  gbps: Gbps
+  kb: KB
+  keypress: keystroke
+  mb: MB
+  pb: PB
+  tb: TB
+  zb: ZB
diff --git a/styles/Microsoft/URLFormat.yml b/styles/Microsoft/URLFormat.yml
new file mode 100644
index 0000000..4e24aa5
--- /dev/null
+++ b/styles/Microsoft/URLFormat.yml
@@ -0,0 +1,9 @@
+extends: substitution
+message: Use 'of' (not 'for') to describe the relationship of the word URL to a resource.
+ignorecase: true
+link: https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/u/url
+level: suggestion
+action:
+  name: replace
+swap:
+  URL for: URL of
diff --git a/styles/Microsoft/Units.yml b/styles/Microsoft/Units.yml
new file mode 100644
index 0000000..f062418
--- /dev/null
+++ b/styles/Microsoft/Units.yml
@@ -0,0 +1,16 @@
+extends: existence
+message: "Don't spell out the number in '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/units-of-measure-terms
+level: error
+raw:
+  - '[a-zA-Z]+\s'
+tokens:
+  - '(?:centi|milli)?meters'
+  - '(?:kilo)?grams'
+  - '(?:kilo)?meters'
+  - '(?:mega)?pixels'
+  - cm
+  - inches
+  - lb
+  - miles
+  - pounds
diff --git a/styles/Microsoft/Vocab.yml b/styles/Microsoft/Vocab.yml
new file mode 100644
index 0000000..eebe97b
--- /dev/null
+++ b/styles/Microsoft/Vocab.yml
@@ -0,0 +1,25 @@
+extends: existence
+message: "Verify your use of '%s' with the A-Z word list."
+link: 'https://docs.microsoft.com/en-us/style-guide'
+level: suggestion
+ignorecase: true
+tokens:
+  - above
+  - accessible
+  - actionable
+  - against
+  - alarm
+  - alert
+  - alias
+  - allows?
+  - and/or
+  - as well as
+  - assure
+  - author
+  - avg
+  - beta
+  - ensure
+  - he
+  - insure
+  - sample
+  - she
diff --git a/styles/Microsoft/We.yml b/styles/Microsoft/We.yml
new file mode 100644
index 0000000..97c901c
--- /dev/null
+++ b/styles/Microsoft/We.yml
@@ -0,0 +1,11 @@
+extends: existence
+message: "Try to avoid using first-person plural like '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/grammar/person#avoid-first-person-plural
+level: warning
+ignorecase: true
+tokens:
+  - we
+  - we'(?:ve|re)
+  - ours?
+  - us
+  - let's
diff --git a/styles/Microsoft/Wordiness.yml b/styles/Microsoft/Wordiness.yml
new file mode 100644
index 0000000..8a4fea7
--- /dev/null
+++ b/styles/Microsoft/Wordiness.yml
@@ -0,0 +1,127 @@
+extends: substitution
+message: "Consider using '%s' instead of '%s'."
+link: https://docs.microsoft.com/en-us/style-guide/word-choice/use-simple-words-concise-sentences
+ignorecase: true
+level: suggestion
+action:
+  name: replace
+swap:
+  "sufficient number(?: of)?": enough
+  (?:extract|take away|eliminate): remove
+  (?:in order to|as a means to): to
+  (?:inform|let me know): tell
+  (?:previous|prior) to: before
+  (?:utilize|make use of): use
+  a (?:large)? majority of: most
+  a (?:large)? number of: many
+  a myriad of: myriad
+  adversely impact: hurt
+  all across: across
+  all of a sudden: suddenly
+  all of these: these
+  all of(?! a sudden| these): all
+  all-time record: record
+  almost all: most
+  almost never: seldom
+  along the lines of: similar to
+  an adequate number of: enough
+  an appreciable number of: many
+  an estimated: about
+  any and all: all
+  are in agreement: agree
+  as a matter of fact: in fact
+  as a means of: to
+  as a result of: because of
+  as of yet: yet
+  as per: per
+  at a later date: later
+  at all times: always
+  at the present time: now
+  at this point in time: at this point
+  based in large part on: based on
+  based on the fact that: because
+  basic necessity: necessity
+  because of the fact that: because
+  came to a realization: realized
+  came to an abrupt end: ended abruptly
+  carry out an evaluation of: evaluate
+  close down: close
+  closed down: closed
+  complete stranger: stranger
+  completely separate: separate
+  concerning the matter of: regarding
+  conduct a review of: review
+  conduct an investigation: investigate
+  conduct experiments: experiment
+  continue on: continue
+  despite the fact that: although
+  disappear from sight: disappear
+  doomed to fail: doomed
+  drag and drop: drag
+  drag-and-drop: drag
+  due to the fact that: because
+  during the period of: during
+  during the time that: while
+  emergency situation: emergency
+  establish connectivity: connect
+  except when: unless
+  excessive number: too many
+  extend an invitation: invite
+  fall down: fall
+  fell down: fell
+  for the duration of: during
+  gather together: gather
+  has the ability to: can
+  has the capacity to: can
+  has the opportunity to: could
+  hold a meeting: meet
+  if this is not the case: if not
+  in a careful manner: carefully
+  in a thoughtful manner: thoughtfully
+  in a timely manner: timely
+  in addition: also
+  in an effort to: to
+  in between: between
+  in lieu of: instead of
+  in many cases: often
+  in most cases: usually
+  in order to: to
+  in some cases: sometimes
+  in spite of the fact that: although
+  in spite of: despite
+  in the (?:very)? near future: soon
+  in the event that: if
+  in the neighborhood of: roughly
+  in the vicinity of: close to
+  it would appear that: apparently
+  lift up: lift
+  made reference to: referred to
+  make reference to: refer to
+  mix together: mix
+  none at all: none
+  not in a position to: unable
+  not possible: impossible
+  of major importance: important
+  perform an assessment of: assess
+  pertaining to: about
+  place an order: order
+  plays a key role in: is essential to
+  present time: now
+  readily apparent: apparent
+  some of the: some
+  span across: span
+  subsequent to: after
+  successfully complete: complete
+  take action: act
+  take into account: consider
+  the question as to whether: whether
+  there is no doubt but that: doubtless
+  this day and age: this age
+  this is a subject that: this subject
+  time (?:frame|period): time
+  under the provisions of: under
+  until such time as: until
+  used for fuel purposes: used for fuel
+  whether or not: whether
+  with regard to: regarding
+  with the exception of: except for
diff --git a/styles/Microsoft/meta.json b/styles/Microsoft/meta.json
new file mode 100644
index 0000000..297719b
--- /dev/null
+++ b/styles/Microsoft/meta.json
@@ -0,0 +1,4 @@
+{
+  "feed": "https://github.com/errata-ai/Microsoft/releases.atom",
+  "vale_version": ">=1.0.0"
+}
diff --git a/tests/__init__.py b/tests/__init__.py
new file mode 100644
index 0000000..83bd1dc
--- /dev/null
+++ b/tests/__init__.py
@@ -0,0 +1 @@
+"""Tests for Humanizer scripts."""
diff --git a/tests/test_install_adapters.py b/tests/test_install_adapters.py
new file mode 100644
index 0000000..00dfd38
--- /dev/null
+++ b/tests/test_install_adapters.py
@@ -0,0 +1,145 @@
+# ruff: noqa: S101, PLR2004, PLR0913
+"""Tests for the install_adapters script."""
+
+from pathlib import Path
+from unittest.mock import MagicMock, patch
+
+import pytest
+
+from scripts.install_adapters import (
+    install_file,
+    main,
+)
+
+
+def test_install_file_success(tmp_path: Path) -> None:
+    """Verify that a file is correctly copied to the destination."""
+    source = tmp_path / "source.txt"
+    source.write_text("content", encoding="utf-8")
+    dest_dir = tmp_path / "dest"
+
+    install_file(source, dest_dir, "installed.txt")
+
+    dest_file = dest_dir / "installed.txt"
+    assert dest_file.exists()
+    assert dest_file.read_text(encoding="utf-8") == "content"
+
+
+def test_install_file_source_missing(
+    caplog: pytest.LogCaptureFixture, tmp_path: Path
+) -> None:
+    """Verify that a warning is logged when the source file is missing."""
+    caplog.set_level("WARNING")
+    install_file(Path("missing.txt"), tmp_path / "dest", "dest.txt")
+    assert "Source not found: missing.txt" in caplog.text
+
+
+@patch("scripts.install_adapters.subprocess.run")
+@patch("scripts.install_adapters.shutil.copytree")
+@patch("scripts.install_adapters.shutil.rmtree")
+@patch("scripts.install_adapters.install_file")
+@patch("scripts.install_adapters.Path.home")
+@patch("scripts.install_adapters.Path.exists")
+def test_main_success(
+    mock_exists: MagicMock,
+    mock_home: MagicMock,
+    mock_install: MagicMock,
+    mock_rmtree: MagicMock,
+    mock_copytree: MagicMock,
+    mock_run: MagicMock,
+    tmp_path: Path,
+) -> None:
+    """Verify the main installation flow with successful validation."""
+    mock_home.return_value = tmp_path / "home"
+    mock_run.return_value = MagicMock(returncode=0)
+
+    # 1. First run: all exist (covers rmtree call)
+    mock_exists.return_value = True
+    with patch("sys.argv", ["install_adapters.py", "--skip-validation"]):
+        main()
+
+    assert mock_install.call_count == 7
+    mock_copytree.assert_called_once()
+    mock_rmtree.assert_called_once()
+
+    # 2. Second run: gemini_extensions doesn't exist (covers NO rmtree call)
+    mock_rmtree.reset_mock()
+    mock_copytree.reset_mock()
+    mock_install.reset_mock()
+
+    # source_gemini.exists() -> True, gemini_extensions.exists() -> False,
+    # then 7 calls to install_file (each calling source.exists())
+    mock_exists.side_effect = [True, False, True, True, True, True, True, True, True]
+    with patch("sys.argv", ["install_adapters.py", "--skip-validation"]):
+        main()
+
+    assert mock_install.call_count == 7
+    mock_copytree.assert_called_once()
+    mock_rmtree.assert_not_called()
+
+
+@patch("scripts.install_adapters.subprocess.run")
+@patch("scripts.install_adapters.shutil.copytree")
+@patch("scripts.install_adapters.shutil.rmtree")
+@patch("scripts.install_adapters.install_file")
+@patch("scripts.install_adapters.Path.home")
+@patch("scripts.install_adapters.Path.exists")
+def test_main_validation_success(
+    mock_exists: MagicMock,
+    mock_home: MagicMock,
+    mock_install: MagicMock,
+    mock_rmtree: MagicMock,
+    mock_copytree: MagicMock,
+    mock_run: MagicMock,
+    tmp_path: Path,
+) -> None:
+    """Verify that validation runs and succeeds before installation."""
+    mock_home.return_value = tmp_path / "home"
+    mock_run.return_value = MagicMock(returncode=0)
+    mock_exists.return_value = True
+
+    with patch("sys.argv", ["install_adapters.py"]):
+        main()
+
+    assert mock_run.call_count == 1
+    assert mock_install.call_count == 7
+    mock_rmtree.assert_called_once()
+    mock_copytree.assert_called_once()
+
+
+@patch("scripts.install_adapters.Path.exists")
+@patch("scripts.install_adapters.Path.home")
+def test_main_gemini_missing(
+    mock_home: MagicMock,
+    mock_exists: MagicMock,
+    caplog: pytest.LogCaptureFixture,
+    tmp_path: Path,
+) -> None:
+    """Verify that a warning is logged if the Gemini source adapter is missing."""
+    caplog.set_level("WARNING")
+    mock_home.return_value = tmp_path / "home"
+    # Return False for source_gemini.exists()
+    mock_exists.return_value = False
+
+    with (
+        patch("sys.argv", ["install_adapters.py", "--skip-validation"]),
+        patch("scripts.install_adapters.install_file"),
+    ):
+        main()
+
+    assert "Source not found" in caplog.text
+
+
+@patch("scripts.install_adapters.subprocess.run")
+def test_main_validation_fails(
+    mock_run: MagicMock, caplog: pytest.LogCaptureFixture
+) -> None:
+    """Verify that installation aborts if validation fails."""
+    mock_run.return_value = MagicMock(returncode=1, stderr="Some error")
+
+    with patch("sys.argv", ["install_adapters.py"]):
+        with pytest.raises(SystemExit) as excinfo:
+            main()
+        assert excinfo.value.code == 1
+
+    assert "Validation failed" in caplog.text
diff --git a/tests/test_sync_adapters.py b/tests/test_sync_adapters.py
new file mode 100644
index 0000000..c508fcf
--- /dev/null
+++ b/tests/test_sync_adapters.py
@@ -0,0 +1,114 @@
+# ruff: noqa: S101, PLR2004
+"""Tests for the sync_adapters script."""
+
+from pathlib import Path
+from unittest.mock import MagicMock, patch
+
+import pytest
+
+from scripts.sync_adapters import (
+    get_skill_version,
+    main,
+    sync_antigravity_skill,
+    update_metadata,
+)
+
+
+@pytest.fixture
+def temp_skill_file(tmp_path: Path) -> Path:
+    """Create a temporary SKILL.md file with version metadata."""
+    skill_file = tmp_path / "SKILL.md"
+    skill_file.write_text("version: 1.2.3\nSome content", encoding="utf-8")
+    return skill_file
+
+
+def test_get_skill_version_success(temp_skill_file: Path) -> None:
+    """Verify that the version is correctly extracted from the skill file."""
+    assert get_skill_version(temp_skill_file) == "1.2.3"
+
+
+def test_get_skill_version_not_found() -> None:
+    """Verify that FileNotFoundError is raised when the skill file is missing."""
+    with pytest.raises(FileNotFoundError, match=r"Source file .* not found!"):
+        get_skill_version(Path("nonexistent.md"))
+
+
+def test_get_skill_version_invalid_format(tmp_path: Path) -> None:
+    """Verify that ValueError is raised when the version format is invalid."""
+    skill_file = tmp_path / "SKILL_invalid.md"
+    skill_file.write_text("no version here", encoding="utf-8")
+    with pytest.raises(ValueError, match="Could not parse version from"):
+        get_skill_version(skill_file)
+
+
+def test_sync_antigravity_skill(tmp_path: Path) -> None:
+    """Verify that the Antigravity skill adapter is synced correctly."""
+    source = tmp_path / "SKILL.md"
+    source.write_text("original content", encoding="utf-8")
+    dest = tmp_path / "dest" / "SKILL.md"
+
+    sync_antigravity_skill(source, dest, "1.2.3", "2026-01-31")
+
+    assert dest.exists()
+    content = dest.read_text(encoding="utf-8")
+    assert "skill_version: 1.2.3" in content
+    assert "last_synced: 2026-01-31" in content
+    assert "original content" in content
+
+
+def test_update_metadata_success(tmp_path: Path) -> None:
+    """Verify that metadata is updated in an existing adapter file."""
+    dest = tmp_path / "ADAPTER.md"
+    dest.write_text(
+        "skill_version: 0.0.0\nlast_synced: 2000-01-01\nOther text", encoding="utf-8"
+    )
+
+    update_metadata(dest, "1.2.3", "2026-01-31")
+
+    content = dest.read_text(encoding="utf-8")
+    assert "skill_version: 1.2.3" in content
+    assert "last_synced: 2026-01-31" in content
+    assert "Other text" in content
+
+
+def test_update_metadata_not_found(caplog: pytest.LogCaptureFixture) -> None:
+    """Verify that a warning is logged when the adapter file to update is missing."""
+    update_metadata(Path("nonexistent.md"), "1.2.3", "2026-01-31")
+    assert "Warning: nonexistent.md not found." in caplog.text
+
+
+@patch("scripts.sync_adapters.argparse.ArgumentParser.parse_args")
+@patch("scripts.sync_adapters.get_skill_version")
+@patch("scripts.sync_adapters.sync_antigravity_skill")
+@patch("scripts.sync_adapters.update_metadata")
+def test_main_success(
+    mock_update: MagicMock,
+    mock_sync: MagicMock,
+    mock_get_version: MagicMock,
+    mock_parse_args: MagicMock,
+) -> None:
+    """Verify the main sync flow."""
+    mock_parse_args.return_value = MagicMock(source=Path("SKILL.md"))
+    mock_get_version.return_value = "1.2.3"
+
+    main()
+
+    mock_get_version.assert_called_once_with(Path("SKILL.md"))
+    mock_sync.assert_called_once()
+    assert mock_update.call_count == 5
+
+
+@patch("scripts.sync_adapters.argparse.ArgumentParser.parse_args")
+@patch("scripts.sync_adapters.get_skill_version")
+def test_main_error(
+    mock_get_version: MagicMock,
+    mock_parse_args: MagicMock,
+    caplog: pytest.LogCaptureFixture,
+) -> None:
+    """Verify that errors during version extraction are logged."""
+    mock_parse_args.return_value = MagicMock(source=Path("SKILL.md"))
+    mock_get_version.side_effect = ValueError("Test Error")
+
+    main()
+
+    assert "Error: Test Error" in caplog.text
diff --git a/tests/test_validate_adapters.py b/tests/test_validate_adapters.py
new file mode 100644
index 0000000..df8d5fb
--- /dev/null
+++ b/tests/test_validate_adapters.py
@@ -0,0 +1,142 @@
+# ruff: noqa: S101, PLR2004
+"""Tests for the validate_adapters script."""
+
+from pathlib import Path
+from unittest.mock import MagicMock, patch
+
+import pytest
+
+from scripts.validate_adapters import (
+    get_skill_metadata,
+    main,
+    validate_adapter,
+)
+
+
+@pytest.fixture
+def mock_skill_file(tmp_path: Path) -> Path:
+    """Create a temporary SKILL.md file with metadata."""
+    skill_file = tmp_path / "SKILL.md"
+    skill_file.write_text("name: humanizer\nversion: 1.2.3\n", encoding="utf-8")
+    return skill_file
+
+
+def test_get_skill_metadata_success(mock_skill_file: Path) -> None:
+    """Verify that name and version are correctly extracted from the skill file."""
+    name, version = get_skill_metadata(mock_skill_file)
+    assert name == "humanizer"
+    assert version == "1.2.3"
+
+
+def test_get_skill_metadata_not_found() -> None:
+    """Verify that FileNotFoundError is raised when the skill file is missing."""
+    with pytest.raises(FileNotFoundError, match=r"Source file .* not found!"):
+        get_skill_metadata(Path("nonexistent.md"))
+
+
+def test_get_skill_metadata_missing_fields(tmp_path: Path) -> None:
+    """Verify that ValueError is raised when required metadata fields are missing."""
+    skill_file = tmp_path / "SKILL_bad.md"
+    skill_file.write_text("nothing here", encoding="utf-8")
+    with pytest.raises(ValueError, match="Failed to read name/version from"):
+        get_skill_metadata(skill_file)
+
+
+def test_validate_adapter_success(tmp_path: Path) -> None:
+    """Verify that a valid adapter file returns no errors."""
+    adapter = tmp_path / "ADAPTER.md"
+    adapter_content = (
+        "skill_name: humanizer\n"
+        "skill_version: 1.2.3\n"
+        "last_synced: 2026-01-31\n"
+        "source_path: SKILL.md"
+    )
+    adapter.write_text(adapter_content, encoding="utf-8")
+    errors = validate_adapter(adapter, "humanizer", "1.2.3", "SKILL.md")
+    assert not errors
+
+
+def test_validate_adapter_failures(tmp_path: Path) -> None:
+    """Verify that an invalid adapter file returns all expected errors."""
+    adapter = tmp_path / "ADAPTER.md"
+    adapter.write_text(
+        "skill_name: wrong\nskill_version: 0.0.0\nsource_path: WRONG.md",
+        encoding="utf-8",
+    )
+    errors = validate_adapter(adapter, "humanizer", "1.2.3", "SKILL.md")
+    assert len(errors) == 4
+    assert any("skill_name mismatch" in e for e in errors)
+    assert any("skill_version mismatch" in e for e in errors)
+    assert any("missing last_synced" in e for e in errors)
+    assert any("source_path mismatch" in e for e in errors)
+
+
+def test_validate_adapter_missing() -> None:
+    """Verify that a missing adapter file returns an error."""
+    errors = validate_adapter(Path("missing.md"), "n", "v", "s")
+    assert errors == ["Missing adapter file: missing.md"]
+
+
+@patch("scripts.validate_adapters.get_skill_metadata")
+@patch("scripts.validate_adapters.validate_adapter")
+def test_main_success(
+    mock_validate: MagicMock,
+    mock_get_meta: MagicMock,
+    caplog: pytest.LogCaptureFixture,
+) -> None:
+    """Verify the main validation flow with successful validation."""
+    caplog.set_level("INFO")
+    mock_get_meta.return_value = ("humanizer", "1.2.3")
+    mock_validate.return_value = []
+
+    with patch(
+        "scripts.validate_adapters.argparse.ArgumentParser.parse_args"
+    ) as mock_args:
+        mock_args.return_value = MagicMock(source=Path("SKILL.md"))
+        with pytest.raises(SystemExit) as excinfo:
+            main()
+        assert excinfo.value.code == 0
+
+    assert "Adapter metadata validated" in caplog.text
+
+
+@patch("scripts.validate_adapters.get_skill_metadata")
+@patch("scripts.validate_adapters.validate_adapter")
+def test_main_failure(
+    mock_validate: MagicMock,
+    mock_get_meta: MagicMock,
+    caplog: pytest.LogCaptureFixture,
+) -> None:
+    """Verify that validation failures exit with code 1."""
+    mock_get_meta.return_value = ("humanizer", "1.2.3")
+    mock_validate.return_value = ["Error 1", "Error 2"]
+
+    with patch(
+        "scripts.validate_adapters.argparse.ArgumentParser.parse_args"
+    ) as mock_args:
+        mock_args.return_value = MagicMock(source=Path("SKILL.md"))
+        with pytest.raises(SystemExit) as excinfo:
+            main()
+        assert excinfo.value.code == 1
+
+    assert "Error 1" in caplog.text
+    assert "Error 2" in caplog.text
+
+
+@patch("scripts.validate_adapters.get_skill_metadata")
+def test_main_source_not_found(
+    mock_get_meta: MagicMock,
+    caplog: pytest.LogCaptureFixture,
+) -> None:
+    """Verify that missing source file logs an error and exits with code 1."""
+    mock_get_meta.side_effect = FileNotFoundError("Missing file")
+
+    with patch(
+        "scripts.validate_adapters.argparse.ArgumentParser.parse_args"
+    ) as mock_args:
+        mock_args.return_value = MagicMock(source=Path("SKILL.md"))
+        with pytest.raises(SystemExit) as excinfo:
+            main()
+        assert excinfo.value.code == 1
+
+    assert "Error: Missing file" in caplog.text