Results for “design-debt”

Identify, categorize, and prioritize technical debt into a ranked, defensible backlog that ties each remediation to impact and effort — a register, not a wish list.

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

Designs an approval-gated feature specification from approved requirements, covering architecture decisions, component boundaries, quality constraints, and definition of done.

Set a deliberate visual direction before any UI is built — the single biggest lever against generic AI output. Derives a posture from product-soul/PRD/specs, scores a curated archetype palette, then generates 2-3 GENUINELY DISTINCT directions and compares them side-by-side before committing to one. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, explore visual options, says "what should this look like", "make it feel like [Linear/Apple/ Duolingo]", "give me design directions", "explore some looks", or when frontend-design routes here. Replaces design-archetype. Sub-skill of frontend-design.

Design or revise a company's commercial policy governing discounts, approver thresholds, exception flows, and deal frameworks using data-backed matrices and linting tools.

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

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