repo-architect

---

What's in the box

Resource	Type	Purpose
autopilot	Pi Extension	Approval-gated workflow runner with continuation manifests and v2 flow.
bambu-slicer · plugin	Skill + Claude Code plugin	End-to-end Bambu Lab pipeline: OpenSCAD design, MakerWorld browsing, OrcaSlicer-backed STL→3MF, plate arrangement, printer control.
harness-audit	Skill (global-first)	Audits a repo for AI-harness readiness across the 10-artifact stack and dispatches surgical fixes.
scaffold-notes	Skill	Maintenance helper for adding resources to this repo consistently.
youtube-analyzer	Claude Code plugin	Format-aware YouTube video analysis with multi-agent transcript chunking.
critical-bug-hunt	Prompt template	Recent-commit audit for high-severity correctness bugs and minimal fixes.
hello	Example extension	Smoke-test scaffold exposing /agentic-utilities and agentic_utilities_ping.

The full catalog (with statuses) lives in docs/catalog.md.

Quick start

As a Pi package

pi -e .                    # try the package for one Pi run
pi install .               # install globally from this checkout
pi install -l .            # install into the current project's .pi/settings.json

After edits inside a running Pi session, run /reload.

Once published:

pi install git:github.com/AojdevStudio/agentic-utilities
pi install git:github.com/AojdevStudio/[email protected]

As a Claude Code marketplace

Add the marketplace, then install plugins from it:

/plugin marketplace add AojdevStudio/agentic-utilities
/plugin install bambu-slicer@agentic-utilities
/plugin install youtube-analyzer@agentic-utilities

The marketplace manifest is .claude-plugin/marketplace.json.

Layout

agentic-utilities/
├── .claude-plugin/         # Claude Code marketplace manifest
├── claude-code/plugins/    # Claude Code plugins (bambu-slicer, youtube-analyzer)
├── extensions/             # Pi extensions: TypeScript modules loaded by Pi
│   └── <name>/index.ts
├── skills/                 # Agent Skills: each skill owns a SKILL.md
│   └── <name>/SKILL.md
├── prompts/                # Prompt templates, named *.prompt.md
├── themes/                 # Pi theme JSON files
├── rules/                  # Authoritative rule files (extensions, skills, identity, secrets)
├── docs/                   # Catalog, conventions, autopilot reference, GC ritual
└── scripts/                # Local scaffolding (new-extension, new-skill, list-resources)

Add a resource

npm run new:extension -- my-extension "Short description"
npm run new:skill -- my-skill "Use when ..."
npm run list                                # inventory check

Conventions in one breath:

• Extensions → extensions/<kebab-name>/index.ts. Tool names use snake_case and are globally namespaced (e.g. agentic_utilities_ping).
• Skills → skills/<kebab-name>/SKILL.md, frontmatter name matches the directory. Daily-use skills are global-first: develop under ~/.pi/agent/skills/<name>/, then keep canonical files here and symlink the global skill back so Pi loads it globally and npm pack ships it.
• Prompts → prompts/<name>.prompt.md (the .prompt.md suffix keeps READMEs out of the prompt list).
• Themes → themes/<name>.json.
• Claude Code plugins → claude-code/plugins/<name>/, registered in .claude-plugin/marketplace.json.

Full conventions: docs/conventions.md. Authoritative rule files: rules/.

Verify before shipping

npm install
npm run lint
npm run typecheck
npm test
npm run check         # bundles lint + typecheck + tests
npm run pack:dry      # confirm tarball contents
pi -e .               # smoke-test the package