Skip to main content
IntentLang
The first Intent-Oriented language for the AI era

Intent-Oriented Programming for the AI era.

IntentLang is a programming language by SkillsTech that lets engineers describe software in clear, structured intent while AI, compilers, and verification tools help produce reliable implementations.

The core promise: Write what your software should do. Let AI and the compiler help determine how to build it, verify it, and keep it understandable.

CreateInvoice.intent
1Mission CreateInvoice
2
3Goal
4 Generate an invoice from approved orders
5
6Requires
7 Customer
8 ApprovedOrders
9
10Input
11 customer: Customer
12 orders: List<Order>
13
14Output
15 invoice: Invoice
16
17Guarantees
18 invoice.total is never negative
19 duplicate invoices are not created
20 every invoice is auditable
21
22Never
23 create invoice for unapproved order
24 expose payment token in logs
25
26Target
27 TypeScript
28 Python
29 DotNet
30
31Verify
32 unit tests
33 duplicate prevention test
34 audit trail test
35 security scan

Draft syntax, illustrative only.

Why Intent

Software is being written faster than it can be understood.

Intent-Oriented Programming puts the meaning of software first, so engineers and AI can move quickly without losing the thread of what the code is supposed to do.

AI writes faster than we can review

AI can generate code faster than humans can read, review, and trust it. Reviewing output line by line does not scale.

Traditional languages start with the how

Most languages ask you to commit to implementation first. The original intent is scattered across code, tickets, and memory.

Intent starts with the what and why

Intent focuses on what the software should do, why it exists, which constraints matter, and how it should be verified.

Engineers stay in control

The goal is not to replace engineers. It is to help them express, verify, and own software far more clearly.

Core philosophy

Intent → Contract → Plan → Implementation → Verification → Proof

A single, honest path from what you meant to evidence that it holds. Every stage is inspectable, and nothing is hidden from the engineer who owns it.

01

Intent

What the software should do, and why it exists.

02

Contract

The guarantees and constraints that must hold.

03

Plan

A deterministic implementation plan, before any code.

04

Implementation

Code in your target language, human or AI authored.

05

Verification

Types, tests, and checks that the contract holds.

06

Proof

Durable evidence that intent and reality agree.

Example syntax

Describe the mission. Let tooling handle the rest.

A Mission states a goal, what it requires, the guarantees that must hold, and the languages it should target. It reads top-to-bottom like structured pseudocode.

TypeScriptPython.NETJavaGoRust
This is draft syntax. Names, keywords, and structure will change as the language and compiler take shape.
CreateInvoice.intent
1Mission CreateInvoice
2
3Goal
4 Generate an invoice from approved orders
5
6Requires
7 Customer
8 ApprovedOrders
9
10Input
11 customer: Customer
12 orders: List<Order>
13
14Output
15 invoice: Invoice
16
17Guarantees
18 invoice.total is never negative
19 duplicate invoices are not created
20 every invoice is auditable
21
22Never
23 create invoice for unapproved order
24 expose payment token in logs
25
26Target
27 TypeScript
28 Python
29 DotNet
30
31Verify
32 unit tests
33 duplicate prevention test
34 audit trail test
35 security scan

Language principles

Ten commitments that shape the language.

These principles are the north star for every design decision in Intent.

Intent-first

Code begins with what the software should accomplish, not with the implementation.

Reads like structured pseudocode

A senior engineer, architect, product manager, or AI agent should understand the file on first read.

Contracts by default

Every mission can declare its requirements, guarantees, constraints, and forbidden behavior.

AI-assisted but deterministic

AI may help generate implementation, tests, docs, and explanations, but the build stays reproducible.

Multi-target

One mission can target TypeScript, Python, .NET, Java, Go, or Rust through adapters.

Verification-first

A mission is not complete because code exists. It is complete when its guarantees are verified.

Architecture-aware

Intent understands services, APIs, events, databases, dependencies, ownership, and boundaries.

Repository-aware

Intent maps missions to real repo files, services, tests, docs, and ownership.

Human + AI collaboration

Intent gives humans a clear way to express judgment and gives AI a structured way to help.

Proof-producing

Every completed mission can produce proof: tests, reports, docs, an implementation trace, and a verification summary.

What Intent is not

Clear about what we are not claiming.

Being honest about the boundaries is part of being a serious language project.

Not an AI wrapper

Intent is a language with its own model of intent, contracts, and verification, not a thin shell over a chat API.

Not a prompt format only

Prompts are one way to draft intent, but Intent is structured, reviewable source, not a paragraph of instructions.

Not a no-code tool

Intent is for engineers. It makes engineering intent explicit; it does not hide the system from the people who own it.

Not a replacement for every language

Intent sits above Python, TypeScript, .NET, Java, Go, and Rust as an intent and verification layer. It targets them; it does not erase them.

Not magic

There is no hidden trick. Intent makes goals and guarantees explicit so tools can help you keep them.

Not production-ready yet

Not until the compiler, runtime, tests, and verification engine prove it. And it makes no claim to outperform the languages it targets today.

SkillsTech ecosystem

Intent is the center of a larger system.

Intent defines what software should do. The rest of the SkillsTech ecosystem helps you build it, understand it, master it, and prove it.

Intent

Define what software should do

The intent-oriented language at the center: a clear, structured statement of goals, constraints, and guarantees.

OpenThunder

Verify and understand it

Reads intent, compares it to the real repo, detects drift, and surfaces unverified guarantees and ownership gaps.

Repo Mastery

Master the codebase

Turns a large, unfamiliar repository and its intent into learning paths an engineer can actually internalize.

SkillsTech Talk

Explain it

Practice articulating and defending the design decisions behind the software you own.

SkillsTech Certified

Prove it

A path to demonstrate real, verifiable command of a codebase and the intent behind it.

SkillsTech IDE

Build it

The editor where you write, preview, compile, and verify intent, and connect it to real repo files.

Early access

Help shape the first Intent-Oriented language.

Join the waitlist to follow the language as it takes shape and get early access to docs, examples, and the playground.