Future Only

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.

201 stars 12 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add swyxio/skills --skill future-only
Manual install
git clone --depth 1 https://github.com/swyxio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/future-only ~/.claude/skills/future-only

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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.
Read the full skill on GitHub

Details

Skill name
future-only
Repository
swyxio/skills
Path
future-only/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Future Only skill do?

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.

How do I install the Future Only skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add swyxio/skills --skill future-only. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Future Only popular?

It lives in swyxio/skills, which has 201 GitHub stars and 12 forks.

Related skills

Accelevents API

201

swyxio/skills

Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.

Software Development12

Accelevents Speaker Sync

201

swyxio/skills

Use when website speaker, session, schedule, room, track, or headshot changes must be synchronized back to Accelevents for AI Engineer Europe 2026.

AI, LLMs & Agents12

Agents SDK

201

swyxio/skills

Build or debug stateful applications that specifically use Cloudflare's `agents` package, including Agent classes, routing, callable methods, synchronized state, scheduling, AIChatAgent, durable execution, or Agents SDK client hooks. Do not trigger for generic AI-agent design, the OpenAI Agents SDK, or ordinary Durable Object work that does not use the Cloudflare Agents SDK.

AI, LLMs & Agents12

IOS Testing

228

pproenca/dot-skills

Testing practices for iOS 26 / Swift 6.2 clinic modular MVVM-C applications. Covers unit/UI/snapshot testing, protocol-based mocks, async actor isolation, and dependency-injected test architecture aligned with Domain protocols, App-target composition, and Data-owned I/O boundaries. Use when writing, reviewing, or refactoring tests for ios-* and swift-* clinic modules.

Testing & QA19

Dx Harness

228

pproenca/dot-skills

Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions. Audits the repo, scores findings, scaffolds canonical fixes (bootstrap.sh, reset.sh, seed.sh, AGENTS.md, task-runner entries), then verifies the harness end-to-end in a scratch worktree against a 60-second time-to-first-commit target. Triggers on phrases like "audit dx", "fix dev friction", "time to first commit", "set up the harness", "I keep doing X manually", "every time I reset the db I have to...", and on new-repo bootstrapping

Testing & QA19

Mom Test

150

guia-matthieu/clawfu-skills

Extract honest customer insights by asking questions about their life instead of your idea. Master Rob Fitzpatrick's methodology for conversations that can't lie to you. Use when: **Before building anything** to validate if the problem is real and painful; **Customer discovery calls** to get honest feedback without leading questions; **Pivoting decisions** to understand if you should change direction; **Feature prioritization** to learn what customers actually need vs. say they want; **Pricin...

Testing & QAIn 1 list32

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.