Normalize drafts to the project's explicit writing style and formatting rules at docs/instructions/rules/writing-style.md. Use as the last pass before publish.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Eliyce/paqad-ai --skill style-enforcer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Style Enforcer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/eliyce-style-enforcer)More formats (shields.io, HTML) on the badges page.
---
name: style-enforcer
description: Normalize drafts to the project's explicit writing style and formatting rules at docs/instructions/rules/writing-style.md. Use as the last pass before publish.
---
# Style Enforcer
## What It Does
Applies the project's writing-style rules (and only those rules) to a draft so style is enforced consistently rather than guessed each time.
## Use This When
Use this as the final pass before publish, after `content-reviewer` and (when applicable) `seo-optimizer` have run.
## Inputs
- The draft.
- `docs/instructions/rules/writing-style.md` (the source of truth — never override with general rules).
- `assets/default-rules.txt` only when the project has no writing-style file.
## Procedure
1. Run `scripts/check-style.sh <draft>` — flags violations of the style file (e.g. forbidden phrases, required cases, Oxford-comma policy).
2. For each flagged line, apply the project rule, never a generic preference.
3. Format the change list per `assets/output.template.md`.
## Output Contract
- Match `assets/output.template.md`: `## Style Edits` (one bullet per change with line number and rule citation).
## Resources
- `references/style-source.md`
- `scripts/check-style.sh`
- `assets/output.template.md`
- `assets/default-rules.txt`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
