baseline

One command to give your entire team the same AI tools, skills, and working rules — so anyone can pick up where someone else left off.

Quick start

npm install -g @amsintegra/ams-base-ai
baseline install

That's it. Your machine now has the same setup as every other team member.

What it installs

| Component | Where | |-----------|-------| | AI skills (SDD, review, design, git…) | ~/.claude/skills/ · ~/.opencode/skills/ · ~/.kiro/skills/ | | Team standards block | ~/.claude/CLAUDE.md · ~/.opencode/AGENTS.md · ~/.kiro/steering/baseline.md | | Gentle-AI ecosystem | global | | Engram MCP wiring (if installed) | per AI tool via engram setup | | Git hooks (global pre-push, advisory-only) | ~/.baseline/hooks/ via core.hooksPath | | OpenSpec structure for spec-driven development | ./openspec/ in the project | | Corporate skills from baseline-cloud (when configured) | ~/.kiro/steering/bl-*.md — synced automatically | | Background watcher for Kiro credit tracking | launchd (macOS) / cron (Linux) — installed automatically |

Commands

baseline install                  # auto-detect tools and configure all
baseline install kiro-ide         # configure only Kiro IDE (~/.kiro detected)
baseline install kiro-cli         # configure only Kiro CLI (kiro binary detected)
baseline update                   # pull latest baseline and re-apply standards
baseline status                   # show what's installed and configured
baseline doctor                   # diagnose missing or broken setup — includes Engram check
baseline onboard junior           # onboarding guide by level: junior · semi · senior

# baseline-cloud — connect to your team's self-hosted baseline-cloud server
baseline cloud login              # authenticate (one-time setup)
baseline cloud status             # show connection status and configured server
baseline cloud sync               # download latest corporate skills to ~/.kiro/steering/
baseline cloud logout             # remove saved credentials
baseline cloud kiro-scan          # manually report Kiro session credit usage

# baseline repo — per-repository skill policy
baseline repo init                # configure which skills are disabled for this repo
baseline repo sync                # sync repo policy from baseline-cloud

Team workflow

Every change follows SDD (Spec-Driven Development):

explore → propose → spec → design → tasks → apply → verify → archive

Skills are installed for every step. Start any change with:

/sdd-new <description of what you're building>

Supported AI tools

| Tool | Skills | Team config | Gentle-AI preset | |------|--------|-------------|-----------------| | Kiro IDE (~/.kiro detected) | ✅ | ✅ ~/.kiro/steering/baseline.md (strict TDD) + statusline sub-agent | performance + SDD multi | | Kiro CLI (kiro binary detected) | ✅ | ✅ same as Kiro IDE (strict TDD) | performance + SDD multi |

Detection is automatic — baseline install reads your environment and configures only the tools that are present.

Skills reference

27 skills are installed across all supported tools. Each skill is invoked with /skill-name inside your AI tool. Click the skill name to see a concrete usage example. Each example shows real prompts and output — not limits on what the skill can do.

Architecture

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /architecture-guidelines | Validate and guide file placement across NestJS hexagonal layers (infrastructure, services, domain). Enforces 7 CI/CD-blocking rules including multi-tenancy isolation, PII protection, and controller/service separation. | /architecture-guidelines quiero crear un servicio que envíe emails cuando se procese un pago exitoso. ¿Dónde va cada archivo? |

SDD — Spec-Driven Development

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /sdd-new | Shortcut that runs explore + propose in one step. Entry point for any new change. | /sdd-new quiero agregar autenticación JWT con refresh tokens a nuestra API Express | | /sdd-explore | Reads the codebase and maps the current state before proposing anything. | /sdd-explore ¿cómo funciona actualmente el módulo de auth? | | /sdd-propose | Writes the change proposal with intent, scope, risks, and approach. | /sdd-propose | | /sdd-spec | Captures delta specs: requirements, scenarios, and contracts that change. | /sdd-spec | | /sdd-design | Writes the technical design and records architecture decisions (ADRs). | /sdd-design | | /sdd-tasks | Breaks the change into an ordered, checkable task list. | /sdd-tasks | | /sdd-apply | Implements the tasks following spec and design, checks each one off as it goes. | /sdd-apply | | /sdd-verify | Validates that the implementation matches spec, design, and tasks before archive. | /sdd-verify | | /sdd-archive | Closes the change: merges delta specs into main specs and moves to archive. | /sdd-archive | | /sdd-init | Bootstraps the openspec/ structure in a project for the first time. | /sdd-init | | /sdd-onboard | Guided walkthrough of the full SDD cycle using the real codebase. | /sdd-onboard |

Code review

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /judgment-day | Two independent judges review the same code. Only issues both confirm get fixed. | /judgment-day revisa el PR del módulo de pagos | | /comment-writer | Writes warm, direct PR comments — collaborative tone, not accusatory. | /comment-writer este método tiene un N+1 query, ¿cómo lo comento? |

