skills.rest
Dowwie
DowwieCOMMUNITY
Explore all skills by this author →
Website𝕏@darin_gordonGitHub

antipattern-catalog

Catalog anti-patterns with severity levels and remediation steps from framework analyses.

5|Updated Dec 23, 2025
Search Tags:#code quality#architecture#anti-patterns#remediation#forensics#do not repeat
One-click install
npx skills add https://github.com/Dowwie/agent_framework_study --skill antipattern-catalog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antipattern-catalog
Source: https://github.com/Dowwie/agent_framework_study/tree/main/.claude/skills/antipattern-catalog
Command: npx skills add https://github.com/Dowwie/agent_framework_study --skill antipattern-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Anti-Pattern Catalog helps teams document technical debt, anti-patterns, and patterns to avoid across analyzed frameworks, enabling consistent remediation decisions and reusable lessons learned.

Core Features & Use Cases

  • Cataloging: Collect and classify observed structural, behavioral, observability, and performance anti-patterns.
  • Severity & Remediation: Assign severity levels and generate concrete remediation steps.
  • Do Not Repeat: Create and maintain Do Not Repeat checklists to guide future architecture decisions and knowledge sharing.
  • Use Case: After analyzing multiple frameworks, generate a consolidated catalog entry to guide future implementations and strategic decisions.

Quick Start

Review phase findings, write initial catalog entries for major anti-patterns, and share the Do Not Repeat checklist with your team.

Frequently Asked Questions about antipattern-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architectural anti-patterns found during framework analysis?▼

To document architectural anti-patterns, catalog observed structural, behavioral, observability, and performance issues into a structured format. This consolidates analysis findings and assigns severity levels to guide consistent remediation decisions.

What is a Do Not Repeat checklist for software architecture?▼

A Do Not Repeat checklist captures lessons learned from architectural anti-patterns to guide future design decisions. It helps teams avoid repeating technical debt by providing structured categorization and knowledge sharing across framework implementations.

How do I assess the severity of technical debt across multiple frameworks?▼

Assess the severity of technical debt by consolidating Phase 1 and 2 analysis findings into a centralized catalog. This approach applies structured categorization and severity assessment to anti-patterns observed across analyzed architectures.

Can I generate remediation steps for code quality issues from framework forensics?▼

Yes, you can generate concrete remediation steps by cataloging anti-patterns identified during framework forensics. The catalog assigns severity levels and produces actionable guidance to address code quality issues.

When do I need an anti-pattern catalog for remediation planning?▼

You need an anti-pattern catalog when you have completed analyzing multiple frameworks and need to consolidate findings. It enables consistent remediation planning by providing structured categorization and Do Not Repeat checklists for future implementations.

Related Skills

Explore More Software Engineering Skills→
moogahmoogah
1

architecture-analyzer

Analyze codebases through iterative dialogue and visual architecture diagrams.

Community
Advanced
ngochuy13ngochuy13

tech-debt

Identify, categorize, and prioritize technical debt with impact, risk, and effort scoring.

Community
Intermediate
mlbrightmlbright

code-review

Analyzes Rails code quality and security via automated tools.

Community
Intermediate
apacheapache
79

magpie-issue-deduplicate

Identify and merge duplicate issues in issue trackers with maintainer confirmation.

Official
Intermediate