refactor: consolidate writing voice rules

.agents/skills/article-writing/SKILL.md

@@ -23,50 +23,23 @@ Write long-form content that sounds like an actual person with a point of view,
 4. Use proof instead of adjectives.
 5. Never invent facts, credibility, or customer evidence.
 
-## Voice Capture Workflow
+## Voice Handling
 
-If the user wants a specific voice, collect one or more of:
+If the user wants a specific voice, run `brand-voice` first and reuse its `VOICE PROFILE`.
-- published articles
+Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.
-- newsletters
-- X posts or threads
-- docs or memos
-- launch notes
-- a style guide
-
-Then extract:
-- sentence length and rhythm
-- whether the writing is compressed, explanatory, sharp, or formal
-- how parentheses are used
-- how often the writer asks questions
-- whether the writer uses fragments, lists, or hard pivots
-- formatting habits such as headers, bullets, code blocks, pull quotes
-- what the writer clearly avoids
 
 If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.
 
-## Affaan / ECC Voice Reference
-
-When matching Affaan / ECC voice, bias toward:
-- direct claims over scene-setting
-- high specificity
-- parentheticals used for qualification or over-clarification, not comedy
-- capitalization chosen situationally, not as a gimmick
-- very low tolerance for fake thought-leadership cadence
-- almost no bait questions
-
 ## Banned Patterns
 
 Delete and rewrite any of these:
 - "In today's rapidly evolving landscape"
 - "game-changer", "cutting-edge", "revolutionary"
-- "no fluff"
-- "not X, just Y"
 - "here's why this matters" as a standalone bridge
 - fake vulnerability arcs
 - a closing question added only to juice engagement
-- forced lowercase
-- corny parenthetical asides
 - biography padding that does not move the argument
+- generic AI throat-clearing that delays the point
 
 ## Writing Process
 
@@ -101,6 +74,6 @@ Delete and rewrite any of these:
 Before delivering:
 - factual claims are backed by provided sources
 - generic AI transitions are gone
-- the voice matches the supplied examples
+- the voice matches the supplied examples or the agreed `VOICE PROFILE`
 - every section adds something new
 - formatting matches the intended medium

.agents/skills/content-engine/SKILL.md

@@ -38,50 +38,28 @@ Before drafting, identify the source set:
 If the user wants a specific voice, build a voice profile from real examples before writing.
 Use `brand-voice` as the canonical workflow when voice consistency matters across more than one output.
 
-## Voice Capture Workflow
+## Voice Handling
 
-Run `brand-voice` first when:
+`brand-voice` is the canonical voice layer.
+
+Run it first when:
 
 - there are multiple downstream outputs
 - the user explicitly cares about writing style
 - the content is launch, outreach, or reputation-sensitive
 
-At minimum, produce a compact `VOICE PROFILE` covering:
+Reuse the resulting `VOICE PROFILE` here instead of rebuilding a second voice model.
-- rhythm
+If the user wants Affaan / ECC voice specifically, still treat `brand-voice` as the source of truth and feed it the best live or source-derived material available.
-- compression
-- capitalization
-- parenthetical use
-- question use
-- preferred moves
-- banned moves
-
-Do not start drafting until the voice profile is clear enough to enforce.
-
-## Affaan / ECC Voice Reference
-
-When the user wants Affaan / ECC voice specifically, default to this unless newer examples clearly override it:
-- direct, compressed, concrete
-- strong preference for specific claims, numbers, mechanisms, and receipts
-- parentheticals used to qualify, narrow, or over-clarify, not to do corny bits
-- lowercase is optional, not mandatory
-- questions are rare and should not be added as bait
-- transitions should feel earned, not polished
-- tone can be sharp or blunt, but should not sound like a content marketer
 
 ## Hard Bans
 
 Delete and rewrite any of these:
 - "In today's rapidly evolving landscape"
 - "game-changer", "revolutionary", "cutting-edge"
-- "no fluff"
-- "not X, just Y"
 - "here's why this matters" unless it is followed immediately by something concrete
-- "Excited to share"
-- fake curiosity gaps
 - ending with a LinkedIn-style question just to farm replies
-- forced lowercase when the source voice does not call for it
 - forced casualness on LinkedIn
-- parenthetical jokes that were not present in the source voice
+- fake engagement padding that was not present in the source material
 
 ## Platform Adaptation Rules
 

.agents/skills/crosspost/SKILL.md

@@ -39,13 +39,8 @@ Use `content-engine` first if the source still needs voice shaping.
 
 Run `brand-voice` first if the source voice is not already captured in the current session.
 
-Before adapting, note:
+Reuse the resulting `VOICE PROFILE` directly.
-- how blunt or explanatory the source is
+Do not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.
-- whether the source uses fragments, lists, or longer transitions
-- whether the source uses parentheses
-- whether the source avoids questions, hashtags, or CTA language
-
-The adaptation should preserve that fingerprint.
 
 ### Step 3: Adapt by Platform Constraint
 
@@ -91,7 +86,6 @@ Delete and rewrite any of these:
 - "Here's what I learned"
 - "What do you think?"
 - "link in bio" unless that is literally true
-- "not X, just Y"
 - generic "professional takeaway" paragraphs that were not in the source
 
 ## Output Format

.agents/skills/everything-claude-code/SKILL.md

@@ -5,7 +5,7 @@ description: Development conventions and patterns for everything-claude-code. Ja
 
 # Everything Claude Code Conventions
 
-> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-04-02
+> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-03-20
 
 ## Overview
 
@@ -34,13 +34,13 @@ Follow these commit message conventions based on 500 analyzed commits.
 ### Prefixes Used
 
 - `fix`
+- `test`
 - `feat`
 - `docs`
-- `chore`
 
 ### Message Guidelines
 
-- Average message length: ~57 characters
+- Average message length: ~65 characters
 - Keep first line concise and descriptive
 - Use imperative mood ("Add feature" not "Added feature")
 
