Scaling your productivity with spec docs in your IDE - Anti Gravity.

Source: Dev.to

What I am doing with my IDE and AI now

I’ve moved away from “chatting” with AI and started creating small .md files that act as Instruction Layers for Gemini. This shift turns an LLM from a conversational assistant into a predictable, modular part of my technical stack.

The Core Concept: Prompts as Configuration

Instead of re‑explaining requirements every time you open a terminal, treat prompts like Angular components. Create a simple Markdown file that tells Gemini exactly how to behave for a specific task. Various tools may call this a workflow, skill, or rule, but the premise is the same: write something easily referencable by your IDE so you can regularly bring it into your AI prompts without re‑writing.

When you find yourself prompting the same thing multiple times—whether in Anti Gravity or any integrated IDE—you shouldn’t be typing; you should be referencing a spec and updating it.

An “Angular‑Style” Instruction File

• Encapsulated: A clearly defined purpose.
• Reusable: Use it across any feature branch.
• Consistent: Standardized output every single time.

Example: pr-assistant.md

# PR Comment Assistant

## Goal
Draft and post high‑quality GitHub PR comments via the git CLI.

## Rules
- Keep feedback actionable, professional, and concise.
- Call out uncertainty explicitly; no speculation.

## Structure
Context → Suggestion → Reasoning.

## Execution
- Output via git CLI; do not use inline IDE comments.
- Treat comments as notes for reviewers and future contributors.

Why This Works (Anti Gravity in Practice)

Without structure you suffer from Prompt Drift: instructions become lazy, output inconsistent, and you repeat yourself constantly. Using .md instruction files provides Cognitive Offloading:

• Predictability: Gemini follows the spec, not the “vibe” of your last message.
• Efficiency: Stay focused in your IDE, invoking capabilities rather than brainstorming prompts.
• Scalability: Files live in your repo, evolve with your codebase, are version‑controlled, and can be shared across the entire team.

Angular as the Language of Focus

This approach mirrors core Angular principles:

• Separation of Concerns: Each .md file has one specific job.
• Reusability: The same instruction file works across different PRs and projects.
• Consistency: You get standardized outputs every time.

Instead of just “talking” to an AI, you are composing it into your development environment.

Closing Thought

The real power of Anti Gravity within an Angular codebase isn’t just writing code faster; it’s reducing the mental overhead of the development process. Pair a high‑performance IDE with small, well‑designed instruction files, and you get something bigger than an assistant—a custom‑built, automated collaborator.