Plan and execute major architectural redesigns across codebase subsystems.
npx skills add https://github.com/jeff-hamm/ai-tools --skill design-update-jeff-hamm
Please help me install this Agent Skill. Skill: design-update Source: https://github.com/jeff-hamm/ai-tools/tree/main/src/skills/design-update Command: npx skills add https://github.com/jeff-hamm/ai-tools --skill design-update-jeff-hamm
Perform a major architectural redesign of a codebase: write a design plan, update architecture docs, then implement changes across all affected files. Use for 'redesign', 'generalize', 'refactor architecture', 'tiered integration', or any large-scale structural change.
Phase 1: Deep Exploration (NEVER skip this) Read every source file, understand dependencies, and review existing documentation to map current architecture. Phase 2: Design Plan (write BEFORE any code) Create a detailed design plan document at docs/plans/<name>.md covering problem statement, tier/integration model, architecture changes, config design, migration path, scope exclusions, and implementation order. Phase 3: Update Architecture Rules Update the project's architecture document to reflect the new design, including updated workspace layout, design principles, integration tier descriptions, and configuration details. Phase 4: Implement (bottom-up, foundation first) Implement in dependency order: configuration system, presets, detection/sniffing, core modules, UI widget, loader, headless client, and server/proxy. For each file, re-read before writing, preserve functionality, make config-driven changes, and maintain backward compatibility. Phase 5: Verify Build, server startup, and syntax checks to ensure all changes integrate cleanly. Phase 6: Summary Provide a recap of new/modified files, testing steps, and environment notes.
Draft a comprehensive design plan and begin the architectural redesign workflow.
High-intent search queries and answers about installing and using this skill.
A major codebase refactor requires a structured workflow: deep exploration of source files, writing a design plan document, updating architecture rules, and implementing changes bottom-up in dependency order. This approach preserves backward compatibility by making config-driven changes and re-reading files before writing.
Documenting an architectural redesign involves creating a detailed design plan covering the problem statement, integration model, config design, and migration path. You should also update the project's architecture document to reflect new workspace layouts and design principles before implementation begins.
Yes, tiered integration across multiple subsystems is explicitly supported. The workflow handles large-scale structural changes, generalization, and subsystem integration by implementing changes in dependency order: configuration systems first, then core modules, UI widgets, and server proxies.
Bottom-up implementation for architectural migration starts with foundational elements like the configuration system and presets, then progresses to detection, core modules, UI, and server components. This dependency-ordered approach ensures each layer integrates cleanly before higher-level components are built.
A design plan for codebase generalization should include the problem statement, tier or integration model, architecture changes, configuration design, migration path, scope exclusions, and implementation order. This document must be written and finalized before any code modifications begin.
Verifying a structural redesign involves running build checks, server startup tests, and syntax validation to ensure all changes integrate cleanly. The workflow concludes with a summary recap of modified files, testing steps, and environment notes to confirm system stability.
lobehubGenerate a structured overview of codebase architecture, modules, and dependencies.
wientjesSwitch Docker runtime to Apple Container for macOS NanoClaw deployments.
Julian0444Convert design documents into TDD-ordered implementation plans with exact file paths.
spideynoloveIdentify and document code smells and refactoring opportunities in JavaScript, TypeScript, and Python codebases.
