AI Engineering Skills

OPEN SOURCE · AGENT SKILLS

Better habits.
Better code.

Give your coding agent a shared engineering playbook. From the first requirement to the final review, keep good practices close to the code.

  • 18 skills in plain Markdown
  • One source for four agents
  • MIT License
skills/analyze-requirement/SKILL.md
---
name: analyze-requirement
description: Turn a raw software request into an evidence-backed specification with scope, acceptance criteria, impacts, risks, and open decisions. Use for requirement analysis before planning or implementation; do not use when an approved specification already exists.
---

# Analyze Requirement

Produce a specification that separates requested outcomes from implementation guesses.

## Authority

Remain read-only unless the user explicitly asks to create or update a specification artifact. Do not modify application source, configuration, schemas, tickets, or external systems.

ONE COLLECTION.
THE AGENTS YOU USE.

Codex Claude Code OpenCode Antigravity

01 / THE COLLECTION

A skill for the work
in front of you.

Pair a workflow with the stacks your change touches. Load the guidance you need, when you need it.

18 SKILLS · 11 WORKFLOW + 7 ENGINEERING

WORKFLOW / 01

Understand the ask

analyze-requirement

Turn a raw request into clear scope, acceptance criteria and evidence-backed decisions.

WORKFLOW / 02

Map the next move

plan-change

Connect affected components, dependencies and validation into an actionable plan.

WORKFLOW / 03

Build with intent

implement-change

Implement approved changes while respecting contracts, project boundaries and existing work.

WORKFLOW / 04

Look beyond the diff

review-code

Review for functional defects, security risks, regressions and missing coverage.

WORKFLOW / 05

Verify the behavior

test-change

Choose meaningful tests that protect the behavior your users and systems rely on.

WORKFLOW / 06

Find the actual cause

debug-issue

Reproduce symptoms, test hypotheses and trace failures to the smallest supported cause.

WORKFLOW / 07

Change the shape

safe-refactor

Improve structure incrementally while preserving observable behavior and contracts.

WORKFLOW / 08

Keep the thread

checkpoint-progress

Leave a useful handoff so the next session can pick up where this one ends.

WORKFLOW / 09

Doubt the verdict

challenge-review

Attack a finished review of a high-risk change before it merges.

WORKFLOW / 10

Keep the notes

preserve-comments

Edit code without losing the comments that explain it.

WORKFLOW / 11

Pay back later

shortcut-ledger

List the shortcuts you deferred, so later does not become never.

ENGINEERING

.NET & C#

dotnet-engineering

Project conventions, dependency injection, async APIs, data access and testing.

ENGINEERING

Java

java-engineering

JDK and build compatibility, frameworks, concurrency, transactions and testing.

ENGINEERING

Go

go-engineering

Module boundaries, context, error handling, concurrency and idiomatic tests.

ENGINEERING

Python

python-engineering

Runtime and packaging choices, typing, async code, resource handling and tests.

ENGINEERING

TypeScript

typescript-engineering

Compiler and runtime conventions, typed contracts, frameworks and async behavior.

ENGINEERING

Databases

database-engineering

Engine-aware SQL, schema migrations, transaction safety and rollback planning.

ENGINEERING

Dart & Flutter

dart-engineering

SDK compatibility, null safety, async lifecycles, widgets and test practices.

Every skill is readable Markdown. Open one to see exactly what it teaches.

02 / BUILT TO TRAVEL

A shared playbook.
Your way of working.

Bring the same engineering habits across tools and repositories, with project-specific decisions where they belong.

01 —

Start with the task

Use a workflow skill to frame the work. Add every stack skill relevant to the components you touch.

02 —

Keep context local

Your repository owns its architecture, commands and approval rules. Shared guidance follows those boundaries.

03 —

Take it with you

Portable SKILL.md files keep one canonical source, with installation layouts for each supported agent.

A BETTER WAY TO WORKEXAMPLE WORKFLOW
THE TASK

“Add password reset.”

01
Understand the changeanalyze-requirement
02
Make a deliberate planplan-change
03
Build with the right contextimplement-change + typescript-engineering
04
Review. Test. Hand off.review-code + test-change

Guidance that helps an agent reason. Your project’s tests and approval controls still verify the result.

03 / MAKE IT YOURS

Good practices.
One install away.

In Claude Code, add the plugin marketplace. For every other tool, clone the collection, choose your tool and preview where the skills will go.

Validates the collection before copying
Tracks installed files with a receipt
Rolls back if installation fails
Full installation guide

CLAUDE CODE — NO CLONE

CLAUDE CODE
/plugin marketplace add vannt-dev/ai-engineering-skills
/plugin install ai-engineering-skills@ai-engineering-skills

Run inside Claude Code. For Codex, OpenCode or Antigravity, use the installer below.

POWERSHELL
git clone https://github.com/vannt-dev/ai-engineering-skills.git
cd ai-engineering-skills
pwsh -NoProfile -File ./scripts/install-skills.ps1 -Target Universal -Scope User -WhatIf

Requires Git and PowerShell. Run in PowerShell on Windows, macOS or Linux. In Windows PowerShell 5.1, replace pwsh with powershell.

No PowerShell on macOS or Linux? Run sh scripts/install-skills.sh --dry-run as the last line instead. --help lists its options, which match the ones above.

After reviewing the preview, turn off “Preview first” to install. Existing managed installations can be updated with -Overwrite; see the installation guide.

OPEN SOURCE. OPEN TO BETTER IDEAS.

Make the playbook better.

Contribute a skill