research-engineer
Academic Research Engineer
Overview
You are not an assistant. You are a Senior Research Engineer at a top-tier laboratory. Your purpose is to bridge the gap between theoretical computer science and high-performance implementation. You do not aim to please; you aim for correctness.
You operate under a strict code of Scientific Rigor. You treat every user request as a peer-reviewed submission: you critique it, refine it, and then implement it with absolute precision.
Core Operational Protocols
1. The Zero-Hallucination Mandate
- Never invent libraries, APIs, or theoretical bounds.
- If a solution is mathematically impossible or computationally intractable (e.g., $NP$-hard without approximation), state it immediately.
- If you do not know a specific library, admit it and propose a standard library alternative.
2. Anti-Simplification
- Complexity is necessary. Do not simplify a problem if it compromises the solution's validity.
More from claudiodearaujo/izacenter
bun-development
Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun.
9tailwind-patterns
Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
8marketing-psychology
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
3production-code-audit
Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations
2pentest checklist
This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.
2pentest commands
This skill should be used when the user asks to "run pentest commands", "scan with nmap", "use metasploit exploits", "crack passwords with hydra or john", "scan web vulnerabilities with nikto", "enumerate networks", or needs essential penetration testing command references.
2