DEVELOPER TOOLING · PRIVATE BETA
Cursor will edit the wrong files. You still only approve the change.
Cursor .cursorrules are soft suggestions that models easily forget. Launchfiles bounds Cursor and coding agents with hard file scopes, forbidden actions, and signed receipts.
Private beta · No card required · No auto-approval of mutations
.cursorrules vs work orders
Keep rules for style. Use work orders for the task.
| Dimension | .cursorrules | Work orders |
|---|---|---|
| Nature | Soft style advice | Task contract |
| Scope | Repo-wide suggestion | Whitelisted files |
| When agent drifts | Often ignored | Fail-closed gate |
| Tests | Optional | Required |
| Proof | None | Signed receipt |
| Merge authority | Hope | Human approve |
Yes — use both. Rules for formatting. Work orders for this PR.
What work orders add that .cursorrules cannot
Four deterministic boundaries that stop agent regressions before they merge.
Hard file whitelist
Agent can only edit declared paths — out-of-scope diffs fail closed.
Forbidden actions
Block schema mutations, environment configs, and dependency drift.
Gate asserts
Unit tests, linter rules, and tsc --noEmit must pass with exit code 0.
Signed receipt
Immutable cryptographic proof of the exact run and verified assertions.
Concrete artifact specification
Sample work order: lf_wo_cursor_8b11
Real YAML work order contract for Cursor and Claude Code.
# Launchfiles Scoped Work Order
work_order_id: "lf_wo_cursor_8b11"
owner: "Alex Morgan"
objective: "Refactor rate limiter in core engine"
file_scope:
- "src/core/workflow.ts"
- "src/core/engine.ts"
acceptance_checks:
- "unit:workflow.spec.ts"
- "lint:eslint"
- "typecheck:tsc"
forbidden_actions:
- "modify_config_or_apis"
- "install_packages"
status: "READY_FOR_REVIEW"
Built for engineers using Cursor
Frequently asked questions about combining Cursor rules with work orders.
- How do AI work orders differ from .cursorrules or CLAUDE.md files?
- Cursor rules and system prompts provide static style advice that agents can ignore during long context turns. Work orders are dynamic, task-specific contracts enforced by deterministic gate harnesses that fail-closed on violations.
- Can I use Launchfiles work orders alongside Cursor rules?
- Yes — use both. Cursor rules establish repository-wide formatting standards, while Launchfiles work orders define specific task bounds, forbidden file mutations, and required test assertions for individual PRs.
- Does Launchfiles automatically merge or deploy code?
- No. Launchfiles enforces a strict human-in-the-loop doctrine. Quality gates generate an immutable signed receipt proving that assertions passed, but a human engineer always reviews and approves the merge.
Looking for the core work order specification?
Explore how work orders define file boundaries, forbidden actions, and signed receipts for any coding agent.
Developer tooling · private beta
Cursor will edit the wrong files. You still only approve the change.
Cursor .cursorrules are soft suggestions that models easily forget. Launchfiles bounds Cursor and coding agents with hard file scopes, forbidden actions, and signed receipts.