@@ -48,49 +48,49 @@ Follow these commit message conventions based on 500 analyzed commits.
 *Commit message example*
 
 ```text
-feat: add everything-claude-code ECC bundle (.claude/commands/add-or-update-skill.md)
+feat(rules): add C# language support
 ```
 
 *Commit message example*
 
 ```text
-refactor: extract social graph ranking core
+chore(deps-dev): bump flatted (#675)
 ```
 
 *Commit message example*
 
 ```text
-fix: port safe ci cleanup from backlog
+fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691)
 ```
 
 *Commit message example*
 
 ```text
-docs: close bundle drift and sync plugin guidance
+docs: add Antigravity setup and usage guide (#552)
 ```
 
 *Commit message example*
 
 ```text
-chore: ignore local orchestration artifacts
+merge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer
 ```
 
 *Commit message example*
 
 ```text
-feat: add everything-claude-code ECC bundle (.claude/commands/refactoring.md)
+Revert "Add Kiro IDE support (.kiro/) (#548)"
 ```
 
 *Commit message example*
 
 ```text
-feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
+Add Kiro IDE support (.kiro/) (#548)
 ```
 
 *Commit message example*
 
 ```text
-feat: add everything-claude-code ECC bundle (.claude/enterprise/controls.md)
+feat: add block-no-verify hook for Claude Code and Cursor (#649)
 ```
 
 ## Architecture
@@ -184,11 +184,33 @@ try {
 
 These workflows were detected from analyzing commit patterns.
 
+### Database Migration
+
+Database schema changes with migration files
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create migration file
+2. Update schema definitions
+3. Generate/update types
+
+**Files typically involved**:
+- `**/schema.*`
+- `migrations/*`
+
+**Example commit sequence**:
+```
+feat: implement --with/--without selective install flags (#679)
+fix: sync catalog counts with filesystem (27 agents, 113 skills, 58 commands) (#693)
+feat(rules): add Rust language rules (rebased #660) (#686)
+```
+
 ### Feature Development
 
 Standard feature implementation workflow
 
-**Frequency**: ~19 times per month
+**Frequency**: ~22 times per month
 
 **Steps**:
 1. Add feature implementation
@@ -196,197 +218,205 @@ Standard feature implementation workflow
 3. Update documentation
 
 **Files typically involved**:
-- `.opencode/*`
+- `manifests/*`
-- `.opencode/plugins/*`
+- `schemas/*`
-- `.opencode/plugins/lib/*`
 - `**/*.test.*`
 - `**/api/**`
 
 **Example commit sequence**:
 ```
-feat(install): add CodeBuddy(Tencent) adaptation with installation scripts (#1038)
+feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer
-chore(deps-dev): bump c8 from 10.1.3 to 11.0.0 (#1065)
+docs(skills): align documentation-lookup with CONTRIBUTING template; add cross-harness (Codex/Cursor) skill copies
-chore(deps): bump actions/checkout from 4.3.1 to 6.0.2 (#1060)
+fix: address PR review — skill template (When to use, How it works, Examples), bun.lock, next build note, rust-reviewer CI note, doc-lookup privacy/uncertainty
 ```
 
-### Refactoring
+### Add Language Rules
 
-Code refactoring and cleanup workflow
+Adds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create a new directory under rules/{language}/
+2. Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content
+3. Optionally reference or link to related skills
+
+**Files typically involved**:
+- `rules/*/coding-style.md`
+- `rules/*/hooks.md`
+- `rules/*/patterns.md`
+- `rules/*/security.md`
+- `rules/*/testing.md`
+
+**Example commit sequence**:
+```
+Create a new directory under rules/{language}/
+Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content
+Optionally reference or link to related skills
+```
+
+### Add New Skill
+
+Adds a new skill to the system, documenting its workflow, triggers, and usage, often with supporting scripts.
 
 **Frequency**: ~4 times per month
 
 **Steps**:
-1. Ensure tests pass before refactor
+1. Create a new directory under skills/{skill-name}/
-2. Refactor code structure
+2. Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.)
-3. Verify tests still pass
+3. Optionally add scripts or supporting files under skills/{skill-name}/scripts/
+4. Address review feedback and iterate on documentation
 
 **Files typically involved**:
-- `src/**/*`
+- `skills/*/SKILL.md`
+- `skills/*/scripts/*.sh`
+- `skills/*/scripts/*.js`
 
 **Example commit sequence**:
 ```
-refactor: collapse legacy command bodies into skills
+Create a new directory under skills/{skill-name}/
-feat: add connected operator workflow skills
+Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.)
-feat: expand lead intelligence outreach channels
+Optionally add scripts or supporting files under skills/{skill-name}/scripts/
+Address review feedback and iterate on documentation
 ```
 
-### Add Or Update Skill
+### Add New Agent
 
-Adds a new skill or updates an existing skill, including documentation and registration in manifests.
+Adds a new agent to the system for code review, build resolution, or other automated tasks.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create a new agent markdown file under agents/{agent-name}.md
+2. Register the agent in AGENTS.md
+3. Optionally update README.md and docs/COMMAND-AGENT-MAP.md
+
+**Files typically involved**:
+- `agents/*.md`
+- `AGENTS.md`
+- `README.md`
+- `docs/COMMAND-AGENT-MAP.md`
+
+**Example commit sequence**:
+```
+Create a new agent markdown file under agents/{agent-name}.md
+Register the agent in AGENTS.md
+Optionally update README.md and docs/COMMAND-AGENT-MAP.md
+```
+
+### Add New Workflow Surface
+
+Adds or updates a workflow entrypoint. Default to skills-first; only add a command shim when legacy slash compatibility is still required.
+
+**Frequency**: ~1 times per month
+
+**Steps**:
+1. Create or update the canonical workflow under skills/{skill-name}/SKILL.md
+2. Only if needed, add or update commands/{command-name}.md as a compatibility shim
+
+**Files typically involved**:
+- `skills/*/SKILL.md`
+- `commands/*.md` (only when a legacy shim is intentionally retained)
+
+**Example commit sequence**:
+```
+Create or update the canonical skill under skills/{skill-name}/SKILL.md
+Only if needed, add or update commands/{command-name}.md as a compatibility shim
+```
+
+### Sync Catalog Counts
+
+Synchronizes the documented counts of agents, skills, and commands in AGENTS.md and README.md with the actual repository state.
 
 **Frequency**: ~3 times per month
 
 **Steps**:
-1. Create or modify SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
+1. Update agent, skill, and command counts in AGENTS.md
-2. Update manifests/install-modules.json and/or manifests/install-components.json to register the skill
+2. Update the same counts in README.md (quick-start, comparison table, etc.)
-3. Update AGENTS.md, README.md, and docs/zh-CN/AGENTS.md for documentation and agent tables
+3. Optionally update other documentation files
-4. Optionally add or update reference files or assets under the skill directory
+
+**Files typically involved**:
+- `AGENTS.md`
+- `README.md`
+
+**Example commit sequence**:
+```
+Update agent, skill, and command counts in AGENTS.md
+Update the same counts in README.md (quick-start, comparison table, etc.)
+Optionally update other documentation files
+```
+
+### Add Cross Harness Skill Copies
+
+Adds skill copies for different agent harnesses (e.g., Codex, Cursor, Antigravity) to ensure compatibility across platforms.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md
+2. Optionally add harness-specific openai.yaml or config files
+3. Address review feedback to align with CONTRIBUTING template
 
 **Files typically involved**:
