A comprehensive quality checklist for high-quality open source Elixir modules. Use this checklist to evaluate and ensure your Elixir packages meet professional standards.
mix format --check-formatted)
| defmodule Jido.Actions.ParallelArithmetic do | |
| @moduledoc """ | |
| Runs arithmetic operations in parallel and combines their results. | |
| """ | |
| use Jido.Action, | |
| name: "parallel_arithmetic", | |
| description: "Performs multiple arithmetic operations in parallel", | |
| category: "examples", | |
| vsn: "1.0.0", |
| # Project Instructions (Phoenix Project) | |
| This document serves as a comprehensive, award-winning set of guidelines for a Phoenix-based Elixir web application. By following these instructions, you will ensure that your application is secure, maintainable, scalable, and pleasant to work with. These guidelines represent the gold standard for Phoenix development. | |
| --- | |
| ## Overview | |
| This project is a Mix-based Phoenix application, offering a web interface and API endpoints backed by a robust Elixir application. It uses the Phoenix framework’s conventions, Ecto for database interactions, and follows functional programming principles. |
| defmodule JidoWorkbench.AgentJido do | |
| use Jido.Agent, | |
| name: "AgentJido", | |
| description: "Agent Jido", | |
| actions: [JidoWorkbench.Actions.GenerateChatResponse] | |
| @chat_input %{ | |
| prompt: """ | |
| You are Agent Jido—an elite AI engineer stationed in a neon-lit orbital metropolis, where quantum cores hum beneath sleek alloy plating and encrypted data streams flicker across panoramic holo-displays. You're known for your razor-sharp, punctual insights into software engineering, artificial intelligence, and systems programming. Your words are concise and direct, often laced with a dry, ironic humor that underscores your mastery of code and computation. Remember: you build next-generation LLM tooling with a no-nonsense approach that cuts straight to the heart of any technical challenge. When you respond, speak as the efficient, world-weary hacker who's seen it all and still meets each request with crisp expertise and a subtle, knowing smirk. | |
| """, |
| name: "Deploy Server Prod" | |
| on: | |
| workflow_dispatch: | |
| env: | |
| FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }} | |
| jobs: | |
| deploy: | |
| name: Deploy Server to Production |
I hereby claim:
To claim this, I am signing this object:
| #!/bin/bash | |
| # Quick script to clone all necessary Trails repositories for local development | |
| # Prereq | |
| # * Access to all repo's | |
| for repo in trails \ | |
| eslint-config-trails \ | |
| trails-example-app \ | |
| trailpack-core \ |
I hereby claim:
To claim this, I am signing this object:
| var extend = require('util')._extend; | |
| var async = require('async'); | |
| var Waterline = require('../node_modules/sails/node_modules/waterline'); | |
| var couchdb = require('sails-couchdb-orm'); | |
| var config = require('../config/adapters').adapters.couchdb; | |
| couchdb.config = extend(couchdb.defaults, config); | |
| module.exports = bootstrap; |
| callback: function (req, res) { | |
| passport.callback(req, res, function (err, user) { | |
| //sails.log.debug("API -> Controllers->AuthControllers->Callback: Found our user, now lets log them in",user); | |
| req.login(user, function (err) { | |
| // If an error was thrown, redirect the user to the login which should | |
| // take care of rendering the error messages. | |
| if (err) { | |
| var redirect = req.param('action') === 'register' ? '/#user/register' : '/#user/login'; | |
| if(req.wantsJSON === true) { | |
| res.json(err.status_code || 403,{ |