Anti Patterns
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Install
npx skills add jeremybrasher/grokbot-skills --skill anti-patternsgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/anti-patterns ~/.claude/skills/anti-patternsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# SDLC anti-patterns to reject Reference catalogue. Cite the anti-pattern by name when blocking a proposal — gives the user a clear vocabulary to discuss the issue. ## Architecture anti-patterns ### A-1. God service **Smell:** One service does auth, billing, search, file storage, and email. **Why bad:** Single deploy unit, single point of failure, every team touches it, change velocity drops over time. **Fix:** Split by business capability (DDD bounded context). ### A-2. Distributed monolith **Smell:** 12 microservices but they share a database and deploy together. **Why bad:** All cost of distributed (latency, eventual consistency, ops overhead) with none of the benefits (independent deploy, isolation). **Fix:** Either truly separate (own DB, own deploy pipeline) or merge. ### A-3. Synchronous chains **Smell:** Request → Service A → Service B → Service C → Service D. **Why bad:** Compound failure probability, p99 latency adds up. **Fix:** Async with events, or co-locate hot path. ### A-4. Premature optimization **Smell:** Custom Redis Lua scripts, hand-tuned binary protocols, before the first paying user. **Why bad:** Complexity cost paid up front, never recouped. **Fix:** Start simple. Optimize when you have load data. ### A-5. Resume-driven development **Smell:** "Let's use Kubernetes / GraphQL / event sourcing / DDD" with no current pain it solves. **Why bad:** Optimizes for engineer's resume, not user's outcome.
Details
- Skill name
anti-patterns- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/anti-patterns/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Anti Patterns skill do?
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
How do I install the Anti Patterns skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill anti-patterns. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Anti Patterns popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Avoid AI Writing
38jeremybrasher/grokbot-skills
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Observe the text first. Do not use it to decide authorship, hiring, academic integrity, or attribution from the flags. Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.
Create Verification Skill
38jeremybrasher/grokbot-skills
Generate a project-local verification skill that drives your app the way a user does \u2014 any language, framework, or platform. Use for /create-verification-skill, \\"make a control skill for this repo\\", or when a project has no scripted way to prove UI/CLI/service behavior. Observe required inputs first; HOLD when they are missing rather than guessing.
Zero Trust Architecture
48sethdford/claude-skills
Design and implement zero-trust architecture to authenticate and authorize all access, eliminating trust based on location.
Discovery
38jeremybrasher/grokbot-skills
Structured pre-design questioning to surface hidden constraints before any architecture decision is locked in. Forces the architect/auditor/reviewer to enumerate what they DON'T know before proposing.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.