New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

@mobrienv/autoloop-presets

Package Overview
Dependencies
Maintainers
1
Versions
11
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@mobrienv/autoloop-presets

Bundled preset definitions (data-only) for autoloop

Source
npmnpm
Version
0.9.2
Version published
Weekly downloads
14
133.33%
Maintainers
1
Weekly downloads
 
Created
Source

@mobrienv/autoloop-presets

Bundled preset definitions for autoloop (data-only).

Each subdirectory under presets/ is a self-contained preset — a directory that autoloop recognizes as a project via its autoloops.toml and supporting role / topology files. Presets are static configuration plus prompt fragments; this package ships them as files only, no runtime code.

Shape

presets/
  autocode/
    autoloops.toml      # preset-as-project config
    harness.md          # system prompt fragment + metadata
    topology.toml       # role graph (optional)
    roles/*.md          # per-role prompts (optional)
    README.md           # "Use when/after …" description surfaced by `autoloop list`
  …

Consumption

@mobrienv/autoloop-cli resolves this package via require.resolve at runtime to locate bundled presets. @mobrienv/autoloop-core helpers (resolvePresetDir, resolveBundledPresetDir) fall back to this package's presets/ directory when no project-local or user-local preset is found.

Users override individual presets by dropping a same-named directory under $XDG_CONFIG_HOME/autoloop/presets/<name>/ — user presets win over bundled ones during resolution.

Adding a preset

  • Create presets/<name>/ with at minimum autoloops.toml and README.md.
  • Add <name> to the built-in list in packages/cli/src/chains/load.ts::listKnownPresets.
  • Follow the "Use when/after …" convention in the README description so the preset-list test passes.

FAQs

Package last updated on 13 Jul 2026

Related posts