Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

horizon-foundry

@horizon-foundry source repo

11 published skills

  1. ▌
    Frame · horizon-foundry
    Use before scaffolding or building anything new, or when a project cannot answer who it is for and why it matters. The builder declares a one-page product frame plus a four-line security frame; this skill audits it and reports blank or vague entries as findings. Never runs discovery, never questionnaires the builder, never invents answers.
    0
    installs
  2. ▌
    Mobile · horizon-foundry
    Use when building or fixing a mobile, touch, or small-screen experience, when a layout breaks on a phone, or when a desktop-designed feature needs to hold up on a real device. Not for products with no mobile surface; that gate resolves not-applicable, and no work is invented.
    0
    installs
  3. ▌
    Foundry · horizon-foundry
    Use when a project is approaching a release decision and you want one pass over its pre-ship gates instead of remembering each one. Resolves the project's release policy, then runs `check` (read-only preview) or `prepare` (invokes the gate skills to close the gaps). Not an inspector; production-audit issues the authoritative verdict afterward.
    0
    installs
  4. ▌
    Readout · horizon-foundry
    Use when building or reviewing a surface that DISPLAYS measurements (a dashboard, a report, an experiment read-out, a metrics email), when someone doubts the numbers a surface is showing, or when a surface is accurate but nobody reads or acts on it. Not for adding events or wiring capture, that is instrumentation; not for choosing what to measure, that is frame.
    0
    installs
  5. ▌
    Document · horizon-foundry
    Use to keep a project's documentation true to the code and current across every surface, or to turn the repo's own docs into a product surface (the public hub, the overview deck, showcase copy). Modes, public, internal, reconcile; idempotent and safe to re-run. Not for creating a doc set from nothing (that is scaffold) or judging release readiness (that is production-audit).
    0
    installs
  6. ▌
    Scaffold · horizon-foundry
    Use when starting a new project, or when an existing project still has placeholder markers in its docs. Declares the project's profile (experiment, internal-tool, web-product, service, or library), then stands up what that profile needs. Not for maintaining docs on an already-scaffolded project (that is document) or deciding whether the idea is worth building (that is frame).
    0
    installs
  7. ▌
    Phase Plan · horizon-foundry bundle
    Use when a unit of work is closing (a PR about to merge, a phase complete) and the next unit needs a plan, when a close has no next unit and the chain needs an honest terminal entry, or when writing any plan file. Writes the handoff while context is warm and indexes it so the next session can resume. Not for whole-product master planning or mid-execution task tracking.
    0
    installs
  8. ▌
    Brand Voice · horizon-foundry bundle
    Use when writing or reviewing any user-facing copy, marketing, landing pages, UI labels, error messages, empty states, docs prose, or when a project needs its brand voice defined. Not for deciding what a surface may claim (the forever spec owns capability truth) or for visual design.
    0
    installs
  9. ▌
    Feature Design · horizon-foundry
    Use when a substantial feature is being designed inside an existing codebase, before any implementation plan is written. The builder declares the feature; the skill audits the declaration against the repository and reports what the code contradicts or already provides. Never an interview, never the implementation plan (phase-plan), never a verdict (production-audit).
    0
    installs
  10. ▌
    Instrumentation · horizon-foundry
    Use when adding analytics or event tracking, instrumenting a funnel or an activation flow, wiring a product-analytics tool (PostHog, etc.), or when you need to measure whether a feature works. Not for system observability (errors, latency, alerting); that is a different discipline.
    0
    installs
  11. ▌
    Production Audit · horizon-foundry bundle
    Use when a product is approaching launch, an invite wave, or a release decision and needs a whole-application readiness audit ending in a scope-qualified ship/no-ship verdict. Also for "is this safe to ship", "pre-launch review", or "audit the whole app", or to audit one dimension alone (security, concurrency, reliability, accessibility, ui, infra, operability, testing-confidence, data-migration-safety, release-safety, performance-capacity). Not for reviewing a single diff or applying fixes; it reads the whole application and only reports.
    0
    installs