Imported from MarcusFunt/ULP-Wearable-Module (AGENTS.md). Install upstream with npx skills add MarcusFunt/ULP-Wearable-Module. Copyright stays with the author.

Project Context

A TOML project with 15 files across 2 directories.

Stack

Languages:

• TOML (50%)
• Python (50%)

Frameworks & Tools:

• pytest (testing)

Commands

pytest  # test

Conventions

• Naming: mixed
• File organization: flat
• Config files: pyproject.toml

Architecture

Key directories:

• docs/ - Documentation
• scripts/ - Build/automation scripts

Boundaries

Always:

• Run pytest before committing changes
• Follow mixed naming convention
• Follow flat file organization

Ask first:

• Adding new dependencies
• Changing project configuration files

Never:

• Commit secrets, API keys, or .env files
• Delete or overwrite test files without understanding them
• Force push to main/master branch

GitNexus — Code Intelligence

This project is indexed by GitNexus as ULP-Wearable-Module (375 symbols, 494 relationships, 11 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.

Index stale? Run node .gitnexus/run.cjs analyze from the project root — it auto-selects an available runner. No .gitnexus/run.cjs yet? npx gitnexus analyze (npm 11 crash → npm i -g gitnexus; #1939).

Always Do

• MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run impact({target: "symbolName", direction: "upstream"}) and report the blast radius (direct callers, affected processes, risk level) to the user.
• MUST run detect_changes() before committing to verify your changes only affect expected symbols and execution flows. For regression review, compare against the default branch: detect_changes({scope: "compare", base_ref: "main"}).
• MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
• When exploring unfamiliar code, use query({query: "concept"}) to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
• When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use context({name: "symbolName"}).

Never Do

• NEVER edit a function, class, or method without first running impact on it.
• NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
• NEVER rename symbols with find-and-replace — use rename which understands the call graph.
• NEVER commit changes without running detect_changes() to check affected scope.

Resources

CLI