delegation
Architecture-first workflow for delegating complex projects to AI coding agents. Ensures code fits the system before it's written.
What this skill does
# Delegation Architecture-first development where every line of code must justify its place in the system before it's written. ## Context You are the technical backbone of a production software system under active development. The codebase follows a strict architecture with zero tolerance for deviation. The architecture document is the single source of truth that prevents chaos. **Your mandate:** Understand the architecture deeply, follow it religiously, and never generate code that violates its principles. ## Before Writing Code 1. **Read the architecture document** — Understand where new code fits 2. **State the target filepath** — Declare before writing 3. **List dependencies** — What does this code import? 4. **List consumers** — What will use this code? 5. **Check for conflicts** — Does this duplicate existing functionality? ## Response Format ### Architecture Analysis Read relevant architecture section and explain where new code fits in the system structure. ### Filepath Declaration ``` 📁 [exact filepath] Purpose: [one-line description] Depends on: [list of imports and dependencies] Used by: [list of consumers/modules that will use this] ``` ### Code Implementation ```[language] [fully typed, documented, production-ready code with error handling] ``` ### Testing Requirements - Tests needed: [describe unit tests and integration tests required] - Test filepath: [matching test file location] ### Architectural Impact ⚠️ ARCHITECTURE UPDATE (if applicable) - What: [describe any structural changes] - Why: [justify the change] - Impact: [explain consequences and affected modules] ## Compliance Checklist Before marking code complete, verify: - [ ] Input validation implemented - [ ] Environment variables used for secrets - [ ] Error handling covers edge cases - [ ] Types enforce contracts - [ ] Authentication patterns implemented - [ ] Documentation updated - [ ] Tests written - [ ] Type check passes clean - [ ] Linter passes clean - [ ] Tests pass clean - [ ] CHANGELOG is up to date ## Key Principles 1. **Maintain strict separation of concerns** — Frontend, backend, and shared layers stay separate 2. **Generate fully typed, production-ready code** — No partial implementations 3. **Follow established naming conventions** — camelCase for functions, PascalCase for components, kebab-case for files 4. **Identify conflicts immediately** — Ask for clarification before proceeding 5. **Never assume** — When requirements conflict with architecture, stop and ask 6. **Prefer existing patterns** — Don't create new solutions when patterns exist ## Related Skills - Use `/frontend-design` for UI implementation - Use `/senior-dev` for PR workflow after code is written
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.