feat: Add AI-assisted setup path for complex repos (setup.sh --ai)

.agents/skills/agentic-os-setup/adapters/antigravity.md

@@ -0,0 +1,148 @@
+# Adapter: Antigravity
+
+## Purpose
+
+Describes how to format agentic-os generated output for Antigravity AI consumption via AGENTS.md.
+
+## File Path Convention
+
+- **Primary:** `AGENTS.md` at repo root
+- **Behavior:** Always EXTEND existing content — never replace
+
+## Format Specification
+
+Antigravity reads AGENTS.md as its primary instruction file. It expects structured markdown with:
+
+- `##` headers for major sections (Personas, Rules, Standards)
+- `###` headers for subsections (individual personas, rule groups)
+- Tables for structured data (scope boundaries, relationships)
+- Bullet lists for behavioral rules
+- Imperative tone ("Focus on X", "Validate Y", "Never Z")
+
+## Constraints
+
+- Single file (AGENTS.md)
+- Must coexist with user-written content
+- Agentic-os content lives ONLY within managed block markers
+- User content above the managed block is never touched
+- If no AGENTS.md exists, create one entirely within managed markers
+
+## Managed Block Format
+
+```markdown
+<!-- MANAGED BY AGENTIC-OS | hash:sha256:<content-hash> | DO NOT EDIT -->
+{generated content goes here}
+<!-- END MANAGED BY AGENTIC-OS -->
+```
+
+- **Start marker:** `<!-- MANAGED BY AGENTIC-OS | hash:sha256:<hash> | DO NOT EDIT -->`
+- **End marker:** `<!-- END MANAGED BY AGENTIC-OS -->`
+- **Hash:** SHA-256 of the content between markers (enables future re-run detection)
+- **Placement:** Always at the END of AGENTS.md (below any user content)
+
+## Pre-Existing File Behavior
+
+| Scenario | Action |
+|----------|--------|
+| No AGENTS.md exists | Create AGENTS.md with content entirely within managed block |
+| AGENTS.md exists without managed block | Append managed block at end of file |
+| AGENTS.md exists with managed block | Replace managed block content (preserve everything outside) |
+| User edited content inside managed block | Detect hash mismatch → warn user and skip overwrite |
+
+## Extend Semantics
+
+```
+AGENTS.md structure:
+┌─────────────────────────────────────────────────────────────────┐
+│ [User's original content]                                        │ ← never touched
+│ ...                                                              │
+├─────────────────────────────────────────────────────────────────┤
+│ <!-- MANAGED BY AGENTIC-OS | hash:sha256:<hash> | DO NOT EDIT -->│
+│ ## Agentic-OS Generated Rules                                    │
+│ {all generated content here}                                     │
+│ <!-- END MANAGED BY AGENTIC-OS -->                               │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+## Examples
+
+### Example 1: New AGENTS.md (no existing file)
+
+```markdown
+<!-- MANAGED BY AGENTIC-OS | hash:sha256:a1b2c3d4e5f6 | DO NOT EDIT -->
+## Agentic-OS Generated Rules
+
+### Project Context
+
+This is a Go microservices project with 3 services.
+
+### Quality Gates
+
+- Run `go test ./...` before completing work
+- Run `golangci-lint run` for code quality
+- Ensure new packages have corresponding test files
+
+<!-- END MANAGED BY AGENTIC-OS -->
+```
+
+### Example 2: Extending existing AGENTS.md (Complex tier)
+
+User's existing content (preserved as-is):
+```markdown
+# Team Agents
+
+## Product Manager
+Responsible for roadmap decisions...
+
+## Tech Lead
+Responsible for architecture decisions...
+```
+
+After agentic-os extension:
+```markdown
+# Team Agents
+
+## Product Manager
+Responsible for roadmap decisions...
+
+## Tech Lead
+Responsible for architecture decisions...
+
+<!-- MANAGED BY AGENTIC-OS | hash:sha256:f7e8d9c0b1a2 | DO NOT EDIT -->
+## Agentic-OS Generated Rules
+
+### Personas
+
+#### Architect
+**Scope:** `/Designs/`
+**Focus:** System design, scalability, requirements traceability
+**Behavioral rules:**
+- Prioritize structural patterns over quick fixes
+- Reference existing blueprints before proposing new structures
+
+#### Operations Specialist
+**Scope:** `/Operations/`
+**Focus:** Process efficiency, documentation completeness
+**Behavioral rules:**
+- Follow documentation standards
+- Enforce cross-reference rules
+
+### Scope Boundaries
+
+| Domain | Isolated From | Rationale |
+|--------|--------------|-----------|
+| Designs/ | Operations/ | Architecture and HR are independent |
+| Operations/ | Designs/ | Recruitment is independent of design |
+
+### Cross-References
+
+| Source | Target | Link Format |
+|--------|--------|-------------|
+| Operations/interviews/ | Operations/job-descriptions/ | `Job-ID: jd-*` |
+
+<!-- END MANAGED BY AGENTIC-OS -->
+```
+
+## Usage Context
+
+The AI reads this adapter when the user has targeted Antigravity as a runtime. It formats the assembled proposal (from templates) into AGENTS.md content within managed block markers, preserving any existing user content above the block.

.agents/skills/agentic-os-setup/adapters/claude.md

@@ -0,0 +1,86 @@
+# Adapter: Claude Code
+
+## Purpose
+
+Describes how to format agentic-os generated output for Claude Code consumption.
+
+## File Path Convention
+
+- **Primary:** `CLAUDE.md` at repo root
+- **If CLAUDE.md already exists:** Create `CLAUDE-agentic-os.md` as a companion file. Never modify the existing CLAUDE.md.
+
+## Format Specification
+
+Claude Code reads CLAUDE.md as a markdown file with freeform structure. Effective patterns:
+
+- Use `##` headers to organize sections (Persona Routing, Scope Isolation, Quality Gates, etc.)
+- Bullet lists for rules and constraints
+- Code blocks for commands and patterns
+- Keep instructions direct and imperative ("Do X", "Never Y")
+
+## Constraints
+
+- Single file (no directory structure like Cursor)
+- No frontmatter or metadata — pure markdown
+- No glob-based routing — all rules apply globally (Claude Code doesn't have file-scoped rules)
+- Rules must be self-describing (include "when editing in X" context inline)
+
+## Pre-Existing File Behavior
+
+| Scenario | Action |
+|----------|--------|
+| No CLAUDE.md exists | Create `CLAUDE.md` |
+| CLAUDE.md exists | Create `CLAUDE-agentic-os.md` as companion. Add a note at top: "This file supplements the existing CLAUDE.md with agentic-os configuration." |
+
+Never modify an existing CLAUDE.md.
+
+## Examples
+
+### Example 1: Simple Tier (single-purpose project)
+
+```markdown
+# Project Context
+
+This is a Python FastAPI project using pytest for testing.
+
+## Quality Gates
+
+Before completing work:
+- Run tests: `pytest`
+- Run type checking: `mypy src/`
+- Run formatting: `ruff format --check .`
+
+## Project Structure
+
+- `src/` — Application source (FastAPI routes and models)
+- `tests/` — Test files (pytest)
+- `alembic/` — Database migrations
+```
+
+### Example 2: Multi Tier (multiple concerns)
+
+```markdown
+# Agentic-OS Configuration
+
+## Persona Routing
+
+- **Backend Mode:** Triggered when editing `/backend/`. Focus on API design, data modeling, and performance.
+- **Frontend Mode:** Triggered when editing `/frontend/`. Focus on component architecture, accessibility, and UX.
+- **DevOps Mode:** Triggered when editing `/infra/`. Focus on reliability, security, and cost optimization.
+
+## Scope Isolation
+
+Do not cross-reference between isolated domains unless explicitly asked:
+- `/backend/` and `/frontend/` have distinct conventions
+- `/infra/` is independent from application code
+
+## Quality Gates
+
+- Backend: `cd backend && pytest && mypy .`
+- Frontend: `cd frontend && npm test && npm run lint`
+- Infrastructure: `cd infra && terraform validate`
+```
+
+## Usage Context
+
+The AI reads this adapter when the user has targeted Claude Code as a runtime. It formats the assembled proposal (from templates) into Claude-appropriate markdown, respecting the constraints above.

.agents/skills/agentic-os-setup/adapters/cline.md

@@ -0,0 +1,85 @@
+# Adapter: Cline
+
+## Purpose
+
+Describes how to format agentic-os generated output for Cline AI consumption.
+
+## File Path Convention
+
+- **Primary:** `.clinerules` at repo root
+- **If `.clinerules` already exists:** Create `.clinerules-agentic-os` as a companion file. Never modify the existing `.clinerules`.
+
+## Format Specification
+
+Cline reads `.clinerules` as a plain text/markdown file containing behavioral instructions. Effective patterns:
+
+- Use `##` headers to organize sections
+- Direct imperative rules ("Always X", "Never Y", "When doing Z, ensure W")
+- Bullet lists for grouped rules
+- Keep language concise and actionable
+
+## Constraints
+
+- Single file (no directory-based rule system like Cursor)
+- No frontmatter or metadata
+- No glob-based routing — all rules apply globally
+- Rules must be self-describing (include path context inline where needed)
+- Simpler format than Claude or Cursor — focus on behavioral directives
+
+## Pre-Existing File Behavior
+
+| Scenario | Action |
+|----------|--------|
+| No `.clinerules` exists | Create `.clinerules` |
+| `.clinerules` exists | Create `.clinerules-agentic-os` as companion. Never modify existing file. |
+
+## Examples
+
+### Example 1: Simple Tier
+
+```markdown
+# Project Rules
+
+## Quality Gates
+
+- Always run `npm test` before completing work
+- Always run `npm run lint` before completing work
+- New source files must have corresponding test files
+
+## Project Structure
+
+- Source code lives in `src/`
+- Tests live in `tests/`
+- Follow existing naming conventions
+```
+
+### Example 2: Multi Tier
+
+```markdown
+# Agentic-OS Rules
+
+## Persona Routing
+
+When working in `/backend/`:
+- Focus on API design, data modeling, and performance
+- Follow Python conventions (PEP 8, type hints)
+
+When working in `/frontend/`:
+- Focus on component architecture and accessibility
+- Follow React/TypeScript conventions
+
+## Scope Isolation
+
+- Do not suggest content from `/backend/` when working in `/frontend/`
+- Do not suggest content from `/frontend/` when working in `/backend/`
+- Keep suggestions scoped to the current domain
+
+## Quality Gates
+
+- Backend: run `pytest` and `mypy` before completing work
+- Frontend: run `npm test` and `npm run lint` before completing work
+```
+
+## Usage Context
+
+The AI reads this adapter when the user has targeted Cline as a runtime. It formats the assembled proposal (from templates) into Cline-appropriate rules, respecting the single-file, directive-focused format.