SPECTRL
A lot of the time I've noticed that codebases have the same problem: the decisions that actually matter - why we picked this pattern, what that module is supposed to do, what not to touch - live in someone's head, a stale Confluence page, or a Slack thread that I can't find. Spectrl is my attempt to fix that. You write a spec, version it, publish it, and anyone on the team can pull it down from the CLI like a package. Context becomes something you can actually ship. It can be technical documents, PRDs or anything you deem useful for the context.
You can also create "powers" - personalised bits on how you like your code, and AI agents would pick up on that. Push them to the registry so others can find and install your specs. Agent configs, testing styles, architecture patterns - whatever is useful.
These documents are structured enough for AI agents to parse and act on. Ultimately, this gives your team and your tools the vital context.
VISIT SPECTRL.PRO ↗