intent-migrate
Migrate existing local intents from .sejas folder to the global intents folder. Use when transitioning from local to global intent storage.
What this skill does
# Intent Migrate
You are helping the user migrate existing intents from the local `.sejas/` folder to the global intents folder.
## Workflow
1. Get the current repository info:
- Repository name: `basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $(pwd)`
- Git root: `git rev-parse --show-toplevel 2>/dev/null || pwd`
2. Check if `.sejas/` folder exists at the git root:
- If not found, inform user: "No local .sejas/ folder found. Nothing to migrate."
3. Get the target intents folder:
- Run: `echo "${CLAUDE_INTENTS_FOLDER:-$HOME/.claude-intents}"`
4. List intents to migrate from both `.sejas/in-progress/` and `.sejas/done/`:
- Show the user what will be migrated
- Display old path → new path for each intent
5. For each intent folder, transform the name:
- **Old format:** `YYYY-MM-DD-description`
- **New format:** `YYYY-MM-DD-{repository-name}-{description}`
- Example: `2026-01-15-add-feature` → `2026-01-15-my-repo-add-feature`
6. Ask user for confirmation before proceeding
7. Perform the migration:
- Create `{CLAUDE_INTENTS_FOLDER}/in-progress/` and `{CLAUDE_INTENTS_FOLDER}/done/` if they don't exist
- Move each intent folder from `.sejas/in-progress/` to `{CLAUDE_INTENTS_FOLDER}/in-progress/` with new name
- Move each intent folder from `.sejas/done/` to `{CLAUDE_INTENTS_FOLDER}/done/` with new name
- Use `mv` command to move folders
8. After successful migration:
- Ask user if they want to delete the old `.sejas/` folder
- If yes, remove it: `rm -rf {git_root}/.sejas`
- If no, leave it in place
9. Show migration summary:
- Number of open intents migrated
- Number of done intents migrated
- New location path
## Example Output
```
## Migration Preview
**Source:** /path/to/repo/.sejas/
**Target:** ~/.claude-intents/
**Repository:** my-repo
### Open Intents (3)
- 2026-01-15-add-feature → 2026-01-15-my-repo-add-feature
- 2026-01-18-fix-bug → 2026-01-18-my-repo-fix-bug
- 2026-01-20-update-docs → 2026-01-20-my-repo-update-docs
### Done Intents (1)
- 2026-01-10-initial-setup → 2026-01-10-my-repo-initial-setup
Proceed with migration? (y/n)
```
## Important Notes
- **CLAUDE_INTENTS_FOLDER:** Use the environment variable for target path. Default is `~/.claude-intents`
- **Preserve all files:** Move entire folder contents (spec.md, notes.md, pr.md, and any other files)
- **No overwrites:** If a target folder already exists, warn the user and skip that intent
- **Repository name:** Extracted from git or current folder name
- **Backup suggestion:** Recommend user backs up `.sejas/` before migration if they have important data
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.