Laravel and PHP 8.4 framework-level guidance covering architecture, Eloquent, migrations, queues, and testing, grounded in real failure modes.
Publisher
Skills by iliaal
32 published skills, 911 installs in total.
Diagnoses software bugs through a 7-step process anchored to a failing reproduction before any fix.
Run spec-first code reviews with severity-ranked findings and an optional multi-agent deep mode.
Get an approved design document before writing a single line of code.
Write tests that verify real behavior—not mocks—with named scenarios, edge cases, and silent-failure coverage.
Tailwind CSS v4 patterns: CSS-first config, @theme tokens, component variants, and v3 migration fixes.
Structured implementation plans with durable .plan/ state, scoped phases, and explicit decision rules.
Simplify code without changing behavior, with guardrails for AI slop and ambiguous edits.
Review documents for gaps, clarity, completeness, and organization before the next workflow step.
React, TypeScript, and Next.js patterns for components, state, performance, and testing.
Patterns for building production Node.js backends: layered architecture, validation, error handling, and observability.
Python patterns for CLI tools, async services, background jobs, and modern tooling like uv, ruff, and ty.
Rewrite prose to strip AI tells while preserving voice, or audit a draft for AI patterns without rewriting.
PostgreSQL schema design, query optimization, indexing, and administration. Use when working with PostgreSQL, JSONB, partitioning, RLS, CTEs, window functions, or EXPLAIN ANALYZE.
Manages project documentation: CLAUDE.md, AGENTS.md, README.md, CONTRIBUTING.md, DOCS.md. Use when asked to update, create, or init these context files. Not for general markdown editing.
Rust patterns for CLI tools, backend services, and general application code. Use when working with Rust, Cargo workspaces, axum/tokio services, clap CLIs, async concurrency, or configuring clippy, rustfmt, cargo-nextest, or Cargo.toml.
Enforces fresh verification evidence before any completion claim. Use when about to claim "tests pass", "bug fixed", "done", "ready to merge", handing off work, or before editing when a request has ambiguous scope.
Visual design and aesthetic direction for frontend interfaces. Use when building web pages, landing pages, dashboards, Next.js server components, or applications where visual identity matters. For React patterns and testing, use react-frontend.
Coordinate multi-agent swarms for parallel and pipeline workflows. Use when coordinating multiple agents, running parallel reviews, building pipeline workflows, or implementing divide-and-conquer patterns with subagents.
Transforms vague prompts into precise, structured AI instructions. Use when asked to refine, improve, or sharpen a prompt, do prompt engineering, write a system prompt, or make AI instructions more effective.
Manage Git worktrees for isolated parallel development. Use when creating, listing, switching, or cleaning up git worktrees, or when needing isolated branches for concurrent reviews or feature work.
Terraform and OpenTofu configuration, modules, testing, state management, and HCL review. Use when working with Terraform, OpenTofu, HCL, tfvars, tftest, state migration, or IaC patterns.
Process code review feedback critically: check correctness before acting, push back on incorrect suggestions, no performative agreement. Use when responding to PR/MR review comments or implementing reviewer suggestions received from others.
Design agent-native applications where agents replace UI users as the primary actor. Use when designing MCP tools, agent-loop architectures, system prompt design, hooks policy, shared-workspace file patterns, or self-modifying agent systems.
Session retrospective and skill audit. Use when asked to reflect, do a retrospective, review lessons learned, audit what went well or wrong, or review session effectiveness.
Defensive Bash scripting for Linux: safe foundations, argument parsing, production patterns, ShellCheck compliance. Use when writing bash scripts, shell scripts, cron jobs, or CLI tools in bash.
Structured decision modifiers (/think, /verify, /adversarial, /edge, /confidence, /assumptions, etc.) to stress-test conclusions, evidence, assumptions, alternatives, and edge cases. Use when validating an important design, architecture decision, or ambiguous plan before committing.
Pine Script v6: syntax, performance, error diagnosis, backtesting, visualization. Use when writing or debugging `.pine` files or TradingView Pine indicators/strategies.
Capture solved problems for team reuse.
Manage persistent project todos in files.
Modern C++ patterns: RAII and ownership, rule of zero/five, exceptions and error handling, API and ABI boundaries, templates, and CMake tooling. Use when writing, reviewing, refactoring, or debugging C++, working with smart pointers, move semantics, memory leaks, template errors, or gtest. For plain C, see ia-c-systems.
C patterns for systems code, libraries, and native extensions: module layout, function decomposition, status-enum errors, memory safety, undefined behavior, and performance measurement. Use when writing, reviewing, refactoring, or debugging C, working with malloc lifetimes, buffer overflows, sanitizers, or Valgrind, or building native extensions. For C++, see ia-cpp-systems.
About Ottermind skills
Every published skill from iliaal. Following a publisher whose work already fits how you operate is often faster than evaluating individual skills one at a time.
Skills cover the full range of what an Ottermind agent does: building editable PowerPoint decks, generating product and brand images, writing and running code on a machine you connect, producing video from a script or a still, and cleaning and analysing spreadsheet data. A skill is what turns a general model into something that handles your specific version of one of those jobs the same way every time.
A skill is a plain Markdown file with a short frontmatter header, which means you can read exactly what it will do before running it, edit it to match your own conventions, and share it with colleagues. Once a skill produces the result you wanted, it can be attached to an agent or scheduled as an automation so the same work happens again without anyone rewriting the prompt.
- What is an Ottermind skill?
- A reusable instruction package written in Markdown. It gives an agent the context, steps, and constraints for one kind of task, so results stay consistent instead of depending on how well you phrased the prompt that day.
- How do I install and use a skill?
- Open any skill's detail page, read the full document, and install it into your workspace. From then on the agent can use it automatically when the task matches, or you can invoke it by name.
- Can I create my own skill?
- Yes. A skill is a Markdown file with frontmatter naming it and describing when it should be used. If you have a workflow you keep re-explaining to an agent, writing it down once as a skill is usually the shortest path to making it repeatable.
- Do skills cost extra?
- Browsing and installing skills from this library does not cost anything on its own. Running one consumes the same credits as any other agent task, depending on the model you choose and how much work the task involves.