scaffold
Generate incremental local code modules following existing codebase patterns. Use for endpoints, components, packages, collections, or modules inside an existing repo; not for full project scaffolds.
What this skill does
# Scaffold Generate incremental code inside an existing repository, following local codebase patterns. ## Contract Inputs: - Scaffold target type and name - Repository root - Existing examples to follow Outputs: - Files created or modified - Patterns copied from existing code - Manual follow-up steps and tests to run Creates/Modifies: - Local source, test, and export files for the requested module/component/package - Does not create a full product repo External Side Effects: - None Confirmation Required: - Before overwriting existing files - Before introducing a new pattern when fewer than 3 matching examples exist Delegates To: - `project-init-orchestrator` when the user needs a whole new project - `fullstack-workspace-init` / `npx @shipshitdev/v0` when the user needs a new Shipshit.dev product repo - Framework-specific skills such as `nestjs-expert`, `react-patterns`, `shadcn`, or `typescript-expert` ## Steps 1. **Determine what to scaffold** from arguments: - `endpoint [name]` — New API endpoint (controller + service + module) - `module [name]` — New backend module with full structure - `component [name]` — New UI component with proper typing - `package [name]` — New shared package - `collection [name]` — New database collection with schema + service 2. **Find 3+ existing examples**: - Search for similar implementations in the codebase - Identify the exact patterns used (imports, naming, file structure) - Note any module-specific conventions 3. **Scaffold based on type**: ### API Endpoint - Controller, Service, Module in appropriate directory - Follow: auth guards, tenant filtering, serializer response ### UI Component - Component file with proper typing - Props interface in dedicated props file - Export from barrel ### Shared Package - Directory with package.json - Barrel export: `src/index.ts` - TypeScript config ### Database Collection - Schema/model file - Interface in shared interfaces package - Serializer in shared serializers package (if applicable) 4. **Apply critical rules**: - Interfaces in dedicated files, not inline - Path aliases, not relative imports - Tenant/organization filter in all queries (if applicable) 5. **Report**: List all files created and any manual steps needed ## Arguments - Required: what to scaffold (e.g., "endpoint tasks", "component ImageGrid", "collection workflows")
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.