Showing 6211–6240 of 10205 skills
Cria um endpoint Minimal API no padrão IUseCaseEndpoint do projeto. Use este skill quando solicitado a criar um novo endpoint HTTP, rota, controller ou API para um caso de uso.
biellts/universidade-automatiza
Cria erros de domínio tipados para um agregado ou feature. Use este skill quando solicitado a criar novos erros de domínio, códigos de erro, Error records ou mensagens de validação de negócio.
biellts/universidade-automatiza
Cria testes unitários de domínio no padrão xUnit + Shouldly + AAA + Builder do projeto. Use este skill quando solicitado a criar testes unitários, testes de domínio ou cobertura de testes para um agregado, Value Object ou regra de negócio.
biellts/universidade-automatiza
Cria um novo caso de uso completo no padrão Vertical Slice + CQRS do projeto. Use este skill quando solicitado a criar um novo Use Case, Command, Query, Handler ou operação CRUD em qualquer módulo.
biellts/universidade-automatiza
Cria um Validator para validações assíncronas que requerem acesso ao banco de dados. Use este skill quando solicitado a criar validações de existência, unicidade ou consistência que precisam consultar o banco antes de executar um command.
biellts/universidade-automatiza
Cria um novo Value Object (VO) com factory estático, validação e igualdade estrutural. Use este skill quando solicitado a criar um novo Value Object, tipo de valor, VO ou campo validado do domínio como título, e-mail, nota, código etc.
biellts/universidade-automatiza
Guia de uso do Result Pattern para criação e encadeamento de resultados, extração de valores e tratamento de erros. Use este skill quando for trabalhar com Result<T>, Result, erros de domínio, retornos de factory ou encadeamento de operações.
biellts/universidade-automatiza
沿两个轴审查自某个固定点(fixed point,commit、分支、tag 或 merge-base)以来的变更 — Standards(代码是否符合本仓库文档化的 coding standards?)和 Spec(代码是否实现了原始 issue/spec 所要求的内容?)。两个审查在并行 sub-agents 中运行,并排报告结果。当用户想审查一个分支、一个 PR、进行中的变更,或说 "review since X" 时使用。
gongyijie85/mattpocock-skills-dsh-zh
Code review with subagents in T3 Code. Use when the user asks to review uncommitted changes, a branch, a commit, or a pull request. Accepts --profile. Runs report-only reviewers and an oracle, merges the findings, and offers fixes.
gabimoncha/oh-my-t3
Deprecated name; the skill formerly here is now opinionated-research:interactive-research. Retained as a context-level notice because Claude Code now ships a built-in deep-research workflow that runs one-shot, non-interactive fan-out research (no conversation after the report). interactive-research instead runs a persistent agent team you can keep questioning after the report is delivered. Guidance for Claude: when the user makes a research request, ask whether they want the interactive team (interactive-research) or the built-in non-interactive deep-research workflow before starting.
Pyroxin/opinionated-claude-skills
Decide WHERE video/image generation runs when cost, volume, or capability forces a choice - subscription credits vs pay-per-use APIs vs cloud ComfyUI. Use when asked "which video engine should I use", "is Higgsfield/fal/RunComfy worth it", "credits ran out", "cheapest way to generate N clips", "do I need ComfyUI", "should I run this locally", or when the video-gen skill escalates a budget or capability ceiling. Contains the pricing table, graduation triggers, and the never-local rule for iGPU machines.
frankxai/creator-skills
审查 branch、PR、固定点或工作区代码变更;自动审查按规模与风险选择单 Agent 轻审或双 Agent 全审,并核查仓库标准、代码异味及按需路由的本地规则。
ducafecat/skills
Rules for when an agent should recall from long-term memory before acting and when it should save decisions, corrections and failures afterwards. Works with any memory backend.
ranbot-ai/awesome-skills
Find animation and video references on 1human, consult a human-agent shared library, and contribute public creations only with prior owner permission.
ranbot-ai/awesome-skills
Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory.
ranbot-ai/awesome-skills
Build production-ready LLM applications, advanced RAG systems, and intelligent agents. Implements vector search, multimodal AI, agent orchestration, and enterprise AI integrations.
ranbot-ai/awesome-skills
Search and preview free sound effects through the Lots of Sounds public API without an API key. Use when a user needs audio or sound effects for an app, game, video, website, prototype, notification, user interface, or AI agent. Use the full Lots of Sounds API only when the user needs advanced filters, pagination, or downloads.
lotsofsounds/free-sound-effects-api
Identify, score, and prioritize Salesforce AI use cases before any implementation begins — opportunity identification, Impact-Effort matrix scoring, feasibility evaluation across Technical/Operational/Data/Risk dimensions, and ROI framing. NOT for the license checks and enablement steps once a use case is approved — use agentforce/agentforce-service-ai-setup or agentforce/agentforce-sales-ai-setup. NOT for making the data model AI-ready — use architect/ai-ready-data-architecture.
PranavNagrecha/AwesomeSalesforceSkills
Use this skill to determine whether a Salesforce Commerce project should use B2B Commerce (account-gated, BuyerGroup-based, contract pricing) or D2C Commerce (consumer storefront, guest checkout, individual-based). Trigger keywords: B2B vs B2C, commerce platform selection, buyer journey, account-based purchasing, consumer storefront, licensing decision. NOT for implementation mechanics — use admin/b2b-commerce-store-setup or admin/b2c-commerce-store-setup for configuration work. NOT for Salesforce B2C Commerce (SFCC/Business Manager) setup.
PranavNagrecha/AwesomeSalesforceSkills
Configuring Salesforce case management: case queues, assignment rules, escalation rules, auto-response rules, Email-to-Case, Web-to-Case, case teams, entitlements, and milestones. Use when setting up or troubleshooting the Service Cloud case handling layer. Trigger keywords: email-to-case, web-to-case, escalation rules, case teams, entitlements, milestones, auto-response, case queue. NOT for Standard vs On-Demand Email-to-Case and routing-address setup — use admin/email-to-case-configuration. NOT for routing case work items to agents — use admin/omni-channel-routing-setup.
PranavNagrecha/AwesomeSalesforceSkills
Use this skill when defining clinical data model requirements for Health Cloud: HL7/FHIR data mapping, interoperability requirements, FHIR R4-aligned object activation, CodeableConcept constraints, and middleware translation requirements. NOT for the field-level mapping work itself — use data/fhir-data-mapping. NOT for choosing legacy HC24__ EHR objects vs standard clinical objects — use data/health-cloud-data-model.
PranavNagrecha/AwesomeSalesforceSkills
Use this skill when configuring or troubleshooting the Salesforce CPQ Guided Selling wizard: Quote Process records, ProcessInput questions that filter products by field value, mapping answers to Product2 classification fields, and search type choice (Standard, Enhanced, Custom). Trigger keywords: CPQ guided selling, quote process wizard, product selection wizard, SBQQ__QuoteProcess__c, SBQQ__ProcessInput__c, guided product selection, auto select product, product search plugin. NOT for bundles, product options, or product rules — use admin/cpq-product-catalog-setup. NOT for writing a custom ProductSearchPlugin in Apex — use apex/cpq-apex-plugins.
PranavNagrecha/AwesomeSalesforceSkills
Use this skill when setting up or modifying product bundles, product options, product rules, configuration attributes, and product features in Salesforce CPQ. Trigger keywords: CPQ product bundle, product rule, option constraint, feature configuration, dynamic bundle, filter rule, configuration attribute, bundle nesting. NOT for plain Products and Pricebooks without CPQ — use admin/products-and-pricebooks. NOT for moving an existing CPQ catalog between orgs — use data/product-catalog-migration-cpq. NOT for price rules, price actions or discount schedules — use admin/cpq-pricing-rules.
PranavNagrecha/AwesomeSalesforceSkills
Configuring Salesforce Email-to-Case: Standard vs On-Demand mode selection, routing address setup, email threading via Lightning tokens, auto-response rules, attachment limits, and per-address case field defaults. Trigger keywords: email-to-case, routing address, on-demand email-to-case, email threading, case from email, email agent, routing address setup, Case.settings-meta.xml, EmailToCaseRoutingAddress, emailServicesAddress, isVerified, caseOrigin, enableThreadTokenInBody, useEmailHeadersForThreading, overEmailLimitAction, unauthorizedSenderAction, enableE2CAttachmentAsFile, saveEmailHeaders, newEntityRecordType, casePriority, EmailMessage.EmailRoutingAddressId, auto-response loop. NOT for the wider case layer (queues, escalation rules, case teams, entitlements) - use admin/case-management-setup. NOT for routing case work items to agents after creation - use admin/omni-channel-routing-setup. NOT for the email templates or letterheads themselves - use admin/email-templates-and-alerts.
PranavNagrecha/AwesomeSalesforceSkills
Use this skill when configuring or troubleshooting FSC Referral Management: setting up referral types via ReferralRecordTypeMapping custom metadata, routing referrals through Lead Assignment Rules keyed on the Expressed Interest picklist, tracking Referrer Score, and partner referral visibility in Experience Cloud. Trigger keywords: referral routing, FSC referral types, ReferralRecordTypeMapping, Expressed Interest picklist, partner referral Contact, Referrer Score Experience Cloud. NOT for clinical referrals in Health Cloud — use admin/referral-management-health. NOT for standard Lead capture and conversion outside FSC — use admin/lead-management-and-conversion.
PranavNagrecha/AwesomeSalesforceSkills
Use this skill to configure and manage Field Service Lightning workforce capacity — covering ServiceResourceCapacity for individual resource caps, WorkCapacityLimit for territory-level demand throttling, and reporting strategies for capacity vs. utilization analysis. NOT for resource skills, certifications, or preference setup — use admin/fsl-resource-management. NOT for work rules and service objectives — use admin/fsl-scheduling-policies. NOT for Omni-Channel agent capacity — use architect/omni-channel-capacity-model.
PranavNagrecha/AwesomeSalesforceSkills
Use this skill to configure Field Service Lightning service resources — including ServiceResource types, skill assignments via ServiceResourceSkill, capacity-based resource setup, and ResourcePreference rules. NOT for territory-level WorkCapacityLimit throttling or capacity-vs-utilization reporting — use admin/fsl-capacity-planning. NOT for service territory setup — use admin/fsl-service-territory-setup. NOT for work rules and service objectives — use admin/fsl-scheduling-policies.
PranavNagrecha/AwesomeSalesforceSkills
Use this skill to configure Field Service Lightning service territories — including territory types, operating hours, time slots, territory hierarchy, member types, and polygon boundaries. NOT for Enterprise Territory Management (Territory2) in Sales Cloud — use admin/enterprise-territory-management. NOT for bulk-loading territory polygons or members — use data/fsl-territory-data-setup.
PranavNagrecha/AwesomeSalesforceSkills
Configure FSL Shifts, ShiftTemplates, ShiftPatterns, and Crew ServiceResources — availability windows layered on Operating Hours, bulk shift generation via ShiftPattern + ShiftPatternEntry, and the two Crew models (Static vs. Shell/Dynamic). NOT for setting up the resources themselves — types, skills, ResourcePreference — use admin/fsl-resource-management. NOT for capping how many hours or appointments a resource can take — use admin/fsl-capacity-planning.
PranavNagrecha/AwesomeSalesforceSkills
Orchestrate several ank agents in parallel, each on its own task, worktree and branch. Use only inside a herdr-core terminal, when asked to fan ank tasks out across agents in a repository with a .ank/ directory.
haksolot/ank