Updated 3w ago
by openreachtech
hora-core
Hora kit core modules
56 GitHub stars (56)
- 17 skills (17 skills found in its SKILL.md files)
- 0 forks (0 forks)
- 3w ago last update (Last updated 3w ago)
Install
Skills CLI
npx skills add openreachtech/hora-core
Asks which skills and agents to install. Just one: npx skills add openreachtech/hora-core --skill flatten — add -g for every project.
Claude Code
git clone https://github.com/openreachtech/hora-corecp -r "hora-core/.claude/skills/flatten" ~/.claude/skills/
Copies the flatten skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add openreachtech/hora-core
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
flatten
Repository-specific build convention: everything under kit/ is copied into dist/ whole and unchanged, kit/ holds one directory per thing .claude/ accepts (agents/, skills/ today), the test suite checks that dist/ mirrors kit/ byte for byte and that each name: matches its folder, and dist/ — not kit/ — is both what this package publishes and what its installer mirrors into a consuming repository.…
.claude/skills/flatten/SKILL.md on GitHub (opens in a new tab) -
hora-accept
Run acceptance and record what passed and what did not — the full unit suites every time, plus an acceptance review at the reach the invocation calls for. Invoked as checkpoint 18 of /hora-build, as the whole-version sweep, or directly as /hora-accept.
kit/skills/hora-accept/SKILL.md on GitHub (opens in a new tab) -
hora-addon
How an add-on extends the hora skills — the Hora Kit range it is built for, the wings every hora skill resolves before it acts, how several add-ons combine where they touch the same section, and the precedence a person may set between them. Read by every hora skill once its version is fixed, and again after a resume or a compacted context. Invoked directly as /hora-addon to set or check that prec…
kit/skills/hora-addon/SKILL.md on GitHub (opens in a new tab) -
hora-build
Build one feature by taking it through the eighteen checkpoints — spec, backend, frontend, acceptance — in order, one gate at a time. Runs at the root of the hora repository, one feature per invocation. Invoked by /hora, or directly as /hora-build.
kit/skills/hora-build/SKILL.md on GitHub (opens in a new tab) -
hora-fast
Build a version's features several at a time, each in its own git worktree, after the parts they share have been built once. Uses the same spec, plan, feature files and acceptance as /hora, and replaces only the scheduling. Invoked instead of /hora, by an explicit /hora-fast, when one feature at a time is too slow for the version.
kit/skills/hora-fast/SKILL.md on GitHub (opens in a new tab) -
hora-hotfix
Fix one urgent defect and ship it through six gates, giving up the acceptance review but writing down everything it gave up. Invoked directly as /hora-hotfix when a live product is broken and the normal /hora route is too slow.
kit/skills/hora-hotfix/SKILL.md on GitHub (opens in a new tab) -
hora-plan
Plan one version from its spec. Fixes which version is being built, verifies the spec for holes and contradictions in conversation, and writes the feature-level task list. Runs at the root of the hora repository. Invoked by /hora, or directly as /hora-plan.
kit/skills/hora-plan/SKILL.md on GitHub (opens in a new tab) -
hora-progress
The rules behind the one line hora's progress takes — a checkpoint, a stage, a feature or the version passed, a verdict that sent the run back, and a wait for a person. /hora-build, /hora-accept, /hora-spec and the asking rules write these lines themselves, beside what each line reports, and read this skill wherever a line is in doubt — never invoked by a person. The questions themselves, stop di…
kit/skills/hora-progress/SKILL.md on GitHub (opens in a new tab) -
hora-spec-backend
Stage 4 of /hora-spec. Declare the repositories and servers, then design the data model, the operation list and the background jobs that every stage-1 use case can be walked against. Invoked by /hora-spec, or directly.
kit/skills/hora-spec-backend/SKILL.md on GitHub (opens in a new tab) -
hora-spec-frontend
Stage 5 of /hora-spec. Design the screens each use case passes through and the operations each screen calls, so nothing on a screen lacks an operation and no operation is unreachable — the empty, failed, waiting and forbidden states included. Invoked by /hora-spec, or directly.
kit/skills/hora-spec-frontend/SKILL.md on GitHub (opens in a new tab) -
hora-spec-horizon
Stage 2 of /hora-spec. Narrow the release to the fewest use cases somebody needs, and split the rest into deferred-with-a-seam and never-built. Writes the implementation scope, the build order, and the version's own acceptance criteria. Invoked by /hora-spec, or directly.
kit/skills/hora-spec-horizon/SKILL.md on GitHub (opens in a new tab) -
hora-spec-nonfunctional
Stage 3 of /hora-spec. Turn "it should be fast" into the four numbers that change a design — users now, users foreseen, the heaviest operation, and how long data is kept — plus availability, the security level and the middleware. Invoked by /hora-spec, or directly.
kit/skills/hora-spec-nonfunctional/SKILL.md on GitHub (opens in a new tab) -
hora-spec-review
Stage 7 of /hora-spec. Read the whole spec against itself — required sections, observable criteria, nothing reaching forward, every use case satisfiable, no contradiction — and send each shortfall back to the stage that owns it. Invoked by /hora-spec, or directly.
kit/skills/hora-spec-review/SKILL.md on GitHub (opens in a new tab) -
hora-spec-security
Stage 6 of /hora-spec. Give every operation and every screen a stated caller and a stated refusal, name every piece of personal or regulated data, and record why the role-or-endpoint split went the way it did. The one gate with no not-applicable case. Invoked by /hora-spec, or directly.
kit/skills/hora-spec-security/SKILL.md on GitHub (opens in a new tab) -
hora-spec-usecases
Stage 1 of /hora-spec. Fix who uses the product and what each of them completes end to end, and — where something already runs — how far each feature is built and whether it is specified or only listed. Writes the document information, the actors, the terminology, the existing assets, and every feature's two blocks. Invoked by /hora-spec, or directly.
kit/skills/hora-spec-usecases/SKILL.md on GitHub (opens in a new tab) -
hora-spec
Write one version's spec, in conversation, through stage 0 and seven stages. Reads what already exists first, so nobody dictates a running product from memory; from the second version on it writes a diff. Invoked by /hora when a version has no spec, by /hora-plan when a finding needs design work, or directly.
kit/skills/hora-spec/SKILL.md on GitHub (opens in a new tab) -
hora
Implement an application from its spec. Decides where a project stands and runs the five skills that do the work — spec, setup, plan, build, accept — one feature at a time, each to acceptance before the next starts. Runs at the root of the hora repository. Started or restarted only by an explicit `/hora` invocation.
kit/skills/hora/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.