@bastani/atomic 0.6.8-0 → 0.7.0-1

package/.agents/skills/impeccable/scripts/pin.mjs

@@ -1,214 +0,0 @@
-#!/usr/bin/env node
-/**
- * Pin/unpin sub-commands as standalone skill shortcuts.
- *
- * Usage:
- *   node <scripts_path>/pin.mjs pin <command>
- *   node <scripts_path>/pin.mjs unpin <command>
- *
- * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit.
- * `unpin audit` removes that shortcut.
- *
- * The script discovers harness directories (.claude/skills, .cursor/skills, etc.)
- * in the project root and creates/removes the pin in all of them.
- */
-
-import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs';
-import { join, resolve, dirname } from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-const __dirname = dirname(fileURLToPath(import.meta.url));
-
-// All known harness directories
-const HARNESS_DIRS = [
-  '.claude', '.cursor', '.gemini', '.codex', '.agents',
-  '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev',
-];
-
-// Valid sub-command names
-const VALID_COMMANDS = [
-  'craft', 'teach', 'extract', 'document', 'shape',
-  'critique', 'audit',
-  'polish', 'bolder', 'quieter', 'distill', 'harden', 'onboard', 'live',
-  'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive',
-  'clarify', 'adapt', 'optimize',
-];
-
-// Marker to identify pinned skills (so unpin doesn't delete user skills)
-const PIN_MARKER = '<!-- impeccable-pinned-skill -->';
-
-/**
- * Walk up from startDir to find a project root.
- */
-function findProjectRoot(startDir = process.cwd()) {
-  let dir = resolve(startDir);
-  while (dir !== '/') {
-    if (
-      existsSync(join(dir, 'package.json')) ||
-      existsSync(join(dir, '.git')) ||
-      existsSync(join(dir, 'skills-lock.json'))
-    ) {
-      return dir;
-    }
-    const parent = resolve(dir, '..');
-    if (parent === dir) break;
-    dir = parent;
-  }
-  return resolve(startDir);
-}
-
-/**
- * Find harness skill directories that have an impeccable skill installed.
- */
-function findHarnessDirs(projectRoot) {
-  const dirs = [];
-  for (const harness of HARNESS_DIRS) {
-    const skillsDir = join(projectRoot, harness, 'skills');
-    // Only pin in harness dirs that already have impeccable installed
-    const impeccableDir = join(skillsDir, 'impeccable');
-    if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) {
-      dirs.push(skillsDir);
-    }
-  }
-  return dirs;
-}
-
-/**
- * Load command metadata (descriptions for pinned skills).
- */
-function loadCommandMetadata() {
-  const metadataPath = join(__dirname, 'command-metadata.json');
-  if (existsSync(metadataPath)) {
-    return JSON.parse(readFileSync(metadataPath, 'utf-8'));
-  }
-  return {};
-}
-
-/**
- * Generate a pinned skill's SKILL.md content.
- */
-function generatePinnedSkill(command, metadata) {
-  const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`;
-  const hint = metadata[command]?.argumentHint || '[target]';
-
-  return `---
-name: ${command}
-description: "${desc}"
-argument-hint: "${hint}"
-user-invocable: true
----
-
-${PIN_MARKER}
-
-This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`.
-
-Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions.
-`;
-}
-
-/**
- * Pin a command: create shortcut skill in all harness dirs.
- */
-function pin(command, projectRoot) {
-  const metadata = loadCommandMetadata();
-  const harnessDirs = findHarnessDirs(projectRoot);
-
-  if (harnessDirs.length === 0) {
-    console.log('No harness directories with impeccable installed found.');
-    return false;
-  }
-
-  const content = generatePinnedSkill(command, metadata);
-  let created = 0;
-
-  for (const skillsDir of harnessDirs) {
-    // Check if skill already exists (and isn't a pin)
-    const skillDir = join(skillsDir, command);
-    if (existsSync(skillDir)) {
-      const existingMd = join(skillDir, 'SKILL.md');
-      if (existsSync(existingMd)) {
-        const existing = readFileSync(existingMd, 'utf-8');
-        if (!existing.includes(PIN_MARKER)) {
-          console.log(`  SKIP: ${skillDir} (non-pinned skill already exists)`);
-          continue;
-        }
-      }
-    }
-
-    mkdirSync(skillDir, { recursive: true });
-    writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8');
-    console.log(`  + ${skillDir}`);
-    created++;
-  }
-
-  if (created > 0) {
-    console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`);
-    console.log(`You can now use /${command} directly.`);
-  }
-
-  return created > 0;
-}
-
-/**
- * Unpin a command: remove shortcut skill from all harness dirs.
- */
-function unpin(command, projectRoot) {
-  const harnessDirs = findHarnessDirs(projectRoot);
-  let removed = 0;
-
-  for (const skillsDir of harnessDirs) {
-    const skillDir = join(skillsDir, command);
-    if (!existsSync(skillDir)) continue;
-
-    const skillMd = join(skillDir, 'SKILL.md');
-    if (!existsSync(skillMd)) continue;
-
-    // Safety: only remove if it's a pinned skill
-    const content = readFileSync(skillMd, 'utf-8');
-    if (!content.includes(PIN_MARKER)) {
-      console.log(`  SKIP: ${skillDir} (not a pinned skill)`);
-      continue;
-    }
-
-    rmSync(skillDir, { recursive: true, force: true });
-    console.log(`  - ${skillDir}`);
-    removed++;
-  }
-
-  if (removed > 0) {
-    console.log(`\nUnpinned '${command}' from ${removed} location(s).`);
-    console.log(`Use /impeccable ${command} to access it.`);
-  } else {
-    console.log(`No pinned '${command}' shortcut found.`);
-  }
-
-  return removed > 0;
-}
-
-// --- CLI ---
-const [,, action, command] = process.argv;
-
-if (!action || !command) {
-  console.log('Usage: node pin.mjs <pin|unpin> <command>');
-  console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`);
-  process.exit(1);
-}
-
-if (action !== 'pin' && action !== 'unpin') {
-  console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`);
-  process.exit(1);
-}
-
-if (!VALID_COMMANDS.includes(command)) {
-  console.error(`Unknown command: ${command}`);
-  console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`);
-  process.exit(1);
-}
-
-const root = findProjectRoot();
-
-if (action === 'pin') {
-  pin(command, root);
-} else {
-  unpin(command, root);
-}

