cfsa-antigravity
v2.19.4
Published
CFSA Pipeline — Constraint-First Specification Architecture for AI agents. Production-grade from line one.
Maintainers
Readme
CFSA Antigravity
Constraint-First Specification Architecture — production-grade from line one
A pipeline that turns a raw idea into exhaustively specified, test-driven, production-quality code through progressive gates. Stack-agnostic. Built for Antigravity on Linux/WSL. Every line of code is production-grade from the moment it's written.
Quick Install
npx cfsa-antigravity initThis installs the selected agent runtime (.agent/ by default, or .claude/ with --agent claude), the docs/ structure, and agent config files into your project.
CLI
| Command | Description |
|---------|-------------|
| cfsa-antigravity init | Install the pipeline into your project |
| cfsa-antigravity status | Check installation + unfilled placeholders |
| cfsa-antigravity init --force | Overwrite existing installation |
| cfsa-antigravity init --dry-run | Preview what would be installed |
| cfsa-antigravity init --path ./dir | Install into specific directory |
Choosing the runtime directory
- Antigravity-style installs use
.agent/ - Claude Code installs use
.claude/
If you are using an editor that indexes agent files for slash commands, do not hide the runtime directory you actually installed.
Recommended Solution:
Keep the installed runtime directory out of shared .gitignore rules when your tool needs to index it. Prefer .git/info/exclude for local-only exclusions.
Examples:
- Antigravity install → keep
.agent/out of.gitignore - Claude install → keep
.claude/out of.gitignore - Use
.git/info/excludefor local exclusions instead of changing shared ignore rules
Get Started
/ideateThe pipeline tells you what to run next at every step. You never have to guess.
Keeping Up to Date
The kit evolves independently of your project. To pull improvements into an existing project:
/sync-kitThis performs a semantic merge — it applies new workflows, skills, and rules from the upstream kit while preserving your project-specific values (tech stack, validation commands, filled placeholders). It will never overwrite your project decisions.
- First sync does a full comparison; subsequent syncs are incremental (commit-scoped)
- Tracks sync state in the installed agent runtime (
.agent/kit-sync.mdor.claude/kit-sync.md) so it knows what changed since last update - Flags any structural migrations needed (e.g., ideation format changes)
Documentation
| Document | Contents | |----------|----------| | Pipeline Guide | Full walkthrough — every command, every stage | | Kit Architecture | How the kit's internals work |
Five Principles
- Constraints before decisions — map what's decided before presenting options
- Exhaustive iteration over shallow speed — no ambiguity moves forward
- Work shifted left — design decisions made in spec, not in code
- Progressive decision locking — each stage locks decisions for downstream
- TDD as the implementation contract — Red → Green → Refactor, every slice
Contributing
See CONTRIBUTING.md for how to set up, make changes, and submit PRs.
