Results for “design-debt”

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.

Debt that exists only in engineers' heads cannot be prioritised, funded, or

Load this skill when the user says "tech debt", "tech-debt", or "/tech-debt", or asks to file/track something they've identified as tech debt. Verifies the claimed problem still exists in the current code, drafts a single [Tech Debt]-prefixed issue from `.github/ISSUE_TEMPLATE/tech-debt-issue.md`, and creates it via `gh issue create` only after the user approves the draft.

Practical technical debt scanning and prioritization for Nick's projects. Use during maintenance reviews, when a codebase feels slow to work in, or when checking what debt is actually hurting development velocity. Focus on high-impact debt, not style nitpicks.

Identifies, classifies, and prioritizes tech debt to build a refactoring roadmap, drawing on twelve classic engineering books.

Design in-game economies including currencies, progression systems, loot tables, monetization, and resource flow. Use when building the economic backbone of a game. Also trigger for "game economy", "loot table", "drop rates", "currency system", "progression design", "monetization strategy", or "reward system".

Designs, constructs, and improves offers by applying value equation analysis, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure.

A B Testing Based Design Skill

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Provides technical leadership frameworks for architecture decisions, engineering team scaling, technology strategy, and technical debt assessment.

ateam-spec

Design decentralized exchanges. TRIGGERS - Use when user needs help with dex-design related tasks.

Algebra Design Expert Skill

Design decentralized exchanges. TRIGGERS - Use when user needs help with dex-design related tasks.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

阶段② 详细设计。根据 design.md 第一章补全第二章各模块设计 + 第四章 ADR。

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

Translate design decisions into business value by reading financials, mapping competitive landscapes, and defending design work in ROI terms.

Drafts professional legal letters for personal injury litigation including settlement demands, cease-and-desist, notice letters, and response correspondence. Tailors tone by recipient type. Use when drafting demand letters, pre-suit correspondence, insurance claim letters, cease-and-desist notices, or litigation response letters.

ateam-design

Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", or "decompose conditional". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation to apply to a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.