Skip to main content
command CX Codex

via-negativa — Claude Code command: what it does, how to install

via-negativa applies the principle of subtraction to your code, features, or plans, identifying bloat to cut rather than adding new complexity.

MIT ★ 1,988 updated 2026-04-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources
Open on GitHub

What via-negativa does

The command guides Claude Code through a via negativa evaluation. Instead of brainstorming what to build next, it audits the ongoing discussion or a specified problem to spot features, commitments, or code that degrade the outcome simply by existing.

The output follows a clear structure: an assessment of current state, items recommended for removal with the expected payoff, an explicit list of components that proved genuine value, and boundaries defining what future additions to decline. Without arguments, it defaults directly to your active chat context.

What it helps with

  • eliminate feature bloat without breaking core workflows
  • identify low-value tasks to drop from the backlog
  • define boundaries for incoming change requests
  • trim system complexity to reduce long-term maintenance

Example prompts for the agent

  • /via-negativa our current auth service architecture
  • /via-negativa backlog for next week
  • /via-negativa

How to install via-negativa

1Plugin marketplace

/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources

2Manually: put the files in place

.claude/commands/via-negativa.md

Call it with /via-negativa. For all projects use ~/.claude/commands/

Questions about via-negativa

How to install via-negativa in Claude Code?

Add the marketplace source with /plugin marketplace add glittercowboy/taches-cc-resources, then run /plugin install taches-cc-resources@taches-cc-resources. Alternatively, place the file into .claude/commands/via-negativa.md.

What does the via-negativa command do?

It reviews a system or task by focusing on subtraction. Claude Code lists what to eliminate, justifies the decision, protects essential parts, and outlines future proposals to reject.

Do I need to supply an argument when invoking the command?

No, arguments are optional. Leaving the command blank instructs Claude Code to inspect the immediate context of the ongoing conversation.

Source text

via-negativa.md · MIT
---
description: Improve by removing rather than adding
argument-hint: [situation or leave blank for current context]
---

<objective>
Apply via negativa to $ARGUMENTS (or the current discussion if no arguments provided).

Instead of asking "What should I add?", ask "What should I remove?" Subtraction often beats addition.
</objective>

<process>
1. State the current situation or goal
2. List everything currently present (activities, features, commitments, beliefs)
3. For each item, ask: "Does removing this improve the outcome?"
4. Identify what to stop, eliminate, or say no to
5. Describe the improved state after subtraction
</process>

<output_format>
**Current State:**
[What exists now - activities, features, commitments]

**Subtraction Candidates:**
- [Item]: Remove because [reason] → Impact: [what improves]
- [Item]: Remove because [reason] → Impact: [what improves]
- [Item]: Remove because [reason] → Impact: [what improves]

**Keep (Passed the Test):**
- [Item]: Keep because [genuine value]

**After Subtraction:**
[Description of leaner, better state]

**What to Say No To:**
[Future additions to reject]
</output_format>

<success_criteria>
- Identifies genuine bloat vs. essential elements
- Removes without breaking core function
- Creates space and simplicity
- Reduces maintenance burden
- Improves by doing less, not more
</success_criteria>

© Lex Christopherson · MIT · glittercowboy/taches-cc-resources

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set48

The whole set →
5-whys 5-whys runs the five whys technique on the problem you hand it and returns a root cause with one action to take. Useful when a bug keeps coming back after a fix. CX Codex +1 ★ 1,988repo stars first-principles first-principles deconstructs problems down to irreducible truths, removes conventions, and designs solutions from the ground up. CX Codex +1 ★ 1,988repo stars one-thing one-thing is a Claude Code command that picks one action with the greatest effect on the rest of a goal. Run it with a goal or let it use the current discussion. CX Codex +1 ★ 1,988repo stars inversion Applies inversion thinking: instead of asking “how do I succeed”, it asks “what guarantees failure” and builds a plan by avoiding those traps. Surfaces risks that optimistic planning misses. CX Codex +1 ★ 1,988repo stars occams-razor The occams-razor command weighs competing explanations against the facts and removes unsupported assumptions. Use it when a bug or decision has several plausible causes. CX Codex +1 ★ 1,988repo stars pareto pareto ranks the factors behind a decision by impact, keeps the few that carry most of the result and names the rest as safe to defer. CX Codex +1 ★ 1,988repo stars 10-10-10 10-10-10 evaluates choices across three distinct horizons: 10 minutes, 10 months, and 10 years. Spot tensions between immediate friction and lasting outcomes. CX Codex +1 ★ 1,988repo stars opportunity-cost The opportunity-cost command weighs a choice against the best alternative use of the same resources. Use it when you want to see what a decision costs in time, money, energy, or attention. CX Codex +1 ★ 1,988repo stars

Project sponsors

Companies that keep this analytics open