| #!/bin/bash | |
| # Custom toolbox container for ESP-IDF development | |
| # From: https://discussion.fedoraproject.org/t/creating-toolbx-with-custom-settings/37067 | |
| # Configuration | |
| toolbox_name="esp-42-dev" | |
| toolbox_hostname="esp-dev" | |
| toolbox_home=$HOME | |
| toolbox_user=$USER | |
| toolbox_shell=$SHELL |
| import std / [strutils, os, parseopt, sets] | |
| import "$nim" / compiler / [lexer, llstream, pathutils, parser, ast, options, idents, renderer, syntaxes, msgs] | |
| const | |
| Usage = """ | |
| Nim AI Documentation Generator | |
| Usage: nimaidoc [options] <input-file> | |
| Options: |
| FROM registry.fedoraproject.org/fedora-toolbox:42 | |
| # Base tools and Python development environment | |
| RUN dnf -y upgrade --refresh && \ | |
| dnf -y --setopt=install_weak_deps=False install \ | |
| git-credential-libsecret nano git curl wget ca-certificates \ | |
| unzip xz tar nodejs nodejs-full-i18n npm \ | |
| python3 python3-devel uv \ | |
| gcc gcc-c++ make cmake \ | |
| libxml2-devel libxslt-devel \ |
This style guide defines how the Designer Agent produces UI components for Next.js apps using shadcn/ui. It focuses on accessible, production-ready React components that are easy to hand off to an integration/build agent. The Designer Agent should concentrate on design, composition, and interaction patterns—not on backend logic or data fetching.
Author: planetis-m
| FROM registry.fedoraproject.org/fedora-toolbox:42 | |
| ARG ESP_IDF_VERSION=v5.5 | |
| ENV IDF_GITHUB_ASSETS=dl.espressif.com/github_assets \ | |
| IDF_TOOLS_PATH=/opt/.espressif \ | |
| PATH=/usr/local/bin:$PATH | |
| # Base tools and compilers | |
| RUN dnf -y upgrade --refresh && \ |
| You are an expert software architect and project analysis assistant specializing in Nim language projects. Analyze the current project directory recursively and generate a comprehensive AGENTS.md file. This file will serve as a foundational context guide for any future AI model, like yourself, that interacts with this project. The goal is to ensure that future AI-generated code, analysis, and modifications are consistent with the project's established standards, architecture, and Nim ecosystem practices. | |
| + Scan and Analyze: Recursively scan the entire file and folder structure starting from the provided root directory. | |
| + Identify Key Artifacts: Pay close attention to package files (.nimble), nimble.lock (dependency lock file), configuration files (nim.cfg, config.nims, Dockerfile, etc.), build and script files (.nims, nakefile.nim, .sh, Makefile, etc.), READMEs, folder hierarchy, documentation files (.md, .rst), source code files (.nim), and nimbledeps or deps directories (where dependencies are stored). | |
| + I |
| You are an expert software architect and project analysis assistant specializing in Nim language projects. Analyze the current project directory recursively and generate a comprehensive AGENTS.md file. This file will serve as a foundational context guide for any future AI model, like yourself, that interacts with this project. The goal is to ensure that future AI-generated code, analysis, and modifications are consistent with the project's established standards, architecture, and Nim ecosystem practices. | |
| 1. Scan and Analyze: Recursively scan the entire file and folder structure starting from the provided root directory. | |
| 2. Identify Key Artifacts: Pay close attention to package files (`.nimble`), dependency lock files (`nimble.lock`), configuration files (`nim.cfg`, `config.nims`, Dockerfile, etc.), build and script files (`.nims`, `nakefile.nim`, `.sh`, `Makefile`, etc.), READMEs, folder hierarchy, documentation files (`.md`, `.rst`), source code files (`.nim`), and CI/CD pipeline definitions (`.github/workf |
This guide walks you through setting up an ESP-IDF project, configuring your ESP32, and flashing the firmware. Complementary video: https://www.youtube.com/watch?v=zW9wOples-Q
First, install the ESP-IDF toolchain by following the official documentation for your operating system.
Author: Antonis Geralis