analyze
Analyze phase entry. Aggregates scoring, follow-up, and scope-check rules; loads references/assets/scripts on demand.
Design phase entry. Aggregates plan-level selection, task breakdown, and package output rules; loads references/assets/scripts on demand.
$ npx -y skills add evidentloop/sopify --skill design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/designContext preview
The summary Claude sees to decide when to auto-load this skill.
Design phase entry. Aggregates plan-level selection, task breakdown, and package output rules; loads references/assets/scripts on demand.
name: design description: Design phase entry. Aggregates plan-level selection, task breakdown, and package output rules; loads references/assets/scripts on demand.
> Check the current system first, then choose the smallest sufficient path.
1. Load `references/design-rules.md`. 2. Check existing implementation, governing contracts, applicable platform capabilities, and installed dependencies. 3. Choose the smallest sufficient path and select `light/standard/architecture`. 4. Generate the plan files from the matching `assets/` templates. 5. Produce tasks with explicit dependencies and verification. 6. Report `Ready` or `Needs decision` with evidence using `assets/output-summary.md`.
Use the selector when `plan.level=auto` must be auditable:
python3 skills/en/skills/sopify/design/scripts/select_plan_level.py \ --file-count 6 \ --new-feature \ --cross-module
The script returns JSON with the suggested level and explicit reasons.
Resumable AI coding — ask first, plans stay with the repo AI coding tools are fast. But when they jump to code before the facts are clear, speed turns into rework.
Analyze phase entry. Aggregates scoring, follow-up, and scope-check rules; loads references/assets/scripts on demand.
Develop phase entry; routes task execution, state updates, KB sync, and plan close-out through references/assets/scripts.
Manage long-lived `.sopify/` knowledge, including bootstrap, progressive materialization, reads, retention, and knowledge_sync policy.
Knowledge-base document templates, loaded when long-lived knowledge files are created or materialized.