AWS-first framework for Kiro that auto-detects your project type, validates and installs tooling, loads the right agents and skills per profile, and leaves your environment ready to build in seconds.

🇪🇸 Documentación en Español

Every AWS project starts the same way: copy-paste configs, install linters, hunt for the right agent prompts, wire up hooks, remember which steering rules apply. It is repetitive, error-prone, and burns time before you write a single line of business logic.

Orbit eliminates that friction. It reads your project, resolves the right profile, validates your environment, and loads a curated set of agents, skills, steering rules, and hooks — all tailored to your stack. You go from a blank directory to a fully configured AI-assisted workspace in one command.

Orbit runs a 6-step pipeline when you prepare a project:

1. Session Gates          Ask once per session if you want to prepare the environment
2. Detect / Select Profile  Auto-detect project type or launch an interactive wizard
3. Validate Environment   Check system tools (git, node, python3, aws, terraform)
                          and auto-install missing ones via brew / apt / nvm / corepack
4. Load Artifacts         Copy agents, steering packs, skills, hooks, and extensions
                          from the framework into .kiro/ scoped to your profile
5. Install Tooling        Install project devDependencies (eslint, prettier, vitest,
                          ruff, black, pytest, tsc, mypy) using the detected package manager
6. Write Project State    Write .kiro/.orbit-project.json with profile metadata

Profile resolution uses 4 dimensions:

Auto-detection evaluates required files, globs, package.json dependencies (wildcard support like @aws-sdk/*), and text patterns. If no profile matches, the wizard kicks in.

curl -sL https://raw.githubusercontent.com/eliecer2000/kiro-bootstrap/main/install.sh | bash

After installing:

~/.kiro/orbit/install.sh --help
~/.kiro/orbit/install.sh --update
~/.kiro/orbit/install.sh --resync-project .
~/.kiro/orbit/install.sh --status
~/.kiro/orbit/install.sh --doctor

14 specialized agents assigned per profile. Each agent has a declared role, responsibilities, and handoff rules so they coordinate automatically without manual wiring.

Handoffs are declared in agents-registry.json: orbit to aws-architect when architecture is needed, aws-architect to aws-iam-security when decisions touch IAM or networking, aws-lambda agents to aws-test-quality when tests are required.

22 local skills organized by domain. Skills are Markdown documents loaded into agent context — they carry domain rules, code examples, anti-patterns, and validation checklists.

find-skills is mandatory in every profile — lets agents discover and activate additional skills on demand.

Steering packs are context rules injected into every Kiro session. They encode team standards, AWS best practices, and runtime-specific conventions so agents follow them without being told.

Shared packs in every profile: core, git, security, aws-shared, testing, observability.

Additional packs per profile: runtime-typescript, runtime-python, runtime-javascript, lambda, api, cdk, terraform, amplify.

Three inclusion modes: always (every session), fileMatch (when a matching file is opened), manual (user-triggered via # in chat).

Automated hooks run on IDE events with no manual setup. Each profile gets the hooks that match its runtime:

Everything in Orbit is declarative. The catalog is the source of truth:

• manifest.json — pipeline steps, policies (conflict strategy, remote skills, session opt-out), wizard questions, public commands
• profiles/*.json — one file per profile: dimensions, detection rules, tooling, agents, steering, skills, hooks, validations
• agents-registry.json — full contract per agent: role, responsibilities, handoffs, skills, model, acceptance checklist, remote skills allowlist

The runtime (lib/orbit_catalog.py) reads the catalog and acts. No hardcoded logic.

python3 lib/orbit_catalog.py --bootstrap-dir . validate-catalog

Cross-validates manifest, profiles, and agents-registry: required fields, agent references, remote skills allowlist, and presence of agent files.

When Orbit operates from the Kiro chat, it runs the real pipeline before any scaffolding:

ORBIT_BOOTSTRAP_DECISION=yes \
ORBIT_HOME_DECISION=no \
ORBIT_PROJECT_PROFILE_ID=<profile-id> \
ORBIT_REMOTE_SKILL_DECISION=no \
~/.kiro/orbit/install.sh --resync-project "<path>"

Orbit resolves the profile-id internally from the wizard. It never asks for the raw ID, AWS credentials, or CLI profile during normal bootstrap. Scaffolding only starts after .kiro/.orbit-project.json exists and all artifact directories are loaded.

agents/          Agent JSON definitions
profiles/        Project profiles (detection, tooling, validations, agents, skills)
steering/        Steering packs by technical layer
skills/          Local skills with full documentation
hooks/           Automated hooks by runtime (format, lint, test)
extensions/      Kiro extension packs per profile
lib/             Runtime: pipeline, session, catalog, artifact loading, tooling install
validations/     System tool validation and auto-install
docs/            Technical documentation
templates/       Context templates for project onboarding
tests/           Framework test suite

bash tests/test-all.sh

• Architecture — Components, declarative catalog, runtime
• Bootstrap Flow — Step-by-step pipeline
• Profile Matrix — Detail per profile
• Agent Catalog — Roles, responsibilities, handoffs
• Authoring Guide — How to add agents, skills, profiles, steering

bash release.sh 2.5.0

See CONTRIBUTING.md for details.

See CONTRIBUTING.md for how to add profiles, agents, skills, and steering packs.

Please read our Code of Conduct before participating.

To report a vulnerability, see SECURITY.md. Do not open public issues for security concerns.

MIT — Eliezer Rangel