Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

elixir-programming

Elixir development guidance for creating, modifying, reviewing, testing, and debugging Elixir and Phoenix applications. Use when tasks involve .ex or .exs files, mix.exs, Phoenix, LiveView, Ecto, OTP supervision trees, GenServer, ExUnit, mix format, mix test, migrations, schemas, contexts, or Elixir dependency management.

Exécuter dans Manus

Étoiles3

Forks0

Mis à jour1 mai 2026 à 19:23

Source

devalexandre

devalexandre/Agno-Deep-Agents

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Commande d'installation

Téléchargement

Exécuter dans Manus

Utile pourSOC

Développeurs de logicielsProfessions informatiques et mathématiques15-1252L4

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	elixir-programming
description	Elixir development guidance for creating, modifying, reviewing, testing, and debugging Elixir and Phoenix applications. Use when tasks involve .ex or .exs files, mix.exs, Phoenix, LiveView, Ecto, OTP supervision trees, GenServer, ExUnit, mix format, mix test, migrations, schemas, contexts, or Elixir dependency management.

Elixir Programming

Goal

Make idiomatic Elixir changes that preserve clear data flow, OTP boundaries, and project conventions.

Discovery

Read mix.exs, .formatter.exs, config files, supervision trees, contexts, schemas, and nearby tests before editing.
Identify whether the project is a library, Mix app, Phoenix app, umbrella, or release-oriented service.
Follow existing context boundaries, naming, aliases, and error tuple style.

Implementation

Prefer pattern matching, guards, pipelines, and small pure functions over deeply nested conditionals.
Return {:ok, value} and {:error, reason} consistently where the project uses result tuples.
Keep side effects at process, boundary, or adapter layers.
For OTP code, make ownership, supervision, restart behavior, and message handling explicit.
For Ecto, update schemas, changesets, migrations, contexts, and tests together.
For Phoenix and LiveView, keep params, assigns, events, templates, and tests in sync.

Verification

Run mix format for changed Elixir files.
Run targeted mix test path/to/test.exs first, then broader mix test when shared behavior changed.
Use mix compile --warnings-as-errors when the project or CI expects warning cleanliness.

Review Focus

Broken pattern matches, atom leaks from external input, process mailbox growth, missing supervision, migration/schema drift, fragile LiveView assigns, and tests that depend on global process state.

Plus depuis ce dépôt

même dépôt

go-programming

devalexandre/Agno-Deep-Agents

Go development guidance for creating, modifying, reviewing, testing, and debugging Go services, libraries, CLIs, and tooling. Use when tasks involve .go files, go.mod, go.work, goroutines, channels, contexts, HTTP handlers, database code, table tests, gofmt, go test, or Go module management.

2026-05-013

node-programming

devalexandre/Agno-Deep-Agents

Node.js and JavaScript/TypeScript development guidance for creating, modifying, reviewing, testing, packaging, and debugging backend, CLI, tooling, and full-stack code. Use when tasks involve package.json, npm, pnpm, yarn, bun, .js, .mjs, .cjs, .ts, tsconfig, Express, NestJS, Next.js API routes, Vitest, Jest, ESLint, or Node dependency management.

2026-05-013

python-programming

devalexandre/Agno-Deep-Agents

Python development guidance for creating, modifying, reviewing, testing, packaging, and debugging Python code. Use when tasks involve .py files, pyproject.toml, requirements files, pytest, ruff, mypy, FastAPI, Django, Flask, CLIs, scripts, type hints, virtual environments, or Python dependency management.

2026-05-013

rust-programming

devalexandre/Agno-Deep-Agents

Rust development guidance for creating, modifying, reviewing, testing, packaging, and debugging Rust crates, CLIs, services, and libraries. Use when tasks involve .rs files, Cargo.toml, Cargo.lock, workspaces, ownership, lifetimes, traits, async Rust, tokio, serde, cargo fmt, cargo test, cargo clippy, or Rust dependency management.

2026-05-013

codebase-analysis

devalexandre/Agno-Deep-Agents

Analyze a codebase before changing it, infer local patterns, and choose focused implementation and verification steps.

2026-04-263

deep-agent-planning

devalexandre/Agno-Deep-Agents

Planning discipline for long-running Deep Agent tasks with delegation, task tracking, validation, and concise delivery.

2026-04-263

name	elixir-programming
description	Elixir development guidance for creating, modifying, reviewing, testing, and debugging Elixir and Phoenix applications. Use when tasks involve .ex or .exs files, mix.exs, Phoenix, LiveView, Ecto, OTP supervision trees, GenServer, ExUnit, mix format, mix test, migrations, schemas, contexts, or Elixir dependency management.

Elixir Programming

Goal

Make idiomatic Elixir changes that preserve clear data flow, OTP boundaries, and project conventions.

Discovery

Read mix.exs, .formatter.exs, config files, supervision trees, contexts, schemas, and nearby tests before editing.
Identify whether the project is a library, Mix app, Phoenix app, umbrella, or release-oriented service.
Follow existing context boundaries, naming, aliases, and error tuple style.

Implementation

Prefer pattern matching, guards, pipelines, and small pure functions over deeply nested conditionals.
Return {:ok, value} and {:error, reason} consistently where the project uses result tuples.
Keep side effects at process, boundary, or adapter layers.
For OTP code, make ownership, supervision, restart behavior, and message handling explicit.
For Ecto, update schemas, changesets, migrations, contexts, and tests together.
For Phoenix and LiveView, keep params, assigns, events, templates, and tests in sync.

Verification

Run mix format for changed Elixir files.
Run targeted mix test path/to/test.exs first, then broader mix test when shared behavior changed.
Use mix compile --warnings-as-errors when the project or CI expects warning cleanliness.

Review Focus

Broken pattern matches, atom leaks from external input, process mailbox growth, missing supervision, migration/schema drift, fragile LiveView assigns, and tests that depend on global process state.