ComputerConnection/architect
skills/architect/SKILL.md
Design system architecture for new features or major refactors. Use when planning complex implementations, evaluating trade-offs, or designing new systems.
development
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add ComputerConnection/zach-pack architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 11:06 PM9.5s3 files scanned
SKILL.md
- name:
- architect
- description:
- Design system architecture for new features or major refactors. Use when planning complex implementations, evaluating trade-offs, or designing new systems.
- context:
- fork
- agent:
- Plan
- allowed-tools:
- Read, Grep, Glob, Bash(find *), Bash(wc *), Bash(git log *), Bash(git show *)
- argument-hint:
- [feature-or-system-description]
System Architect
Design architecture for: $ARGUMENTS
Phase 1: Discovery
Codebase Analysis
- Identify existing patterns (MVC, hexagonal, microservices, etc.)
- Map current directory structure and module boundaries
- Find similar features already implemented
- Locate shared utilities, base classes, and abstractions
- Check for existing interfaces/contracts this must integrate with
Dependency Mapping
- External services and APIs involved
- Database schemas affected
- Message queues, caches, or other infrastructure
- Third-party libraries that may help or constrain
Constraints Identification
- Performance requirements (latency, throughput, scale)
- Security boundaries and data sensitivity
- Backwards compatibility requirements
- Team/organizational constraints
Phase 2: Design Options
Present 2-3 architectural approaches. For each:
## Option [N]: [Name]
### Overview
[2-3 sentence summary]
### Architecture Diagram
[ASCII diagram showing components and data flow]
### Key Components
- Component A: [responsibility]
- Component B: [responsibility]
- ...
### Data Flow
1. [Step-by-step flow]
### Trade-offs
| Pros | Cons |
|------|------|
| ... | ... |
### Complexity: [Low/Medium/High]
### Risk: [Low/Medium/High]
### Fits Existing Patterns: [Yes/Partial/No]
Phase 3: Recommendation
Recommended Approach: Option [N]
Rationale:
- Why this fits the codebase
- Why this balances trade-offs appropriately
- Migration path from current state
Phase 4: Implementation Plan
## Files to Create
- path/to/new/file.ts: [purpose]
## Files to Modify
- path/to/existing.ts: [changes needed]
## New Dependencies
- package-name: [why needed]
## Database Changes
- [migrations needed]
## Configuration
- [env vars, feature flags]
Phase 5: Risk Mitigation
Technical Risks | Risk | Likelihood | Impact | Mitigation | |------|------------|--------|------------| | ... | ... | ... | ... |
Rollback Strategy
- How to safely revert if issues arise
Testing Strategy
- Unit test focus areas
- Integration test requirements
- Load/performance testing needs
Phase 6: Open Questions
List any decisions that need stakeholder input before proceeding.
Guidelines
- Prefer composition over inheritance
- Favor explicit over implicit
- Design for testability
- Consider observability (logging, metrics, tracing)
- Keep blast radius small (isolate changes)
- Don't over-engineer - solve today's problem, not hypothetical futures
Related Skills
ComputerConnection/zach
data-ai
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 22, 2026
ComputerConnection/skills/vision
tools
VerifiedTrustedCommunity
--- 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
SKILL.mdUpdated Apr 22, 2026
ComputerConnection/tauri
development
VerifiedTrustedCommunity
Tauri-specific development patterns for NEXUS. Use when building desktop app features, handling IPC, or working with Rust backend.
SKILL.mdUpdated Apr 22, 2026
ComputerConnection/store-sop
development
VerifiedTrustedCommunity
Document Computer Connection store processes in AI-queryable format. Use to capture SOPs for the store AI server POC.
SKILL.mdUpdated Apr 22, 2026