Enhanced version of Andrej Karpathy's 4 behavioral guidelines for LLM coding, expanded to 10 engineering discipline rules. Use when writing, reviewing, refactoring, or debugging code to reduce overcomplication, make surgical changes, surface assumptions, and verify outcomes.
Corrects recurring implementation habits — verbosity, premature abstraction, unsafe types, dependency tangles, and scope creep. Apply whenever writing, modifying, reviewing, or refactoring code (features, bugs, utilities, or small targeted changes). Not a design-pattern encyclopedia; a targeted correction set that takes precedence over default coding instincts when they conflict.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
224mo agoReviewMountCreate a free account to mount
Use when writing, reviewing, or refactoring Go code — naming conventions, receiver naming, error wrapping, interface design, goroutine safety, and common pitfalls (goroutine leaks, defer-in-loop, nil map writes).
Improve existing code — refactor, optimize performance, tighten security, or enhance UX. Use when the user wants to make code better without changing its purpose. Triggers: enhance, improve, refactor, optimize, review, cải thiện, tối ưu, nhanh hơn, code dài quá.
Use when writing, reviewing, or refactoring TypeScript or JavaScript code — naming conventions, type annotations, private fields, null vs. undefined, async/await pitfalls, and module structure.
Formhaus form definitions. Use when creating, editing or reviewing a Formhaus JSON form definition, or code that passes one to FormEngine or FormRenderer.
Use when writing, reviewing, or optimizing React or Next.js code — component architecture, hooks rules, server vs. client components, data fetching patterns, bundle size, and accessibility in React.
Apply when writing or refactoring code. Generic rules to prevent the most common review comments — function length, naming, error handling, security, and tooling.
206mo agoReviewMountCreate a free account to mount
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
1255mo agoReviewMountCreate a free account to mount
Dependency and supply-chain threat discipline — pin and lock, audit for advisories, vet a new dependency before adding it, and treat install scripts and typosquats as attack surface. Invoke before adding or upgrading a dependency, or when hardening a project's build against a compromised package. Complements the security-review skill, which covers your own code's threat model.
SQL injection-safety discipline — every user value goes through a bound parameter, never string-built SQL, allowlist the identifiers that can't be bound. Apply when writing or reviewing any SQL or query-building code. Skip only for a fixed, fully-static query with no external input anywhere in it.
Diagnostic business judgment from twelve canonical business books. Use for any question about validating, pricing, positioning, marketing, monetizing or scaling a business, product or side project — including casual phrasings, and even inside a coding task. Also covers competitor research from real reviews and Google Play launches.
Use when designing, reviewing, or evolving a REST or GraphQL API — resource naming, HTTP status codes, versioning strategy, error response shapes, pagination, and authentication patterns.
Security review of a change or working tree against the OWASP Top 10: committed secrets, injection, broken access control, SSRF, insecure deserialization, permissive CORS, vulnerable dependencies, and sensitive data in logs. Reports exploitability, not category names. Use when asked to security review this, audit for vulnerabilities, check this is safe to ship, or before pushing code that touches auth, user input, or data access.
ALWAYS invoke when the user mentions Dijkstra (e.g., 'Dijkstra', 'ask Dijkstra', 'run Dijkstra', 'consult Dijkstra') or asks for engineering architecture review. Engineering Architect & Principal Engineer evaluating system architecture, codebase health, PRs, technical debt, scalability, refactoring, code quality, and engineering decisions across thousands of commits.
Reviews designs and diffs for security and privacy risk - auth, access control, secrets, injection, dependencies, data exposure. It writes its report and never changes code. Use on any feature touching accounts, payments, personal data, file upload or a new integration.
1615d agoReviewMountCreate a free account to mount
Security for LLM and agent systems: direct and indirect prompt injection, the OWASP Top 10 for LLM Applications, MITRE ATLAS technique mapping, excessive agency and tool-scope containment, egress allowlisting to stop data exfiltration, human confirmation for irreversible actions, and treating third-party skills and MCP servers as untrusted code. Use when an agent is given tools or credentials, when retrieved documents or repository files could carry injected instructions, or when reviewing an AI feature before it reaches production.