Getting Started

Install and configure Awesome AGV in minutes.

Table of contents

1. Prerequisites
2. Installation
   1. Option 1: Copy the .agent folder
   2. Option 2: Git submodule
3. Configuration
   1. Antigravity / Roo Code / Claude Code
   2. Gemini CLI
   3. Other AI Coding Assistants
4. Verifying Installation
5. What Happens Next?
6. Quick Tour
   1. Try the Feature Workflow
   2. Try a Quick Fix
   3. Try an Audit
7. Next Steps

---

Prerequisites

• An AI Coding Assistant (Antigravity, Roo Code, Claude Code, Cline, etc.)
• A project where you want to enforce high standards

Installation

Option 1: Copy the .agent folder

Clone this repository or copy the .agent folder into the root of your project:

# Clone the repo
git clone https://github.com/irahardianto/awesome-agv.git

# Copy the .agent folder into your project
cp -r awesome-agv/.agent /path/to/your-project/

Option 2: Git submodule

Add as a submodule for easy updates:

cd your-project
git submodule add https://github.com/irahardianto/awesome-agv.git .awesome-agv
ln -s .awesome-agv/.agent .agent

Configuration

Antigravity / Roo Code / Claude Code

These tools read from the .agent directory by default. No additional configuration is needed — just drop the folder in and start coding.

Gemini CLI

Ingest the rules as custom system prompt context. You can reference individual rule files:

# Point Gemini CLI to the rules directory
# Refer to Gemini CLI documentation for custom instructions

Other AI Coding Assistants

For any tool that supports custom system prompts or context loading:

1. Load all files from .agent/rules/ into the system prompt
2. Optionally load .agent/skills/ for specialized capabilities
3. Optionally load .agent/workflows/ for structured development processes

Verifying Installation

After installation, test that your agent is picking up the rules:

1. Ask your agent: “What rules are you following?”
2. Check that it mentions the Rugged Software Constitution or Security Mandate
3. Try writing code and watch for:
   • Automatic input validation on API handlers
   • Structured logging at operation entry points
   • Interface-based I/O abstraction

What Happens Next?

Once installed, the setup activates automatically:

Component	Activation	Effect
Mandates	Always loaded	Agent always validates code, adds logging, follows security rules
Principles	Contextual	Agent applies database rules when writing queries, CI/CD rules when editing pipelines, etc.
Skills	On demand	Agent uses debugging protocol when stuck, guardrails before/after writing code
Workflows	Slash commands	Use /orchestrator for features, /quick-fix for bugs, /audit for reviews

Everything is modular. Rules and skills work independently — you don’t need workflows to benefit from them. Use only the rules you want, build your own workflows, or skip workflows entirely. The setup is a toolkit, not a framework.

Quick Tour

Try the Feature Workflow

Start building a feature with the structured workflow:

/orchestrator

This chains the full development lifecycle:

1. Research — understand context, search documentation
2. Implement — TDD cycle (Red → Green → Refactor)
3. Integrate — test with real infrastructure (Testcontainers)
4. Verify — full lint, test, and build validation
5. Ship — git commit with conventional format

Try a Quick Fix

For a small bug fix:

/quick-fix

This skips research and integration, going straight to: Diagnose → Fix + Test → Verify → Ship.

Try an Audit

Review existing code quality:

/audit

This produces a structured findings report graded by severity (Critical → Major → Minor → Nit).

Next Steps

• Rules Reference — Explore all 38 rules
• Skills Reference — Learn about specialized skills
• Workflows Reference — Understand the development workflows
• Adapting — Customize for your project type