migrate-things
Migrate shared resources and infrastructure from the old flat .things/ layout. Handles directory relocation, shared data (personas, companies), bootstrap cleanup, and config.yml archival. Per-plugin data migration is handled by each plugin's own migrate command.
What this skill does
<references>
<reference name="migration-guide" path="references/migration-guide.md" />
</references>
<purpose>
Migrate shared resources and infrastructure from the old flat `.things/` layout to the new per-plugin directory structure. This handles directory relocation, shared data (personas, companies), bootstrap cleanup, and config.yml archival.
**Config migration** (config.yml -> config.json + per-plugin preferences.json) is handled by `/things:setup-things`. Run `/things:setup-things` first if config.json doesn't exist yet.
**Per-plugin data migration** is handled by each plugin's own migrate command:
- `/migrate-idat` -- logs, arsenal, resumes, index files
- `/migrate-wdyd` -- sessions, questions, progress conversion
- `/migrate-wdyk` -- sessions, study plans, progress + knowledge map conversion
- `/migrate-mmw` -- voice profiles, blog working directory
</purpose>
<steps>
<step id="detect-state" number="1">
<description>Detect Current State</description>
<load-config>
Resolve the user's home directory (run `echo $HOME` via Bash). Use this absolute path for all file operations below -- never pass `~` to the Read tool.
<phase name="check-config">
1. Check if `<home>/.things/config.json` exists.
<if condition="config-json-missing">Tell the user: "Run `/things:setup-things` first - it handles config migration and directory setup." Then stop.</if>
2. Read `<home>/.things/config.json` for git workflow settings.
</phase>
<phase name="check-old-layout">
Check for old layout artifacts:
```bash
echo "bootstrap: $([ -f <home>/.claude/things.local.md ] && echo 'yes' || echo 'no')"
echo "config.yml: $([ -f <home>/.things/config.yml ] && echo 'yes' || echo 'no')"
echo "personas: $([ -d <home>/.things/personas ] && echo 'yes' || echo 'no')"
echo "companies-flat: $([ -d <home>/.things/companies ] && ls <home>/.things/companies/ 2>/dev/null | head -1 || echo 'no')"
echo "old-logs: $([ -d <home>/.things/logs ] && echo 'yes' || echo 'no')"
echo "old-interview-prep: $([ -d <home>/.things/interview-prep ] && echo 'yes' || echo 'no')"
echo "old-learning: $([ -d <home>/.things/learning ] && echo 'yes' || echo 'no')"
echo "old-voices: $([ -d <home>/.things/voices ] && echo 'yes' || echo 'no')"
```
</phase>
<phase name="check-non-convention-path">
3. Check if `<home>/.claude/things.local.md` exists (legacy bootstrap).
<if condition="bootstrap-exists">Read `things_path` from it (expand `~` to `<home>`). This tells us the old `.things/` location.</if>
</phase>
<if condition="no-old-artifacts">
Tell the user: "No old layout artifacts found. Your .things directory is already migrated." Then check if per-plugin data still needs moving (show which per-plugin migrate commands to run if old data directories exist). Then stop.
</if>
</load-config>
</step>
<step id="check-git-sync" number="2">
<description>Check Git Sync Status</description>
<critical-safety-check>
Before migrating, verify git sync status to prevent data loss.
</critical-safety-check>
Check if `.things` is a git repository:
```bash
cd <home>/.things && git rev-parse --git-dir >/dev/null 2>&1 && echo "is-repo" || echo "not-repo"
```
<if condition="is-git-repo">
```bash
cd <home>/.things && git status --porcelain && git status -sb && git log -1 --oneline
```
<if condition="has-uncommitted-changes">
<output>
Warning: You have uncommitted changes in `.things`.
Recommendation: Commit or stash changes before proceeding.
</output>
<if condition="not-dry-run">
<ask-user>Use AskUserQuestion: "You have uncommitted changes. How do you want to proceed?"
- Continue anyway -- changes will be preserved but uncommitted
- Abort -- I'll commit first
</ask-user>
</if>
</if>
<if condition="behind-remote">
<output>
Warning: Your local `.things` is behind the remote. Pull before migrating to avoid losing remote changes.
</output>
<if condition="not-dry-run">
<ask-user>Use AskUserQuestion: "Your local .things is behind remote. How do you want to proceed?"
- Pull and continue -- pull from remote, then migrate
- Abort -- I'll pull manually
</ask-user>
</if>
</if>
</if>
</step>
<step id="show-plan" number="3">
<description>Show Migration Plan</description>
Present the plan based on detected artifacts:
<output>
things migration plan:
<if condition="non-convention-path">Directory relocation:
- `<old_path>` -> `~/.things/` (convention path)
</if>
<if condition="personas-exist">Shared resources:
- `~/.things/personas/` -> `~/.things/shared/roles/`
</if>
<if condition="companies-flat-exist">
- `~/.things/companies/` -> `~/.things/shared/companies/`
</if>
<if condition="config-yml-exists">Cleanup:
- `config.yml` -> `config.yml.bak` (archived)
</if>
<if condition="bootstrap-exists">
- `~/.claude/things.local.md` removed (legacy bootstrap)
</if>
<if condition="old-plugin-data-exists">
Per-plugin data migration (run separately after this completes):
<if condition="old-logs"> - `/migrate-idat`</if>
<if condition="old-interview-prep"> - `/migrate-wdyd`</if>
<if condition="old-learning"> - `/migrate-wdyk`</if>
<if condition="old-voices"> - `/migrate-mmw`</if>
</if>
</output>
<if condition="dry-run-flag">Show the plan and stop. Do not modify any files.</if>
<ask-user>
Use AskUserQuestion: "Proceed with shared migration?"
- Yes -- migrate now
- No -- cancel
</ask-user>
</step>
<step id="relocate-directory" number="4">
<description>Relocate to Convention Path</description>
<if condition="non-convention-path">
```bash
mv <old_things_path> <home>/.things
```
<if condition="old-path-different-location">
Create a symlink for backwards compatibility:
```bash
ln -s <home>/.things <old_things_path>
```
</if>
</if>
<if condition="already-at-convention-path">Skip this step.</if>
</step>
<step id="create-shared-directories" number="5">
<description>Create Shared Directories</description>
```bash
mkdir -p <home>/.things/shared/roles
mkdir -p <home>/.things/shared/companies
mkdir -p <home>/.things/shared/people
mkdir -p <home>/.things/shared/contexts
```
</step>
<step id="move-shared-resources" number="6">
<description>Move Shared Resources</description>
<constraint>Use `mv` (not `cp`) to avoid duplicates. Skip items that don't exist.</constraint>
<phase name="personas-to-roles">
```bash
mv <home>/.things/personas/* <home>/.things/shared/roles/ 2>/dev/null || true
```
</phase>
<phase name="companies">
```bash
mv <home>/.things/companies/* <home>/.things/shared/companies/ 2>/dev/null || true
```
</phase>
</step>
<step id="cleanup" number="7">
<description>Clean Up Old Artifacts</description>
<phase name="archive-config-yml">
<if condition="config-yml-exists">
```bash
mv <home>/.things/config.yml <home>/.things/config.yml.bak
```
</if>
</phase>
<phase name="remove-bootstrap">
<if condition="bootstrap-exists">
```bash
rm <home>/.claude/things.local.md
```
</if>
</phase>
<phase name="clean-empty-dirs">
```bash
rmdir <home>/.things/personas 2>/dev/null || true
rmdir <home>/.things/companies 2>/dev/null || true
```
</phase>
<phase name="create-local-json">
<if condition="local-json-missing">
Write `Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.