home / skills / omer-metin / skills-for-antigravity / development

development skill

/skills/development

This skill helps you master AI development tools to code faster, automate tasks, and generate full applications end-to-end.

npx playbooks add skill omer-metin/skills-for-antigravity --skill development

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.2 KB
---
name: development-ai-tools
description: Master the AI tools that supercharge software development. From code completion to full application generation, write better code faster and automate the tedious parts. Use when "AI coding, code assistant, Copilot, Cursor, code generation, AI developer tools, development, coding, ai-assistant, productivity, code-generation" mentioned. 
---

# Development Ai Tools

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill helps developers master AI tools that accelerate software development, from inline code completion to full application generation. It focuses on practical guidance, safe patterns, and validation rules so you can write better code faster while avoiding common AI-driven pitfalls.

How this skill works

The skill inspects your development goals, code snippets, and tool choice to recommend workflows and configurations for AI coding assistants. It grounds recommendations in the authoritative creation patterns, explains risks using the sharp-edge diagnostics, and validates outputs against the formal validation rules before suggesting changes.

When to use it

  • When adopting or evaluating AI code assistants (Copilot, Cursor, etc.) in a project
  • When automating repetitive coding tasks or generating boilerplate
  • When setting up CI checks that include AI-generated code
  • When you need to validate AI output against strict project constraints
  • When diagnosing surprising or incorrect behavior from AI tools

Best practices

  • Follow the defined creation patterns for how code should be produced and integrated into your codebase
  • Use the diagnostic checklist to identify root causes of unsafe or incorrect suggestions
  • Enforce validation rules automatically in CI to reject nonconforming AI-generated changes
  • Keep prompts minimal and contextual; provide just enough code and tests for reliable generation
  • Treat AI output as draft code: run tests, linting, and manual review before merging

Example use cases

  • Generate CRUD endpoints from a schema and validate routes against project rules before committing
  • Set up an AI-assisted pair programming workflow that applies vetted generation patterns
  • Automate repetitive refactors while using diagnostic guidance to avoid introducing logic regressions
  • Create test scaffolding from function signatures and ensure tests meet the validation constraints
  • Review and triage surprising AI suggestions using a sharp-edges checklist to find failure modes

FAQ

How do I ensure AI-generated code is safe to merge?

Run automated validations and linters, follow the creation patterns, and use the diagnostic sharp-edge checklist to catch logic and security issues before merging.

Which AI tools work best with this skill?

This skill is tool-agnostic and supports common developer assistants like Copilot and Cursor by focusing on patterns, risk diagnostics, and validation rules rather than a single vendor.