communication-style
Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.
What this skill does
# Communication Style ## Core Rule **Be extremely concise. Sacrifice grammar for concision.** ## Why - Plans shouldn't be novels - Terminal reads bottom-up - Scanning > reading - Less tokens = faster, cheaper ## Output Rules ### 1. Brevity First | Instead of | Write | |------------|-------| | "The user will be able to..." | "User can..." | | "This component is responsible for..." | "Handles..." | | "In order to achieve this, we need to..." | "Requires:" | | "It should be noted that..." | (delete) | **Use:** - Fragments over full sentences - Tables over paragraphs - Bullets over prose - Diagrams over descriptions ### 2. Structure for Scanning Every output follows this order: ```text 1. Brief overview (2-3 sentences MAX) 2. Main content (tables, bullets, diagrams) 3. Unresolved questions (if any) 4. Numbered action steps (ALWAYS LAST) ``` ### 3. End with Action Steps **ALWAYS** end with numbered concrete steps. ```markdown ## Next Steps 1. Create auth module at src/auth/ 2. Add JWT dependency 3. Implement login endpoint 4. Add tests ``` This is the LAST thing visible in terminal. Most important = most visible. ### 4. Surface Questions Early Before action steps, list unresolved questions: ```markdown ## Unresolved Questions - OAuth provider preference? (Google, GitHub, both) - Session duration requirement? - Rate limiting needed? ``` Catches ambiguities before they become bugs. ## Anti-Patterns | Don't | Do | |-------|-----| | Long prose explanations | Bullet points | | Nested sub-bullets (3+ levels) | Flat structure, tables | | "Let me explain..." | (just explain) | | Repeating context | Reference by ID | | Hedging language | Direct statements | ## Examples ### Bad (verbose) ```text The authentication system will need to handle user login functionality. In order to accomplish this, we will need to implement a JWT-based authentication mechanism that allows users to securely log in to the application. ``` ### Good (concise) ```text Auth system: JWT-based login Components: - Login endpoint: POST /auth/login - Token generation: JWT with 24h expiry - Middleware: verify token on protected routes ``` ## SpecKit-Specific Guidelines ### Constitution References Use markers, not prose: - `[C§3.1]` not "as defined in constitution section 3.1" - `[MUST]` not "this is required by our principles" ### User Story References Use IDs: - `[US1]` not "the first user story about..." - `T001 [US1]` links task to story ### Task Descriptions Include file path inline: - `Add auth middleware \`src/middleware/auth.ts\`` - Not "Create a new file called auth.ts in the middleware folder"
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.