Results for “software-design”

Reviews code through the lens of 12 classic software engineering books, catching design smells, coupling issues, and architectural risks that linters miss.

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

Model software around the business domain using bounded contexts, aggregates, and ubiquitous language, with scoring and diagnostic tools for evaluating domain model quality.

Design system architecture, evaluate microservices vs monolith, create architecture diagrams, analyze dependencies, choose databases, and make technical decisions with architecture decision records.

Compare tradeoffs and recommend architectural patterns — dependency injection, service-oriented architecture, repository, domain events, circuit breaker, and anti-corruption layer. Use when choosing between design patterns, planning microservices boundaries, evaluating system design alternatives, or asking 'which pattern should I use' for a specific coupling or resilience problem.

Convierte especificaciones aprobadas en un plan técnico detallado, documentando decisiones de arquitectura, flujo de datos y cambios de archivos.

Guides coding workflows with planning, implementation, verification, and testing, storing user preferences locally on request.

Designs application architecture, selects patterns, structures code modules, and manages dependencies for new projects.

Shared vocabulary for designing deep modules — a small interface hiding a lot of behavior. Use when designing or improving a module's interface, deciding where a seam belongs, deciding whether to extract or merge modules, or making code more testable.

Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. (gstack)

Identifies common software anti-patterns in code and suggests refactoring solutions to improve code quality.

Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.

Domain-Driven Design methodology using bounded contexts, ubiquitous language, and strategic/tactical patterns

Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. Standalone design exploration you can run anytime. Use when: "explore designs", "show me options", "design variants", "visual brainstorm", or "I don't like how this looks". Proactively suggest when the user describes a UI feature but hasn't seen what it could look like. (gstack)

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

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.

Design precise, production-grade enterprise UI — dashboards, admin panels, SaaS interfaces, and data-heavy applications. Use this skill for professional software interfaces that need Jony Ive-level craft: clean, minimal, functional, with intentional personality. Do NOT use for creative landing pages, marketing sites.

Design pricing, packaging, and monetization strategy for a software or AI product. Use when the team needs plan structure, free-tier logic, usage vs seat pricing tradeoffs, paywall timing, or monetization guardrails tied to product value and costs.

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

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.