jterrazz

shared

Shared project skill; exercises the per-agent .claude/skills / .agents/skills emission.

Skill that ships a binary-shaped sidecar file.

Skill with only frontmatter, no body.

New-form skill alongside the legacy bare-markdown one.

Exercises nested sidecar directory preservation.

Skill directory name contains a space.

First of several skills in this project.

Content strategy and distribution to grow reach — what to write, topic clusters, refreshing decayed pages, repurposing, directories, feeds, third-party presence. Use when the user mentions "more traffic", "content strategy", "content plan", "what should I write", "promote my article/app/site", "distribution", "newsletter", "nobody reads my posts", or wants to grow an audience. For technical ranking issues see jterrazz-seo; for AI citations see jterrazz-geo.

AI search & LLM visibility (GEO/AEO) — getting cited by ChatGPT, Claude, Perplexity, and Google AI Overviews. Use when the user mentions "GEO", "AEO", "AI SEO", "LLM visibility", "AI citations", "llms.txt", "AI crawlers", "ChatGPT doesn't mention my site", "AI Overviews", or wants their content/product to show up in AI answers. For classic search rankings see jterrazz-seo; for JSON-LD see jterrazz-structured-data.

Wire a site into @jterrazz/reach — defineSite/person/page model, projections (identity JSON-LD, sitemap, robots, llms.txt), Next adapter one-liners, and the conformance rule pack run via specification.website(). Use when adding SEO surfaces to a site, creating reach.config.ts, writing page providers, or running/debugging the reach conformance suite.

Technical and on-page SEO for web projects — audit workflow, crawlability, indexation, Core Web Vitals, metadata, canonicals, hreflang, internal linking. Use when the user mentions "SEO", "SEO audit", "not ranking", "traffic dropped", "meta tags", "sitemap", "robots.txt", "canonical", "hreflang", "Core Web Vitals", "indexing", or wants more organic traffic — even a vague "my SEO is bad" starts here with an audit. For AI/LLM search visibility see jterrazz-geo; for JSON-LD see jterrazz-structured-data; for content strategy and distribution see jterrazz-content-reach.

JSON-LD structured data (schema.org) — choosing types, required properties, validation, rich results. Use when the user mentions "schema", "structured data", "JSON-LD", "rich results", "rich snippets", or when adding machine-readable markup to pages. For the broader SEO audit see jterrazz-seo; for AI citation formatting see jterrazz-geo.

The exact tool roster provisioned on a jterrazz machine — modern CLI replacements (fd, ripgrep, eza, bat, sd, dust, zoxide, difftastic), AI tooling (rtk, qmd, ollama, skills), dev apps and services (gh, lazygit, docker/orbstack, linear, notion). Activates at the start of shell work, when searching or listing files, processing text, diffing, or checking whether a tool or capability is available on this machine.

Use when organizing or restructuring a repository's documentation, skills, AGENTS.md/CLAUDE.md, README, or generated docs — where knowledge lives, what gets committed, corpus vs injection layers vs compiler, projections vs presentations.

Overview of the @jterrazz ecosystem — shared npm packages, project naming ({product}-{role}, package-*), required files, CI/CD workflows, testing and architecture conventions. Use when working on any jterrazz project, choosing a package, scaffolding decisions, or understanding how the stack composes.

Scaffolds a new @jterrazz project with all conventions — package.json, tsconfig, Makefile, CI workflows, linting. Use when creating a new app or library from scratch.

Infrastructure and deployment for jterrazz projects — k3s, Helm, Traefik, CI/CD deploy. Use when deploying apps, configuring Kubernetes, adding domains, or troubleshooting infra.

Infrastructure and deployment for jterrazz projects — K3s, Helm, Traefik, CI/CD deploy. Use when deploying apps, configuring Kubernetes, adding domains, or troubleshooting infra.

Use when linting, formatting, type-checking, or detecting unused code. Covers oxlint/oxfmt config presets, `codestyle check`/`codestyle fix`, knip setup, and hexagonal architecture enforcement.

Testing conventions for @jterrazz projects — unit/integration/e2e structure, vitest, testcontainers, golden files, mocks. Use when writing, organizing, or debugging tests in a jterrazz repo.

Cryptographic article attestation via @jterrazz/attestation — EIP-712 signature over canonicalized content, Bitcoin anchoring through OpenTimestamps, browser-safe verification. Use when signing or verifying article attestations, working with .attestation.json / .ots files, the attestation CLI (sign, verify, upgrade), canonicalization, content digests, or proof/verify pages.

Multi-channel announcements via @jterrazz/broadcast — App Store in-app events, push notifications. Use when creating, sending, or managing announcements.

Shared CI/CD workflows for jterrazz projects — validate, release-npm, release-docker, release-go. Use when setting up GitHub Actions, configuring CI, releasing, or debugging workflow failures in a jterrazz repo.

Use when building, checking, linting, formatting, or configuring a TypeScript project with @jterrazz/typescript — build/bundle/dev/start, typescript check|fix failures, oxlint/oxfmt/knip/tsconfig presets, compose() lint config, docs generation command.

Thin composition layer over AI SDK v7 — provider factories, cost/fallback/logging middleware, and a config-driven factory. Observability goes through OpenTelemetry. Activates when configuring AI model access, cost tracking, fallback models, or AI SDK middleware.