Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems.
Install Anti Patterns
$ npx skills add avelikiy/great_cto --skill anti-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install avelikiy/great_cto anti-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/anti-patterns .claude/skills/anti-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "anti-patterns" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/anti-patterns into .claude/skills/anti-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "anti-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/avelikiy/great_cto/tree/main/skills/anti-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add avelikiy/great_cto --skill anti-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install avelikiy/great_cto anti-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/anti-patterns .agents/skills/anti-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "anti-patterns" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/anti-patterns into .agents/skills/anti-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "anti-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add avelikiy/great_cto --skill anti-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install avelikiy/great_cto anti-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/anti-patterns .cursor/skills/anti-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "anti-patterns" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/anti-patterns into .cursor/skills/anti-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "anti-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/avelikiy/great_cto.git --path skills/anti-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add avelikiy/great_cto --skill anti-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install avelikiy/great_cto anti-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/anti-patterns .gemini/skills/anti-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "anti-patterns" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/anti-patterns into .gemini/skills/anti-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "anti-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install avelikiy/great_cto anti-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add avelikiy/great_cto --skill anti-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/anti-patterns .github/skills/anti-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "anti-patterns" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/anti-patterns into .github/skills/anti-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "anti-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add avelikiy/great_cto --skill anti-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install avelikiy/great_cto anti-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/anti-patterns .opencode/skills/anti-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "anti-patterns" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/anti-patterns into .opencode/skills/anti-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "anti-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
anti-patterns- GitHub stars
- 103
- Token cost
- ~1.7k tokens
- SKILL.md length
- 841 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- MIT
At a glance
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems.
- Works in 4 steps: Cite the code (A-3, P-1, etc.) so the… → Quote the specific smell from the proposal → Propose the specific fix → …
- Tasks that involve Runbooks and postmortems
- SKILL.md covers Architecture anti-patterns, Plan / process anti-patterns, Code-level anti-patterns and UI anti-patterns, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Anti Patterns is an agent skill from avelikiy/great_cto. Catalogue of known SDLC anti-patterns that greatcto 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).
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Runbooks and postmortems. The repository describes itself as: You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the next… The licence is MIT.
When your agent uses it
- Tasks that involve Runbooks and postmortems
Example prompts
- “/anti-patterns”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Cite the code (A-3, P-1, etc.) so the user has a vocabulary
- Quote the specific smell from the proposal
- Propose the specific fix
- If the user disagrees, capture as ADR with the alternatives section
What it can do on your machine
Read from SKILL.md and the folder at commit 5d6e760. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlob
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Anti Patterns loads about 1.7k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 841 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from avelikiy/great_cto at commit 5d6e760, republished under its MIT licence (© avelikiy). 841 words, ~1,653 tokens.
Download SKILL.mdSave it as
.claude/skills/anti-patterns/SKILL.md (or your agent's skills folder).- name
- anti-patterns
- description
- 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).
- allowed-tools
- Read, Grep, Glob
- when_to_use
- Apply when: - architect is writing ARCH/ADR and might be tempted by a known bad pattern - pm is decomposing tasks and the breakdown smells like a known…
- effort
- low
- paths
- docs/**, src/**, lib/**
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. Fix: Ask "what's the simplest thing that could work?"
Plan / process anti-patterns
P-1. Big-bang rewrite
Smell: "Let's rewrite this in <new framework>."
Why bad: 80% of rewrites fail. The old system has years of bug fixes
baked in.
Fix: Strangler-fig. New behaviour in new code, old code coexists,
delete when traffic moves.
P-2. Hero culture
Smell: "Senior X always fixes the 3am incidents." Why bad: Bus factor 1. X burns out. Knowledge doesn't transfer. Fix: Runbooks, post-mortems, rotating on-call, pair-debugging.
P-3. No reversibility plan
Smell: Plan ships a one-way door (data migration, public API change, breaking-contract release). Why bad: If wrong, recovery is days or weeks. Fix: Mandate dry-run + rollback path before approval.
P-4. Plan without timeboxes
Smell: Tasks named "implement feature X" with no end criteria. Why bad: Open scope, time inflates to fit. Fix: Each task ≤ 4 hours, with explicit "done = X" criteria.
Code-level anti-patterns
C-1. God class / God function
Smell: A class > 500 lines or function > 100 lines doing 5 unrelated things. Why bad: Tests become integration tests. Diff readability collapses. Fix: Single responsibility. Extract collaborators.
C-2. Stringly typed
Smell: Status passed as strings ("open", "closed", "blocked") with no enum. Why bad: Typos compile. New status forgotten in switch. Fix: Enum / discriminated union / branded type.
C-3. Catch-and-continue
Smell:
try { doThing(); } catch (e) { console.log(e); }Why bad: Hides bugs. Silent corruption. Fix: Catch only what you can handle; re-throw the rest; log with context.
C-4. Hardcoded secrets
Smell: API keys, passwords, DB URLs in source.
Why bad: Leaks in git history forever; rotation requires force-push (impossible).
Fix: Env vars or secret manager. Pre-commit hook to grep for sk-, ghp_, etc.
UI anti-patterns
Taken from Google AI Studio's guide to polishing generated interfaces (2026-09-16): the fastest way to spot one is decoration that means nothing.
Show full SKILL.md (350 more words)Show less
U-1. Chips that mean nothing
Smell: Status pills, badges, counters and tags that no state drives — "New", "Beta", "AI", "3 insights" on a screen where nothing is new, beta, or counted. Why bad: The reader cannot tell signal from ornament, so a real warning in the same visual language is ignored. It is the most reliable tell of a generated UI. Fix: Each chip names its meaning and the state behind it, or it is removed.
U-2. Placeholder imagery
Smell: Grey boxes, lorem photos, broken or hotlinked stock image URLs in a build that is meant to be shown. Why bad: The first impression is of an unfinished product; hotlinked assets break or change without notice and may not be licensed. Fix: Every image has a named source — generated for this product, owned, or licensed — and is served from the product's own assets.
Incident / ops anti-patterns
O-1. No SLO
Smell: "Production seems slow today" but no SLO target. Why bad: Can't tell breach from normal. Fix: Set p99 latency, error rate, availability SLOs. Track burn.
O-2. Alert spam
Smell: Every error pages. Engineers stop reading alerts. Why bad: Real incidents get missed in noise. Fix: Page only on user-visible failure. Other signals to dashboard, not pager.
O-3. Post-mortem blame
Smell: "Engineer X deployed without testing." Why bad: Suppresses future post-mortems. Blame doesn't fix the system. Fix: Blameless post-mortems. Focus on missing guardrails, not the human.
O-4. Snowflake servers
Smell: "Don't reboot SRV-PROD-3, it has special config that's not in IaC." Why bad: Disaster recovery impossible. Fix: Everything in IaC. Servers are cattle, not pets.
How to use this catalogue
When you find one of these in a proposal/review:
- Cite the code (A-3, P-1, etc.) so the user has a vocabulary
- Quote the specific smell from the proposal
- Propose the specific fix
- If the user disagrees, capture as ADR with the alternatives section filled in
When NOT to apply
- Hobby projects, learning exercises — anti-patterns are about scale
- Throwaway code with explicit
// TODO delete in 2 weeks - Time-boxed POCs where the goal is "does the API actually work"
© avelikiy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/anti-patterns of avelikiy/great_cto.
Open the folder on GitHubat commit 5d6e760
Compare with similar skills
Anti Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Anti Patterns this skillavelikiy/great_cto | 103 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Trader Memory Coretradermonty/claude-trading-skills | 3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Author Migrationnrwl/nx | 29k | — | ~12k | Automated safety check: Notes | MIT | |
| Write Notes Like Deepseekczm15053/write-notes-like-deepseek | 497 | — | ~2k | Automated safety check: Pass | None | |
| OpenRig Upgrade Proceduremvschwarz/openrig | 6.2k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| GreptimeDB Release RunbookGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Author Migration
nrwl/nx
Author or scope a first-party Nx migration. An agent skill from nrwl/nx.
Write Notes Like Deepseek
czm15053/write-notes-like-deepseek
A skill your agent uses when a change is non-trivial by DSH standards (behavior, architecture, cross-file contracts, process/tooling, testing strategy, or on-disk/wire/config formats), when choosing…
OpenRig Upgrade Procedure
mvschwarz/openrig
Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.
GreptimeDB Release Runbook
GreptimeTeam/greptimedb
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
Statem
henryqin1997/statem
A skill your agent uses when a long coding or research task should be managed with statem state-machine runbooks, including creating specs, starting or resuming runs, checking current state…
More from avelikiy/great_cto
All 27 skills in this repoAnyDesign Design Analyzer
avelikiy/great_cto
Analyzes a screenshot, website or Figma file and writes a `design.md` with its token system, component inventory and reconstruction notes, or an `element.md` for one element.
Opportunity Solution Tree
avelikiy/great_cto
Builds an Opportunity Solution Tree that links one measurable outcome to customer opportunities, candidate solutions and experiments.
Outcome-Focused Roadmap Rewriter
avelikiy/great_cto
Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes.
Exposed Secret Rotation
avelikiy/great_cto
Turns a leaked key, token or password into one tracked rotation task the moment it's spotted, instead of a reminder repeated every session.
Skeptical Triage
avelikiy/great_cto
Runs a three-round self-challenge plus an arbiter over high-stakes findings, so false positives from reviews, audits and flaky-test verdicts do not become blockers.
Aesthetic Instrument
avelikiy/great_cto
greatcto's own committed aesthetic — the instrument panel. An agent skill from avelikiy/great_cto.
Related
Categories
Questions about Anti Patterns
What does Anti Patterns do?
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Anti Patterns is an agent skill from avelikiy/great_cto. Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems.
When should I use Anti Patterns?
Anti Patterns fits situations like: tasks that involve Runbooks and postmortems.
How do I install Anti Patterns in Claude Code?
Run `npx skills add avelikiy/great_cto --skill anti-patterns -a claude-code`. Or copy the skill folder (skills/anti-patterns in avelikiy/great_cto) into .claude/skills/anti-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Anti Patterns in Codex?
Run `npx skills add avelikiy/great_cto --skill anti-patterns -a codex`. Or copy the skill folder (skills/anti-patterns in avelikiy/great_cto) into .agents/skills/anti-patterns in your project. Codex loads it when a task matches its description.
Can I use Anti Patterns in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avelikiy/great_cto --skill anti-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/anti-patterns, .gemini/skills/anti-patterns, .github/skills/anti-patterns and .opencode/skills/anti-patterns in your project.
What does Anti Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: Anti Patterns is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob.
Does Anti Patterns access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Anti Patterns safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Anti Patterns use?
Anti Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Anti Patterns use?
About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Anti Patterns?
Skills that share tags, products or a category with Anti Patterns: Trader Memory Core (tradermonty/claude-trading-skills, 3k stars), Author Migration (nrwl/nx, 29k stars), Write Notes Like Deepseek (czm15053/write-notes-like-deepseek, 497 stars) and OpenRig Upgrade Procedure (mvschwarz/openrig, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Anti Patterns?
avelikiy (a GitHub user) maintains it in avelikiy/great_cto, which has 103 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 9, 2026.
Source: avelikiy/great_cto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.