architecture
Manage tech stack and architecture decisions
What this skill does
# Architecture Manage the project's tech stack and architecture decisions. ## Instructions Ask the user what they want to do: 1. **Update tech stack** - Add or modify technologies in `docs/strategy/tech-stack.md` 2. **New decision** - Create an Architecture Decision Record in `docs/strategy/architecture/` 3. **Review decisions** - List existing ADRs and check if any need updating ### Option 1: Update Tech Stack 1. Check if `docs/strategy/tech-stack.md` exists 2. If it exists, read it and ask what to add/change 3. If it doesn't exist, gather the current tech stack through conversation 4. Update or create the file Tech stack document should cover: - **Languages** - Programming languages used - **Frameworks** - Core frameworks - **Infrastructure** - Hosting, CI/CD, etc. - **Data** - Databases, caching, etc. - **Key Libraries** - Important dependencies ### Option 2: New Decision Create a new ADR in `docs/strategy/architecture/`. Use numbered filenames like `001-title.md`. 1. Check existing ADRs to determine the next number 2. Ask the user about: - **Title**: Short name for the decision - **Context**: Why are we making this decision? What's the situation? - **Decision**: What did we decide? - **Consequences**: What does this mean going forward? (good and bad) 3. Create the ADR with status "accepted" ADR format: ```markdown # [NUMBER]. [TITLE] **Status**: accepted ## Context [Why we're making this decision] ## Decision [What we decided] ## Consequences [What this means - both positive and negative] ``` ### Option 3: Review Decisions 1. List all ADRs in `docs/strategy/architecture/` 2. Show a summary of each (title + status) 3. Ask if any decisions need to be revisited 4. If yes, update the status (deprecated, superseded) and optionally create a new ADR ## Output Locations - Tech stack: `docs/strategy/tech-stack.md` - ADRs: `docs/strategy/architecture/NNN-title.md` ## Notes - Keep ADRs concise - capture the essence, not every detail - ADRs are immutable once accepted - create new ones to supersede old decisions - Tech stack should reflect what's actually in use, not aspirational ## Resources - For detailed ADR guidance, see [adr-guide.md](adr-guide.md)
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.