skills/zach/SKILL.md
Inject Zach's full identity, business context, and working preferences. Use at session start to eliminate cold starts. Lightweight context load — not a full agent like Vision, just who Zach is and how to work with him.
npx skillsauth add ComputerConnection/zach-pack zachInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read these files in order to load full context about who you're working with:
~/.claude/skills/zach/IDENTITY.md — Who Zach is, the business, the team, the vision~/.claude/skills/vision/memory/taught.md — Permanent facts and preferences Zach has explicitly stated~/.claude/skills/vision/memory/zach_profile.md — Living profile with current priorities and recent decisionsAfter reading, confirm context is loaded with a brief one-liner. Don't summarize everything back — Zach knows who he is. Just signal you're oriented and ready.
If Zach passed arguments (e.g., /zach what's the team schedule), answer the question directly after loading context. Don't make him wait for a readiness check.
tools
--- name: vision description: "Zach's personal AI — his Jarvis. NOT a store agent. This is the owner's private command center that sits above everything else. Handles anything Zach needs — business, personal, technical, strategic, creative. High-systems AI: precise, anticipatory, authoritative. Invoke for ANY task." context: fork allowed-tools: Read, Grep, Glob, Bash, Edit, Write, Task, TodoWrite argument-hint: [what-do-you-need] — freeform. Vision figures out the rest. --- # VISION — Zach's Ja
development
Tauri-specific development patterns for NEXUS. Use when building desktop app features, handling IPC, or working with Rust backend.
development
Document Computer Connection store processes in AI-queryable format. Use to capture SOPs for the store AI server POC.
development
Orchestrates the full product strategy pipeline: product audit → roadmap → sprint plan with PM decision gates. This skill reads ACTUAL source code, cross-references git history, and produces three deliverables — a brutally honest product audit, a thesis-driven roadmap, and a sprint plan with PM decision gates between every phase. Use this skill whenever someone mentions: "sprint plan", "product roadmap", "plan the sprints", "PM questions", "product strategy", "audit this app", "roadmap this feature", "plan development", "break this into sprints", "phase this work", "create a development plan", "quarter planning", "what should we build next", "evaluate this app", "feature audit", "product review", "development roadmap", or any request for deliberate, methodical planning of software work. Also trigger when users want to evaluate whether features earn their place, when they reference PM decision gates or go/no-go checkpoints, or when they want to understand what's worth keeping in a codebase before planning new work. Even if the user only asks for one stage (just an audit, just a sprint plan), use this skill — it will guide them through the appropriate subset.