-- `skills/*/SKILL.md`
 - `.agents/skills/*/SKILL.md`
-- `manifests/install-modules.json`
+- `.cursor/skills/*/SKILL.md`
-- `manifests/install-components.json`
+- `.agents/skills/*/agents/openai.yaml`
-- `AGENTS.md`
-- `README.md`
-- `docs/zh-CN/AGENTS.md`
 
 **Example commit sequence**:
 ```
-Create or modify SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
+Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md
-Update manifests/install-modules.json and/or manifests/install-components.json to register the skill
+Optionally add harness-specific openai.yaml or config files
-Update AGENTS.md, README.md, and docs/zh-CN/AGENTS.md for documentation and agent tables
+Address review feedback to align with CONTRIBUTING template
-Optionally add or update reference files or assets under the skill directory
 ```
 
-### Add Or Update Command
+### Add Or Update Hook
 
-Adds or updates a workflow command for the Claude agentic system.
+Adds or updates git or bash hooks to enforce workflow, quality, or security policies.
 
-**Frequency**: ~2 times per month
+**Frequency**: ~1 times per month
 
 **Steps**:
-1. Create or modify a markdown file in commands/ or .claude/commands/
+1. Add or update hook scripts in hooks/ or scripts/hooks/
-2. Document the workflow, arguments, and usage
+2. Register the hook in hooks/hooks.json or similar config
-3. Optionally update related documentation (README.md, AGENTS.md, etc.)
+3. Optionally add or update tests in tests/hooks/
-
-**Files typically involved**:
-- `commands/*.md`
-- `.claude/commands/*.md`
-
-**Example commit sequence**:
-```
-Create or modify a markdown file in commands/ or .claude/commands/
-Document the workflow, arguments, and usage
-Optionally update related documentation (README.md, AGENTS.md, etc.)
-```
-
-### Refactor Skill Or Agent Logic
-
-Refactors core logic or merges/splits skills, updating documentation and manifests accordingly.
-
-**Frequency**: ~2 times per month
-
-**Steps**:
-1. Edit or move SKILL.md files in skills/ or .agents/skills/
-2. Update manifests/install-modules.json and/or manifests/install-components.json
-3. Update documentation files (AGENTS.md, README.md, docs/zh-CN/AGENTS.md, etc.)
-
-**Files typically involved**:
-- `skills/*/SKILL.md`
-- `.agents/skills/*/SKILL.md`
-- `manifests/install-modules.json`
-- `manifests/install-components.json`
-- `AGENTS.md`
-- `README.md`
-- `docs/zh-CN/AGENTS.md`
-
-**Example commit sequence**:
-```
-Edit or move SKILL.md files in skills/ or .agents/skills/
-Update manifests/install-modules.json and/or manifests/install-components.json
-Update documentation files (AGENTS.md, README.md, docs/zh-CN/AGENTS.md, etc.)
-```
-
-### Add Or Update Install Target
-
-Adds or updates an install target (e.g., Gemini, CodeBuddy) including scripts, schemas, and registration.
-
-**Frequency**: ~2 times per month
-
-**Steps**:
-1. Add new directory and scripts under .<target>/ (e.g., .gemini/, .codebuddy/)
-2. Update manifests/install-modules.json and schemas/ecc-install-config.schema.json
-3. Add or update scripts/lib/install-targets/<target>-project.js and registry.js
-4. Update or add tests for install targets
-
-**Files typically involved**:
-- `.<target>/*`
-- `manifests/install-modules.json`
-- `schemas/ecc-install-config.schema.json`
-- `schemas/install-modules.schema.json`
-- `scripts/lib/install-manifests.js`
-- `scripts/lib/install-targets/<target>-project.js`
-- `scripts/lib/install-targets/registry.js`
-- `tests/lib/install-targets.test.js`
-
-**Example commit sequence**:
-```
-Add new directory and scripts under .<target>/ (e.g., .gemini/, .codebuddy/)
-Update manifests/install-modules.json and schemas/ecc-install-config.schema.json
-Add or update scripts/lib/install-targets/<target>-project.js and registry.js
-Update or add tests for install targets
-```
-
-### Documentation Sync And Update
-
-Synchronizes and updates documentation across multiple files and languages.
-
-**Frequency**: ~3 times per month
-
-**Steps**:
-1. Edit AGENTS.md, README.md, README.zh-CN.md, WORKING-CONTEXT.md
-2. Edit docs/zh-CN/AGENTS.md, docs/zh-CN/README.md
-3. Optionally update .agents/skills/*/SKILL.md and related documentation
-
-**Files typically involved**:
-- `AGENTS.md`
-- `README.md`
-- `README.zh-CN.md`
-- `WORKING-CONTEXT.md`
-- `docs/zh-CN/AGENTS.md`
-- `docs/zh-CN/README.md`
-
-**Example commit sequence**:
-```
-Edit AGENTS.md, README.md, README.zh-CN.md, WORKING-CONTEXT.md
-Edit docs/zh-CN/AGENTS.md, docs/zh-CN/README.md
-Optionally update .agents/skills/*/SKILL.md and related documentation
-```
-
-### Update Or Add Hooks And Ci
-
-Updates or adds new hooks, CI scripts, and related tests for code quality and automation.
-
-**Frequency**: ~2 times per month
-
-**Steps**:
-1. Edit hooks/hooks.json and/or scripts/hooks/*.js
-2. Update or add tests in tests/hooks/*.test.js or tests/scripts/*.test.js
-3. Update CI workflow files in .github/workflows/
 
 **Files typically involved**:
+- `hooks/*.hook`
 - `hooks/hooks.json`
 - `scripts/hooks/*.js`
 - `tests/hooks/*.test.js`
-- `tests/scripts/*.test.js`
+- `.cursor/hooks.json`
-- `.github/workflows/*.yml`
 
 **Example commit sequence**:
 ```
-Edit hooks/hooks.json and/or scripts/hooks/*.js
+Add or update hook scripts in hooks/ or scripts/hooks/
-Update or add tests in tests/hooks/*.test.js or tests/scripts/*.test.js
+Register the hook in hooks/hooks.json or similar config
-Update CI workflow files in .github/workflows/
+Optionally add or update tests in tests/hooks/
+```
+
+### Address Review Feedback
+
+Addresses code review feedback by updating documentation, scripts, or configuration for clarity, correctness, or convention alignment.
+
+**Frequency**: ~4 times per month
+
+**Steps**:
+1. Edit SKILL.md, agent, or command files to address reviewer comments
+2. Update examples, headings, or configuration as requested
+3. Iterate until all review feedback is resolved
+
+**Files typically involved**:
+- `skills/*/SKILL.md`
+- `agents/*.md`
+- `commands/*.md`
+- `.agents/skills/*/SKILL.md`
+- `.cursor/skills/*/SKILL.md`
+
+**Example commit sequence**:
+```
+Edit SKILL.md, agent, or command files to address reviewer comments
+Update examples, headings, or configuration as requested
+Iterate until all review feedback is resolved
 ```
 
 

.agents/skills/investor-outreach/SKILL.md

@@ -24,6 +24,11 @@ Write investor communication that is short, concrete, and easy to act on.
 4. Stay concise.
 5. Never send copy that could go to any investor.
 
+## Voice Handling
+
+If the user's voice matters, run `brand-voice` first and reuse its `VOICE PROFILE`.
+This skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system.
+
 ## Hard Bans
 
 Delete and rewrite any of these:
@@ -31,7 +36,6 @@ Delete and rewrite any of these:
 - "excited to share"
 - generic thesis praise without a real tie-in
 - vague founder adjectives
-- "no fluff"
 - begging language
 - soft closing questions when a direct ask is clearer
 

.claude/commands/add-or-update-skill.md

@@ -1,41 +0,0 @@
----
-name: add-or-update-skill
-description: Workflow command scaffold for add-or-update-skill in everything-claude-code.
-allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
----
-
-# /add-or-update-skill
-
-Use this workflow when working on **add-or-update-skill** in `everything-claude-code`.
-
-## Goal
-
-Adds a new skill or updates an existing skill, including documentation and registration in manifests.
-
-## Common Files
-
-- `skills/*/SKILL.md`
-- `.agents/skills/*/SKILL.md`
-- `manifests/install-modules.json`
-- `manifests/install-components.json`
-- `AGENTS.md`
-- `README.md`
-
-## Suggested Sequence
-
-1. Understand the current state and failure mode before editing.
-2. Make the smallest coherent change that satisfies the workflow goal.
-3. Run the most relevant verification for touched files.
-4. Summarize what changed and what still needs review.
-
-## Typical Commit Signals
-
-- Create or modify SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
-- Update manifests/install-modules.json and/or manifests/install-components.json to register the skill
-- Update AGENTS.md, README.md, and docs/zh-CN/AGENTS.md for documentation and agent tables
-- Optionally add or update reference files or assets under the skill directory
-
-## Notes
-
-- Treat this as a scaffold, not a hard-coded script.
-- Update the command if the workflow evolves materially.

.claude/commands/feature-development.md

@@ -14,9 +14,8 @@ Standard feature implementation workflow
 
 ## Common Files
 
-- `.opencode/*`
+- `manifests/*`
-- `.opencode/plugins/*`
+- `schemas/*`
-- `.opencode/plugins/lib/*`
 - `**/*.test.*`
 - `**/api/**`
 

.claude/commands/refactoring.md

@@ -1,35 +0,0 @@
----
-name: refactoring
-description: Workflow command scaffold for refactoring in everything-claude-code.
-allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
----
-
-# /refactoring
-
-Use this workflow when working on **refactoring** in `everything-claude-code`.
-
-## Goal
-
-Code refactoring and cleanup workflow
-
-## Common Files
-
-- `src/**/*`
-
-## Suggested Sequence
-
-1. Understand the current state and failure mode before editing.
-2. Make the smallest coherent change that satisfies the workflow goal.
-3. Run the most relevant verification for touched files.
-4. Summarize what changed and what still needs review.
-
-## Typical Commit Signals
-
-- Ensure tests pass before refactor
-- Refactor code structure
-- Verify tests still pass
-
-## Notes
-
-- Treat this as a scaffold, not a hard-coded script.
-- Update the command if the workflow evolves materially.

.claude/ecc-tools.json

@@ -2,7 +2,7 @@
   "version": "1.3",
   "schemaVersion": "1.0",
   "generatedBy": "ecc-tools",
-  "generatedAt": "2026-04-02T17:50:22.851Z",
+  "generatedAt": "2026-03-20T12:07:36.496Z",
   "repo": "https://github.com/affaan-m/everything-claude-code",
   "profiles": {
     "requested": "full",
@@ -148,9 +148,9 @@
     ".claude/research/everything-claude-code-research-playbook.md",
     ".claude/team/everything-claude-code-team-config.json",
     ".claude/enterprise/controls.md",
+    ".claude/commands/database-migration.md",
     ".claude/commands/feature-development.md",
-    ".claude/commands/refactoring.md",
+    ".claude/commands/add-language-rules.md"
-    ".claude/commands/add-or-update-skill.md"
   ],
   "packageFiles": {
     "runtime-core": [
@@ -178,9 +178,9 @@
       ".claude/enterprise/controls.md"
     ],
     "workflow-pack": [
+      ".claude/commands/database-migration.md",
       ".claude/commands/feature-development.md",
-      ".claude/commands/refactoring.md",
+      ".claude/commands/add-language-rules.md"
-      ".claude/commands/add-or-update-skill.md"
     ]
   },
   "moduleFiles": {
@@ -209,9 +209,9 @@
       ".claude/enterprise/controls.md"
     ],
     "workflow-pack": [
+      ".claude/commands/database-migration.md",
       ".claude/commands/feature-development.md",
-      ".claude/commands/refactoring.md",
+      ".claude/commands/add-language-rules.md"
-      ".claude/commands/add-or-update-skill.md"
     ]
   },
   "files": [
@@ -285,6 +285,11 @@
       "path": ".claude/enterprise/controls.md",
       "description": "Enterprise governance scaffold for approvals, audit posture, and escalation."
     },
+    {
+      "moduleId": "workflow-pack",
+      "path": ".claude/commands/database-migration.md",
+      "description": "Workflow command scaffold for database-migration."
+    },
     {
       "moduleId": "workflow-pack",
       "path": ".claude/commands/feature-development.md",
@@ -292,27 +297,22 @@
     },
     {
       "moduleId": "workflow-pack",
-      "path": ".claude/commands/refactoring.md",
+      "path": ".claude/commands/add-language-rules.md",
-      "description": "Workflow command scaffold for refactoring."
+      "description": "Workflow command scaffold for add-language-rules."
-    },
-    {
-      "moduleId": "workflow-pack",
-      "path": ".claude/commands/add-or-update-skill.md",
-      "description": "Workflow command scaffold for add-or-update-skill."
     }
   ],
   "workflows": [
+    {
+      "command": "database-migration",
+      "path": ".claude/commands/database-migration.md"
+    },
     {
       "command": "feature-development",
       "path": ".claude/commands/feature-development.md"
     },
     {
-      "command": "refactoring",
+      "command": "add-language-rules",
-      "path": ".claude/commands/refactoring.md"
+      "path": ".claude/commands/add-language-rules.md"
-    },
-    {
-      "command": "add-or-update-skill",
-      "path": ".claude/commands/add-or-update-skill.md"
     }
   ],
   "adapters": {
@@ -320,9 +320,9 @@
       "skillPath": ".claude/skills/everything-claude-code/SKILL.md",
       "identityPath": ".claude/identity.json",
       "commandPaths": [
+        ".claude/commands/database-migration.md",
         ".claude/commands/feature-development.md",
-        ".claude/commands/refactoring.md",
+        ".claude/commands/add-language-rules.md"
-        ".claude/commands/add-or-update-skill.md"
       ]
     },
     "codex": {

.claude/identity.json

@@ -10,5 +10,5 @@
     "javascript"
   ],
   "suggestedBy": "ecc-tools-repo-analysis",
-  "createdAt": "2026-04-02T18:07:47.335Z"
+  "createdAt": "2026-03-20T12:07:57.119Z"
 }

.claude/research/everything-claude-code-research-playbook.md

@@ -18,4 +18,4 @@ Use this when the task is documentation-heavy, source-sensitive, or requires bro
 
 - Primary language: JavaScript
 - Framework: Not detected
-- Workflows detected: 8
+- Workflows detected: 10

.claude/rules/everything-claude-code-guardrails.md

@@ -4,7 +4,7 @@ Generated by ECC Tools from repository history. Review before treating it as a h
 
 ## Commit Workflow
 
-- Prefer `conventional` commit messaging with prefixes such as fix, feat, docs, chore.
+- Prefer `conventional` commit messaging with prefixes such as fix, test, feat, docs.
 - Keep new changes aligned with the existing pull-request and review flow already present in the repo.
 
 ## Architecture
@@ -24,9 +24,9 @@ Generated by ECC Tools from repository history. Review before treating it as a h
 
 ## Detected Workflows
 
+- database-migration: Database schema changes with migration files
 - feature-development: Standard feature implementation workflow
-- refactoring: Code refactoring and cleanup workflow
+- add-language-rules: Adds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines.
-- add-or-update-skill: Adds a new skill or updates an existing skill, including documentation and registration in manifests.
 
 ## Review Reminder
 

.claude/skills/everything-claude-code/SKILL.md

@@ -5,7 +5,7 @@ description: Development conventions and patterns for everything-claude-code. Ja
 
 # Everything Claude Code Conventions
 
-> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-04-02
+> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-03-20
 
 ## Overview
 
@@ -34,13 +34,13 @@ Follow these commit message conventions based on 500 analyzed commits.
 ### Prefixes Used
 
 - `fix`
+- `test`
 - `feat`
 - `docs`
-- `chore`
 
 ### Message Guidelines
 
-- Average message length: ~57 characters
+- Average message length: ~65 characters
 - Keep first line concise and descriptive
 - Use imperative mood ("Add feature" not "Added feature")
 
@@ -48,49 +48,49 @@ Follow these commit message conventions based on 500 analyzed commits.
 *Commit message example*
 
 ```text
