Start with the task
Use a workflow skill to frame the work. Add every stack skill relevant to the components you touch.
OPEN SOURCE · AGENT SKILLS
Give your coding agent a shared engineering playbook. From the first requirement to the final review, keep good practices close to the code.
Plain Markdown. Your tools. Your project’s rules.
“Add password reset.”
analyze-requirementplan-changeimplement-change + typescript-engineeringreview-code + test-changeONE COLLECTION.
THE AGENTS YOU USE.
01 / THE COLLECTION
Pair a workflow with the stacks your change touches. Load the guidance you need, when you need it.
15 SKILLS · 8 WORKFLOW + 7 ENGINEERING
analyze-requirementTurn a raw request into clear scope, acceptance criteria and evidence-backed decisions.
plan-changeConnect affected components, dependencies and validation into an actionable plan.
implement-changeImplement approved changes while respecting contracts, project boundaries and existing work.
review-codeReview for functional defects, security risks, regressions and missing coverage.
test-changeChoose meaningful tests that protect the behavior your users and systems rely on.
debug-issueReproduce symptoms, test hypotheses and trace failures to the smallest supported cause.
safe-refactorImprove structure incrementally while preserving observable behavior and contracts.
checkpoint-progressLeave a useful handoff so the next session can pick up where this one ends.
dotnet-engineeringProject conventions, dependency injection, async APIs, data access and testing.
java-engineeringJDK and build compatibility, frameworks, concurrency, transactions and testing.
go-engineeringModule boundaries, context, error handling, concurrency and idiomatic tests.
python-engineeringRuntime and packaging choices, typing, async code, resource handling and tests.
typescript-engineeringCompiler and runtime conventions, typed contracts, frameworks and async behavior.
database-engineeringEngine-aware SQL, schema migrations, transaction safety and rollback planning.
dart-engineeringSDK compatibility, null safety, async lifecycles, widgets and test practices.
Try another term or switch to “All skills”.
Every skill is readable Markdown. Open one to see exactly what it teaches.
02 / BUILT TO TRAVEL
Bring the same engineering habits across tools and repositories, with project-specific decisions where they belong.
Use a workflow skill to frame the work. Add every stack skill relevant to the components you touch.
Your repository owns its architecture, commands and approval rules. Shared guidance follows those boundaries.
Portable SKILL.md files keep one canonical source, with installation layouts for each supported agent.
Guidance that helps an agent reason. Your project’s tests and approval controls still verify the result.
03 / MAKE IT YOURS
Clone the collection, choose your tool and preview where the skills will go.
Replace this with your project’s path, relative to the cloned collection or absolute.
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 -WhatIfRequires Git and PowerShell. Run in PowerShell on Windows, macOS or Linux. In Windows PowerShell 5.1, replace pwsh with powershell.
After reviewing the preview, turn off “Preview first” to install. Existing managed installations can be updated with -Overwrite; see the installation guide.