Menu

Individual skill

future-only

0upvotes

Prefer the clean future product contract over legacy or backward compatibility. Use when the user invokes $future-only, says the product is preproduction or has no users, permits breaking changes, or explicitly says not to preserve legacy APIs, schemas, data, migrations, configuration, behavior, or tests.

future-only/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
197
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Future Only

Treat the intended future behavior as the only supported contract.

- Proactively find and remove compatibility shims, deprecated routes, fallback fields, adapters, aliases, dual-write paths, adoption logic, and tests that exist only for obsolete behavior.
- Prefer one canonical API, schema, configuration, and implementation. Update all in-repository callers together.
- Treat preproduction data as disposable. Prefer a fresh baseline, reset, or seed path over backfills, upgrade ladders, historical migration replay, or parallel schemas.
- Delete obsolete coverage only after distinguishing it from tests that still prove current authorization, correctness, security, or user-visible behavior.
- Update active documentation and tooling so they describe only the surviving contract. Historical records may remain clearly historical.
- Do not add a compatibility layer merely to reduce the diff or make old tests pass.

This skill authorizes breaking code, API, schema, configuration, fixture, and test changes within the requested scope. It does not authorize destroying confirmed production or third-party user data. If such data actually exists, stop before irreversible loss and request the smallest explicit approval; otherwise do not preserve hypothetical compatibility.
Back to top