-feat: add everything-claude-code ECC bundle (.claude/commands/add-or-update-skill.md)
+feat(rules): add C# language support
 ```
 
 *Commit message example*
 
 ```text
-refactor: extract social graph ranking core
+chore(deps-dev): bump flatted (#675)
 ```
 
 *Commit message example*
 
 ```text
-fix: port safe ci cleanup from backlog
+fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691)
 ```
 
 *Commit message example*
 
 ```text
-docs: close bundle drift and sync plugin guidance
+docs: add Antigravity setup and usage guide (#552)
 ```
 
 *Commit message example*
 
 ```text
-chore: ignore local orchestration artifacts
+merge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer
 ```
 
 *Commit message example*
 
 ```text
-feat: add everything-claude-code ECC bundle (.claude/commands/refactoring.md)
+Revert "Add Kiro IDE support (.kiro/) (#548)"
 ```
 
 *Commit message example*
 
 ```text
-feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
+Add Kiro IDE support (.kiro/) (#548)
 ```
 
 *Commit message example*
 
 ```text
-feat: add everything-claude-code ECC bundle (.claude/enterprise/controls.md)
+feat: add block-no-verify hook for Claude Code and Cursor (#649)
 ```
 
 ## Architecture
@@ -184,11 +184,33 @@ try {
 
 These workflows were detected from analyzing commit patterns.
 
+### Database Migration
+
+Database schema changes with migration files
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create migration file
+2. Update schema definitions
+3. Generate/update types
+
+**Files typically involved**:
+- `**/schema.*`
+- `migrations/*`
+
+**Example commit sequence**:
+```
+feat: implement --with/--without selective install flags (#679)
+fix: sync catalog counts with filesystem (27 agents, 113 skills, 58 commands) (#693)
+feat(rules): add Rust language rules (rebased #660) (#686)
+```
+
 ### Feature Development
 
 Standard feature implementation workflow
 
-**Frequency**: ~19 times per month
+**Frequency**: ~22 times per month
 
 **Steps**:
 1. Add feature implementation
@@ -196,197 +218,205 @@ Standard feature implementation workflow
 3. Update documentation
 
 **Files typically involved**:
-- `.opencode/*`
+- `manifests/*`
-- `.opencode/plugins/*`
+- `schemas/*`
-- `.opencode/plugins/lib/*`
 - `**/*.test.*`
 - `**/api/**`
 
 **Example commit sequence**:
 ```
-feat(install): add CodeBuddy(Tencent) adaptation with installation scripts (#1038)
+feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer
-chore(deps-dev): bump c8 from 10.1.3 to 11.0.0 (#1065)
+docs(skills): align documentation-lookup with CONTRIBUTING template; add cross-harness (Codex/Cursor) skill copies
-chore(deps): bump actions/checkout from 4.3.1 to 6.0.2 (#1060)
+fix: address PR review — skill template (When to use, How it works, Examples), bun.lock, next build note, rust-reviewer CI note, doc-lookup privacy/uncertainty
 ```
 
-### Refactoring
+### Add Language Rules
 
-Code refactoring and cleanup workflow
+Adds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create a new directory under rules/{language}/
+2. Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content
+3. Optionally reference or link to related skills
+
+**Files typically involved**:
+- `rules/*/coding-style.md`
+- `rules/*/hooks.md`
+- `rules/*/patterns.md`
+- `rules/*/security.md`
+- `rules/*/testing.md`
+
+**Example commit sequence**:
+```
+Create a new directory under rules/{language}/
+Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content
+Optionally reference or link to related skills
+```
+
+### Add New Skill
+
+Adds a new skill to the system, documenting its workflow, triggers, and usage, often with supporting scripts.
 
 **Frequency**: ~4 times per month
 
 **Steps**:
-1. Ensure tests pass before refactor
+1. Create a new directory under skills/{skill-name}/
-2. Refactor code structure
+2. Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.)
-3. Verify tests still pass
+3. Optionally add scripts or supporting files under skills/{skill-name}/scripts/
-
+4. Address review feedback and iterate on documentation
-**Files typically involved**:
-- `src/**/*`
-
-**Example commit sequence**:
-```
-refactor: collapse legacy command bodies into skills
-feat: add connected operator workflow skills
-feat: expand lead intelligence outreach channels
-```
-
-### Add Or Update Skill
-
-Adds a new skill or updates an existing skill, including documentation and registration in manifests.
-
-**Frequency**: ~3 times per month
-
-**Steps**:
-1. Create or modify SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
-2. Update manifests/install-modules.json and/or manifests/install-components.json to register the skill
-3. Update AGENTS.md, README.md, and docs/zh-CN/AGENTS.md for documentation and agent tables
-4. Optionally add or update reference files or assets under the skill directory
 
 **Files typically involved**:
 - `skills/*/SKILL.md`
-- `.agents/skills/*/SKILL.md`
+- `skills/*/scripts/*.sh`
-- `manifests/install-modules.json`
+- `skills/*/scripts/*.js`
-- `manifests/install-components.json`
-- `AGENTS.md`
-- `README.md`
-- `docs/zh-CN/AGENTS.md`
 
 **Example commit sequence**:
 ```
-Create or modify SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
+Create a new directory under skills/{skill-name}/
-Update manifests/install-modules.json and/or manifests/install-components.json to register the skill
+Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.)
-Update AGENTS.md, README.md, and docs/zh-CN/AGENTS.md for documentation and agent tables
+Optionally add scripts or supporting files under skills/{skill-name}/scripts/
-Optionally add or update reference files or assets under the skill directory
+Address review feedback and iterate on documentation
 ```
 
-### Add Or Update Command
+### Add New Agent
 
-Adds or updates a workflow command for the Claude agentic system.
+Adds a new agent to the system for code review, build resolution, or other automated tasks.
 
 **Frequency**: ~2 times per month
 
 **Steps**:
-1. Create or modify a markdown file in commands/ or .claude/commands/
+1. Create a new agent markdown file under agents/{agent-name}.md
-2. Document the workflow, arguments, and usage
+2. Register the agent in AGENTS.md
-3. Optionally update related documentation (README.md, AGENTS.md, etc.)
+3. Optionally update README.md and docs/COMMAND-AGENT-MAP.md
+
+**Files typically involved**:
+- `agents/*.md`
+- `AGENTS.md`
+- `README.md`
+- `docs/COMMAND-AGENT-MAP.md`
+
+**Example commit sequence**:
+```
+Create a new agent markdown file under agents/{agent-name}.md
+Register the agent in AGENTS.md
+Optionally update README.md and docs/COMMAND-AGENT-MAP.md
+```
+
+### Add New Command
+
+Adds a new command to the system, often paired with a backing skill.
+
+**Frequency**: ~1 times per month
+
+**Steps**:
+1. Create a new markdown file under commands/{command-name}.md
+2. Optionally add or update a backing skill under skills/{skill-name}/SKILL.md
 
 **Files typically involved**:
 - `commands/*.md`
-- `.claude/commands/*.md`
-
-**Example commit sequence**:
-```
-Create or modify a markdown file in commands/ or .claude/commands/
-Document the workflow, arguments, and usage
-Optionally update related documentation (README.md, AGENTS.md, etc.)
-```
-
-### Refactor Skill Or Agent Logic
-
-Refactors core logic or merges/splits skills, updating documentation and manifests accordingly.
-
-**Frequency**: ~2 times per month
-
-**Steps**:
-1. Edit or move SKILL.md files in skills/ or .agents/skills/
-2. Update manifests/install-modules.json and/or manifests/install-components.json
-3. Update documentation files (AGENTS.md, README.md, docs/zh-CN/AGENTS.md, etc.)
-
-**Files typically involved**:
 - `skills/*/SKILL.md`
-- `.agents/skills/*/SKILL.md`
-- `manifests/install-modules.json`
-- `manifests/install-components.json`
-- `AGENTS.md`
-- `README.md`
-- `docs/zh-CN/AGENTS.md`
 
 **Example commit sequence**:
 ```
-Edit or move SKILL.md files in skills/ or .agents/skills/
+Create a new markdown file under commands/{command-name}.md
-Update manifests/install-modules.json and/or manifests/install-components.json
+Optionally add or update a backing skill under skills/{skill-name}/SKILL.md
-Update documentation files (AGENTS.md, README.md, docs/zh-CN/AGENTS.md, etc.)
 ```
 
-### Add Or Update Install Target
+### Sync Catalog Counts
 
-Adds or updates an install target (e.g., Gemini, CodeBuddy) including scripts, schemas, and registration.
+Synchronizes the documented counts of agents, skills, and commands in AGENTS.md and README.md with the actual repository state.
-
-**Frequency**: ~2 times per month
-
-**Steps**:
-1. Add new directory and scripts under .<target>/ (e.g., .gemini/, .codebuddy/)
-2. Update manifests/install-modules.json and schemas/ecc-install-config.schema.json
-3. Add or update scripts/lib/install-targets/<target>-project.js and registry.js
-4. Update or add tests for install targets
-
-**Files typically involved**:
-- `.<target>/*`
-- `manifests/install-modules.json`
-- `schemas/ecc-install-config.schema.json`
-- `schemas/install-modules.schema.json`
-- `scripts/lib/install-manifests.js`
-- `scripts/lib/install-targets/<target>-project.js`
-- `scripts/lib/install-targets/registry.js`
-- `tests/lib/install-targets.test.js`
-
-**Example commit sequence**:
-```
-Add new directory and scripts under .<target>/ (e.g., .gemini/, .codebuddy/)
-Update manifests/install-modules.json and schemas/ecc-install-config.schema.json
-Add or update scripts/lib/install-targets/<target>-project.js and registry.js
-Update or add tests for install targets
-```
-
-### Documentation Sync And Update
-
-Synchronizes and updates documentation across multiple files and languages.
 
 **Frequency**: ~3 times per month
 
 **Steps**:
-1. Edit AGENTS.md, README.md, README.zh-CN.md, WORKING-CONTEXT.md
+1. Update agent, skill, and command counts in AGENTS.md
-2. Edit docs/zh-CN/AGENTS.md, docs/zh-CN/README.md
+2. Update the same counts in README.md (quick-start, comparison table, etc.)
-3. Optionally update .agents/skills/*/SKILL.md and related documentation
+3. Optionally update other documentation files
 
 **Files typically involved**:
 - `AGENTS.md`
 - `README.md`
-- `README.zh-CN.md`
-- `WORKING-CONTEXT.md`
-- `docs/zh-CN/AGENTS.md`
-- `docs/zh-CN/README.md`
 
 **Example commit sequence**:
 ```
-Edit AGENTS.md, README.md, README.zh-CN.md, WORKING-CONTEXT.md
+Update agent, skill, and command counts in AGENTS.md
-Edit docs/zh-CN/AGENTS.md, docs/zh-CN/README.md
+Update the same counts in README.md (quick-start, comparison table, etc.)
-Optionally update .agents/skills/*/SKILL.md and related documentation
+Optionally update other documentation files
 ```
 
-### Update Or Add Hooks And Ci
+### Add Cross Harness Skill Copies
 
-Updates or adds new hooks, CI scripts, and related tests for code quality and automation.
+Adds skill copies for different agent harnesses (e.g., Codex, Cursor, Antigravity) to ensure compatibility across platforms.
 
 **Frequency**: ~2 times per month
 
 **Steps**:
-1. Edit hooks/hooks.json and/or scripts/hooks/*.js
+1. Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md
-2. Update or add tests in tests/hooks/*.test.js or tests/scripts/*.test.js
+2. Optionally add harness-specific openai.yaml or config files
-3. Update CI workflow files in .github/workflows/
+3. Address review feedback to align with CONTRIBUTING template
 
 **Files typically involved**:
-- `hooks/hooks.json`
+- `.agents/skills/*/SKILL.md`
-- `scripts/hooks/*.js`
+- `.cursor/skills/*/SKILL.md`
-- `tests/hooks/*.test.js`
+- `.agents/skills/*/agents/openai.yaml`
-- `tests/scripts/*.test.js`
-- `.github/workflows/*.yml`
 
 **Example commit sequence**:
 ```
-Edit hooks/hooks.json and/or scripts/hooks/*.js
+Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md
-Update or add tests in tests/hooks/*.test.js or tests/scripts/*.test.js
+Optionally add harness-specific openai.yaml or config files
-Update CI workflow files in .github/workflows/
+Address review feedback to align with CONTRIBUTING template
+```
+
+### Add Or Update Hook
+
+Adds or updates git or bash hooks to enforce workflow, quality, or security policies.
+
+**Frequency**: ~1 times per month
+
+**Steps**:
+1. Add or update hook scripts in hooks/ or scripts/hooks/
+2. Register the hook in hooks/hooks.json or similar config
+3. Optionally add or update tests in tests/hooks/
+
+**Files typically involved**:
+- `hooks/*.hook`
+- `hooks/hooks.json`
+- `scripts/hooks/*.js`
+- `tests/hooks/*.test.js`
+- `.cursor/hooks.json`
+
+**Example commit sequence**:
+```
+Add or update hook scripts in hooks/ or scripts/hooks/
+Register the hook in hooks/hooks.json or similar config
+Optionally add or update tests in tests/hooks/
+```
+
+### Address Review Feedback
+
+Addresses code review feedback by updating documentation, scripts, or configuration for clarity, correctness, or convention alignment.
+
+**Frequency**: ~4 times per month
+
+**Steps**:
+1. Edit SKILL.md, agent, or command files to address reviewer comments
+2. Update examples, headings, or configuration as requested
+3. Iterate until all review feedback is resolved
+
+**Files typically involved**:
+- `skills/*/SKILL.md`
+- `agents/*.md`
+- `commands/*.md`
+- `.agents/skills/*/SKILL.md`
+- `.cursor/skills/*/SKILL.md`
+
+**Example commit sequence**:
+```
+Edit SKILL.md, agent, or command files to address reviewer comments
+Update examples, headings, or configuration as requested
+Iterate until all review feedback is resolved
 ```
 
 

.claude/team/everything-claude-code-team-config.json

@@ -7,9 +7,9 @@
     ".agents/skills/everything-claude-code/SKILL.md"
   ],
   "commandFiles": [
+    ".claude/commands/database-migration.md",
     ".claude/commands/feature-development.md",
-    ".claude/commands/refactoring.md",
+    ".claude/commands/add-language-rules.md"
-    ".claude/commands/add-or-update-skill.md"
   ],
-  "updatedAt": "2026-04-02T17:50:22.851Z"
+  "updatedAt": "2026-03-20T12:07:36.496Z"
 }

WORKING-CONTEXT.md

@@ -111,3 +111,4 @@ Keep this file detailed for only the current sprint, blockers, and next actions.
 - 2026-04-01: Added `connections-optimizer` as the review-first social-graph reorganization workflow for X and LinkedIn, with explicit pruning modes, browser fallback expectations, and Apple Mail drafting guidance.
 - 2026-04-01: Added `manim-video` as the reusable technical explainer lane and seeded it with a starter network-graph scene so launch and systems animations do not depend on one-off scratch scripts.
 - 2026-04-02: Re-extracted `social-graph-ranker` as a standalone primitive because the weighted bridge-decay model is reusable outside the full lead workflow. `lead-intelligence` now points to it for canonical graph ranking instead of carrying the full algorithm explanation inline, while `connections-optimizer` stays the broader operator layer for pruning, adds, and outbound review packs.
+- 2026-04-02: Applied the same consolidation rule to the writing lane. `brand-voice` remains the canonical voice system, while `content-engine`, `crosspost`, `article-writing`, and `investor-outreach` now keep only workflow-specific guidance instead of duplicating a second Affaan/ECC voice model or repeating the full ban list in multiple places.

skills/article-writing/SKILL.md

@@ -23,50 +23,23 @@ Write long-form content that sounds like an actual person with a point of view,
 4. Use proof instead of adjectives.
 5. Never invent facts, credibility, or customer evidence.
 
-## Voice Capture Workflow
+## Voice Handling
 
-If the user wants a specific voice, collect one or more of:
+If the user wants a specific voice, run `brand-voice` first and reuse its `VOICE PROFILE`.
-- published articles
+Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.
-- newsletters
-- X posts or threads
-- docs or memos
-- launch notes
-- a style guide
-
-Then extract:
-- sentence length and rhythm
-- whether the writing is compressed, explanatory, sharp, or formal
-- how parentheses are used
-- how often the writer asks questions
-- whether the writer uses fragments, lists, or hard pivots
-- formatting habits such as headers, bullets, code blocks, pull quotes
-- what the writer clearly avoids
 
 If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.
 
-## Affaan / ECC Voice Reference
-
-When matching Affaan / ECC voice, bias toward:
-- direct claims over scene-setting
-- high specificity
-- parentheticals used for qualification or over-clarification, not comedy
-- capitalization chosen situationally, not as a gimmick
-- very low tolerance for fake thought-leadership cadence
-- almost no bait questions
-
 ## Banned Patterns
 
 Delete and rewrite any of these:
 - "In today's rapidly evolving landscape"
 - "game-changer", "cutting-edge", "revolutionary"
-- "no fluff"
-- "not X, just Y"
 - "here's why this matters" as a standalone bridge
 - fake vulnerability arcs
 - a closing question added only to juice engagement
-- forced lowercase
-- corny parenthetical asides
 - biography padding that does not move the argument
+- generic AI throat-clearing that delays the point
 
 ## Writing Process
 
@@ -101,6 +74,6 @@ Delete and rewrite any of these:
 Before delivering:
 - factual claims are backed by provided sources
 - generic AI transitions are gone
-- the voice matches the supplied examples
+- the voice matches the supplied examples or the agreed `VOICE PROFILE`
 - every section adds something new
 - formatting matches the intended medium

skills/content-engine/SKILL.md

@@ -38,50 +38,28 @@ Before drafting, identify the source set:
 If the user wants a specific voice, build a voice profile from real examples before writing.
 Use `brand-voice` as the canonical workflow when voice consistency matters across more than one output.
 
-## Voice Capture Workflow
+## Voice Handling
 
-Run `brand-voice` first when:
+`brand-voice` is the canonical voice layer.
+
+Run it first when:
 
 - there are multiple downstream outputs
 - the user explicitly cares about writing style
 - the content is launch, outreach, or reputation-sensitive
 
-At minimum, produce a compact `VOICE PROFILE` covering:
+Reuse the resulting `VOICE PROFILE` here instead of rebuilding a second voice model.
-- rhythm
+If the user wants Affaan / ECC voice specifically, still treat `brand-voice` as the source of truth and feed it the best live or source-derived material available.
-- compression
-- capitalization
-- parenthetical use
-- question use
-- preferred moves
-- banned moves
-
-Do not start drafting until the voice profile is clear enough to enforce.
-
-## Affaan / ECC Voice Reference
-
-When the user wants Affaan / ECC voice specifically, default to this unless newer examples clearly override it:
-- direct, compressed, concrete
-- strong preference for specific claims, numbers, mechanisms, and receipts
-- parentheticals used to qualify, narrow, or over-clarify, not to do corny bits
-- lowercase is optional, not mandatory
-- questions are rare and should not be added as bait
-- transitions should feel earned, not polished
-- tone can be sharp or blunt, but should not sound like a content marketer
 
 ## Hard Bans
 
 Delete and rewrite any of these:
 - "In today's rapidly evolving landscape"
 - "game-changer", "revolutionary", "cutting-edge"
-- "no fluff"
-- "not X, just Y"
 - "here's why this matters" unless it is followed immediately by something concrete
-- "Excited to share"
-- fake curiosity gaps
 - ending with a LinkedIn-style question just to farm replies
-- forced lowercase when the source voice does not call for it
 - forced casualness on LinkedIn
-- parenthetical jokes that were not present in the source voice
+- fake engagement padding that was not present in the source material
 
 ## Platform Adaptation Rules
 

skills/crosspost/SKILL.md

@@ -39,13 +39,8 @@ Use `content-engine` first if the source still needs voice shaping.
 
 Run `brand-voice` first if the source voice is not already captured in the current session.
 
-Before adapting, note:
+Reuse the resulting `VOICE PROFILE` directly.
-- how blunt or explanatory the source is
+Do not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.
-- whether the source uses fragments, lists, or longer transitions
-- whether the source uses parentheses
-- whether the source avoids questions, hashtags, or CTA language
-
-The adaptation should preserve that fingerprint.
 
 ### Step 3: Adapt by Platform Constraint
 
@@ -91,7 +86,6 @@ Delete and rewrite any of these:
 - "Here's what I learned"
 - "What do you think?"
 - "link in bio" unless that is literally true
-- "not X, just Y"
 - generic "professional takeaway" paragraphs that were not in the source
 
 ## Output Format

skills/investor-outreach/SKILL.md

@@ -24,6 +24,11 @@ Write investor communication that is short, concrete, and easy to act on.
 4. Stay concise.
 5. Never send copy that could go to any investor.
 
+## Voice Handling
+
+If the user's voice matters, run `brand-voice` first and reuse its `VOICE PROFILE`.
+This skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system.
+
 ## Hard Bans
 
 Delete and rewrite any of these:
@@ -31,7 +36,6 @@ Delete and rewrite any of these:
 - "excited to share"
 - generic thesis praise without a real tie-in
 - vague founder adjectives
-- "no fluff"
 - begging language
 - soft closing questions when a direct ask is clearer