steroid-scan

Files (1)

• SKILL.md

SKILL.md (first lines)

# Steroid Scan (Codebase Awareness)

This skill runs **before** vibe capture. It builds a `context.md` snapshot of the existing codebase so all downstream phases know what already exists. Without this, the AI works blind — proposing architectures that conflict with existing code, missing available libraries, and duplicating logic.

## Governed Baseline

The live governed authority for this phase is:

- `Steroid runtime contract`
- `Steroid runtime contract`
- `Steroid runtime contract`
- `Steroid runtime contract`

In the live repo, this skill is the execution surface for the governed `steroid-scan-system`.

The governed live scan artifacts are:

- `.memory/changes/<feature>/request.json`
- `.memory/changes/<feature>/context.md`

This skill is adapted from the Steroid Codebase Mapper (see `Steroid internal reference`) and the Steroid AGENTS.md system (see `Steroid internal reference`).

## The Circuit Breaker Mandate

All terminal commands executed by this skill MUST be wrapped in the physical Node.js circuit breaker:

```
node steroid-run.cjs '<command>'
```

For file inspection on hardened or Windows environments, prefer shell-free subcommands like `node steroid-run.cjs fs-cat ...`, `node steroid-run.cjs fs-find ...`, `node steroid-run.cjs fs-grep ...`, and `node steroid-run.cjs fs-ls ...`. Do not fall back to `Get-Content`, `cat`, `type`, `find`, `grep`, pipes, or redirection just to inspect code.

Direct terminal commands are strictly forbidden. See `skills/steroid-engine/SKILL.md` for the full mandate.

## When To Run

This skill triggers automatically when the user expresses intent to build, fix, refactor, migrate, or document something. It runs ONCE per feature, BEFORE the vibe capture phase.

If `.memory/changes/<feature>/context.md` already exists and is less than 24 hours old, skip the scan and report: "✅ Context already captured for this feature."

## The Scan Process

### Step 0: Capture Request Receipt

Before writing `context.md`, create `.memory/changes/<feature>/request.json`.

This is the governed live `feature_request` artifact for the scan slice. It should minimally record:

- `feature`
- `source: scan`
- `requested_at`
- `summary`

The summary may be brief if the raw user request is sparse. The point of this receipt is durable intake identity for the scan phase, not full prompt interpretation.

### Step 1: Detect Tech Stack

Read the project's package manifest to identify language, framework, and key dependencies.

```bash
# Node.js projects
node steroid-run.cjs fs-cat package.json --head=80 --optional

# Python projects  
node steroid-run.cjs fs-cat requirements.txt pyproject.toml --head=50 --optional

# Go projects
node steroid-run.cjs fs-cat go.mod --head=30 --optional

# Rust projects
node steroid-run.cjs fs-cat Cargo.toml --head=30 --optional

# Java/Kotlin projects (v5.4.0)
node steroid-run.cjs fs-cat pom.xml build.gradle --head=40 --optional

# Ruby projects (v5.4.0)
node steroid-run.cjs fs-cat Gemfile --head=30 --optional

# PHP projects (v5.4.0)
node steroid-run.cjs fs-cat composer.json --head=40 --optional

# .NET/C# projects (v5.4.0)
node steroid-run.cjs fs-find . --name=*.csproj --name=*.fsproj --type=file --max-depth=2 --limit=5

# Flutter/Dart projects (v5.4.0)
node steroid-run.cjs fs-cat pubspec.yaml --head=30 --optional
```

Check ALL of the above — a project may use multiple languages (e.g., Node.js frontend + Python backend).

Extract:
- Primary language and version (may be multiple for monorepos)
- Framework (React, Next.js, Express, Django, Spring, Rails, Laravel, etc.)
- Key dependencies (database clients, auth libraries, UI frameworks)
- Build tool (Vite, Webpack, esbuild, Maven, Gradle, Cargo, etc.)

### Step 2: Map Project Structure

Build a condensed file tree (max 2 levels deep, exclude noise directories).

```bash
node steroid-run.cjs fs-ls .
```

Identify:
- Entry points (`src/index.*`, `src/main.*`, `app/page.*`, `src/App.*`)
- API routes (if web project)
- Component directories (if frontend)
- Service/model layers (if backend)

### Step 3: Load Existing Patterns

Check for project-level AI instructions and learnings.

**Source: Steroid AGENTS.md system** (see `Steroid internal reference`)

```bash
# Check for existing AI instructions
node steroid-run.cjs fs-cat AGENTS.md CLAUDE.md GEMINI.md --head=100 --optional

From nzkbuild/steroid-workflow, MIT.

More from nzkbuild/steroid-workflow