Explorar skills
31.375 skills encontradas
event-driven-design
When designing loosely coupled systems that react to state changes asynchronously.
code-review-methodology
Conduct two-stage code review: Stage 1 verifies spec compliance (criterion-to-code mapping), Stage 2 evaluates security, correctness, performance, and maintainability across 6 parallel facets with P1/P2/P3 synthesis and deduplication by file:line. Use when reviewing code changes or pull requests. This skill MUST be consulted because reviewing quality on broken logic is wasted effort, and unmet acc
image-gen
Generate and edit images using AI providers (OpenAI DALL-E, Stability AI, BFL FLUX, Ideogram, FAL, Gemini, Replicate, Clipdrop). Use when user asks to create images, generate artwork, make logos, create visual content, edit photos, remove backgrounds, or modify existing images. Triggers on requests involving pictures, illustrations, graphics, product shots, marketing visuals, or any image creation
security-grc
Use when designing SAP authorization concepts, building or reviewing roles, analyzing SoD conflicts, implementing GRC Access Control (ARA/ARM/EAM/BRM), configuring Firefighter access, auditing security logs, or securing BTP with XSUAA and IAS.
memory-routing
Use whenever the user says 'remember this', 'save to memory', 'запомни', 'в память', 'сохрани', 'в мнемо', solved a bug worth remembering, made a non-obvious decision, or learned a gotcha. Routes each item to Obsidian + optional claude-mem + memory/ + CLAUDE.md with graceful degradation if a backend is unavailable.
fhir-hl7-validator
This skill should be used when the user asks to "validate FHIR resources", "check HL7 messages", "validate healthcare data format", "parse FHIR", "HL7 v2 messages", "FHIR R5 validation", "CDA documents", "healthcare data interchange", "FHIR resource schema", "HL7 specifications", or mentions FHIR validation, HL7 message parsing, CDA validation, healthcare data format compliance, or Fast Healthcare
concept-explanation
Evidence-bound investigation producing a falsifiable architectural mental model of a code concept, pattern, term, or component in large legacy codebases. Use WHENEVER user asks WHAT/HOW/WHERE about code — /explain, "explain X", "what is X", "how does X work", "trace this concept across layers", "preflight before bug-fix", "build mental model", "architectural overview", "layer-by-layer explanation"
ariba
Use when working with SAP Ariba — Ariba Network, Guided Buying, Sourcing, Contracts, Supplier Lifecycle Management, Supplier Risk Management, Procurement, Invoice Management, integration with S/4HANA via CIG, catalog management, or Ariba APIs.
pairwise-ma-methodology
Deep methodology knowledge for pairwise meta-analysis including fixed vs random effects, heterogeneity assessment, publication bias, and sensitivity analysis. Use when conducting or reviewing pairwise MA.
code-quality-principles
Enforce code quality through the Boy Scout Rule (leave code better than found), secret-free commits, production-ready code (no TODOs, console.log, mocks, or commented code), and self-review against an atomic-commits checklist. Use when writing, modifying, or reviewing code. This skill MUST be consulted because production code without these standards causes quality regressions and operational incid
walter-social-media
Use to repurpose source content into platform-native social posts across X/Twitter, LinkedIn, Instagram, and Facebook. Each output follows that platform's voice and length conventions, humanized via Walter.
team-coordination
Coordinate agent teams for adversarial review (paired skeptic/verifier per facet, challenge round with disposition vocabulary, consolidated findings with confidence) or parallel implementation (task sizing 5-6 per teammate, non-overlapping files). Enforces independent analysis before shared conclusions. Reference only (`disable-model-invocation: true`); loaded only when `agentTeams: true` in setti