1. Start Light
Author only <component>.intent with summary + requirements for fast product iteration.
Imagine repositories filled with human-readable intent files instead of source code. AIM makes this real! Specify what you want, let AI synthesize the implementation. Edit intents, not code. Version control meaning, not syntax.
Just clean, readable .intent files describing what your application does. AI agents synthesize implementations on demand. Teams review intent changes, not code diffs. The repository becomes documentation, specification, and source of truthโall in one.
/aim folder, and synthesize. Edit the intent files and rebuild whenever you need.
Write human-readable intent files
AI generates implementation
Compile and package
Deploy and execute
$ sinth
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Sinth โ Synthesize intent into reality โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
What would you like to do?
1. Initialize new project
2. Fetch package from registry
3. List installed packages
4. Generate synthesis prompt
5. Configure tech stack (wizard)
...
$ sinth fetch weather
โ Registry fetched successfully
โ Saved aim/weather.intent
โ Package 'weather' installed
$ sinth synth weather
โ Generated synthesis prompt
โ Copied to clipboard!
$ sinth config set stack.frontend React
โ Configuration updated
Copy this prompt into Claude or any AI assistant to begin:
Paste this into your AI assistant to load AIM capabilities and start synthesizing code from intent files.
Author only <component>.intent with summary + requirements for fast product iteration.
Inline or linked SCHEMA, FLOW, CONTRACT, VIEW, PERSONA facets when deterministic synthesis matters.
Registry fetch is sync only. Local /aim remains source of truth for edits, regeneration, and long-term maintenance.
Picture GitHub repositories without source code. No JavaScript files. No Python modules. No dependency hell.
AIM: weather#[email protected]
INTENT WeatherLookup {
SUMMARY: "Real-time weather lookup with automatic error handling for missing cities."
REQUIREMENTS {
- "User enters a city name to view current temperature and conditions."
- "UI displays a friendly error state if the city is not found."
}
CONTRACT FetchWeather {
INPUT {
city: string required
}
EXPECTS {
- "City string must not be empty"
}
ENSURES {
- "CALLS External.WeatherAPI"
- "RETURNS WeatherSnapshot object on success"
}
}
}
}
Then evolve to detailed facets only when needed.