init-framework
Initialize the katachi framework directory structure
What this skill does
# Initialize Framework
Initialize the katachi development framework directory structure in a project.
## Context
**You must load the following skills before proceeding.**
### Skills
- `katachi:framework-core` - Workflow principles and task management
## Process
### 1. Check Current State
Check if framework is already initialized:
- Does `docs/planning/` directory exist?
If yes, inform the user:
```
Framework directory structure already exists.
You can use these commands to create planning documents:
- `/katachi:vision` - Create project vision
- `/katachi:deltas` - Create the delta inventory
```
### 2. Create Directory Structure
Create the framework directories:
```bash
mkdir -p docs/planning docs/feature-specs docs/feature-designs docs/feature-plans docs/architecture docs/design
```
### 3. Create CLAUDE.md
If CLAUDE.md doesn't exist, create it with this template:
```markdown
# Project: [Project Name]
## Quick Context
[TODO: Add 1-2 sentence description]
## Key Files
- `docs/planning/VISION.md` - Project vision
- `docs/planning/DELTAS.md` - Feature inventory
## Available Commands
Use `/katachi:` commands to work with the framework.
## Current Focus
[TODO: Update when starting a feature]
```
### 4. Next Steps
Inform the user about next steps:
```
Framework initialized! Here are the typical next steps:
For new projects:
1. `/katachi:vision` - Define what you're building
2. `/katachi:deltas` - Create the delta inventory
For existing projects with code:
Ask the user:
"This looks like an existing project with code. Would you like to run a full
project retrofit? This will discover your modules, create specs, designs,
decisions, and synthesize a vision document."
If yes → invoke the `katachi:retrofit-project` skill (it will take over from here)
If no → show individual commands:
- `/katachi:retrofit-spec <path>` - Document one module
- `/katachi:retrofit-design <ID>` - Create design from spec
- `/katachi:retrofit-decision <topic>` - Document one decision
- `/katachi:vision` - Create/synthesize vision
The deltas.py script is available at:
${CLAUDE_PLUGIN_ROOT}/scripts/deltas.py
```
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.