“Prompt engineering”

Use when Malvex needs to turn validated findings into YARA, Sigma, EDR, network, memory, or behavioral detections.

Clarify vague or underspecified creative intent before prompt construction.

Apply general production engineering standards when implementing, fixing, reviewing, or refactoring code in any language or framework.

Select focused debugging, test-first or architecture guidance for code implementation, failures and tests.

Cache the parts of the prompt that don't change so a long-running loop stops paying full price on every turn.

Resilience engineering, fault injection testing, circuit breaker patterns, and graceful degradation protocols.

Expert application security engineer specializing in threat modeling, vulnerability assessment, secure code review, and security architecture design.

General implementation only when no narrower task or ecosystem skill fits.

Orchestrator for ad-hoc work and for a long chat.

Web Vitals, bundle optimization, CDN, caching, and load analysis.

Apply Graph Engineering workflows inside Hermes.

Engineering principles (inviolable) for the software-delivery fabric.

Use explicit human checkpoints for architecture, security, rollout, or operational decisions.

Show rules for a team audio episode about what is broken for customers, what they are asking for, and what shipped.

data has one authoritative form, a model before a store, and safe access.

Comprehensive skill for Babylon.js 3D web rendering engine.

Rigorous agentic engineering workflow — 23 playbooks and 23 principle rules for bug fixes, features, refactors, performance work, investigations, architecture…

Captures reusable agent context after a pull request's reviewer agents have approved.

Classify and route non-trivial software engineering work through the appropriate design, implementation, verification, and review skills.

Build MCP servers with well-named tools, workflow-oriented coverage, and clear errors.

Record architecture decisions with ADRs.

Use when starting a repo-grounded task, switching subsystems, or when output quality drops and the agent needs tighter project context from rules, specs…

Patterns for prerelease Effect applications.

Applies concrete Clean Code, SOLID, and Clean Architecture standards during implementation, review, or scoped refactoring.