Horizon
Structured pause before building. Use when about to implement a feature, ship a change, or when the user invokes /horizon. Forces examination of what's beyond the immediate solution — whether this should be built at all, whether the design is right, whether existing code needs attention first. Triggers on feature requests, implementation starts, or when the user wants to challenge the impulse to build.
Install
npx skills add roby2358/skills --skill horizongit clone --depth 1 https://github.com/roby2358/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/horizon ~/.claude/skills/horizonPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Horizon Check LLMs have a horizon problem. They optimize for the nearest working solution. So do humans — but LLMs turbocharge the impulse by making the path to "done" feel frictionless. The things that matter most are over the horizon: whether this should exist, whether the design compounds well, whether you're building the right thing next. This skill is a forcing function. Run it before building, not after. ## Start Here: What am I trying to accomplish? Before the horizons, before any analysis — answer this in one or two sentences. Not "build feature X" but the business proposition: what outcome are you trying to create and for whom? This question is both broad and narrow. Broad because it opens the full problem space — you might discover the feature you had in mind isn't even the right shape for the goal. Narrow because once you know what you're actually trying to accomplish, entire solution categories die immediately. You don't have to evaluate them, they're just irrelevant. If you can't answer this clearly, you are not ready to build anything. Stop and think until you can. ## The Three Horizons Work through these in order. Each one can kill the task — that's the point. ### Horizon 1: Should this exist? The easiest feature to maintain is one you never ship. LLMs make it trivial to prompt something into existence, which drops the bar for what gets built. Fight that. Take your answer from "What am I trying to accomplish?" and pressure-test it:
Details
- Skill name
horizon- Repository
- roby2358/skills
- Path
horizon/SKILL.md- Repo updated
- 14 November 2026
FAQ
What does the Horizon skill do?
Structured pause before building. Use when about to implement a feature, ship a change, or when the user invokes /horizon. Forces examination of what's beyond the immediate solution — whether this should be built at all, whether the design is right, whether existing code needs attention first. Triggers on feature requests, implementation starts, or when the user wants to challenge the impulse to build.
How do I install the Horizon skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add roby2358/skills --skill horizon. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Horizon popular?
It lives in roby2358/skills, which has 5 GitHub stars and 0 forks.
Related skills
Coding
5roby2358/skills
Project-specific coding conventions and constraints. Use when writing, modifying, or refactoring any code, implementing features, writing tests, or building MCP servers in this project.
Game Design
5roby2358/skills
Design principles for tactics and strategy games. Use when designing new mechanics, tuning existing systems, adding units or abilities, adjusting difficulty, or making any game design decision. Triggers on discussions about game balance, unit roles, terrain, pacing, spawning, healing, combat, win/loss conditions, or UI for conveying game state.
Game Productize
5roby2358/skills
Audit a browser game for ship-readiness and produce a tiered gap list: a SHIP.md in the game repo plus pjpd tasks. Finds what gets forgotten between "the game works" and "a stranger can play it": title/menus/end screens, save and resume, audio and settings, onboarding, the mobile "sorry" screen, localization readiness, error recovery, hosting on the author's site and on portals (itch.io, Newgrounds), credits, asset licenses, and AI disclosure. Use when the user says "productize", "/game-productize", "get this game ready to ship/release/publish/launch", "what's missing before I launch", "prep f
Java Service Standards
9sandbaseai/workbuddy-skill
Use when creating or changing Java service code, especially Spring applications, controllers, services, persistence adapters, configuration, or tests; align with the repository's architecture while enforcing safe contracts, errors, logging, transactions, and verification.
Grounded Vault
9sandbaseai/workbuddy-skill
Use when compiling durable Markdown knowledge from sources and code, and every claim must remain traceable and cheap to check for staleness.
Java Spring Boot
5roby2358/skills
Best practices for Java 21 web services and Spring Boot 3 applications. Use when writing or reviewing Java code in a Spring Boot project — controllers, services, configuration, data access, tests. For bootstrapping a brand-new project, see java-spring-boot-coldstart instead.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.