devctl / rules
Cursor rule2 starsChanged 51 days agoMITView on GitHub
Hexagonal / ports-and-adapters rules for the devctl modular monolith
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,181 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- app/CLAUDE.mdCLAUDE.md
- .cursor/rules/devctl-debug.mdcCursor rule
- .cursor/rules/devctl-onboard.mdcCursor rule
- devctl-debugSkill
- devctl-onboardSkill
The file
We split this architecture.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use a modular monolith with ports-and-adapters.
- Very specific: line 18
Keep module public APIs small.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
---
description: Hexagonal / ports-and-adapters rules for the devctl modular monolith
alwaysApply: true
---
# Architecture
Use a modular monolith with ports-and-adapters. No DI container, no service locator, no new god `*Manager`.
1. Dependencies point inward. Domain must not import adapters, presentation, Google SDKs, TUI, filesystem libraries, or process libraries. Presentation may import application, ports, shared, and domain. Adapters may import ports, domain, and shared only.
2. Constructor injection. One composition root per process (`bootstrap/daemon.ts`, `bootstrap/client.ts`).
3. Ports exist only at replaceable boundaries (`ProcessRuntime`, `Clock`, `FileSystem`, `CredentialProvider`). Do not invent `IService` / `IServiceManager`.
4. CLI, TUI, MCP, and the web UI share application commands. Presentation must not start or kill processes.
5. Commands are explicit calls. Events are facts that already happened. Do not hide control flow on the event bus.
6. Separate `ServiceDefinition` (config) from `ServiceRuntime` (live state). Config becomes an immutable snapshot after load.
7. Google Cloud stays an adapter. Local-only services must run without it.
8. Split decisions into policies/resolvers. Use an explicit lifecycle state machine for service transitions.
9. Keep module public APIs small. `bun run check:architecture` must stay green.
```ts
// BAD — domain reaches Google
import { GoogleAuth } from "google-auth-library";
// GOOD — application depends on a port
constructor(private readonly credentials: CredentialProvider) {}
```
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.