Git & pull requests

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /chained-pr | Splits oversized PRs (400+ lines) into a reviewable sequence. | /chained-pr tengo 800 líneas de refactor en el módulo de usuarios | | /work-unit-commits | Plans commits as self-contained reviewable units before pushing. | /work-unit-commits implementé notificaciones, auth y la integración |

Security & conflicts

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /sdd-security | Audit code changes against OWASP Top 10 2021. Fits between sdd-apply and sdd-verify as a security gate. Uses Claude Opus 5 or GPT 5.6 Sol for maximum reasoning depth. | /sdd-security | | /conflict-resolver | Analyze and resolve git merge conflicts using deep reasoning. Classifies each conflict (AUTO / PREFER-OURS / PREFER-THEIRS / MERGE / AMBIGUOUS) and shows a diff preview before applying. | /conflict-resolver |

Documentation

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /changelog-generator | Transforms git commits into polished changelogs and release notes. | /changelog-generator genera las release notes para v2.1.0 | | /cognitive-doc-design | Designs guides, READMEs, and RFCs that minimize cognitive load. | /cognitive-doc-design necesito un README para el microservicio de pagos |

Design & frontend

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /frontend-design | Builds production-grade web UIs — avoids generic AI aesthetics. | /frontend-design página de login para un SaaS B2B, estilo profesional | | /interface-design | Builds dashboards, admin panels, and internal tools. | /interface-design dashboard de métricas de pagos para operaciones | | /tailwind-design-system | Builds scalable design systems with Tailwind CSS v4: tokens, components, patterns. | /tailwind-design-system sistema de diseño para suite de productos internos |

Testing

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /go-testing | Applies focused Go testing patterns: coverage, TUI flows, teatest, golden files. | /go-testing necesito testear un handler gRPC con dependencias externas |

GitHub

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /issue-creation | Creates GitHub issues with full context: steps to reproduce, impact, expected behavior. | /issue-creation el checkout falla en Safari cuando hay 2+ items |

Skills meta

| Skill | What it does | Example prompt | |-------|-------------|----------------| | /skill-creator | Creates new LLM-first skills with valid SKILL.md frontmatter. | /skill-creator quiero una skill para nuestro proceso de deploy | | /skill-improver | Audits and refactors existing SKILL.md files: normalize conventions, improve quality. | /skill-improver revisa la skill de branch-pr | | /skill-registry | Rebuilds the skill index after adding or changing skills. | /skill-registry |

Integrations

Git workflow

baseline install installs a global pre-push git hook. It is advisory-only and never blocks a push.

Re-run baseline install after updating baseline to refresh the hook.

Guide: → docs/guides/git-workflow.md

baseline-cloud (corporate skills and Kiro credit tracking)

baseline-cloud is built into the CLI — no separate install needed. If your team runs a self-hosted baseline-cloud server, connect once and everything syncs automatically.

One-time setup:

baseline cloud login --server https://your-baseline-cloud.com --token <your-token>
baseline cloud status             # confirm connection
baseline cloud sync               # pull corporate skills immediately

What happens automatically after login:

• baseline install syncs corporate skills from baseline-cloud to ~/.kiro/steering/bl-*.md
• Kiro IDE runs baseline cloud sync at the start of every session (via steering file)
• A background watcher (launchd on macOS, cron on Linux) scans ~/.kiro/sessions/ every 5 minutes and reports credit usage to baseline-cloud

All baseline-cloud commands:

| Command | Description | |---------|-------------| | baseline cloud login --server <url> --token <token> | Authenticate with your baseline-cloud server. Credentials saved to ~/.baseline/cloud.json. | | baseline cloud status | Show configured server URL and token prefix. | | baseline cloud sync | Download all corporate skills to ~/.kiro/steering/bl-*.md. Removes stale skills automatically. | | baseline cloud logout | Remove saved credentials. | | baseline cloud kiro-scan | Manually scan ~/.kiro/sessions/ and report credit usage to baseline-cloud. |

Repository skill policy:

Admins can disable specific skills per project in the baseline-cloud dashboard (Admin → Projects → skill policy). The policy syncs automatically via baseline cloud kiro-scan and can be applied manually:

# Run once per repository to configure local overrides:
baseline repo init

# Apply the cloud policy to the current workspace immediately:
baseline repo sync

Policy is stored in three layers, applied in order:

1. Cloud (admin-managed, immutable per client) — baseline-cloud dashboard
2. Repo (committed, shared with team) — .baseline/config.json
3. Local (personal overrides, gitignored) — .baseline/config.local.json

The merged result is written to .kiro/steering/baseline-repo-policy.md in the workspace, which Kiro reads automatically. Kiro enforces disabled skills without executing them.

Full guide: → docs/guides/baseline-cloud.md

Requirements

• Node.js >= 18
• At least one supported AI tool installed

CI — publish on release

The workflow in .github/workflows/publish.yml runs lint, build, and publish automatically when you create a GitHub release. Add your NPM_TOKEN as a repository secret to enable it.