Loading...
Loading...
Found 5 Skills
Draft or update architecture documents under `easysdd/architecture/` — describe what a subsystem/module looks like currently, how it is divided, and how external interfaces operate, to provide pre-positioning input for subsequent feature-design. Information sources include code + user materials (oral accounts, scattered documents, compound deposits, existing decisions), and the output can be reverse-validated by anchoring to specific `file:line`. Two modes: new (draft a new architecture document from scratch), update (refresh an existing document based on the latest code status and new user materials). Single-target rule — only modify one document at a time. Trigger scenarios: user says "fill in an architecture doc", "draft an architecture document", "update the architecture directory", "write down the structure of this module", or when it is found that "something that should be in the architecture is missing" during the feature-design / feature-acceptance phase.
Explicitly update DESIGN.md with decisions from the current conversation. Use when you want to force a design document update.
Organize and clean up scripts and dependencies in package.json. Use this for requests such as 'I want to clean up package.json', 'I want to organize scripts', or 'I want to remove unused dependencies'. Specifically, it targets the following: (1) Delete or integrate redundant scripts (aliases/passthroughs), (2) Explicitize implicit lifecycle hooks (pre/post), (3) Unify script naming conventions, (4) Detect and remove unused dependency packages, (5) Update documents and CI following script name changes, (6) Regenerate lock files after removing dependencies.
Incrementally update reverse-engineering docs based on git changes since they were last generated. Reads the commit hash from .stackshift-docs-meta.json, diffs against HEAD, analyzes only the changed files, and surgically updates the affected docs. Saves time and cost compared to full regeneration.
Update Knowledge Base — Execute doc-updater, code-reviewer, and learn-eval in sequence to solidify the changes from this session into documents and knowledge.