package/.agents/skills/init/SKILL.md

@@ -1,140 +0,0 @@
----
-name: init
-description: Generate CLAUDE.md and AGENTS.md by exploring the codebase
-metadata:
-  provider: atomic
----
-
-# Generate CLAUDE.md and AGENTS.md
-
-You are tasked with exploring the current codebase with the codebase-analyzer, codebase-locator, codebase-pattern-finder sub-agents, detecting the primary project languages, checking whether the corresponding language servers already exist on the user's machine, optionally installing any missing language servers after explicit user confirmation, and then generating populated `CLAUDE.md` and `AGENTS.md` files at the project root. These files provide coding agents with the context they need to work effectively in this repository.
-
-## Steps
-
-1. **Explore the codebase to discover project metadata:**
-    - Read `package.json`, `Cargo.toml`, `go.mod`, `pyproject.toml`, `Gemfile`, `pom.xml`, or similar manifest files
-    - Scan the top-level directory structure (`src/`, `lib/`, `app/`, `tests/`, `docs/`, etc.)
-    - Check for existing config files: `.eslintrc`, `tsconfig.json`, `biome.json`, `oxlint.json`, `.prettierrc`, CI configs (`.github/workflows/`, `.gitlab-ci.yml`), etc.
-    - Read `README.md` if it exists for project description and setup instructions
-    - Check for `.env.example`, `.env.local`, or similar environment files
-    - Identify the package manager (bun, npm, yarn, pnpm, cargo, go, pip, etc.)
-    - Identify the primary project languages from manifests, lockfiles, and source file extensions
-    - Inspect editor/tooling config such as `.vscode`, language-specific config files, or existing LSP settings when present
-
-2. **Identify key project attributes:**
-    - **Project name**: From manifest file or directory name
-    - **Project purpose**: 1-2 sentence description from README or manifest
-    - **Project structure**: Key directories and their purposes
-    - **Tech stack**: Language, framework, runtime
-    - **Detected languages**: The main implementation languages in the repo
-    - **Recommended LSPs**: The language servers that best match those languages
-    - **Commands**: dev, build, test, lint, typecheck, format (from scripts in manifest)
-    - **Environment setup**: Required env vars, env example files
-    - **Verification command**: The command to run before commits (usually lint + typecheck + test)
-    - **Existing documentation**: Links to docs within the repo
-
-3. **Detect installed language servers and prepare an installation plan:**
-    - For each detected language, choose the most standard LSP for that ecosystem and prefer already configured tooling when the repo clearly indicates a preference
-    - Check whether each LSP is already available by using non-destructive discovery commands such as `command -v`, `--version`, or equivalent read-only checks
-    - Use this default mapping unless the repo clearly points to a different choice:
-      - TypeScript / JavaScript -> `typescript-language-server` (and ensure `typescript` is available when required)
-      - Python -> `pyright`
-      - Go -> `gopls`
-      - Rust -> `rust-analyzer`
-      - Ruby -> `ruby-lsp`
-      - PHP -> `intelephense`
-      - Lua -> `lua-language-server`
-      - Bash / shell -> `bash-language-server`
-      - YAML -> `yaml-language-server`
-      - Docker -> `dockerfile-language-server-nodejs`
-      - Terraform -> `terraform-ls`
-      - Java -> `jdtls`
-      - Kotlin -> `kotlin-language-server`
-      - C / C++ -> `clangd`
-      - C# -> `csharp-ls`
-    - If an LSP is missing, prepare the safest install command that fits the user's available tooling and platform; do not guess a package manager that is not installed
-    - If the required runtime or package manager is missing, stop short of installation and report what is needed instead
-
-4. **Ask for confirmation before installing anything:**
-    - Summarize the detected languages, the LSPs already present, the LSPs that are missing, and the exact install commands you plan to run
-    - Ask the user for confirmation before running any install command
-    - If the user declines, skip installation and continue with documentation generation
-    - After installation, verify each newly installed LSP with a version check or binary lookup and mention any failures clearly
-
-5. **Populate the template below** with discovered values. Replace every `{{placeholder}}` with actual values from the repo. Delete sections that don't apply (e.g., Environment if there are no env files). Remove the "How to Fill This Template" meta-section entirely.
-
-6. **Write the populated content** to both `CLAUDE.md` and `AGENTS.md` at the project root with identical content.
-
-## Template
-
-```markdown
-# {{PROJECT_NAME}}
-
-## Overview
-
-{{1-2 sentences describing the project purpose}}
-
-## Project Structure
-
-| Path         | Type     | Purpose     |
-| ------------ | -------- | ----------- |
-| \`{{path}}\` | {{type}} | {{purpose}} |
-
-## Quick Reference
-
-### Languages and Tooling
-
-- Languages: {{comma-separated detected languages}}
-- LSPs: {{comma-separated installed or recommended language servers}}
-
-### Commands
-
-\`\`\`bash
-{{dev_command}} # Start dev server / all services
-{{build_command}} # Build the project
-{{test_command}} # Run tests
-{{lint_command}} # Lint & format check
-{{typecheck_command}} # Type-check (if applicable)
-\`\`\`
-
-### Environment
-
-- Copy \`{{env_example_file}}\` → \`{{env_local_file}}\` for local development
-- Required vars: {{comma-separated list of required env vars}}
-
-## Progressive Disclosure
-
-Read relevant docs before starting:
-| Topic | Location |
-| ----- | -------- |
-| {{topic}} | \`{{path_to_doc}}\` |
-
-## Universal Rules
-
-1. Run \`{{verify_command}}\` before commits
-2. Keep PRs focused on a single concern
-3. {{Add any project-specific universal rules}}
-
-## Code Quality
-
-Formatting and linting are handled by automated tools:
-
-- \`{{lint_command}}\` — {{linter/formatter names}}
-- \`{{format_command}}\` — Auto-fix formatting (if separate from lint)
-
-Run before committing. Don't manually check style—let tools do it.
-```
-
-## Important Notes
-
-- **Keep it under 100 lines** (ideally under 60) after populating
-- **Every instruction must be universally applicable** to all tasks in the repo
-- **No code style rules** — delegate to linters/formatters
-- **No task-specific instructions** — use the progressive disclosure table
-- **No code snippets** — use `file:line` pointers instead
-- **Include verification commands** the agent can run to validate work
-- **Never install tooling without an explicit user confirmation first**
-- **Prefer read-only discovery before installation** and verify any installed LSP afterward
-- Delete any section from the template that doesn't apply to this project
-- Do NOT include the "How to Fill This Template" section in the output
-- Write identical content to both `CLAUDE.md` and `AGENTS.md` at the project root

