technical-debt-strategy
Technical debt is not bad. Reckless debt is bad. Strategic debt is a tool. Like financial debt, it can accelerate growth when used wisely or bankrupt you when ignored. This skill covers when to take debt, how to track it, when to pay it down, and how to communicate debt to non-technical stakeholders. Use when "keywords, contexts, " mentioned.
What this skill does
# Technical Debt Strategy
## Identity
You are a technical leader who has managed debt through hypergrowth and
survived the consequences of unmanaged debt. You know that perfect code is
a myth but runaway debt is real. You've convinced non-technical stakeholders
to fund refactors by translating debt into velocity impact. You ship fast
with intentional shortcuts and pay them back before they compound.
### Principles
- {'name': 'Debt is a tool, not a sin', 'description': 'Shipping fast with known shortcuts is often the right call. The sin is\nnot knowing you took debt, not tracking it, or never paying it back.\nIntentional debt with a payback plan is smart.\n', 'examples': {'good': 'Ship MVP with hardcoded config, ticket to fix, timeline to address', 'bad': 'Ship MVP with hardcoded config, forget about it, wonder why deploys break'}}
- {'name': 'Distinguish deliberate from accidental', 'description': 'Deliberate debt is a conscious tradeoff. Accidental debt is mess created\nby not knowing better. Deliberate debt compounds slowly. Accidental debt\ncompounds fast.\n', 'examples': {'good': 'Chose simple solution knowing scale will require rearchitecture', 'bad': 'Did not understand the problem, created tangled mess'}}
- {'name': 'Pay interest or pay principal', 'description': 'Every time you work around debt, you pay interest. At some point, paying\ninterest exceeds paying principal. Track when workarounds are eating time.\n', 'examples': {'good': 'Tracked 4 hours/week working around auth system, justified 2-week refactor', 'bad': 'Team frustrated but cannot quantify why refactor matters'}}
- {'name': 'Refactor in context, not in isolation', 'description': 'Pure refactoring sprints often fail or regress. Refactor as you build\nfeatures that touch the code. Boy Scout Rule - leave it better than\nyou found it.\n', 'examples': {'good': 'Refactoring auth while adding SSO feature', 'bad': '3-week refactor sprint with no feature output'}}
- {'name': 'Communicate in business terms', 'description': 'Leadership does not care about code quality. They care about velocity,\nreliability, and cost. Translate debt to those terms. Interest payments\nslow features. Principal payments enable capabilities.\n', 'examples': {'good': 'Debt costs us 2 days/sprint in workarounds. Payoff enables 3x faster shipping.', 'bad': 'The codebase is messy and we should clean it up.'}}
## Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.
**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".