package/.agents/skills/liteparse/SKILL.md

@@ -1,223 +0,0 @@
----
-name: liteparse
-description: Use this skill when the user asks to parse, perform multi-format document conversion or spatially extract text from an unstructured file (PDF, DOCX, PPTX, XLSX, images, etc.) locally without cloud dependencies.
-compatibility: Requires Node 18+ and `@llamaindex/liteparse` installed globally via npm (`npm i -g @llamaindex/liteparse`)
-license: MIT
-metadata:
-  provider: atomic
-  author: LlamaIndex
-  version: "0.1.0"
----
-
-# LiteParse Skill
-
-Parse unstructured documents (PDF, DOCX, PPTX, XLSX, images, and more) locally with LiteParse: fast, lightweight, no cloud dependencies or LLM required.
-
-## Initial Setup
-
-When this skill is invoked, respond with:
-
-```
-I'm ready to use LiteParse to parse files locally. Before we begin, please confirm that:
-
-- `@llamaindex/liteparse` is installed globally (`npm i -g @llamaindex/liteparse`)
-- The `lit` CLI command is available in your terminal
-
-If both are set, please provide:
-
-1. One or more files to parse (PDF, DOCX, PPTX, XLSX, images, etc.)
-2. Any specific options: output format (json/text), page ranges, OCR preferences, DPI, etc.
-3. What you'd like to do with the parsed content.
-
-I will produce the appropriate `lit` CLI command or TypeScript script, and once approved, report the results.
-```
-
-Then wait for the user's input.
-
----
-
-## Step 0 — Install LiteParse (if needed)
-
-If `liteparse` is not yet installed, install it globally:
-
-```bash
-npm i -g @llamaindex/liteparse
-```
-
-Verify installation:
-
-```bash
-lit --version
-```
-
-For Office document support (DOCX, PPTX, XLSX), LibreOffice is required:
-
-```bash
-# macOS
-brew install --cask libreoffice
-
-# Ubuntu/Debian
-apt-get install libreoffice
-```
-
-For image parsing, ImageMagick is required:
-```bash
-# macOS
-brew install imagemagick
-
-# Ubuntu/Debian
-apt-get install imagemagick
-```
-
----
-
-## Step 1 — Produce the CLI Command or Script
-
-### Parse a Single File
-
-```bash
-# Basic text extraction
-lit parse document.pdf
-
-# JSON output saved to a file
-lit parse document.pdf --format json -o output.json
-
-# Specific page range
-lit parse document.pdf --target-pages "1-5,10,15-20"
-
-# Disable OCR (faster, text-only PDFs)
-lit parse document.pdf --no-ocr
-
-# Use an external HTTP OCR server for higher accuracy
-lit parse document.pdf --ocr-server-url http://localhost:8828/ocr
-
-# Higher DPI for better quality
-lit parse document.pdf --dpi 300
-```
-
-### Batch Parse a Directory
-
-```bash
-lit batch-parse ./input-directory ./output-directory
-
-# Only process PDFs, recursively
-lit batch-parse ./input ./output --extension .pdf --recursive
-```
-
-### Generate Page Screenshots
-
-Screenshots are useful for LLM agents that need to see visual layout.
-
-```bash
-# All pages
-lit screenshot document.pdf -o ./screenshots
-
-# Specific pages
-lit screenshot document.pdf --pages "1,3,5" -o ./screenshots
-
-# High-DPI PNG
-lit screenshot document.pdf --dpi 300 --format png -o ./screenshots
-
-# Page range
-lit screenshot document.pdf --pages "1-10" -o ./screenshots
-```
-
----
-
-## Step 3 — Key Options Reference
-
-### OCR Options
-
-| Option | Description |
-|--------|-------------|
-| (default) | Tesseract.js — zero setup, built-in |
-| `--ocr-language fra` | Set OCR language (ISO code) |
-| `--ocr-server-url <url>` | Use external HTTP OCR server (EasyOCR, PaddleOCR, custom) |
-| `--no-ocr` | Disable OCR entirely |
-
-### Output Options
-
-| Option | Description |
-|--------|-------------|
-| `--format json` | Structured JSON with bounding boxes |
-| `--format text` | Plain text (default) |
-| `-o <file>` | Save output to file |
-
-### Performance / Quality Options
-
-| Option | Description |
-|--------|-------------|
-| `--dpi <n>` | Rendering DPI (default: 150; use 300 for high quality) |
-| `--max-pages <n>` | Limit pages parsed |
-| `--target-pages <pages>` | Parse specific pages (e.g. `"1-5,10"`) |
-| `--no-precise-bbox` | Disable precise bounding boxes (faster) |
-| `--skip-diagonal-text` | Ignore rotated/diagonal text |
-| `--preserve-small-text` | Keep very small text that would otherwise be dropped |
-
----
-
-## Step 4 — Using a Config File
-
-For repeated use with consistent options, generate a `liteparse.config.json`:
-
-```json
-{
-  "ocrLanguage": "en",
-  "ocrEnabled": true,
-  "maxPages": 1000,
-  "dpi": 150,
-  "outputFormat": "json",
-  "preciseBoundingBox": true,
-  "skipDiagonalText": false,
-  "preserveVerySmallText": false
-}
-```
-
-For an HTTP OCR server:
-
-```json
-{
-  "ocrServerUrl": "http://localhost:8828/ocr",
-  "ocrLanguage": "en",
-  "outputFormat": "json"
-}
-```
-
-Use with:
-
-```bash
-lit parse document.pdf --config liteparse.config.json
-```
-
----
-
-## Step 5 — HTTP OCR Server API (Advanced)
-
-If the user wants to plug in a custom OCR backend, the server must implement:
-
-- **Endpoint**: `POST /ocr`
-- **Accepts**: `file` (multipart) and `language` (string) parameters
-- **Returns**:
-```json
-{
-  "results": [
-    { "text": "Hello", "bbox": [x1, y1, x2, y2], "confidence": 0.98 }
-  ]
-}
-```
-
-Ready-to-use wrappers exist for EasyOCR and PaddleOCR in the LiteParse repo.
-
----
-
-## Supported Input Formats
-
-| Category | Formats |
-|----------|---------|
-| PDF | `.pdf` |
-| Word | `.doc`, `.docx`, `.docm`, `.odt`, `.rtf` |
-| PowerPoint | `.ppt`, `.pptx`, `.pptm`, `.odp` |
-| Spreadsheets | `.xls`, `.xlsx`, `.xlsm`, `.ods`, `.csv`, `.tsv` |
-| Images | `.jpg`, `.jpeg`, `.png`, `.gif`, `.bmp`, `.tiff`, `.webp`, `.svg` |
-
-Office documents require LibreOffice; images require ImageMagick. LiteParse auto-converts these formats to PDF before parsing.